MOT and vehicle-data checks at the gate: what UK site teams should verify

A vehicle lookup answers only part of the gate question

A contractor arrives in a van. The registration is readable, vehicle details appear on screen and the driver says the company visits every week. Does that establish that the vehicle should enter? No. Matching vehicle information, checking a test record and authorising today's visit are separate tasks. Treating them as one decision creates a weak point in an otherwise careful gate procedure.

This guide helps security companies and organisations running their own premises decide how vehicle-data checks should inform admission. It focuses on interpreting results and assigning decisions, rather than taking better number plate photographs. The procedure suggestions are practical recommendations to agree with the premises operator; the official sources below explain the underlying vehicle requirements.

Priority Service's current public description says number plate reading and manual registration entry are included. Available make, model and colour may be suggested from MOT data, subject to coverage, with an optional paid lookup for missing details where available. That description does not establish a complete roadworthiness, tax, insurance or driver-authorisation checking service. Specify each requirement separately when evaluating the system.

Keep identity, vehicle status and site permission separate

Write the gate instruction around three questions. First, does the recorded registration correspond to the vehicle in front of the guard? Second, has any vehicle-status check required by the client's policy been completed and interpreted correctly? Third, is this vehicle and visit authorised for this site, at this time, for this purpose? A satisfactory answer to one cannot supply a missing answer to another.

GOV.UK's MOT-history service describes test results, recorded mileage and the next test due date. Those are useful records about a vehicle. They do not identify the person driving it or establish that a delivery is expected. Likewise, a familiar make and colour do not establish that the contractor has permission to use a restricted entrance.

For each check, name its purpose, acceptable evidence, person responsible and escalation route. A security provider should agree these instructions with each client. An in-house team should agree them with the relevant site manager. Avoid leaving guards to decide which database fields matter while a queue forms.

Do not confuse no test history with an overdue test

GOV.UK says the usual first-MOT deadline is the third anniversary of registration, while some vehicle categories require testing at one year. It also directs users to different Northern Ireland rules. A blanket instruction to reject every vehicle without a previous pass therefore needs correcting before it reaches the gate team.

Distinguish a confirmed future first-test deadline from an expired certificate, an unresolved lookup and an asserted exemption. GOV.UK separately identifies exempt vehicle categories and annual testing for lorries, buses and trailers. Vehicle category and jurisdiction matter; the guard should not calculate a deadline from the appearance of the registration plate or assume every commercial vehicle follows a passenger-car rule.

Prepare a referral route for a new vehicle, specialist vehicle, overseas registration or unsupported result. Ask the designated person to verify the applicable position through an appropriate source. Until then, record the check as unresolved through the agreed process. Do not relabel missing information as either a pass or a failure to make the screen easier to clear.

A current MOT does not settle present safety

GOV.UK explicitly warns that a vehicle can be unsafe even with a current MOT certificate. Its test-result guidance also distinguishes dangerous, major, minor and advisory findings. A date on its own can omit relevant context, particularly if a subsequent test or an observed defect raises a concern.

HSE's safe-vehicles guidance requires employers to consider suitability, working conditions and the risks of using the equipment. In practical terms, a road-vehicle test record does not establish that a particular vehicle fits a site's route, overhead clearance, loading arrangement or task. Those assessments belong in the site's transport-management process.

Give guards a clear response to an obvious concern, such as a vehicle appearing damaged or carrying an unstable load. Use the site's safe stopping and referral arrangements and involve the competent person responsible. Do not ask an untrained guard to diagnose mechanical defects, climb onto a vehicle or perform an improvised inspection to compensate for a reassuring database result.

Tax and insurance require their own evidence

The GOV.UK tax-check service checks vehicle tax or SORN status using the registration. It says records can take up to two working days to update after an approved tax or SORN application. A disputed result therefore needs a defined verification route rather than an assumption that either the screen or the driver must be lying.

Motor insurance is a separate subject: GOV.UK states that insurance is required for driving on UK roads. Neither a current MOT nor populated make and model fields proves that the relevant insurance arrangements are in place. If the client requires insurance evidence, agree who obtains it, what is sufficient and how uncertainty is referred.

Use only checks and services the organisation is entitled to use, within their access conditions. Do not borrow another person's account or treat a public consumer checker as an unrestricted commercial integration. For private premises, obtain competent advice where the application of road-traffic rules is uncertain; a gate procedure should not improvise a legal conclusion about the access road.

Define how staff handle missing, old or conflicting results

Before rollout, ask the supplier to show what happens when a lookup returns nothing, the connection fails or a previously retrieved result is displayed. Establish whether the screen identifies the source and check time, whether information is cached, and which fields are actually returned. These are acceptance questions, not claims that Priority Service currently exposes all those details.

An unavailable service is an unavailable check. It does not establish an adverse vehicle status. Equally, a result retrieved yesterday should not silently be described as checked today. Agree whether a repeat check is required, who can authorise an alternative process and how the team records that decision without inventing a successful lookup.

If a returned description conflicts with the vehicle, recheck the registration and refer the discrepancy under the site's instructions. Record observations factually. A mismatch warrants investigation; it is not, by itself, proof of fraud. Keep the driver in the designated safe area while the authorised person resolves the question.

Rehearse a new-van arrival before it happens

Consider an illustrative contractor arriving in a recently registered van for an expected maintenance visit. Available vehicle details match, but there is no previous MOT pass. The guard confirms the registration, checks the visit against site instructions and asks the designated supervisor to resolve whether a first test is due. This is a training scenario, not a customer case study.

The supervisor verifies the applicable vehicle category and deadline using the agreed evidence. The receiving team separately confirms the contractor's appointment and any induction requirements. Admission follows the client's procedure once the required checks are resolved. The absence of an old test record is not turned into a failed test, and matching vehicle details are not turned into appointment approval.

Now change the example: the vehicle is unexpected, the lookup is unavailable, or a visible safety concern arises. Staff should know which decision changes, who takes it and what happens while they wait. HSE's workplace-transport checklist treats management, vehicle suitability, maintenance, movements and driver competence as distinct areas; use that breadth when testing the procedure.

Make the outcome understandable after the shift

Agree a concise record of any required check: the registration, the actual result or unresolved issue, when the check occurred, who reviewed it and the admission decision. Use supported fields and an approved supplementary process where necessary. Do not assume that a movement timestamp is also the timestamp of a separate provider check.

Keep test status, observed condition and supervisor permission distinguishable in later review. For example, 'first-test position verified by designated manager; visit approved' communicates more than 'vehicle OK'. Agree where that evidence belongs before expecting guards to create it. Priority Service advertises visit history and administrator CSV reporting, but buyers should verify the specific lookup and approval details available in those records.

Ask for a demonstration of the complete decision

Review the published features at https://priorityservice.co.uk/#features and the simulated vehicle workflow at https://priorityservice.co.uk/demo. Then request a live demonstration at https://priorityservice.co.uk/#demo using a new vehicle, an unavailable lookup and a visit requiring supervisor approval. Ask which checks are included, which need another service and which remain a site responsibility.

Agree the procedure with the people making and reviewing the decisions. The aim is a defensible record of what was checked and who authorised entry, without suggesting that one lookup proves everything. The official sources below were checked on 15 October 2026. Recheck the applicable vehicle and jurisdiction guidance when setting your policy.

Vehicle logging for your operation

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

Explore gatehouse management software