Society Staff Attendance Register: Shifts, Wages and Compliance

The society staff attendance register

A mid-size housing society spends more on staff than on anything else — security, housekeeping, gardening, plumbing, the facility manager. It is usually the largest line in the budget and the least evidenced.

The typical control is a register in the cabin, signed by whoever is present when someone remembers. The society pays the agency's invoice for twelve guards without any independent way of knowing whether twelve turned up. Under-deployment against contracted headcount is one of the most common ways societies lose money, and it is invisible without an attendance record the society itself controls.

This page covers what the register needs to contain, the difference between direct and contracted staff, the compliance obligations that attach, and how to make it stick.

Labour law obligations vary by state and by headcount, and are amended periodically. Take your auditor's or a labour consultant's view for your specific situation.

Direct staff versus contractor staff

This distinction decides most of the obligations, and societies frequently get it wrong.

Direct employees are engaged by the society itself — often the caretaker, sometimes housekeeping or a gardener. The society is the employer, with the obligations that follow: minimum wages, wage records, statutory contributions where thresholds are crossed, leave, and a proper appointment record.

Contractor staff come through an agency — typically security and often housekeeping. The agency is the employer. The society is the principal employer, which is a real status and not a way of avoiding responsibility: where a contractor fails to pay wages or make statutory contributions, the principal employer can be held liable for them.

That is why the attendance register matters beyond deployment checking. If the agency's compliance is later questioned, the society's own attendance data is what shows who actually worked.

Practical protections when engaging through an agency:

• Verify the agency's registrations and licences before contracting, not after a problem
• Require monthly proof of wage payment and statutory contributions for the deployed staff
• Reconcile the invoice against your own attendance record before paying
• Keep the contract, the deployment list and the monthly compliance proofs together

What the register must capture

Two commonly missing fields do the most work. Replacement details — agencies rotate people constantly, and a register that records only the contracted name hides the fact that four different people worked that post this week, none of them verified. And weekly off, because staff working without a rest day is both a compliance exposure and, usually, something the committee did not know was happening.

Getting an accurate record

• Capture at the gate, at shift start and end. Attendance marked in arrears at month end is reconstruction, not a record.
• Prefer a method the staff can actually use. A shared tablet in the cabin with a photo or a code works better than expecting personal smartphones. Biometric devices work but bring their own data-protection questions — decide deliberately, and do not store raw biometric data casually.
• Have the supervisor verify, not self-attest alone. A guard marking their own attendance with no countersignature is the paper register with extra steps.
• Timestamp server-side. If the time comes from the device, the record is only as reliable as the device clock.
• Reconcile monthly against the agency invoice, before payment. This is where the money is.
• Photograph or log the deployment board — contracted headcount by post and shift — so you have a baseline to reconcile against.

The wage compliance layer

Even where staff are on an agency contract, the society should understand what it is buying:

• Minimum wages vary by state, by skill category and by whether the work is classified as scheduled employment. Security guards, sweepers and gardeners typically fall in different categories. An agency quoting below the state minimum for the category is a signal, not a bargain.
• Overtime attracts a premium rate under the applicable law. A guard doing double shifts because the agency is short-staffed is an overtime liability someone is carrying.
• Statutory contributions apply above the relevant thresholds. Ask for the monthly challans for deployed staff.
• Rest days and working hours are regulated. Twelve-hour shifts seven days a week are common in practice and are not lawful.
• Wage records and registers must be maintained by the employer. Where the society is the direct employer, that is the society's job.

The uncomfortable reality is that many societies knowingly accept quotations that cannot support lawful wages, and then treat the resulting non-compliance as the agency's problem. As principal employer, it is not only the agency's problem.

What to review, and when

Monthly, before paying the agency: attendance against contracted deployment, overtime hours, absences without replacement, and the compliance proofs for the month.

Annually, at the AGM: total staff cost, deployment against contract, and any shortfall recovered. Recovering an under-deployment credit is one of the few line items where governance work produces visible money, and it makes the case for the process better than any argument about diligence.

How this works on Plinth

Staff are recorded against the society with their role, shift and whether they are direct or agency staff, and attendance is captured at the gate at shift start and end rather than reconstructed later.

Timestamps are recorded server-side, replacements are logged against the post they covered, and monthly summaries give hours, overtime and absences per person — the figures the committee needs to reconcile the agency invoice before paying it. Because staff records sit alongside the society's other operational data, an attendance shortfall and the vendor bill it should reduce are visible in the same place.

Every entry writes to the society's append-only audit log, so the attendance record cannot be quietly adjusted after an invoice is queried.

Frequently asked questions

What should a society staff attendance register contain? Name and ID, role and shift, date, in and out times, total hours, leave with reason, replacement details, weekly off, and who verified presence.

Is a housing society liable for contractor staff wages? As principal employer, a society can be held liable where the contractor fails to pay wages or make statutory contributions. Verify the agency's compliance monthly rather than assuming.

Can we use biometric attendance for society staff? Yes, and many societies do, but biometric data is sensitive. Be deliberate about what is stored, where, and for how long, and prefer systems that store a template rather than raw biometrics.

How do we check whether the security agency deployed the contracted headcount? Reconcile your own attendance record against the contracted deployment by post and shift, monthly, before paying the invoice. Under-deployment is common and recoverable.

Do we need to keep records for agency staff too? Yes. Your own attendance record is what protects the society if the agency's compliance is later questioned.

What about overtime? Overtime attracts a premium under the applicable law. Track hours rather than only days, or you cannot see it.

Step-by-step guides

• Admin: Mark Daily Staff Attendance
• Admin: Set Up the Society Staff Roster
• Staff Attendance Troubleshooting
• Guard: Mark Society Staff In and Out at Gate
• Committee: View Staff Attendance Reports
• Staff: View My Attendance
• Admin: Payroll Period Export

Related: vendor bills and payment ledger · domestic help police verification · guard patrol and QR checkpoints