Rolling out an attendance system: the sequence that delivers in month one
06.09.2026
In attendance system rollouts, the cause of failure is almost never the technology. The system runs, records arrive - and yet at the end of the first month the timesheet is still corrected by hand and the team asks: what actually changed?
The answer is usually the same: the rules were never written down. Below are the four stages of a rollout and exactly what to check at each.
The real long stage
In a model with no hardware purchase, the technical part is measured in days: the structure is built, points are created, employees are added.
What takes long is something else - putting the company's own rules into writing. In practice these questions are documented in advance at almost no company:
- After how many minutes does a record count as late?
- Is the break included in working time or not?
- How is a day calculated when the record is incomplete?
- Whose approval puts overtime into the record?
- Which marker do business trips carry?
Without answers to those five, whatever system gets built produces the same outcome: a human still makes the decision and the system merely stores records.
Stage 1 - writing the rules
A one-page document is enough. It should hold the work schedules, the lateness threshold, the break rule, the rounding step and the list of exceptions.
The most useful part is the list of exceptions, because most disputes in the first month come from exactly there: a forgotten check-out, a technical failure, a business trip, a site change, a point with no coverage.
HR should not write the document alone. Involving a branch manager and accounting exposes two different kinds of gap: one on the operational side, one on the calculation side.
Stage 2 - a pilot department
Choosing the simplest department for the pilot is instinctive and wrong. In the simplest department everything works and nothing is learned.
The right choice is the department whose rules change most: shift work, a field crew, a unit with frequent business trips. The gaps show up there within a week.
The pilot runs one or two weeks and its purpose is not to produce a report - it is to test how well the rules hold in practice. The output of this stage is an updated rules document.
Stage 3 - a parallel month
The old and new records run side by side for a month. It looks like extra work and there is always a temptation to skip it - yet in practice it is the stage that pays back the most.
It delivers two things. One is technical: at month end two timesheets are reconciled and the differences point precisely at the gaps in the rules. The other is human: the team can compare the new system's output against the old and trust builds.
In rollouts that skip it, the first disputed timesheet usually puts the whole project in question - because there is no baseline to compare against.
Stage 4 - full switchover
The switchover has three steps.
Structure. All branches, departments and recording points are set up. Existing physical access control - a turnstile or a terminal - can stay in place; what matters is that attendance recording is not split in two.
Notifications. Only one or two events are switched on at first - a shift that has not opened and lateness, for example. Turning on everything at once makes notifications meaningless within the first week.
Reports. Who receives which cut and when is agreed: the branch manager gets their branch, HR the full list, accounting the approved final figures.
The five most common mistakes
- Switching the whole company on the same day. When something goes wrong the cause cannot be isolated.
- Leaving the rules for later. The "let's start and refine as we go" approach closes at the first timesheet.
- Not explaining it to the team. What is recorded and where employees can see their own records both have to be explained.
- Switching on every notification. Noise zeroes out the value of notifications.
- Trying to measure indicators after the rollout. The baseline has to be recorded first.
How to measure the result
Four indicators are enough, and all of them must be recorded before the rollout:
- Hours spent preparing the monthly report.
- Rows corrected by hand each month.
- The number of disputed records.
- The date the timesheet closes.
The same four are measured again three months later. The difference serves both as an evaluation of the project and as the budget argument for the next stage.
A worked example: two different rollouts
Two companies of the same size deployed a system in the same month. The results came out completely different, and the reason was not technical.
The first company switched the whole structure over on one day. The rules were not written - the decision had been "let's start and refine as we go". In the first week questions arrived from three departments at once: is the break inside working time, after how many minutes does lateness count, how is a business trip recorded. The answers were given verbally and differed between departments. The first timesheet was disputed and the project was paused for two months.
The second company started with a one-page rules document. For the pilot it picked its most complex unit - the shift-based warehouse. Two weeks of piloting exposed three gaps and the document was updated. Then came a parallel month. Full switchover happened in the fourth month and went through without disputes.
The second company took longer - four months against one. But six months on, the first company was still fixing its original problems.
The whole source of the difference is one document: the rules in writing. It is not technical work, and no system does it for you.
What the rules document should contain
One page is enough. These seven points close practically every first-month question:
- Work schedules - start, end and break for each type.
- Lateness threshold - after how many minutes a record counts as late.
- Break rule - inside working time or not.
- Incomplete days - what happens when there is a check-in and no check-out.
- Overtime - whose approval puts it into the record.
- Exceptions - business trips, site changes, technical failures, points with no coverage.
- Rounding - step and direction, with one example.
HR should not write it alone. Involving a branch manager exposes the operational gaps and involving the accountant exposes the calculation gaps - and those two kinds of gap are different from each other.
The next step
The lightest form of rollout is the model with no hardware purchase: the decision stays reversible and no budget approval is needed to run a trial.
See what QRGate does, or calculate the price for the size of your structure.
