Which Laws Require an Attendance Register for Guards

A security guard's attendance record is required by more than one law at the same time, and each looks at it from a different angle. Under the Contract Labour (Regulation and Abolition) Act 1970 and its rules, and now under the OSH and Working Conditions Code 2020, a contractor must maintain a muster roll and wage register for contract workers, and the principal employer (your client) remains liable for wages, PF and ESI if you default. The muster roll is the document that proves who worked, where and when, and it is what the principal employer's compliance team will ask you for.

The Code on Wages 2019 and the older Minimum Wages and Payment of Wages framework require registers of wages, overtime and deductions, all of which are derived from attendance. The state Shops and Establishments Act applies to your office and, in many states, prescribes an attendance register for employees in its own form. PSARA adds the section 15 register of guards and clients and a general duty to keep records open to inspection by the Controlling Authority.

Finally, EPF and ESIC inspections test the wage register against the attendance record, because contributions are computed on wages for days actually worked. An agency that cannot show the days a guard worked at a site cannot defend the PF and ESI it paid or did not pay for that month. The attendance register and muster roll glossary entries explain the vocabulary; the rest of this article explains the format.

• Contract Labour Act and OSH Code: muster roll and wage register maintained by the contractor
• Code on Wages and minimum-wage rules: registers of wages, overtime and deductions built from attendance
• State Shops and Establishments Act: attendance register for office staff in the state's form
• PSARA: section 15 register plus records open to inspection by the Controlling Authority
• EPF and ESIC: attendance is the evidence behind days worked and contributions paid

The Columns a Guard Attendance Register Must Have

Statutory muster roll forms differ slightly between central and state rules, but every one of them needs the same core data, and a security agency needs a few columns beyond the statutory minimum because a guard's attendance is tied to a site and a post, not just to the employer. If your register cannot answer 'which guard, which site, which post, which shift, from when to when', it is not sufficient for billing or for a contract-labour inspection.

The guard identity columns are the employee ID (the same ID used in the section 15 register and the wage register), the guard's name and the father's or spouse's name as the statutory forms commonly require. The deployment columns are the site or client name, the post and the shift with its scheduled timings. The time columns are actual in-time and out-time, hours worked, and overtime hours. The verification columns are the guard's signature or thumb impression on paper (or a selfie and GPS stamp digitally), and the supervisor's or site in-charge's verification.

Two further columns save arguments later: a status code for each day (P for present, A for absent, WO for weekly off, L for approved leave, H for holiday, R for reliever duty) and a remarks column for late arrival, early exit, site transfer during the shift or a no-show that was covered. The security guard attendance sheet format template lays these out in a printable monthly grid.

• Identity: employee ID, name, father's or spouse's name, guard category (unarmed, armed, supervisor)
• Deployment: client or site, post, shift and scheduled timings
• Time: actual in-time, actual out-time, hours worked, overtime hours
• Verification: guard signature or selfie and GPS stamp; supervisor verification
• Status code per day and a remarks column for exceptions

Site Register vs Agency Consolidated Register

Most agencies maintain two levels of register and get into trouble when they do not match. The site register lives at the client premises: a bound book at the guard room in which each guard signs in and out, countersigned by the site supervisor or the client's security in-charge. It is the document the client trusts, because the client saw it being filled. It is also the document an inspector visiting the client's premises will ask for first.

The agency consolidated register is maintained at your office and covers every guard across every site for the month. It is the source for the wage register, for PF and ESI, and for the invoice annexures. Because relievers move between sites and some guards work two half-months at two clients, a guard's month can only be assembled at this level. The consolidated register must be traceable back to the site registers, day by day, or the wage register built from it cannot be defended.

The mismatch typically arises because the site register is copied to the office by phone or WhatsApp photo at month-end, and the copying is where days are gained or lost. Make the site register the primary record and the consolidated register a strict compilation of it, or better, capture attendance digitally at the site so that both levels are the same data viewed two ways. The contract labour muster roll guide covers the principal-employer view of this problem.

• Site register: one per client site, signed by the guard daily and countersigned by the supervisor
• Consolidated register: one per agency per month, covering all guards and sites
• Every consolidated entry must trace to a site register entry for the same day
• Relievers and transferred guards appear on multiple site registers; consolidate by employee ID
• Collect site registers on a fixed date, not when someone remembers

Sample Register Layout, Column by Column

A monthly guard attendance register for one site is usually laid out with one row per guard and one column per date, plus summary columns at the right. A single sheet covers a site of up to about 25 guards; larger sites use one sheet per post. Print the site name, client name, month, post and the agency's PSARA licence number in the header so that a loose sheet can still be identified.

The row header carries the guard's employee ID, name, category and the shift the guard is rostered on for the month. Under each date, record the daily status code and, in a second line or a separate daily register, the actual in and out times. The summary columns at the right total the present days, weekly offs, paid holidays, approved leave days, absent days, total hours and overtime hours, which are the exact inputs a payroll executive needs to compute payable days on the 26-day basis and overtime at double rate.

Where a daily in-out register is kept separately (common at sites where guards sign a book each shift), keep it to one row per guard per shift with the columns below. At month-end, the daily register generates the monthly grid; the two must reconcile. The muster roll format in Excel template gives a statutory-style layout that can be adapted for guards.

• Header: agency name and PSARA licence number, client, site, post, month and year
• Row: employee ID, guard name, category, rostered shift, week-off day
• Daily cell: status code (P, A, WO, L, H, R) with in-time and out-time
• Summary: present days, WO, holidays, leave, absent, total hours, OT hours, guard signature, supervisor signature
• Daily in-out register: date, employee ID, name, post, shift, in-time, out-time, hours, OT, guard signature, supervisor initials, remarks

Rules for Maintaining the Register Correctly

The register is evidence, and evidence has rules. Entries are made at the time of the event, not filled in at month-end from memory. A guard signs in when arriving and signs out when leaving; the supervisor verifies daily, not weekly. Corrections are made by striking through with a single line and initialling, never by overwriting or using correction fluid, and the reason for the correction goes in the remarks column. Blank cells are filled with the status code, because a blank is read by an inspector as an unrecorded day.

The times recorded must be actual times. A register that shows every guard arriving at exactly 08:00 and leaving at exactly 20:00 for thirty days is a register that was filled in from the roster, and an inspector will treat it as such. Genuine registers show 07:52 and 20:11. Overtime must appear as overtime: a guard who covered a no-show and worked 20:00 to 12:00 the next day has 16 hours on the register, and the wage register must show the double-rate payment that follows.

Keep the register for the retention period that applies to you. The statutory rules commonly require registers to be preserved for a period generally taken as three years, but the exact period depends on which rules apply and may be longer for wage records; check the applicable central or state rules. Keep site registers after the contract ends, because disputes with a former client or a former guard arise after the deployment is over.

• Record at the time of the event; supervisor verifies daily
• Corrections by single strike-through with initials and a remark; no overwriting
• No blank cells: every day has a status code
• Record actual times, not roster times; show overtime hours explicitly
• Retain registers for at least the applicable statutory period (generally three years; verify your rules), including for closed sites

How Inspectors and Clients Use the Register

A labour inspector reconciles three documents: the deployment or contract (how many guards were supposed to be at the site), the attendance register (how many actually were, on which days) and the wage register (what they were paid). Gaps between any two are the finding. Twenty-two guards on the invoice but eighteen on the register is a billing problem; eighteen on the register but PF paid for fifteen is a statutory problem; a guard paid for 26 days who was marked absent on four is a wage-register problem.

Clients use the register for the same reconciliation from the other side. Before approving the month's invoice, the client's admin team compares the invoice annexure with the site register they countersigned. This is why every agency should build its invoice from the register rather than from the roster, as explained in how security agencies bill clients for guard man-hours, and why the site supervisor's daily verification is worth insisting on.

The principal employer's compliance team also relies on your register to prove that the client met its own obligations under the Contract Labour framework. If your register is unreliable, the client is exposed, and clients who have been exposed once tend to change agencies. A clean, verifiable register is therefore a sales asset as much as a compliance document.

• Inspector's test: deployment vs attendance vs wage register
• Client's test: invoice annexure vs countersigned site register
• Principal employer's test: your register supports their Contract Labour compliance
• Build invoices from the register, never from the roster
• Insist on daily supervisor verification; it is what makes the register credible

Replacing Paper With a Digital Register That Exports in Register Format

A paper site register has two weaknesses that no amount of discipline fixes: it can be filled in by someone other than the guard, and it reaches the office late. A digital register captures the same columns at the moment of the event with evidence that paper cannot: a selfie or face-recognition check that the person marking in is the rostered guard, a GPS position inside the site's geofence, and a server timestamp that nobody can back-date. How to verify guards are on site covers the verification methods in detail.

The requirement does not change: you still need a register with the statutory columns, and you still need to produce it on demand. What changes is that the register becomes an export. In Attend Mitra, a guard marks attendance with GPS and selfie at the site, the entry lands against the site, post and shift from the published roster, the supervisor verifies from the app, and the month's site-wise attendance exports as a register-style sheet with present days, hours and overtime, plus the man-hour summary that goes on the invoice. Corrections go through a regularisation request with an approval and an audit trail, which replaces the single strike-through rule with something stronger.

Keep the paper site register during the transition if the client or your state inspector expects it, and reconcile it against the digital export for a month or two. Once both agree consistently, the digital export becomes the primary record and the paper book becomes a backup. Details of the security-specific setup are on the security guard attendance software page.

• Digital capture adds identity, location and time evidence to the same statutory columns
• Site, post and shift come from the published roster, so every entry is already deployment-linked
• Supervisor verification and corrections leave an audit trail instead of an initialled strike-through
• Monthly export in register format per site, with hours and overtime for payroll and billing
• Run paper and digital in parallel for a month, then make the export the primary record