InnerWeb
Skip to main content

FAQ: working time recording from cards and QR scans instead of a separate time clock

Working time recording does not have to mean new terminals at every gate. QR scans at the gate create the attendance record in the InnerWeb working time module, and card punches from the existing access control system can be fed into it according to the specification for the access control vendor. Below are answers to the questions that come up most often.

11 h
daily rest period checked by the module
Source: Labour Code art. 132
35 h
weekly rest period checked by the module
Source: Labour Code art. 133
12 h
default presence limit for an external company
Source: D20 cell card

Where the entry and exit record comes from

Plant directors usually ask the same question: do we need to buy separate time clock devices and run cables to every entrance to keep a working time record? The answer depends on which event sources the plant already has. The employer must keep a record of employee working time, which is the basis for pay and other benefits (Labour Code (Kodeks pracy), art. 149 § 1), but the law does not require a particular device, only an effective record.

In the InnerWeb working time module, QR scans at the gate, which are also used for the evacuation list, create the working time record. One scan therefore answers two questions: who is on site in case of an incident and how many hours that person worked. The second source is the employee, who can record entry, exit and break from a phone.

What is the source of truth and what is only an add-on

We treat the gate scan as the primary record. Registration from a phone is a supplement for a reader failure, business trips or work outside the gate, so it has its own rules: the declared time must fall within the range from 13 days back to 180 seconds forward, and a declared entry counts as approved only after the supervisor confirms it.

Questions about the role of the existing access control system and cards

The most common concern is replacing readers. InnerWeb is a software vendor, not an access control equipment vendor: it does not produce or replace readers, it integrates with the customer's existing access control system. It is an independent system that complements the existing systems: access control, time clock, HR and ERP, not a replacement for them.

Do card punches from access control reach the working time record?

The access control vendor passes card punches through an authenticated webhook. The event should contain the event time from the reader, the location, person data, company, active card number, as well as the direction entry/exit and an event identifier. Authentication uses a token with limited validity, renewed automatically by the integration. The rules for pairing entries and exits and for rejecting duplicates are set in the specification agreed with the access control vendor, which is why it is the starting point of the integration talk.

Why the direction and the event identifier matter so much

The direction tells an entry from an exit, and the event identifier makes it possible to filter out duplicates created when the access control system resends an event. Without either of them the working time record ends up with wrong hours, so it is worth putting both fields into the specification already in the talk with the access control vendor.

Do cards or readers have to be replaced?

No. Cards and readers stay as they are. InnerWeb joins the chain as the system that links a punch event with qualifications, permits, attendance and the working time record. The only change on the access control vendor's side is adding the fields from the specification above to the events it sends.

Default thresholds of the working time module

Default thresholds of the working time moduleHorizontal bar chart of the three default thresholds: 13, 34 and 89 minutes020406080100minExit classification toleranceExit classification tolerance: 13 min13Reminder callReminder call: 34 min34Uncertain exitUncertain exit: 89 min89
Source: D20 cell card: working time module settings

HR questions: corrections, missing exits and queues

HR usually asks not about the technology but about what happens when someone forgets to punch out. The answer is the supervisor exception queues: missing exit, changed exit, declared time, lateness, work outside the schedule, exceeding the norm and rest violations. With them, corrections are made by the supervisor as they happen, not by HR at the end of the month.

What does the system do when an exit is missing?

For an internal employee, the automatic closing after the hour limit does not record a real exit. The day is marked as a missing exit and the employee confirms the time personally. By default the module treats an exit as uncertain after 89 minutes, and the reminder call starts after 34 minutes; both thresholds are settings that the plant can adjust.

The system calls the person who has not scanned out with a reminder, once a day per channel. The exit classification tolerance is 13 minutes by default, so small deviations do not flood the queue.

Can a supervisor correct their own working time?

No. A supervisor cannot approve or correct their own record; on their own record the supervisor role gives only a view. A change made by a supervisor is approved by a person with the appropriate role, which closes the typical audit gap.

Who sees what?

The employee sees themselves, HR sees the employees of its own company, the supervisor sees their subtree, and the administrator sees everything. The reason for an absence, that is the leave code, is visible to the employee, HR and the administrator; the supervisor sees only the information that an absence is excused.

Questions about external companies, night work and rest

External crews enter through the same gate but are not subject to employee time recording. For an external company, the automatic check-out after the hour limit records the exit, and the default presence limit is 12 hours. The difference from an internal employee is deliberate: a guest does not confirm the exit time, so the system must close their presence on its own.

Is night work counted separately?

Yes. The module counts the minutes worked at night, 22:00-06:00, and passes them to the export column for HR. For a shift that crosses midnight, HR receives a separate value, not a manual split of hours.

Does the system monitor rest periods?

The module warns about a daily rest violation below 11 hours, a weekly rest violation below 35 hours, and exceeding the weekly norm. The Labour Code guarantees the employee 11 hours of uninterrupted daily rest (art. 132) and 35 hours of weekly rest (art. 133). The warning goes into the supervisor exception queue before the problem reaches an inspection.

Questions about product status and honest limits

The module is disabled by default and the administrator turns it on. Visibility can first be limited to a list of testers, where an empty list means everyone. This way the plant can start with one department and, without affecting the rest of the staff, check whether the queues and thresholds fit its reality.

The module was piloted on one installation. It is not rolled out widely and does not settle pay: the customer's ERP should receive only the quantities of hours and days per employee and component, without rates and amounts. The schedule, HR and ERP export screens are at the preview stage with demo data, so we present them as an option under development, not as a ready standard.

Checklist

Video

Frequently asked questions

Is a separate time clock device needed to keep the record?

No. A QR scan at the gate creates the record in the working time module, and card punches from access control can be connected according to the vendor's specification.

Does InnerWeb replace card readers?

No. InnerWeb is a software vendor and integrates with the customer's existing access control system, without replacing readers or cards.

Does the module settle pay?

No. Only quantities of hours and days per employee and component go to ERP, without rates and amounts; pay stays in the payroll system.

Sources

Let's talk about records from your gates

We will show how a QR scan and punches from your existing access control system create a working time record without replacing readers. Book a call with the InnerWeb team.

Let's talk