PAT Testing Without the Downtime: How to Prepare Your Site

Most of the frustration people report about testing visits has nothing to do with testing. It's the engineer waiting for a key. It's the meeting room that couldn't be entered. It's the second visit needed for the eleven items nobody knew about. All of that is preventable, and most of it is preventable by you rather than by us.

What you're actually paying for

Worth understanding before the rest makes sense: the cost and disruption of a visit are strongly influenced by the engineer's time on site, even where the quotation is fixed or priced per item. The test itself takes seconds to a couple of minutes per item. Everything else, the waiting, the walking, the hunting for equipment, the negotiating with the person who needs their laptop for the next hour, is time too. Which is why two premises with identical item counts can differ by half a day.

So preparation isn't a favour to your contractor. It's the lever on your own invoice and your own disruption.

The five things that make the difference

Know what you've got, roughly. An approximate count by area beats an exact count of nothing. It lets us schedule properly and quote accurately, and it means the storeroom on the second floor doesn't get discovered at four o'clock.

Sort out access before the day. Keys, codes, locked cupboards, the cabinet only one person can open, and crucially that person's shift pattern. Access is the single biggest cause of overrun in our experience.

Make equipment reachable. Anything under a desk behind a wall of cables takes several times longer than something you can get to. Clear a route where you can.

Tell your staff it's happening. A one-line email the day before removes almost all the friction. People save their work, expect a brief interruption, and don't treat the engineer as an intruder.

Name one point of contact. Someone who knows the building and can make decisions. Not necessarily senior; the facilities or site person is usually ideal.

Sequencing beats speed

If parts of your premises can't be interrupted at particular times, say so in advance rather than on the day. A kitchen tested before service, a meeting room done between bookings, a shop floor handled early: all easy to plan, all disruptive to improvise. We'd much rather work to your rhythm than push through it.

The bit we'll own

A fair share of the disruption people describe is our industry's fault, not the client's: engineers who don't explain what they're doing, who unplug things without asking, who leave equipment plugged into the wrong sockets, or who hand over a list of failures with no explanation. If you've had a visit like that, it wasn't inevitable.

What you should expect is an engineer who introduces themselves, works to an agreed order, puts everything back where it was, and walks you through the failures before leaving rather than emailing them a week later.

Prepare well and most workplaces experience testing as a few minutes of interruption per person. Our PAT testing page covers how visits run, and our guide to how long testing takes gives realistic timings.

Get in touch

Want a visit planned properly rather than squeezed in? Get in touch and we'll work out the sequence with you first.