HR operations
Attendance & Leave Management Checklist
Managing attendance and leave in a spreadsheet works until about thirty people, and then it stops working quietly rather than all at once. This is what a manual process needs to have in it to stay trustworthy — and, at the end, an honest account of the failures no amount of discipline fixes.
Who it is for
- HR teams running attendance and leave on spreadsheets or a register
- Founders who approve leave over chat and reconcile it later
- Companies with field, shift or client-site staff
- Anyone whose month end involves an argument about a leave balance
What it helps with
- Capture attendance in a way that survives month end
- Apply lateness and half-day rules the same way for everyone
- Stop leave balances becoming a matter of opinion
- Hand payroll a clean, frozen record on a known date
Daily attendance
The whole month is decided here. Anything not captured on the day is reconstructed from memory at month end, and reconstruction is where the arguments start.
| Task | Owner | Done | Notes |
|---|---|---|---|
| Attendance captured for every employee, every working day | HR | ||
| One agreed source of truth — not a register and a sheet and a group chat | HR | ||
| Field, client-site and remote staff recorded the same way as everybody else | HR | ||
| Missing entries chased the same week, not at month end | HR | ||
| Holidays and week-offs marked before the month starts | HR | ||
| Shift or roster changes recorded when they are agreed | Reporting manager |
Late arrivals and early exits
| Task | Owner | Done | Notes |
|---|---|---|---|
| A written rule for what counts as late, and what follows | HR | ||
| Grace period defined, and applied to everybody the same way | HR | ||
| Repeated lateness raised with the manager, not silently deducted | HR | ||
| Early exits recorded with a reason, or they become disputes later | Reporting manager | ||
| Half-day rules stated in writing and applied consistently | HR |
Absences
| Task | Owner | Done | Notes |
|---|---|---|---|
| Unplanned absence reported to a named person by a stated time | Employee | ||
| Absence classified within two working days: leave, unpaid, or something else | HR | ||
| Long or repeated absences escalated before payroll rather than at it | HR | ||
| Absence without information followed up in writing | HR | ||
| Medical or extended absences documented per your policy | HR |
Work from home and on-duty
| Task | Owner | Done | Notes |
|---|---|---|---|
| Written rule for who can work from home, and how it is requested | HR | ||
| Approval recorded before the day, not reconstructed after it | Reporting manager | ||
| Work-from-home marked distinctly from both present and leave | HR | ||
| Client visits and official travel marked as on-duty, not absence | HR |
Leave requests and approvals
| Task | Owner | Done | Notes |
|---|---|---|---|
| One way to apply for leave, and everybody knows what it is | HR | ||
| Notice expectations stated by leave type | HR | ||
| Requests approved or rejected within a stated number of days | Reporting manager | ||
| Rejections given a reason | Reporting manager | ||
| Backdated leave allowed only by exception, and recorded as one | HR | ||
| Cover agreed before approval for anything longer than a few days | Reporting manager | ||
| Nobody approves their own leave | HR |
Leave balances
| Task | Owner | Done | Notes |
|---|---|---|---|
| Accrual rule written down and applied the same way for everyone | HR | ||
| Balances updated on a fixed date each month | HR | ||
| Employees can see their own balance without asking HR | HR | ||
| Carry-forward and lapse rules stated, and applied at the year end | HR | ||
| Negative balances flagged as they happen, not discovered at exit | HR | ||
| Opening balances set correctly for joiners and for the new year | HR |
Monthly reconciliation
| Task | Owner | Done | Notes |
|---|---|---|---|
| Every day of the month accounted for, for every employee | HR | ||
| Leave taken matches leave approved matches attendance | HR | ||
| Exceptions resolved before the cut-off, not carried forward | HR | ||
| Month closed and locked once agreed | HR | ||
| Anything reopened after locking is recorded with a reason | HR |
Payroll coordination
| Task | Owner | Done | Notes |
|---|---|---|---|
| Attendance and leave frozen at the published cut-off | HR | ||
| Loss-of-pay days agreed with managers before they reach payroll | HR | ||
| Anybody with LOP told before payday | HR | ||
| Encashment and adjustment inputs handed over with the rest | HR |
Records
| Task | Owner | Done | Notes |
|---|---|---|---|
| Monthly attendance kept for the period your policy states | HR | ||
| Approvals kept with the record they approve | HR | ||
| Access limited to the people who need it | HR | ||
| One place, backed up, with no private copies circulating | HR |
Where manual attendance and leave usually goes wrong
Not carelessness. These are the failures that come from the method rather than from the people using it.
The record is rebuilt from memory at month end
A gap noticed on the 28th is filled by asking somebody what they were doing on the 9th. Whatever answer comes back becomes the record, and it is not a record any more.
There is more than one source of truth
A register at the door, a sheet on someone’s laptop, leave approved in a chat thread. Each is right about something and none is right about everything, and the reconciliation is somebody’s whole Friday.
Balances are a matter of opinion
The employee has a number, HR has a different number, and neither can show their working. This is the single most common cause of an exit going sour, because it surfaces during full and final settlement when trust is already thin.
Approvals are not attached to anything
Leave approved verbally or in a message that has since scrolled away means an approval nobody can produce. Six months later, that becomes "I never approved that".
The rules drift by team
One manager applies the grace period, another does not. Nothing was ever decided differently — it simply was never written down, so each manager invented a version.
It fails silently as you grow
At fifteen people, one person holds it all in their head and it genuinely works. At forty it does not, and there is no day on which it announces that. It just gets slowly less accurate while everybody continues to trust it.
It concentrates in one person
When the person who maintains the sheet is on leave, attendance is not maintained. When they resign, a good deal of it leaves with them.
What software actually changes — and what it does not
An HR system helps with a specific and fairly narrow set of these: attendance is captured once, at the time, by the employee rather than reconstructed by HR; a leave balance is computed by one rule rather than by whoever is asked; an approval is attached to the request it approves and can be produced years later; and the same rules apply to every team because they are configured once rather than remembered separately.
What it does not fix is worth saying plainly. It will not decide your grace period, tell you whether a long absence is medical leave, make a manager approve requests promptly, or write your policy. A process nobody agreed will be an unagreed process with a database behind it — and rules that were never written down do not become clearer for being configured.
If most of the checklist above is already true for you, a spreadsheet is doing fine and you have more valuable things to change. It is the companies where four or five of those rows are permanently untickable who get their week back.
How to use it
- Go through it once marking only what is genuinely true today. The untickable rows are the resource; the ticked ones are reassurance.
- Take the rows about written rules first — grace period, half-day, notice by leave type. They cost an afternoon and they remove most of the recurring arguments.
- Fix your cut-off date and publish it to everyone, not just to managers.
- Re-run it after three months. If the same rows are still untickable, the problem is the method rather than the effort.
Questions people ask
It is less about headcount than about shape. Twenty people in one office with fixed hours is manageable for a long time. Twenty people across shifts, client sites and work-from-home is already hard, because the number of exceptions per month is what creates the work, not the number of employees.
One source of truth. Not the best one — just one. Most of the pain in a manual process comes from reconciling two or three records that each know something the others do not.
Where to go next
Flabido keeps the everyday HR work of a growing Indian company in one place — people records, leave, attendance, payroll inputs, hiring and letters. See what it does or ask for a free trial.