PAT testing guides

PAT record-keeping guide

PAT certificates and test records: what to include

A useful PAT record tells the next competent person what was examined, what was measured, what happened and where the item was. It does not need to pretend there is one statutory certificate layout.

Last reviewed: · HSE sources checked:

What “PAT” covers

Portable appliance testing is common shorthand for checking the safety of in-service electrical equipment. The right approach may include user checks, a formal visual inspection and electrical tests. HSE notes that some faults are visible and some can only be found by testing, so a reading on its own is not a complete account of the examination.

Useful fields for a certificate or test record

The fields should help identify the job and item, reconstruct the competent person’s decision and make any required action obvious. Useful groups include:

Not every field or electrical test applies to every item. Equipment construction, environment, use and previous results all matter. The competent person should choose and interpret the checks, rather than treating a template as a test procedure.

Example record layout

Illustrative only. This is not a statutory form, test procedure or statement that the example item is safe. Replace the placeholders with the checks and measurements selected by a competent person.

Certificate header

Client and site
[Example client] · [Example site and address]
Tester
[Name] · [Relevant details]
Job date
[DD Month YYYY]
Scope or limits
[Areas covered, excluded or unavailable]

Asset register extract

AssetItem and locationChecks and readingsResult and action
EXAMPLE-001 [Description]
[Location]
[Visual outcome]
[Test, value and unit]
[Result]
[Action or follow-up]
EXAMPLE-002 [Description]
[Location]
[Visual outcome]
[Test, value and unit]
[Result]
[Action or follow-up]

Printing this page produces a clean copy of the example layout. Keep the full original record, including notes and limitations, rather than relying on a summary row alone.

Make failed items difficult to miss

A failed result should remain understandable without colour. Use a written result, the defect or reading that led to it, and the immediate action taken. If an item was removed from service, isolated, repaired or referred to someone else, say so. A certificate that buries a failed row among passes is hard to act on.

Do not turn the next date into a universal rule

HSE guidance puts the retest decision with the duty-holder, informed by risk. Equipment type, construction, working environment, frequency of use, user behaviour and earlier fault rates can all change the interval. HSG107 says suggested starting intervals are not legal requirements and should be reviewed against experience.

Keep records usable outside the software

Before relying on any record system, export a real job and open the result elsewhere. A PDF is useful for a fixed, human-readable certificate. A structured export such as CSV is useful for sorting, checking and moving rows. A complete backup serves a different purpose: restoring the working data, relationships and attachments after loss or replacement.

Store copies in a location the responsible organisation controls, use clear filenames and retain the context that links each item to its site, test session and result.

How the iPhone app handles the documents

The app being prepared for release records client, site, item, visual-check and measurement details, then creates a light-background certificate PDF and a site asset-register PDF. It also exports records as CSV and a restorable backup file.

It works without an account or signal. The first three certificates use the full workflow; one optional payment unlocks further new certificates. Records already created remain available to read, search, share and export.

Sources

Source check completed . Guidance can change; check the source pages when making a current decision.