Who these recommendations are for
We address these recommendations to the procurement department and the plant's lawyer, who prepare the contract or annex with the security agency, and to the plant's security manager, who assesses whether the clauses can be enforced. We assume the plant has a running security panel, meaning a separate screen for the security role, where a scan of a QR badge or an RFID card gives a verdict on whether the person may be on site right now.
We describe clauses about operating the system, not rates or guard working hours. This is not legal advice: the final wording of the clauses is set by the plant's lawyer.
Seven clauses for the contract or annex
Each recommendation has a justification that follows from how the panel actually works.
1. The scan as a mandatory act of control
Write that every person entering the site is scanned in the panel. In the panel the scan itself is the act of control: there is no separate button to let someone in, and the first scan of an authorized employee records an entry, the second an exit. A clause in the contract therefore enforces behavior the system already supports, and rules out letting people in on word of mouth.
2. A named account for each guard
Require the agency to report each guard by name and every change in the team within an agreed deadline, and the plant to set up accounts with the security role. A shared account breaks the chain of responsibility: it is unclear who scanned and who ignored a refusal.
3. Training requirement on the five panel views
The panel has five views: the gate, the list of companies and employees, the employee card, the work permits for today and the list of people on site. Write that before the first shift a guard completes training on these five views, and that the agency keeps a list of trained guards. The training does not have to be long, but it must be documented.
4. Reaction to a refusal
When access is refused, the panel shows a red banner and plays a voice recording: lack of training takes precedence over lack of a permit, and the other refusals have the signal alone. Write that the guard does not let a refused person in, does not pass their entry through another channel, and reports the refusal under the plant's procedure. Also describe what reporting means: the notification contains information about the person, the place and the missing element, and about what to do.
5. Scope of security powers: read, not close
The work permits for today view is read-only for security: security does not suspend, resume or close permits. It is worth writing this into the contract as a limit of liability, so that the agency does not take over decisions that belong to the plant and the permit owner.
6. Scanner and post: who is responsible for what
Write who maintains the scanner, the cable and the post at the gate, and who reports a failure. A scanner connected to the security post is a working tool of the guard, so the contract should set the time for reporting a fault and the obligation to use a backup method only under the plant's rules.
7. Return of accounts and data at the end of the contract
Set that on the day the contract ends, the guard accounts are deactivated, and the agency confirms that it holds no copies of data outside the plant's system. The plant, in turn, commits to naming the person who performs the deactivation. At an agency change this clause is the basis of the handover plan described in the security agency change scenario.
Clauses by area (number of points in the annex)
What not to promise in the contract
Do not write into the contract a declaration that the system ensures compliance with a specific legal requirement. The panel supports the process, and the register provides evidence for an audit. Also do not write an obligation for the agency to maintain access control readers if the plant or its access control vendor owns them: InnerWeb does not sell readers or cards, it integrates with the plant's system.
How to check that the clauses work
After the annex is signed, the plant's security manager runs a trial at the post: a scan of a person with a full set of valid documents, a scan of a person without training, and a scan of a duplicate. The trial result goes into the acceptance protocol of the post. After a month the plant checks in the register the share of scans ending in a refusal and the time in which refusals were handled.
Video
Frequently asked questions
Can these clauses be added to an existing contract as an annex?
Yes. They concern operating the system, not rates, so they usually fit into a short operational annex.
Can the agency let someone in without training?
It should not. The panel shows the refusal with the missing element, and the contract should forbid letting a refused person in through another channel.
Who is responsible for access control readers?
The plant or its access control vendor. InnerWeb does not sell readers or cards and receives entry events through a webhook.
Renewing your security agency contract?
We will prepare a list of clauses on panel operation for your annex. Let's arrange a call with procurement and security.
Let's talk