Changing gate-security contractors: a vehicle-record handover plan for UK sites

The gate can change hands before the records are ready

A new security contractor may arrive with trained guards and a working phone, yet still inherit an incomplete gate operation. Current permits may sit in the outgoing company's account. Yesterday's arrivals may have no recorded departure. A client may need an older vehicle photograph after the outgoing team's access has ended. Treat the record handover as a separate workstream, not an incidental part of handing over keys.

This guide addresses a specific question: how should a UK site preserve the vehicle information it legitimately needs when a guarding contract or gate-software arrangement changes? The same method applies when an organisation takes its gate operation in-house. It is an operational planning framework, not a determination of the parties' legal roles or a substitute for advice on a disputed contract.

Priority Service advertises vehicle photographs, checked registrations, time-stamped IN and OUT movements, permits, supervisor referrals, searchable history and administrator CSV reports. Those are useful starting points. They do not establish that a complete account can be transferred, that photographs are included in an export, or that another supplier can import the file. Resolve those questions before the final shift.

Name the decision-maker for each record set

Start by separating the premises operator, outgoing security company, incoming security company and software provider. Identify who decides why each record is collected, who may see it and how long it is needed. The organisation paying the software bill is not automatically the controller for every record. Vehicle history, guard employment records and a contractor's own incident records may involve different decisions.

The ICO's controller-and-processor guidance says roles depend on the particular processing activity and who determines its purposes and means. A contractor following a client's instructions may be a processor for that activity; it may be a controller for another activity with its own purpose. Record the assessment rather than assigning one label to the whole commercial relationship.

Use that assessment to name the person authorised to instruct the handover, approve recipients and decide disputed items. Where a controller uses a processor, the ICO says a written contract or other binding legal act is required. Check the relevant processing agreement as well as the guarding contract. An instruction from an incoming supervisor should not replace approval from the organisation entitled to give it.

Agree an exit specification, not just an export promise

Describe the actual handover package: relevant site history, current permits, unresolved approval requests, supporting photographs where needed, and an explanation of the fields supplied. Separate what must continue at the gate from what will remain in a controlled historical archive. Specify the date range, delivery deadline, authorised recipient, format, support contact and any agreed charges.

The ICO's contracts checklist includes end-of-contract terms requiring a processor to delete or return personal data at the controller's choice and delete existing copies unless the law requires storage. Agree how that will be performed and evidenced, including subcontracted storage and backups. Do not infer an immediate technical deletion capability from a general contractual obligation.

Also distinguish this arrangement from an individual's right to data portability. The ICO describes that right as applying to an individual's provided personal data under specified conditions, including automated processing based on consent or contract. It is not a general right for a business buyer to demand an entire gate database. Obtain clear commercial exit terms and appropriate data-processing instructions instead.

Test whether the exported record remains understandable

Run a rehearsal while the outgoing team still has access. Use a small authorised sample, preferably fictional test data for the first format check. Include a completed visit, a missing departure, an overnight visit, a corrected registration and a movement at a second gate if relevant. Compare the resulting file with the records visible in the system.

Check registration formatting, site and gate identifiers, IN/OUT relationships and whether each timestamp includes a timezone or has a documented interpretation. Spreadsheet software can reinterpret dates or identifiers, so preserve the original export and inspect a working copy. Count the expected sample records and investigate omissions or duplicates. A readable CSV is not proof of a complete migration.

Ask separately how photographs are supplied and linked to visits, whether links remain usable after account closure, and which permit or approval information is absent. Record limitations explicitly. The ICO's accuracy guidance requires reasonable accuracy checks and clarity about the source and status of personal data. An unexplained historical record should not become a newly confirmed event merely because it appears in another system.

Transfer only the information needed by the recipient

The incoming guarding team may need current vehicle permissions and unresolved arrivals, while the client's authorised manager needs access to historical records for enquiries. Those are different purposes. Do not send the contractor an entire portfolio export containing other clients' sites because that is the easiest file to produce.

The ICO's data-minimisation guidance says personal data must be sufficient, relevant and limited to what is necessary for the stated purpose. Apply that test to photographs, free-text notes, staff details and historical visits as well as registrations. Decide whether some records should remain available only to the client rather than being copied into the incoming contractor's operational account.

If information is being shared between controllers, use the ICO's data-sharing checklist to assess justification, lawful basis, transparency, recipients and safeguards. Processing under a controller's instructions needs the appropriate processor arrangements instead. In either case, agree who handles later correction or access requests. Changing contractors must not leave individuals' enquiries bouncing between organisations with no named owner.

Protect the package and close access deliberately

Choose an approved transfer method with access restricted to named recipients. Verify the destination through an established contact, not just the address in a last-minute email. Avoid personal email accounts, public download links or broad messaging groups. Confirm receipt and readability without circulating a second copy of the entire register.

The ICO's security guidance calls for technical and organisational measures appropriate to the risk, including suitable access and device controls. Translate that into a handover checklist: who can create the package, where it is stored, who can download it, and when temporary access ends. The exported file needs protection even though it is no longer inside the original portal.

Plan removal of outgoing access at the agreed boundary, with any approved support period narrowly scoped. Review administrators, guards, supervisor accounts, active sessions, shared credentials and locally held exports through the relevant systems' supported controls. Ask each provider to demonstrate revocation behaviour; do not assume that disabling an account instantly closes every session. Record who completed the checks and any unresolved exceptions.

Manage the changeover as a live operational boundary

Choose an exact cutover time and identify which process records movements either side of it. A vehicle may enter under the old arrangement and leave under the new one. Agree how guards will find its arrival and record the departure without inventing a second arrival or silently closing the old visit.

Consider an illustrative warehouse changeover at 07:00. A delivery vehicle entered at 06:40 and is still unloading. An unexpected contractor awaits supervisor approval. The incoming team needs those live exceptions and the person authorised to decide them, not simply a historical CSV. Reconcile the outstanding work before declaring the handover complete.

Have the incoming supervisor confirm that permits have been reviewed against current instructions, unresolved movements are understood and the gate can operate without the outgoing login. Keep any approved overlap controlled and avoid double-recording. Priority Service's public descriptions do not promise cross-organisation account migration, bulk imports or automatic reconciliation, so treat those capabilities as questions to resolve, not assumptions in your changeover plan.

Accept the handover, then manage the remaining copies

Sign off distinct outcomes: live gate work can continue; required historical records are retrievable; the authorised recipient has accepted the package; old access has been checked; and return or deletion actions have an agreed completion process. Keep a concise record of the tests, field limitations, responsible people and outstanding items.

The ICO's storage-limitation guidance says personal data should not be kept longer than needed and retention must be justifiable. Moving records to a new archive does not by itself justify restarting their retention period. Identify any narrowly justified incident or legal-claim exceptions, with appropriate advice where necessary, and account for working copies and exports as well as the principal archive.

Before choosing software, bring this handover scenario to a demonstration. Review Priority Service's published capabilities at https://priorityservice.co.uk/#features and watch the simulated workflow at https://priorityservice.co.uk/demo. Request a live demonstration at https://priorityservice.co.uk/#demo and ask to see the report fields, photograph retrieval and access-removal process relevant to your contract. Sources were checked on 14 October 2026; the ICO flags several pages as under review following the Data (Use and Access) Act. Recheck applicable guidance when finalising your agreement.

Vehicle logging for your operation

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

Explore gatehouse management software