Why 14 days
Fourteen days is enough time to fix what the check reveals: add cards, change the kiosk settings, train the security staff. A shorter time leaves only workarounds, and a longer one means the list gets out of date, because agencies change their plans.
The checklist covers four areas: accounts and invitations, training, temporary cards, and the gate and integrations. Each item has an owner: security, IT, the secretariat or the agency coordinator.
Accounts and invitations
Registration takes the most time at peak. A bulk invitation accepts up to 144 addresses in one invitation and has a limit of 5 requests per 13 minutes per user, so with many agencies agree in advance who sends the invitations and when.
Also check the secretariat address in the email settings. Only after it is set does the invitation window show the option to order a printed QR label, which is useful for people without a phone.
Technical limits to consider before the peak
Training and the kiosk
The training kiosk leads through the material (PDF slides or video) and a multiple choice test in Polish, English, Ukrainian and Russian. At peak the load grows, so count how many people per day will pass the training and whether there are enough stations.
Make sure the training has the answer shuffling switch enabled, which is on by default. With large groups the answer keys spread fastest, and this switch makes them harder to pass on.
Temporary cards and the account search
The account search with an RFID card at the station requires at least 3 characters of the surname and returns up to 13 results. At peak surnames repeat more often, so train the security staff to ask for an extra character, for example the initial of the first name. The card number is not shown in the results.
Check the pool of temporary card numbers and the list of cards to be recovered from the previous season. Cards that were not returned are the most common reason for shortages at peak.
Gate, integrations and duplicate accounts
If the plant passes card registrations from the access control system by webhook, check the authentication rules: the token has a limited validity period and is renewed automatically by the integration. The access control system sends events in real time, with the event time from the reader, the direction (entry or exit) and the event identifier, and InnerWeb receives them through an authenticated webhook. The rules for pairing entries and exits and for rejecting duplicates are set in the specification with the supplier, preferably before the peak.
When the same person is hired again through another agency, duplicate accounts can appear. The training result recorded on a deleted account is redirected to the account it was merged into, for at most 3 successive merges, so plan the merging in advance, not during the peak.
Checklist
Video
Frequently asked questions
Why exactly 14 days?
It is a practical recommendation: enough time to fix the problems found during the check, and not so long that the list gets out of date.
What if an agency sends its list at the last moment?
Paste it into a bulk invitation on the day it is received, watch the statuses, and invite people without email by phone.
Does InnerWeb supply temporary cards?
No. InnerWeb does not produce or replace cards and access control readers; it links registrations from the existing system with accounts and training.
Let us prepare the plant for the peak
We will go through these points on your settings with you and show the gaps. Book a conversation with InnerWeb.
Let's talk