Why PAT testing records drift and what to do about it
Portable appliance testing is one of the most routine compliance activities in a business, and one of the easiest to let drift. The testing itself is straightforward. The problem is everything around it: knowing what equipment exists, when it was last tested, what failed, and what was done afterwards.
Most businesses do not set out to neglect PAT testing. They simply never build the register that would tell them what needs testing in the first place. The first year goes well. The second year, the test engineer tests what is in front of them. By the third year, nobody can say with confidence what is covered and what is not.
What solid PAT control looks like
PAT testing works best as a managed cycle rather than an annual event. The essentials are:
- a register of portable appliances, updated as equipment is added or removed
- a defined testing frequency based on environment and risk
- dated test results for each item
- clear action on failures, with evidence of repair or disposal
- ownership of the schedule and its follow-ups
The register is the foundation. Without it, every test is a partial snapshot rather than part of a controlled programme.
Why drift happens even in well-run businesses
Drift is rarely caused by laziness. It is caused by structure:
- new equipment arrives and is never added to the register
- staff bring personal items onto site that sit outside the programme
- testing frequencies are set once and never reviewed as usage changes
- records live with the contractor and never come back to the business
- failures are repaired informally, leaving no audit trail
Each of these is a small gap. Together they mean the business cannot answer the question that matters most: what equipment is in use, and what is its current test status?
The commercial cost of drift
PAT testing records rarely cause drama on their own. They become important in combination with everything else:
- during audits and risk assessments
- when insurers review electrical safety arrangements
- at property transactions and handovers
- when an incident involving electrical equipment is investigated
In every case, the business with a current register and clean records responds immediately. The business with scattered records discovers that reconstructing history is slower, more expensive, and less convincing than maintaining the records in the first place.
Building a cycle that survives
The fix is not more testing. It is better structure:
- one register, owned and kept current
- clear frequencies per area and equipment type
- contractor records returned and filed after every visit
- a simple process for adding and retiring equipment
- a calendar that makes overdue items visible
Once the structure exists, PAT testing becomes a small, predictable item in the compliance calendar instead of an annual reconstruction project.
The Northstead view
PAT testing is a useful indicator of how a business handles recurring obligations. It is low complexity and high frequency, which means the discipline it requires is the same discipline every other compliance area needs.
Businesses that keep the register current, the schedule visible, and the records centralised rarely struggle with PAT testing. Those that let it drift rarely notice until the records are needed. The difference is structure, not effort.