PAT testing is one of those jobs that is easy to lose track of. Hundreds of items, different test frequencies, equipment that moves between rooms and sites, and a spreadsheet that was last updated by someone who has since left. Then an auditor, insurer or inspector asks for your records.
This guide covers what you actually need to record, how to decide test frequencies, and how to stop PAT testing from slipping through the cracks.
Is PAT testing a legal requirement?
There is no law that says every appliance must be PAT tested every year. What the law does require, under the Electricity at Work Regulations 1989, is that electrical equipment that could cause danger is maintained so it stays safe. Portable appliance testing, alongside regular visual checks, is the most common way organisations show they are meeting that duty.
HSE guidance takes a risk-based approach. How often you inspect and test depends on the type of equipment, how it is used and the environment it is used in. Most organisations follow the IET Code of Practice for In-service Inspection and Testing of Electrical Equipment to set sensible intervals.
What should your PAT records include?
Good records protect you if something goes wrong and make the next round of testing far quicker. For each item, record:
- A unique asset ID, ideally on a label on the item itself
- Description and location, such as “Kettle, 2nd floor kitchen, Building A”
- Equipment class and type, for example Class I or Class II, and whether it is portable, movable or fixed
- Date of the last visual inspection and test, with the result
- Who carried out the test
- The next due date, based on your risk assessment
- Any repairs, failures or withdrawals from use
How often should you test?
Frequencies vary by environment. Equipment on a construction site or in a busy workshop needs checking far more often than a monitor on an office desk. A typical approach is to:
- Carry out frequent user checks before use, especially for equipment that is moved around
- Do formal visual inspections at set intervals
- Combine inspection and testing at longer intervals, based on risk
Write your chosen intervals down, review them when something changes, and make sure the schedule is visible to whoever does the work.
Why spreadsheets let you down
A spreadsheet is fine for a handful of items. It struggles once you have hundreds of assets across several sites:
- Nobody gets reminded. Due dates sit in a column until someone remembers to filter it.
- Failures get lost. A failed test should trigger a repair or replacement job, but there is no link between the two.
- History disappears. When rows are overwritten, you lose the evidence you need for an audit or insurance claim.
- Assets move. Equipment changes rooms and sites, and the spreadsheet rarely keeps up.
A better way: link PAT testing to your helpdesk
The most reliable approach is to manage PAT testing in the same system you use for facilities requests and asset records. With a facilities helpdesk such as SiteHelpDesk-FM, you can:
- Hold every item as an asset record with its location, class and full test history
- Schedule planned preventative maintenance (PPM) so PAT testing jobs are created automatically when they fall due
- Raise a repair or replacement job straight from a failed test
- Track equipment as it is moved or loaned out
- Report on what is due, overdue and completed for any site, at any time
That turns PAT testing from an annual scramble into a routine that runs itself, with an audit trail ready whenever you need it.
Quick checklist
- Do you have a complete, labelled list of portable and movable equipment?
- Are your test intervals written down and based on risk?
- Will someone be reminded automatically when testing is due?
- Do failed tests automatically lead to a repair or withdrawal?
- Could you show an inspector the full history of any item today?
If you answered no to any of these, take a look at SiteHelpDesk for facilities and estates teams, or book a demo and we’ll show you how it works.