InnerWeb
Skip to main content

Card punch review after go-live: checklist after one week

A week after the webhook goes live you can already see which readers work and which stay silent. This checklist helps you check it systematically: place by place, template by template. Catching readers without a template is especially important, because their punches reach only the log and do not trigger the training alarm.

7 days
full cycle of changes before the first review
Source: InnerWeb guide
180 s
window for rejecting duplicate punches
Source: internal fact sheet

Why a review after one week, not after one month

A week covers a full cycle: working shifts, a weekend and the typical traffic of agencies. Configuration errors come to light quickly, and their effects grow over time. The OHS training alarm is raised only for punch places that have a defined template in InnerWeb; readers in other locations do not trigger an alarm. In one audit this concerned dozens of agency workers without training, whom the gate did not stop, because their punch place had no template.

A review after one week makes it possible to close such a gap before it becomes the subject of an audit.

Step 1: list of punch places from the AC system and from InnerWeb

The punch place field distinguishes the reader locations. Take from the AC system the list of readers that registered punches this week and compare it with the list of places that have a template in InnerWeb. Every reader with punches but without a template is a gap. Every template without punches is a reader that may not be sending events or is not in use.

  • Readers with punches and with a template: correct.
  • Readers with punches but without a template: a gap, no training alarm.
  • Templates without punches: to be explained with the AC vendor.

Review dates after go-live

Review dates after go-liveBar chart: first review after 7 days, second after 30 days0102030daysFirst review: 7 days7 daysFirst reviewSecond review: 30 days30 daysSecond review
Source: Recommended review schedule from this page

Step 2: checking events and duplicates

Compare the number of punches in the AC system with the number of records in InnerWeb for several readers. A difference of a few percent may come from rejecting duplicates within less than 180 seconds. A larger discrepancy points to lost events, for example after the expiry of a token valid for 12 hours. Also check whether the punches are visible in the gate entry register, not only in the account history.

Step 3: training alarms and requirements

The OHS training requirement can be set to cover all companies except the indicated exceptions, and a training group can have versions in several languages. Check whether the alarms concern the right companies and whether the exceptions are justified. Too many exceptions weaken the control, too few generate false alarms at the gate.

Review the cases in which the gate reports missing training despite its completion. When the same person has two active accounts, the system transfers the training result to the account with the entry card, but it does not merge accounts by surname. Discrepancies require a manual check by card number.

Step 4: conclusions and the next review

Record the result of the review: the list of gaps, the responsible person and the deadline for the fix. A card punch in the AC system only says that the person passed a point, not where the person is later, so during the review consider whether a link with the location on the map is needed for selected zones. Repeat the review after a month and after every change in the configuration of readers or in the agency data.

Checklist

Video

Frequently asked questions

Why is a reader without a template a risk?

Events from a place without a template go to the log and do not trigger the training alarm, so the gate does not stop people without training.

Does a difference in the number of punches mean an error?

A small difference may come from rejecting duplicates under 180 seconds. A larger one requires checking the token and the retry queue.

When should the review be repeated?

After a month and after every change in the configuration of readers or in the agency data.

Let's do the review after go-live together

We will compare the readers from the AC system with the templates in InnerWeb and point out the gaps. Book a call with the InnerWeb team.

Let's talk