InnerWeb
Skip to main content

Cost of manual fixes for missing exits in RCP: a calculation for a 300-person plant

A missing exit in RCP looks harmless, but each one starts a chain: the employee, the supervisor and HR must establish an hour nobody swiped. For a 300-person plant an illustrative calculation points to several dozen hours a month. Below are the assumptions, the formula and the place where the system shortens this chain.

31.5 h
manual handling of missing exits before the change, monthly
Source: illustrative calculation
6.3 h
handling after the change, monthly
Source: illustrative calculation
89 min
default threshold for an uncertain exit
Source: component card

Why a missing exit costs more than it seems

A single correction takes little time, but it touches three people. The employee has to recall the exit time, the supervisor approves it, and HR takes the change into account when closing the period. The employer is responsible for the working time record, which is the basis for pay and other benefits (Labour Code (Kodeks pracy), art. 149 § 1), so a gap in the record cannot be left open.

The cost also grows through delay: the later someone notices the gap, the harder it is to establish the real hour. That is why the calculation counts not only the minutes of the correction itself but also the time spent searching and asking.

How the system shortens the fixing of missing exits

The InnerWeb time module has three elements that reduce the number of manual interventions. The first is detection: by default an exit is treated as uncertain after 89 minutes. The second is reminding: a reminder call starts after 34 minutes, and the system calls the person who did not scan the exit, once a day per channel. The third is the supervisor's exception queue with the missing exit category.

What happens to a day without an exit

For an internal employee, automatic check-out after the hour limit does not record a real exit. The day is marked as a missing exit and the employee confirms the hour themselves. The record is therefore not invented by the system, which protects it from inflated hours.

Where manual work remains

The supervisor still has to approve the confirmed hour. A supervisor cannot approve or correct their own record, so even with automation a control element remains. The calculation does not assume zero corrections, only less time per correction.

Hours a month on corrections of missing exits (300 people)

Hours a month on corrections of missing exits (300 people)Before and after chart: 31.5 hours a month manually and 6.3 hours with reminders and the queue010203040hManual: Handling missing exits: 31.5 h31.5 hManualWith reminders and queue: Handling missing exits: 6.3 h6.3 hWith reminders and queue
Source: Illustrative calculation on the assumptions in the Calculation section

Calculation for a 300-person plant

The figures below are an illustrative calculation on explicit assumptions, which each plant can replace with its own measurements from the last three months. They do not describe any specific plant. The most important parameter is the share of days with a missing exit, which is best read from the exception report, not estimated from memory.

  • Working days per month: 21 per person, which is 6,300 person-days for 300 people.
  • Share of person-days with a missing exit before the change: 3%, which is 189 cases a month.
  • Manual handling time for one missing exit: employee 3 min, supervisor 4 min, HR 3 min, in total 10 min.
  • Time after the change: the reminder cuts the share of missing exits to 1%, and handling one takes 6 min.

Result and sensitivity to the assumptions

Before the change: 189 cases at 10 minutes is 1,890 minutes, or about 31.5 hours a month. After the change: 63 cases at 6 minutes is 378 minutes, or about 6.3 hours. The difference is about 25 hours a month across the plant. This is an illustrative calculation and we do not promise this result; it serves as a comparison with your own measurement.

The share of missing exits has the greatest impact on the result. If a plant has 6% instead of 3%, the manual cost doubles to about 63 hours and the saving grows proportionally. Where missing exits are rare, it pays back faster to tidy up the thresholds than to extend the system.

Hidden costs beyond the minutes

Besides the correction time there is a risk of error when closing the period. The settlement period is closed and reopened only by the HR or administrator role, so every correction after closing requires an additional operation. The fewer gaps at the end of the month, the fewer such returns.

Example calculation

Monthly time spent handling missing exits in a 300-person plant

Assumptions
ParameterValue
Number of employees300 people
Working days per employee21 days/month
Share of missing exits before the change3 %
Handling time before the change10 min/case
Share of missing exits after the change1 %
Handling time after the change6 min/case

Result: Before: 189 x 10 min = 1,890 min, about 31.5 h. After: 63 x 6 min = 378 min, about 6.3 h. Difference about 25 h a month.

Note: Illustrative calculation on the assumptions above; the plant should substitute its own data from the exception report. It is not a promise of a result.

Video

Frequently asked questions

Where do I get the share of missing exits?

From the exception queue for the last three months: the number of records in the missing exit category divided by the number of person-days.

Does the system fill in the missing exit by itself?

No. The day is marked as a missing exit and the employee confirms the hour themselves, which protects the record from inflated hours.

Are these hours converted into money savings?

We do not convert them into amounts, because the cost of an hour of HR or supervisor time differs in every plant. It is time that can be spent on other tasks.

Sources

Let's calculate missing exits in your plant

We will put your data from the exception report into this calculation and show where most of the time goes. Book a conversation with the InnerWeb team.

Let's talk