InnerWeb
Skip to main content

Gate refusal codes as an indicator of entry process quality

Every refusal at the gate has a reason: no declaration, training, qualifications or permit. If the quality department reads them once a month as an indicator, it sees which stage of guest invitation fails most often. Below are practices for turning refusal reasons into concrete process corrections.

3
gate responses: admit, refuse and a required declaration
Source: feature card: Health statement
409
server response to a visit attempt when something other than a permit is missing
Source: feature card: Planned Visits

Why refusals are a better indicator than complaints

Complaints from guests and hosts say that something went wrong, but not why. A refusal reason says exactly which gate the person did not pass: account, training, qualifications, permit or declaration. The distribution of reasons over time shows where the invitation process is weak: in the content of the invitation, in the training timing or in the declaration setting.

Practice 1: define what is a refusal and what is a missing declaration

The system makes an important distinction. When the declaration is missing, the gate gives a third response alongside 'admit' and 'refuse': it does not record the entry, does not create a refusal entry in the SIEM log and does not add the person to the training group. That is why, when counting refusals from the security log, you will not see missing declarations. For the monthly review, therefore, combine two sources: the refusal log and the gate register.

Write this rule into the review instructions, so that a new quality employee does not conclude that there are no missing declarations at all.

Example: distribution of refusal reasons in a month

Example: distribution of refusal reasons in a monthHorizontal bar chart: for example no declaration 18, no permit 12, no training 9, no qualifications 5.05101520refusalsNo declarationNo declaration: 18 refusals18No trainingNo training: 9 refusals9No qualificationsNo qualifications: 5 refusals5No permitNo permit: 12 refusals12
Source: Example calculation: illustrative figures, not data from any plant.

Practice 2: group reasons into four buckets

The simplest approach is to group reasons into buckets that match the stages: account, training, qualifications, permit and declaration. Assign an owner of the correction to each bucket. The one who invites is responsible for accounts; the training department for training; the external company and the host for qualifications; the works manager for permits or visits; and the quality department, which sets the wording and the reminder method, for declarations.

Practice 3: read refusals in the context of a visit

The visit button in the security panel appears only when the permit is the only missing item; when other items are missing, the server returns 409 without saving anything. If the monthly summary shows many refusals for lack of a permit for people who arrive without work, that is a sign that invitations should set up a visit. The same pattern repeated several times is cheaper to fix through the process than through the guard.

Practice 4: check whether a missing training is really a language gap

When training in the account's language is missing, the gate requires training in Polish instead of skipping it. If refusals for training concern mainly one group of foreign nationals, the fix is to add a language version or change the account language, not another reminder. Also remember that a passed training does not replace the declaration, so a group that has completed training may still not get in.

Practice 5: close the loop once a month

The monthly report ends with three records: the most frequent reason, the owner of the correction, and the date to check the effect. The following month you compare the same bucket. If it has not fallen, the change did not work and the correction is wrong or incomplete. Such a record is also a clear proof of process improvement in case of a conversation with an auditor; the EU GMP guidelines talk about personnel and hygiene, and this review shows that the plant monitors them.

Checklist

Video

Frequently asked questions

Why can't I see missing declarations in the SIEM log?

When a declaration is missing, the gate does not record the entry and creates no refusal entry in the SIEM log. That is why the review also relies on the gate register.

How often should refusals be reviewed?

We recommend once a month, recording the reason, the owner and the date to check the effect.

Is the data in the chart the plant's own data?

No. These are illustrative figures that show how the distribution works.

Sources

Let us turn refusals into corrections

We will show how to set up a monthly review of refusal reasons from the gate register for your plant.

Let's talk