If you manage multiple locations (or deliver FM services across a client’s estate), PAT testing becomes less about “doing tests” and more about repeatable delivery: the same standard, the same reporting fields, and the same exception process at every site.
This article shares a practical playbook you can use to run a clean multi-site programme — and it’s also exactly what we build into our subcontract delivery approach: Subcontract PAT testing.
A robust programme usually has five components:
Decide the reporting standard once, then apply it everywhere. The goal is for your client to audit the estate without reconciling across different formats.
| Field | Why it matters | Tip |
|---|---|---|
| Unique Asset ID | Prevents duplicates; enables re-test tracking | Use a consistent ID prefix per client or per site |
| Site name + site code | Ensures correct aggregation across the estate | Match the client’s existing naming system |
| Location (area/room) | Speeds up finding items and resolving fails | Keep it practical: “Bar”, “Kitchen pass”, “Store 1” |
| Appliance description | Helps non-technical teams identify assets | Use consistent terms (“kettle”, “extension lead”, “POS screen”) |
| Make/model/serial (if available) | Improves traceability and replacement control | Not all assets have serials; don’t block delivery |
| Class (I / II) | Ensures correct test method and interpretation | Useful for audit defensibility |
| Test date + result | Core compliance evidence | Include pass/fail and a simple result code set |
| Fault / action required | Creates a clear exception list | Separate “minor fix” from “remove from service” |
Site access and readiness cause the biggest delays. Use this checklist before you schedule:
| Area | What to confirm | Owner |
|---|---|---|
| Contacts | Named site contact + deputy, phone number, arrival instructions | Client / FM |
| Access | Keys, security, sign-in process, inductions, permits | Client / FM |
| Operating hours | Quiet windows, shift patterns, peak trading times | Site |
| High-risk zones | Where portable items are stored, and how to access locked areas | Site / H&S |
| Asset availability | Parking permits, loading bays, and time restrictions | Site |
| Parking/loading | Parking permits, loading bays, time restrictions | Site |
A reliable approach for estates is to group sites into waves by:
“Fails” and “cannot access” items will happen. The key is to treat exceptions as a managed workflow.
| Exception type | Immediate action | Next step | Close-out evidence |
|---|---|---|---|
| Fail – unsafe | Label and remove/quarantine (per site process) | Repair/replace authorised by client | Re-test result recorded against same Asset ID |
| Fail – minor issue | Record “no access” with the location | Minor remedial agreed and completed (where permitted) | Updated register notes + re-test where applicable |
| Cannot access item/room | Reschedule with the access owner | Re-test result recorded against the same Asset ID | Revisit logged and completed test entry |
| Item not found | Mark as “not located” | Site to confirm if removed/disposed/relocated | Register updated (removed or reallocated) |
All In One Pro PAT Testing supports multi-site and subcontract delivery across Bournemouth and a wide surrounding radius (approximately two hours), including Poole, Christchurch, Southampton, Salisbury, Winchester, Dorchester, Weymouth, Yeovil, Blandford, Basingstoke and Portsmouth.
If you’re tendering and need delivery support, start here: https://allinonepropat.co.uk/subcontract-pat-testing/
Agree on the asset register fields and naming conventions before delivery starts. Without that, you end up with reports that can’t be compared across sites.
Plan by operational windows (before opening, after service, shift overlaps), and group areas logically (front-of-house first, then back-of-house).
Use a defined quarantine/removal process, an authorisation route for repair/replacement, and a re-test record against the same asset ID so the audit trail is clear.