Contractor vehicles at the gate: permits, induction and safe entry for UK sites

A vehicle permit answers only one part of the question

When a contractor reaches a manned gate, the guard may be asked to decide several things at once: Is this the expected vehicle? Is the driver expected today? Which entrance and route should they use? May they enter the premises, and may the contractor actually begin work? Those questions are related, but they are not interchangeable. A vehicle permit can help identify an approved vehicle and support an access decision. It does not by itself prove that the driver is competent, inducted, insured for the task, authorised under a permit-to-work system or ready to start hazardous work.

That distinction should be explicit in the gate procedure. The Health and Safety Executive's Using contractors guide tells employers to define the job, select a suitable contractor, assess risks, provide information, instruction and training, cooperate with the contractor, and manage and supervise the work. The gate is one control point within that wider arrangement. It should enforce the site's agreed admission rules without becoming an improvised substitute for contractor management.

A useful policy separates three decisions. Vehicle admission concerns the registration, vehicle, route and gate conditions. Person admission concerns identity, expected attendance and any site-specific access requirements. Permission to start work concerns induction, competence, risk controls, supervision and, where required, a separate permit to work. One person may coordinate all three at a small site, but the evidence and authority for each decision should still be clear.

Define the contractor vehicle record before arrival

For regular contractors, create an approved vehicle or permit record only after the responsible site contact has supplied and checked the information required by the organisation's procedure. A proportionate record might contain the registration, contractor company, permitted site or gate, validity period, vehicle category and the internal sponsor or contract reference needed to resolve questions. Avoid turning the vehicle record into a copy of the entire contractor file.

The ICO's data minimisation guidance says personal data must be adequate, relevant and limited to what is necessary for the stated purpose. That is a practical design test for gate teams: if the guard only needs to confirm the vehicle, access window and sponsor, displaying unrelated identity documents, commercial paperwork or historic notes may create risk without improving the decision. Decide which roles can create, approve, view and amend permits, and review old records under the organisation's retention policy.

Priority Service's published features include saved vehicle and permit details, individual guard accounts, supervisor approvals and administrator reporting. The guard app can capture a vehicle photograph, read the number plate from the image or accept manual registration, and lets the guard check or correct the result. Automatic make, model and colour lookup is an optional add-on; those details can also be entered manually. The procedure should identify the registration as a useful matching key, not as conclusive proof that the expected driver or authorised work crew is present.

Give visiting drivers the route and rules they need

Gate approval should be paired with usable movement instructions. HSE's workplace transport guidance recommends separating pedestrians and vehicles where possible, using one-way systems where practicable, avoiding reversing, providing safe loading and unloading areas, and considering separate visitor parking because visiting drivers may not know the site. The gate procedure should translate the site's traffic plan into a short instruction for the actual arrival: speed limit, route, waiting point, unloading area, pedestrian restrictions and any requirement for an escort or banksman.

Reversing deserves specific treatment. HSE says nearly a quarter of deaths involving workplace transport occur during reversing and advises removing the need to reverse where possible. Where it cannot be avoided, routes should minimise it, reversing areas should be planned and people not needed there should be kept clear. A digital IN record does not control these hazards. The guard needs a current site instruction and a clear route for escalating an unsuitable vehicle, blocked bay or driver who will not follow the rules.

Do not overload the gate script with every rule in the contractor manual. Give the driver the information needed to reach the safe reception or work area, then ensure the responsible host completes the next control. For construction sites, HSE says traffic management systems, pedestrian routes, restricted areas, permit-to-work systems and emergency arrangements are among the subjects that site rules may need to cover. Rules should be clear, understandable and brought to the attention of everyone expected to follow them.

Keep vehicle admission separate from site induction

A green vehicle permit should never be treated as a permanent induction badge. The permit may remain valid while the driver changes, the planned work changes or an individual's induction expires under local policy. Equally, an inducted worker may arrive in a replacement van that is not on the approved vehicle list. The guard needs a defined outcome for each mismatch: refer for approval, direct the driver to a holding area, refuse vehicle entry while allowing the person to report through another process, or follow another site-specific instruction.

On construction projects, HSE states that every site worker must receive a suitable site-specific induction and that occasional or one-off visitors should receive an induction proportionate to the nature of the visit. An escorted visitor may need less detail than an unescorted visitor, but still needs awareness of the main hazards and controls. Other sectors should apply their own risk assessment, legal duties and site rules; the construction guidance is helpful here because it makes the separation between arrival, rules and induction easy to see.

The guard should record the vehicle movement and the access decision the system supports, not make unsupported claims about competence. If the authorised host confirms that an induction or work permit is valid, the local process can record or reference that confirmation in the approved system of record. Do not invent a free-text shortcut such as 'all paperwork OK' unless the organisation has defined what it means, who may use it and how it can be verified later.

Use referrals for exceptions, not informal favours

Contractor schedules change. A substitute driver arrives, a van registration was typed incorrectly, or an urgent engineer attends outside the normal access window. These are predictable exceptions, so the operating procedure should name the person or role who can decide each one. A guard should not be pressured to admit a vehicle because the driver says that somebody inside knows about the visit.

Priority Service allows a guard to refer a vehicle requiring approval to a supervisor, with distinct guard, supervisor and administrator roles. Use that workflow to preserve the division of responsibility: the guard captures and checks the registration, reviews available permit information and raises the exception; the authorised decision-maker approves or declines according to the site's rules. The published features do not claim to verify contractor competence, driving entitlement, insurance, induction or a permit to work, so those checks must remain in the customer's appropriate systems and procedures.

Write down the safe holding arrangement while approval is pending. It should not obstruct a public road, emergency access, pedestrian route or another gate lane. Define what happens if the named supervisor cannot be reached and whether the driver must leave and rebook. For higher-risk premises, specify which exceptions cannot be approved remotely. Consistency protects the guard as well as the site: the decision follows a rule rather than the driver's urgency or familiarity.

Close the visit and review the control

At departure, match the vehicle to its earlier IN event, confirm the registration and record OUT. If the vehicle uses another gate, the teams need a shared procedure so an entry is not left open simply because the movement crossed a shift or gate boundary. Priority Service records time-stamped IN and OUT events linked to the site, gate and guard, and authorised administrators can search vehicle history and export CSV reports. Those records support review, but they do not prove that every occupant has left; the site should not use a vehicle log as a complete people roll-call system.

Supervisors should sample contractor visits and ask operational questions: Was the vehicle expected? Did the guard use the correct permit and approval path? Were mismatches escalated? Did the driver receive current route instructions? Was OUT matched to the earlier entry? Are expired permits being reviewed? Look for repeated exceptions by contractor, sponsor, gate or time of day. The aim is to improve planning and controls, not to reward guards for admitting vehicles quickly.

Test the complete scenario before buying or rolling out software. Ask to see an approved contractor vehicle, an incorrect registration, a substitute vehicle requiring referral, a normal IN and OUT, and the later administrator search. Then map what remains outside the application: contractor selection, competence, induction, permits to work, traffic risk assessment and emergency roll call. Priority Service's current feature summary is at https://priorityservice.co.uk/#features, and the short simulated workflow is at https://priorityservice.co.uk/demo. Use the demo enquiry at https://priorityservice.co.uk/#demo to request a walkthrough against your own contractor and gate procedure.

Vehicle logging for your operation

Explore the workflow, plans and demo options for your team.

• Construction sites

Explore gatehouse management software