How automatic working time calculation works
06.09.2026
Automatic working time calculation means that hours are derived from records without human effort, according to rules defined in advance. This is not only a question of speed - automatic calculation ensures that results are produced by the same logic in every department. This guide shows how the calculation is built, which rules must be supplied, and how to verify the result.
Where the calculation starts
Automatic calculation has two inputs: the records and the schedule. Without records there is no fact to calculate; without a schedule there is no basis for comparison. That is why the first step of any rollout is writing the schedules into the system.
A schedule provides three pieces of information: the start and end time of the working day, the daily norm, and the break policy. For shift patterns the rotation and its cycle are added.
The rules that must be supplied
- Lateness threshold - up to how many minutes an arrival is not counted as late.
- Break - fixed deduction, recorded, or included in working time.
- Overtime - when it starts and whether it requires approval.
- Rounding - a step of one, five or fifteen minutes.
- Incomplete record - how the day is counted when there is no check-out.
- Exceptions - business trips, leave, training, sickness.
These six rules fit on one page and are written once. In practice the success of the rollout depends precisely on how carefully this list is completed.
The calculation logic
| Step | Input | Output |
|---|---|---|
| 1 | Entry and exit records | Raw duration |
| 2 | Break rule | Net duration |
| 3 | Schedule and lateness threshold | Lateness, early leaving |
| 4 | Daily norm | Overtime or shortfall |
| 5 | Exception records | Final day status |
The order matters: calculating lateness before deducting the break produces a different result. In a system this sequence is fixed and does not vary by department.
What does not get automated
Honesty is required here: automatic calculation does not solve everything. Two things stay with people:
- The rules themselves. Whether the lateness threshold is five or fifteen minutes is a management decision.
- Approval of exceptions. Business trips and corrections are confirmed by a person.
Expecting these two is correct. The system does not make decisions; it applies them consistently.
A practical example
At a wholesale company the warehouse and office staff worked different patterns: the office from 09:00 to 18:00, the warehouse from 08:00 to 17:00 and frequently with overtime. The calculation ran on a single Excel template built for the office pattern.
As a result the warehouse overtime came out wrong - hours after 17:00 were sometimes counted and sometimes not. Complaints repeated at the end of every month.
When the calculation was automated, two separate schedules were written and the overtime rule was defined for each. A month later the warehouse overtime figure came out higher than before, because part of it had simply been disappearing. The complaints stopped.
How to verify the result
After switching to automatic calculation, a simple check in the first month is worthwhile:
- Five employees are chosen: standard, shift, flexible, one with heavy overtime and one with many exceptions.
- Their month is calculated by hand.
- The results are compared with the system's output.
If there is a difference, the cause is almost always an incompletely written rule rather than an error in the calculation.
The link to payroll
The final purpose of the calculation is pay. The format should therefore be agreed once with the payroll team: which columns, which rounding, and overtime on which separate line. Without that agreement the automatically calculated result is reformatted by hand and part of the time gained is lost.
Complex cases
Automatic calculation is tested not by the standard working day but by exceptions. Four cases cause the most trouble in practice.
Night shifts. The shift falls across two calendar days. The correct approach is to count it as one whole and assign it to the starting day.
Shift handover. Who gets the fifteen to thirty minutes where two shifts overlap? The rule must be uniform.
Several record pairs in one day. If an employee moves between sites, three or four pairs appear in a day and the system must join them correctly by sequence.
Partial days. Half-day leave, a medical certificate or training - on these days the norm falls and the lateness calculation changes.
All four exist in every company and must be tested during system selection.
Documenting the calculation rules
A hidden benefit of automatic calculation is that it forces the rules into one place. In a manual process the rules live in people's heads and differ from department to department; moving to a system compels them to be written down.
The document is one page long and covers six points: lateness threshold, break, overtime, rounding, incomplete records and exceptions.
Its practical value shows in two places. First, explaining the system to a new employee becomes easy. Second, it becomes the reference point in a dispute - the decision rests on an announced rule rather than on personal judgement.
In practice preparing this document often delivers more benefit than the software itself, because the absence of rules is the real source of the problem.
Managing changes
Rules change over time: the lateness threshold is revised, the break policy shifts, a new working pattern is added. Managing those changes deserves separate attention.
The main principle is that a rule change is not applied retrospectively. Applying a new threshold to past months is both unfair and destructive to approved reports.
The second principle is notice. A rule change must reach the team in advance - in practice the start of the next reporting period is the natural boundary.
The third is version retention: it must be possible to know which rule was in force during which period. That makes past reports explainable again.
Transparency of the calculation
The decisive factor in whether automatic calculation is accepted is transparency: the employee must be able to see how their hours were produced.
In practice that means visibility at three levels. The first level holds the raw records - the moments of entry and exit. The second shows the rules applied: the break was deducted, the lateness was calculated. The third holds the final figure.
When this chain is visible, disputes practically stop, because the logic behind every number can be followed.
Conversely, systems that show only the final figure enjoy low trust - the employee cannot verify the result and every unexpected number raises a question.
Transparency has a practical benefit too: errors are spotted the same day rather than at month end, and the correction is simple.
In summary
Automatic working time calculation rests on two inputs - records and schedule. Without a schedule the calculation cannot run, so formalising the schedules is always the first step.
When the six rules - lateness threshold, break, overtime, rounding, incomplete records and exceptions - are written on one page, building the system moves quickly. The decision, however, stays with people: the software does not create the rule, it applies it consistently.
The next step
The most practical way to start is to write the rules and trial them for a month in one department, keeping the old method in place for comparison.
QRGate stores schedules and rules in one place and performs the calculation the moment a record arrives. See what QRGate can do or calculate the price.
