Why the Question Comes Back After a Complaint
A customer complaint or a quality incident usually ends with the question of who could have had contact with a line or zone on a given day. The answer has two parts: who entered, and whether each of those people met the conditions of entry, including the health statement.
The quality department should not assemble this answer from several hand-typed sources. When the data comes from one register, the answer has one version and can be defended before an auditor or a customer.
Step 1: The Entry Register for the Chosen Day
Start with the entry register for the day. It contains entries scanned at the gate, so it shows everyone who passed through the gate, including guests, couriers, suppliers and external companies.
An important limit: the register is a source of information about entries and exits through the gate, not about where a person is inside the building. 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. It does not know where a person is inside the building.
Time to rebuild the guest list: target example in minutes
Step 2: The Attendance List and Groups of People
For the current day use the attendance list, and for past days use the summary from the register. Division into six groups speeds up the work: first check the groups that could have had contact with the product, that is external companies and suppliers, then guests.
The uncertain group needs separate attention. These are people whose assignment the system is not sure of, so the quality department confirms their status by hand, ideally with the help of security, before it closes the answer.
Step 3: Health Statements for That Day
A statement is recorded once per person per day, with the signing channel (workstation, reception, security panel, training, portal) and the time of confirmation. For each person in the entry register you therefore check whether they have an entry from that day.
For statements confirmed verbally, the security person who confirmed them is visible. Each entry carries a SHA-256 hash of the text shown to the person, which makes it possible to show which wording applied on that day. A statement is valid for one calendar day, so yesterday's entry does not replace today's.
Step 4: The Evidence Package Within an Hour
Put the answer together from three elements: the summary of entries for the day, the division of people into groups, and the list of statements with the signing channel. Add the people with gaps, if any, and their explanation.
A good practice is to rehearse this procedure once a quarter on a chosen past day, timing it. The goal is one hour from the question to a complete package. If it takes longer, the usual reason is gaps in the input data, for example no company assigned to an account or incorrectly completed statements.
- The entry register for the day the event concerns.
- The division of people into six groups from the attendance list.
- Health statements for the day, the signing channel and the hash of the text version.
- Explanations for people in the uncertain group.
Checklist
Video
Frequently asked questions
Will the list show which hall a person was in?
No. The attendance list is built from QR scans at the gate and does not know where a person is inside the building.
Is the statement from the previous day enough?
No. A statement is valid for one calendar day, so a separate entry must exist for each day.
How do we know which statement text a guest saw?
Each statement stores a SHA-256 hash of the text shown to the person, so a later change of wording does not rewrite the history.
Rehearse rebuilding the guest list
We will show, using a food plant as an example, how to assemble the evidence package from the register. Book a call or a demo.
Let's talk