What We Check Before an Engineer Ever Reaches Your Site

Nobody photographs the verification pack. It doesn't make a good site photo, and it doesn't show up in a case study next to a rack of neatly dressed fibre. But it's the part of the job that decides whether your programme runs or whether your first morning is spent explaining to a site manager why the engineer at the gate can't come in. Here's what happens before anyone's name goes on a deployment list.

What gets checked, every time

Before an engineer is on our register — let alone booked onto your site — five things get verified. Not glanced at. Verified.

• Right to work — current status, checked against the actual document, not “was fine last time we looked.”
• ECS or CSCS card — valid, in date, matching the trade being booked.
• Trade-specific certification — fibre, MEP, electrical, whatever the scope actually requires. A cabling cert doesn't clear someone for MEP work, and we don't pretend it does.
• A reference from comparable work — not a LinkedIn recommendation, a conversation.
• A1 certificates for anyone deploying into the EU — sorted before travel, not chased after a border query.

Document-checked is not reference-checked

A lot of workforce suppliers stop at the document scan. The card's valid, the box is ticked, the engineer goes on the list. That tells you the paperwork is real. It tells you nothing about whether the person can actually do the work in front of them.

Our references get checked by someone who knows what the answer should sound like — an engineer talking to a previous site contact about a specific scope, not an admin ticking a box that a phone call happened. “He was fine” and “he terminated 200 Cat6A points to spec and re-tested two marginal links without being asked” are both technically positive references. Only one of them means anything.

A spreadsheet of names with valid cards is not a vetted register. A vetted register is one where every card has been checked twice: once for the document, once for the work behind it.

Why this is slower — and why that's the point

Verifying properly takes longer than trusting a document at face value. That's a trade we make on purpose. The alternative is finding out on day one, at the gate, that an engineer's right-to-work status lapsed three weeks ago, or that a “fibre engineer” has never actually spliced anything smaller than a patch lead. Both of those cost you more than the extra day it takes us to check properly — they cost you the programme day, plus the scramble to find a replacement, plus the client conversation about why the crew that turned up couldn't start.

Kept current, not checked once

Documents expire. ECS cards lapse, certifications need renewing, right-to-work status changes. A verification that was accurate six months ago isn't automatically accurate today, and a site security desk that catches an expired card on morning one doesn't care that it was valid when someone last looked.

• Compliance records are reviewed on a schedule, not only when a new deployment comes up.
• Anyone with a certification approaching expiry gets flagged before it lapses, not after a site rejects them at induction.
• Cross-border paperwork — A1 certificates, right-to-work equivalents — gets sorted for the specific country of deployment, because “compliant in the UK” and “compliant to work in Germany” are not the same statement.

A compliance gap discovered mid-programme isn't an admin problem. On a critical site it's a shutdown risk, and shutdown risk is not something you fix with an apology email.

What this buys you

When we tell you an engineer is booked, that engineer has already cleared right to work, holds the correct card for the trade, has the certification the scope demands, and has a reference that was checked by someone who'd actually notice if the answer was vague. None of that is visible on site. All of it is the reason the person standing on site doesn't get turned away at the gate, doesn't get pulled off a live rack for working outside their ticket, and doesn't need replacing in week two.

It's slower for us and faster for you. That's the trade we chose.

This started as a LinkedIn post — follow Hristiyan Dimitrov on LinkedIn for the daily version. Tell us the trade, headcount, site, and timeline and we'll tell you exactly what gets checked before your crew arrives.