Why name-based attendance registers cause pay disputes

How does a name-based register go wrong?

Picture a 40-person site with a Ramesh, a Rakesh, a Suresh and two Maheshes. The supervisor fills the register at the end of a long shift, from memory, on a printed sheet where every row looks the same. Nobody is trying to cheat. Here is what happens anyway:

• Wrong-row ticks. Rakesh is marked present on Ramesh's row. At month end, one is paid for a day he did not work and the other loses one.
• Same-name mix-ups. Two Maheshes, one register. Whose absence was that on the 14th?
• Proxy attendance. A staff member asks a friend to "mark me, I'm coming late" and does not come. On paper, the post was covered.
• Back-filled sheets. The register is filled in a batch days later, and the gaps are guessed.
• Site transfers. A worker moves to another site mid-month and appears on both registers, or on neither.

Why do these mistakes turn into disputes?

Every attendance mistake becomes a money mistake twice:

1. In salary. A wrong day changes someone's pay. A staff member who loses ₹700 for a day they worked remembers it. They raise it on payday, often in front of others.
2. In the client bill. You bill the client by staff-day. If the client's own records show an empty post on a day you billed, you lose more than the day: you lose the client's trust in every bill after it.

Then nobody can settle the argument, because a tick in a paper register proves nothing about who was actually at the site. Was it a mistake, a proxy, or a genuine absence? The supervisor's memory against the staff member's word.

Worked example: what one mix-up costs

Over a month at one site, a supervisor makes three wrong-row ticks and lets two proxy marks through:

The amounts are small. The hours spent arguing, re-checking registers and calming staff are not. Across ten sites, this is a part-time job for someone in your office.

Why don't the usual fixes work?

• Signature columns slow the register down and are easy to fill for someone else.
• Staff codes help in the office, but supervisors at the site still think in names and faces, not numbers.
• WhatsApp group check-ins show that a phone was somewhere, not that the right person is on duty. They are also hard to turn into a salary sheet.
• Biometric machines cost money per site, need power and upkeep, and are hard to move when staff rotate between many small sites.

HaazriPro works this out every month from your attendance, for every staff member and site. Start 30-day free trial  →

What does marking by face photo change?

Supervisors already know their staff by face, not by name. HaazriPro builds on that. Each staff member's photo is taken once, when they join. At the site, the supervisor's phone shows a grid of faces for everyone assigned to that site and shift, and the supervisor taps the face of each person in front of them to mark present, late, half-day or absent.

There is no face recognition and no camera scan at marking time. The supervisor is looking at the person and at their photo, so a Ramesh cannot be marked as Rakesh by accident. It works offline on a basic Android phone and syncs when the network returns.

• No wrong-row ticks: there are no rows of similar names to choose from.
• Proxy is harder: the supervisor marks the face in front of them, at the site.
• Back-filling is visible: each mark carries the time it was recorded, so the owner sees when a day was filled in later.
• Transfers are clean: a worker is assigned to a site, and only appears on that site's grid.

Is a face photo record useful beyond attendance?

Yes. For security agencies, the Private Security Agencies (Regulation) Act, 2005 already expects photographs: the agency's register must hold the names, addresses, photographs and salaries of its security staff and supervisors (section 15), and staff carry photo identity cards (section 17). A photo for every staff member is a record you need anyway.

What can you do today, even on paper?

1. Use full names and a staff code on every row, never first names only.
2. Mark at the start of the shift, not at the end of the day or the week.
3. One code per cell (P, A, HALF and so on), using a clean monthly attendance sheet.
4. Get the sheet signed by the site in-charge each week, not once a month.
5. Reconcile salary and billing from the same sheet, so a mistake shows up in both places.

When you are ready to stop maintaining paper, send us your current sheet. We load it into HaazriPro and match each name to exactly one staff record, so you start clean.

Sources

• Private Security Agencies (Regulation) Act, 2005, sections 15 and 17 (India Code)
• Private Security Agencies Central Model Rules, 2020: register in Form X, photo identity card in Form XI

This guide explains the rules in plain language. It is not legal or tax advice. Laws and rates change, so check the register requirements for your state before you act on it.