The same engineer code on every panel you have ever fitted

There is a code most installers can type without thinking. It goes into every panel, on every job, and it has done for years. Everyone in the company knows it. So do several people who left four years ago.

Nobody decided this. It happened because it was easier, and because nothing has gone wrong yet.

Why it happens

It is not laziness. It is a rational answer to a real problem.

An engineer gets sent to a site they have never seen, to fault-find a system somebody else commissioned, and they need to be in the panel now. If every site has its own code, and those codes live in a spreadsheet on the office PC, then at eight on a Sunday evening that engineer is stood outside a locked cabinet with nobody answering the phone.

So the company standardises. One code, everyone knows it, nobody is ever stuck.

The same logic produces the shared controller login, the camera password used across an entire estate, and the licence key pasted into the group chat for the third time this year. Every one of those solved a genuine operational problem.

The trouble is what they add up to.

What it actually exposes

Every leaver keeps the keys to your whole portfolio. Not one site. All of them. Someone resigns on Friday and retains access to every system your company maintains, with no realistic way to change it short of revisiting every building.

One leak is a total leak. A photo of a notepad. A subcontractor given the code once. A client’s own staff. It only has to escape from a single site to be live across all of them.

You cannot answer the question when it is asked. A client asks who can get into their fire panel. The honest answer is “roughly forty people, some of whom no longer work here, and I cannot give you a list.” That is the answer that loses the maintenance contract.

It quietly undermines the handover you just did. You have certified the system, produced the O and M pack, and handed over a building whose engineer access is shared with two hundred other premises. The paperwork says one thing. Reality says another.

Your insurer and your certification body have a view. Both increasingly ask how access credentials are controlled. “The same one everywhere” is a poor position to be in after an incident.

The bit nobody mentions

There is a second-order problem, and it is worse.

When the company code is universal, changing a factory default on a new panel creates friction — the code no longer matches what everyone expects. So the default stays. On equipment whose default is printed in a manual that anyone can download.

This is more common than the industry admits, and it is the easiest thing on this page to fix.

What good actually looks like

Not perfection. Four habits.

Unique per site. Every premises gets its own. Not per client, not per contract. Per site.

Recorded somewhere retrievable. This is the one that makes the others possible.

Rotated at handover. The commissioning code and the maintenance code should not be the same one. When you hand over, change it. The client’s building should not still be open to whoever pulled the cable.

Revoked when someone leaves. Only realistic if credentials sit against sites and people rather than in everyone’s head.

The thing that actually decides it

Not policy. Retrieval speed.

Any system where getting a code takes longer than remembering one will be abandoned inside a month. That is why spreadsheets fail, why the group chat wins, and why “we have a policy” is usually a sentence rather than a practice.

Solve retrieval and unique codes become easy. Ignore retrieval and no amount of policy will hold.

Where to start

Pick your worst site — the most sensitive system, or the client most likely to audit you. Give that one unique codes, put them somewhere your engineers can reach in under a minute, and run it for a fortnight.

If retrieval holds up, roll it forward. If it does not, you have learned something more useful than a policy document.

That is what the Graftix Vault is for. Credentials held against the project rather than in somebody’s phone, encrypted in your browser before they reach us, and shared with the engineers who need them. How the Vault works · Security at Graftix