Why does a missing exit cost more than it seems?
A missing exit has three effects: it inflates the employee's hour total, it blocks closing the settlement period, and it requires establishing the real exit time from the memory of the employee or the supervisor. The later the correction, the less reliable the hour. Correcting at the end of the month means asking about events from four weeks earlier.
The cost consists of HR time, supervisor time, the risk of a payroll error and a delay in closing the period. The calculation below counts only the first two components, because they can be measured without payroll data.
How does the system tell a missing exit for an external company from one for an employee?
The default stay limit for an external company is 12 hours, and automatic check-out records the exit. A person who stays on the premises for longer than 12 hours is checked out automatically, the task runs every 3 hours, and the entry is marked as closed automatically. For an internal employee the day is marked as a missing exit and the employee confirms the hour personally.
The distinction makes sense: for a guest and a contractor, the list of people on the premises matters most, so an automatically closed exit is acceptable. For an internal employee the hour affects pay, so automation does not guess, it asks for confirmation.
HR hours on missing exits per month
Exception queues and the reminder call
The working time module has supervisor exception queues: missing exit, late arrival, work outside the schedule, exceeding the norm and a breach of rest. The thresholds for an uncertain exit (89 minutes) and for the reminder call (34 minutes) are settings that you adjust to the length of breaks and the distance from the gate to the changing rooms.
The effect is simple: instead of HR discovering gaps at the end of the period, the supervisor sees them in the queue the next day, and the employee gets a reminder once 34 minutes have passed since the last swipe. If the exit swipe happens, the exception disappears without any involvement from HR.
Example calculation: HR and supervisors
The assumptions are illustrative. Replace them with the data from your report of missing exits for the last three months.
- Employment: 600 employees on card swipes.
- Share of days with a missing exit: 1.5 percent, that is 9 events per working day.
- Correction time by HR without the queue: 12 minutes per event (establishing the hour, entry, confirmation).
- Correction time with the exception queue and employee confirmation: 4 minutes per event.
- Working days: 21 per month.
Result
Without the queue: 9 events times 12 minutes gives 108 minutes per day, that is 1.8 hours, and about 38 hours per month. With the queue: 9 times 4 minutes is 36 minutes per day, that is 0.6 hours and about 12.6 hours per month. The saving is about 25 hours per month, and at a rate of PLN 60 per hour (illustrative assumption) about PLN 1,500.
The reminder call can reduce the number of events themselves. If reminders cut the share of missing exits from 1.5 to 1 percent, the time with the queue falls to about 8.4 hours per month.
What this calculation does not cover and what is the feature status?
We do not count the cost of payroll errors, penalties for exceeding rest norms, or the time of supervisors. The Labour Code guarantees 11 hours of daily rest (art. 132) and 35 hours of weekly rest (art. 133), and the module warns about breaches, but the calculation itself does not price them.
To be open about the feature status: the shift schedule screens and the export to ERP are at the preview stage with demonstration data, and we describe them as an option under development, not a ready standard. The working time module was piloted on one installation. Before you base a budget on it, agree the scope with the InnerWeb team.
Correcting missing exits: HR without and with the queue
| Parameter | Value |
|---|---|
| Employees on swipes | 600 people |
| Days with a missing exit | 1.5 % (9 events per day) |
| Correction without the queue | 12 min per event |
| Correction with the queue | 4 min per event |
| Working days | 21 days per month |
| Illustrative rate | 60 PLN per hour |
Result: About 38 hours per month without the queue and 12.6 hours with the queue: a saving of about 25 hours, or about PLN 1,500 per month.
Note: Example calculation based on illustrative assumptions; it does not include the cost of payroll errors and is not a guarantee of the result.
Video
Frequently asked questions
Who corrects a missing exit for an internal employee?
The day is marked as a missing exit, and the employee confirms the hour personally. The supervisor sees the exception in the queue and approves the entry.
Do external companies also have missing exits?
For an external company the stay limit is 12 hours, after which the exit is recorded automatically.
Do AC swipes already feed the working time records?
It depends on the integration specification: the AC system sends events in real time, with the reader time, direction and event identifier, and InnerWeb receives them through an authenticated webhook. The pairing rules for entries and exits are agreed with the AC vendor, and feeding the working time records is described as an option to be agreed.
Sources
Count the missing exits at your plant
Using the data from your report, we will show how many HR hours the exception queue can recover. Write to the InnerWeb team.
Let's talk