InnerWeb
Skip to main content

Hall Check by Badge Scan: Use Case

A field inspector of external contractors stops next to a contractor's worker in the hall and has to decide within seconds whether this person may work here. We describe a scenario in which a QR badge scan opens one screen on the phone with the verdict, trainings and the contact at the company. This is a concept based on system functions, not a description of a specific installation.

1
server call for the check screen
Source: feature card
4
training statuses: valid, expired, failed, missing
Source: feature card

Scenario: a check in the middle of the hall

A line renovation is under way in the hall, and several external companies work at the plant. The inspector walks between workstations and stops a contractor's worker they do not recognise. The paper list of permissions is in the office, and the question 'who are you and who let you in' settles nothing.

The gate admitted this person in the morning, but a lot may have changed since then: the training may have expired, the company may have ended the contract, or the work permit may have been closed. The inspector needs the current state, not the morning one.

What the inspector sees after scanning the QR badge

After the badge is scanned, the inspector sees on one phone screen: who the person is, whether they may stay on the plant, which company they come from, whom to call, where the company is working today on the map, and who else from it is on site. There is no switching of tabs or searching through menus, because everything is in one view.

The same screen lists all the person's trainings with their validity. The statuses are valid, expired, failed and missing, and the items that block entry come first on the list with a clear marker. The inspector immediately sees what the reason for refusal is and can tell the worker.

Number of server queries per check

Number of server queries per checkComparison: five separate queries versus one server call when a badge is scanned.012345queriesSeparate queries: Before: 5 queries5Separate queriesOne screen: After: 1 queries1One screen
Source: Description of the field check function: one call instead of five

Weak Wi-Fi: why a single server call

Wi-Fi coverage in the hall is sometimes weak, especially near large metal structures. That is why the inspection screen is built with a single server call. Five separate queries for the person, the company, the trainings, the map and the co-workers could hang halfway, and the inspector would be left with an incomplete picture.

One query means one answer or one clear lack of answer. The inspector knows whether they have the full data or must repeat the scan. This simple rule decides whether field checks are used or bypassed.

One verdict for the gate and the hall

The field check shows the same verdict as the gate, from the same service, without duplicated rules. If the person was admitted in the morning and their training expired during the day, the inspector sees the current assessment, not the historical decision of the gate.

Having no two sets of rules means there is no dispute about which version is true. Security at the gate and the inspector in the hall look at the same result, so decisions are consistent and easier to defend to the contractor.

Check history as evidence

Each check is recorded in the history together with a snapshot of what the inspector saw on the screen. When a week later the contractor disputes a refusal, or an auditor asks whether external companies are checked, the answer is the record: who, when and on the basis of which data state.

For the OHS and security departments it is also material for analysis. If refusals concern one training, the problem lies in how that training is organised, not in the behaviour of the workers.

Conclusions for the plant

The value of the scenario lies in shortening the path from scan to decision and in one consistent verdict. The inspector does not need to contact the office, and the contractor sees that the rules are applied equally.

Before go-live it is worth checking coverage at the weakest points of the hall and deciding what the inspector does after a refusal: a call to the company, escorting the person out of the hall, or a report to OHS.

How to prepare the plant for such checks

Before go-live, check coverage at the weakest points of the hall and decide which inspectors get access to the check screen. The scope of permissions is set by the plant administrator, so the list of inspectors should be short and up to date.

Also decide what the inspector does after a refusal: call the contact at the company, escort the person out of the hall, or report the case to OHS. A written procedure shortens discussions in the hall and lets contractors know what to expect. Treat the first two weeks as a trial period and review refusals at a short meeting of inspectors.

Video

Frequently asked questions

Does the inspector need a separate application?

The check works as a screen on the phone after the QR badge is scanned. Security sets the scope of the inspector's permissions.

What if the badge is damaged?

The inspector stops further work until the matter is clarified and directs the person to security. It is worth writing down the replacement procedure before go-live.

Is the check history available to an auditor?

Yes, each check is recorded with a snapshot of the screen. This is evidence that external companies are really being checked.

Checking external contractors in the hall

Tell us how you check contractors today. We will show the check screen and agree which data your inspector should see.

Let's talk