InnerWeb
Skip to main content

Savings from integrating access card punches with RCP

When punches from the access control system flow automatically into time recording, the HR department stops re-entering reports and searching for missing entries by hand. We show a sample calculation for a plant with 800 people, together with the assumptions that everyone can replace with their own figures.

approx. 70 hours
monthly saving in the sample calculation
Source: sample calculation
33,600
punches per month in the assumptions
Source: sample calculation

Where HR time leaks away today

In plants without integration, punches from access control reach HR as a report, which someone transfers to the time recording system and then reconciles against shifts. The largest cost is not the re-entry itself but the search for missing punches: an employee entered but did not leave, or the other way round.

Every such case requires a call to the supervisor, checking the events and a manual correction. This time is invisible in the budget, because it is spread over minutes across the month.

How the integration works from the technical side

InnerWeb does not supply readers or cards. It receives card punch events from the access control system through a webhook and links them with qualifications, permits, attendance and RCP. This pattern works at a packaging manufacturer, where the punch integration from access control to RCP follows the specification prepared for the access control vendor, without our readers.

The platform provides a REST API and webhooks to an automation platform, and rules of the if-then type can trigger a webhook after an event. When the client's network blocks outgoing traffic from the application host, webhooks are stored permanently in a queue and collected by a poller through the incoming channel, so events are not lost.

  • The punch event from access control arrives at InnerWeb as a webhook.
  • The system links it with the person, attendance and permits.
  • RCP receives the full set without manual re-entry.
  • Gaps are visible immediately, not at the end of the month.

HR time on punches: before and after integration

HR time on punches: before and after integrationBefore and after chart: re-entry 40 to 0 hours, corrections 45 to 15 hours a month01020304050hours/monthBefore (Re-entering reports): 40 hours/month40After (Re-entering reports): 0 hours/month0Re-entering reportsBefore (Manual corrections): 45 hours/month45After (Manual corrections): 15 hours/month15Manual corrections
  • Before
  • After
Source: Sample calculation based on the assumptions in the section Sample calculation

Sample calculation: hours per month

We assume a plant with 800 people, 21 working days per month and 2 punches per person per day, which gives 33,600 punches a month. We assume that 4% of punches require manual attention (no matching entry-exit pair), which gives 1,344 cases, at 2 minutes each.

State before integration

Re-entering summary reports: 40 hours a month. Manual corrections: 1,344 cases at 2 minutes, which is about 45 hours. Total about 85 hours.

State after integration

Re-entry disappears. Corrections remain for rare cases, because the system flags gaps as they happen and some are resolved by themselves: we assume about 15 hours a month. Saving about 70 hours.

What this calculation does not cover

We do not count the cost of re-entry errors, which come back as pay disputes, nor the benefit of detecting absences earlier. We also do not count the time of security staff. This means the real benefit may be larger, but we prefer a cautious calculation that can be defended before the board.

The cost of integration depends on the capabilities of your access control and RCP systems, so the price is individual. First we gather the event specification and the channel, and only then agree the scope.

How to check the effect after go-live

Measure three numbers before and after: the time needed to re-enter a report, the number of manual corrections, and the time from the event to its appearance in RCP. One month of comparison is enough to replace the assumptions with your own data.

  • Number of manual corrections per month.
  • HR hours at month close.
  • Delay of the event in RCP.
Example calculation

HR hours saved with 800 people

Assumptions
ParameterValue
Number of people800 people
Working days21 days/month
Punches per person2 per day
Punches requiring attention4 %
Time per correction2 min
Re-entering reports before integration40 hours/month

Result: Before: approx. 85 hours/month (40 re-entry plus 45 corrections). After: approx. 15 hours/month. Saving: approx. 70 hours/month.

Note: Sample calculation. All values are assumptions to be replaced with plant data; they do not describe a specific entity.

Video

Frequently asked questions

Does the integration require replacing the readers?

No. InnerWeb integrates with the existing access control system and receives punches through a webhook. We do not replace readers.

Does InnerWeb replace RCP?

No. We are an independent supplementary system that works alongside the client's existing systems, including access control, RCP, HR and ERP.

What happens to punches when the network is blocked?

Webhooks are stored permanently in a queue and collected by a poller through the incoming channel, so events are not lost.

Let's calculate the saving for your figures

We will replace the assumptions with your plant data and prepare an event specification for your access control vendor. Book a call with the InnerWeb team.

Let's talk