Scout SuiteHow-to guide
PAT testing
One certificate, one visit, results against every appliance it covered, and a compliance count that actually reflects what's been tested, not just what's been bought.
Watch this on its own pageMark the appliances that need it
Not everything needs testing, a battery lantern doesn't, a hall kettle does. On the item, tick PAT testing required. Only equipment marked this way shows up anywhere in the PAT workflow or its compliance counts.
Record a visit
Equipment → PAT → Record PAT test. Choose the tester's certificate (PDF or a photo), or drag it onto the upload box, set the test date and who did it, then add each appliance the visit covered with its result: pass, fail, or advisory, and when it's next due. One certificate can cover as many appliances as it actually tested; each gets its own line.
Past records can't be edited, if something was entered wrong, upload a corrected certificate as a new session rather than editing the old one, so the paper trail matches what was actually tested.
Or record one while you're scanning it
Scan → PAT test jumps straight to recording a result for whatever you scan, skipping the dropdown hunt through every PAT-required appliance. It opens the same dialog, pre-filled with the exact unit: you still confirm the result, sticker code, and next-due date, and still attach the certificate.
ScanPAT testSee what's covered, due, or overdue
The PAT tab's compliance summary counts every appliance that needs testing as never tested, ok, due soon, overdue, or failed, based on the most recent result for that specific unit, not just whether the equipment line has ever had any test recorded. An appliance bought as one of several identical units is tracked individually, so three toasters don't all show as tested because one of them was.
Safety & HQ
More in this topic
Risk, incidents, GDPR, the building, and the kit in it.