InnerWeb
Skip to main content

Health declaration after midnight: raw material supplier at the night shift gate

A supplier driver signs the health declaration at 23:40, the queue in front of the gate moves on, and the vehicle enters after 00:10. For the system it is already a different day, so the declaration no longer applies. Below is a scenario for the night security shift: what they see on screen, what the driver does and how to avoid a queue.

00:00
expiry boundary of the declaration
Source: karta
13 s
refresh interval of the evacuation list
Source: karta
6
groups of people on the evacuation list
Source: karta

Scenario: 23:40 at the gate, entry after 00:10

A food plant also receives raw materials at night. The driver pulls up before midnight, scans the invitation code, completes the health declaration and waits in the queue for a free ramp. At 00:10 security lets them onto the site. This is a conceptual scenario for a food plant, based on the function documentation, not a description of a specific implementation.

The question is whether a declaration signed twenty minutes earlier still counts. The answer follows from the day rule: the health declaration is valid for one calendar day in the plant time zone. A declaration signed yesterday at 23:59 is invalid today, and one signed today at 00:01 is valid until midnight.

What security sees after midnight

If the driver has an active badge but no declaration from the current day, the gate does not refuse entry. It gives a third verdict alongside admission and refusal: it asks for a declaration. In this case it records neither an entry nor a refusal event, so no false trace appears in the register.

The guard does not need to analyse the hours. The system compares the date of the declaration with the current date in the plant time zone and makes the decision. For the night shift this matters, because people at three in the morning should not have to work out whether a declaration is still valid.

Denial codes follow a fixed order

When several things are missing at once, the system shows the codes in a fixed order: inactive account, missing declaration, missing training, missing qualifications, expired permit, no permit or visit. The guard therefore always sees the first obstacle, and the driver does not receive contradictory instructions.

Declaration at 23:40 and entry at 00:10: minutes from signing

Declaration at 23:40 and entry at 00:10: minutes from signingBar chart: 20 minutes to midnight, 30 minutes from signing to entry, 10 minutes after the day boundary.0102030minTo midnight from signing: 20 min20 minTo midnight from signingFrom signing to entry: 30 min30 minFrom signing to entryAfter the day boundary: 10 min10 minAfter the day boundary
Source: Sample calculation: times 23:40 and 00:10 from the scenario description

Two ways to make a declaration after midnight

The driver can make the declaration again at the registration station, on a phone through the training path, or verbally. On the training path, confirmation requires proof of identity: the invitation code, an active badge or the person's active card. The account identifier alone gives a refusal, which protects against declarations being made on behalf of someone else.

In the security panel the guard confirms a verbal declaration with a button on the person's card, and the entry remembers who confirmed it. After the gate asks for a declaration, such a confirmation also records the entry. For a driver with limited command of the language, it matters that the declaration text can have a separate English version, and an empty English version means the Polish text is used.

One declaration per person per day

The declaration is recorded once per person per day, together with the channel and the confirmation time. A second record on the same day returns the first entry. If the driver makes the declaration at 23:40 and again at 00:12, two entries are created in two different calendar days, each with its own time. This naturally documents that the notification was renewed, not stretched out.

Exit and the evacuation list after midnight

The declaration concerns entry only. A person already on site can always leave, so a driver standing at the ramp past midnight is not blocked when leaving the plant. As a result they do not remain on the evacuation list for the night automatic check-out.

The evacuation list is built from QR scans at the gate, refreshes every 13 seconds and divides people into six groups: guests, couriers, suppliers, plant employees, external companies and uncertain. A supplier driver falls into the supplier group, and the system does not know their location in the building.

Conclusions for logistics and security

The simplest organisational change is to ask drivers to make the declaration directly before entering the site, not in a queue tens of minutes earlier. The second is to prepare language versions of the training and declaration for drivers from abroad. The third is an instruction for the night security shift that the gate's third verdict is a request, not a refusal.

Checklist

Video

Frequently asked questions

Is the declaration valid for 24 hours from signing?

No. It is valid for one calendar day in the plant time zone, that is until midnight.

Will the gate record a refusal if the declaration is missing?

No. The gate asks for a declaration and records neither an entry nor a refusal event.

Can a driver already on site leave after midnight?

Yes. The declaration concerns entry only, so leaving is always possible.

Sources

Do you receive deliveries at night too?

We will walk through the night gate operation with you and set up declarations so the queue does not build up in front of the ramp.

Let's talk