Why we certify a system before we agree to cover it

Every service plan in this industry is, underneath the brochure language, a promise about time. We will be there inside so many hours. We will have it working by such and such. That is the product. The gear is somebody else's; the response is ours.

Which is why we will not sell one on a system we have never seen.

It sounds like caution. It is really just arithmetic. A twenty-four-hour response promise on a house whose rack we have never opened is not a promise, it is a guess with a subscription attached. We would be quoting a number we have no way to stand behind, and the first time we failed to hit it the client would be entirely right to be angry.

What certification actually is

Half a day to a day on site, depending on the house. Nobody is selling anything during it. The work is dull and it is the most valuable thing we do.

• Every device, found and written down. Make, model, firmware, where it physically is, what it is plugged into, and what it depends on. Houses accumulate. There is almost always something in a cupboard that nobody remembers buying.
• Labels at both ends. If a cable is not labeled it does not really exist — it is a thing you will one day spend two hours tracing at an hourly rate.
• Photographs, filed against the plan. Rack front and back, every device location, every wall plate. Five years from now this is what turns a two-hour diagnostic into a ten-minute one.
• Every path tested, not just the obvious ones. Not “does the television turn on” but does every source reach every zone, does every keypad button do what its engraving says, does the shade group actually stop where it is supposed to stop.
• The network, properly. Signal survey rather than a bar count. Switch port map. Where the DHCP scope ends and how much of it is already gone.
• Credentials, in one place. Who owns the account. Where the passwords live. What happens if the person who set it up is unreachable — which, for a startling number of houses, is the actual answer today.

What we usually find

Rarely a catastrophe. Almost always three or four small things that were going to become a Saturday evening phone call eventually.

An ISP router doing the work of a commercial network. One access point trying to cover a footprint it was never going to cover, in a house with spray foam and stone. Firmware two or three years behind on a processor that has since had a security fix. A subwoofer wired out of phase since the day it went in, which nobody flagged because nobody had heard it any other way. A camera recorder with a full disk that stopped retaining footage months ago and never said so.

None of these announce themselves. They wait.

Sometimes the answer is no

This is the part that costs us money and we do it anyway.

Occasionally certification ends with us saying that we cannot cover the system as it stands — not until a specific thing is put right. Usually it is the network. Sometimes it is a piece of equipment so far out of support that no response time we quote would be honest, because the fix might simply not exist any more.

We would rather have that conversation on day one than take a monthly fee for a promise we privately know we cannot keep. A service plan that quietly excludes the things most likely to break is not a service plan. It is a subscription.

What the client is left holding

Here is the part people do not expect. Even a client who never once uses their response time gets something durable out of the visit: a document. What is in the house, where it is, what it is connected to, who owns the accounts, and photographs of all of it.

That document outlives us. If this house sells, it goes to the next owner and their system does not become a mystery. If they ever choose to work with someone else, they can hand it over and that firm can be useful on day one instead of billing three hours to work out what they are looking at.

We are aware that is an odd thing to build into your own service product. It is also the clearest way we know to say that the plan is about the house rather than about locking anyone in.

Then, and only then, the response time

Once we know the system, the promise stops being a guess. We know which failures are likely, which are remotely fixable, which need a van, and which need a part that takes a week to arrive — so we can tell you honestly what we will do and how quickly, and then actually do it.

That is the whole reason certification comes first. Not diligence for its own sake. It is the only way the number on the plan means anything at all.