InnerWeb
Skip to main content

Peak season: agency staff and access cards

During peak season a distribution centre takes on several hundred temp agency workers within a few days, and each of them needs a card, induction training and an entry in the attendance register. This scenario shows how to spread these steps over time so that no queue forms at the gate on the first day. We describe a concept for a warehouse with an existing access control system, not an implementation at a specific client.

144
addresses in one bulk invitation
4
kiosk training languages: PL, EN, UK, RU
13 s
refresh interval of the evacuation list

The situation: several hundred people in a few days

The concept applies to a logistics centre that works with several temp agencies and runs its own access control system. Before the peak season the site director orders extra workers, and the agencies usually deliver their lists a few days before the start. The list is often incomplete, changes up to the last moment, and some people turn up at the gate with no prior contact with the site.

For the calculation we use explicit example assumptions that are not tied to any site: 400 agency workers within 5 working days, three agencies, three shifts. The figures show the scale of the work, not a comparison with a particular facility.

Step 1: bulk invitations before anyone arrives

The first step is preliminary registration of people before they appear at the gate. In InnerWeb the operator pastes the text with e-mail addresses received from the agency, the system extracts the addresses, converts them to lower case, removes duplicates and stops at a limit of 144 addresses per invitation. Before sending, it shows a preview of the message, and each person receives a separate invitation.

A bulk invitation does not create accounts. The person registers on their own, and the invitation row changes its status to registered once an account with that e-mail address appears. If the mail server rejects the message with a permanent error, the row gets the status rejected together with the error text, so the operator knows immediately whom to call. For 400 people and a limit of 144 addresses, three invitations per agency are needed, and the limit of 5 requests per 13 minutes per user is not an obstacle here.

  • The agency sends a list of e-mail addresses or phone numbers, because one of these fields is enough for an invitation.
  • The security operator sends invitations in batches of 144 addresses.
  • The HR department sees the statuses: sent, rejected, registered.

Kiosk training throughput per day, example

Kiosk training throughput per day, exampleBar chart: two kiosks train about 38 people per day, four train 76, six train 114.0255075100125people per day2 kiosks: 38 people per day382 kiosks4 kiosks: 76 people per day764 kiosks6 kiosks: 114 people per day1146 kiosks
Source: Example calculation: 8 hours of work, 25 minutes per person, no breaks (assumptions from the Step 2 section).

Step 2: induction training before the first shift

Training runs on a kiosk system: the person goes through the material in the form of PDF slides or a video, and then takes a multiple-choice test in Polish, English, Ukrainian or Russian. The result belongs to the person's account, so when a permit or site access is created, the system checks the validity of the qualifications automatically.

With 400 people, the capacity of the kiosks decides the schedule. If one attempt takes an example 25 minutes and four kiosks stand in the centre, within 8 hours it is possible to train about 4 x 19 = 76 people per day. Training 400 people therefore takes about 5 days at full use of the stations. The conclusion is that invitations must go out earlier than the start date of the shift, and training must be spread across agency groups.

Step 3: the card and the first swipe at the gate

After training the person collects the card at the security desk. The access control system stays on the client's side: InnerWeb does not replace readers, it only receives card swipe events from the existing access control system via a webhook. The notification contains the data of the person and the company, so a person unknown to InnerWeb gets an account and a company created from the notification data.

The recorded entry appears in the On site view and on the evacuation list, which is built from QR scans at the gate and refreshes every 13 seconds. The same scans create the working time record with the supervisor console and exception queues, which gives HR and the warehouse manager one source of truth about attendance.

Result and conclusions for the centre director

The biggest gain is moving the administrative work away from the gate to the days before the start: registration and training take place before the person reaches the card issue point. In the example calculation, security at the gate only handles card issue and the first swipe, not the full registration of 400 people.

The director should agree three things with the agencies: the deadline for delivering lists, a uniform way of writing the agency name, and a training schedule per agency. Without these, even a well configured system will collect duplicate companies and people without a valid training on the first day.

Example calculation

How many days it takes to train 400 agency workers

Assumptions
ParameterValue
Number of agency workers400 people
Time of one attempt25 minutes
Number of kiosks4 pcs
Kiosk working time8 hours per day

Result: About 76 people per day, which is about 5.3 working days for 400 people.

Note: Example calculation on explicit assumptions, not tied to a specific site.

Video

Frequently asked questions

Does a bulk invitation create accounts for agency workers?

No. The person registers on their own, and the invitation row changes its status to registered once an account with that e-mail address appears.

What if a person has no e-mail address?

An invitation needs either an e-mail or a phone number. When one field is filled in, the other becomes optional.

Does InnerWeb replace the card readers in the warehouse?

No. InnerWeb integrates with the client's existing access control system and receives card swipe events via a webhook.

How does security know who is on site during peak season?

From the On site view and the evacuation list, which are built from gate scans and refresh every 13 seconds.

Plan the peak season in advance

Book a call about the concept for your distribution centre. We will go through invitations, training and card swipes before the agencies arrive.

Let's talk