Starting point: a check without a work permit
The concept covers a food plant where a packing line needs a quarterly mechanical check carried out by an external service company. The check is not hazardous work under the plant procedures, so no work permit is issued. Even so, the technician enters a zone where an auditor under BRCGS or IFS will ask three things: who entered, whether they were trained, and whether they made a health declaration on that day.
This is an implementation scenario prepared for the maintenance manager, not a description of a finished project. It shows how to configure the mechanisms available in the system so that the check can take place without bypassing procedures and without manual exceptions at the gate.
Problem: the gate requires a permit that does not exist
Without additional configuration, the gate checks in order: account activity, health declaration, training, qualifications, permit validity and finally the presence of a permit or visit. A technician without a permit would be stopped at the last step, even though everything else is in order. Security staff on the night or morning shift would then have to call the manager and decide outside the system, and those are exactly the decisions an auditor challenges.
The order of denial codes is fixed, so security always sees the reason in the same sequence. For the maintenance manager this means predictability: if the technician has training and a declaration, the only missing item will be the basis for entry.
Planning limits for a service visit
Solution: a visit as a one-day substitute for a permit
A planned visit acts in the system as a one-day substitute for a work permit, with no time of day set. It removes only the permit requirement. An active account, training and qualifications still decide on entry, so the visit is not a loophole, only a deliberate marking that this person has a justified reason to be present on that day.
The visit is planned by the host, meaning an active internal employee of the plant. The coordinator of the external company cannot plan visits, because that would let them bypass the permit requirement. In this scenario the host is a maintenance employee who knows the line and is responsible for the technician.
Planning window
A visit can be planned for days from today up to 377 days ahead, and up to 34 days at once. For quarterly checks one batch of days is enough, and the system skips a day on which the person already has a visit and does not overwrite another host.
Induction training before arrival
A supplier, courier or guest can complete the induction training on a tablet or phone in Polish, English, Ukrainian or Russian. The kiosk recognises a trained person and welcomes them, while an untrained person is shown the material. A service technician arriving for the first time therefore goes through training at the entrance, and later visits do not repeat it without need.
Health declaration on the day of the check
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. The requirement applies to accounts from external companies and guests, while internal employees are exempt. The service technician is fully subject to it.
When a technician has a badge but no declaration for today, the gate does not refuse and does not record an entry. It gives a third verdict: it asks for a declaration. Once the declaration is made, the entry is recorded. As a result the register contains no artificial refusals that later have to be explained to the auditor, and proof of entry arises only when all conditions are met.
Phone call to the host on the first entry
On a guest's first entry on the day of the visit, the dispatcher calls the host once, with no retries. A refusal and an exit do not trigger the call. If the host has no number in their profile, they receive a single email asking them to complete it. For maintenance this is a concrete benefit: the host knows the technician is already on site and can go and meet them, instead of searching the plant.
This design also prevents a flood of calls. If several technicians enter at the same time, notifications are grouped, which is covered in a separate description of the group phone cost.
Effect for the audit and conclusions
After the check the register contains the person, the visit day, the host, the channel used for the declaration and the confirmation time. The system provides audit evidence but does not certify the plant: conformity assessment belongs to the certification body. The maintenance manager gains one consistent path for all checks that do not require a permit.
Implementation conclusions: first, appoint hosts in maintenance and complete their phone numbers. Second, schedule recurring visits in advance. Third, agree the wording of the declaration with the quality department, because the version of the text is saved together with the entry.
Checklist
Video
Frequently asked questions
Does a visit exempt the technician from training?
No. A visit removes only the work permit requirement. Training, qualifications and an active account are still checked at the gate.
Who can plan a service visit?
An active internal employee of the plant as the host. The coordinator of the external company does not plan visits, so as not to bypass the permit requirement.
What happens if the technician does not make a declaration?
The gate asks for a declaration and records neither the entry nor a refusal event. The entry is recorded after the declaration is made.
Does the system certify the plant against BRCGS?
No. The system provides the register and audit evidence, while the conformity assessment is issued by the certification body.
Sources
Planning line service with an external provider?
We will show the configuration of visits, training and declarations using your line and your maintenance hosts.
Let's talk