A Closed Permit Is Not a Finished Job
A permit records permission. It has never once recorded work — and everything downstream reads the one as the other.
No, I can see the permit. I know it says closed. I am asking if the job was actually done.
That call happens on every plant.
01What the permit did not see
The crew ran out of time. The pump went back and the permit closed. The work itself never happened.
Nothing about that is dishonest. Closing a permit is the correct end of a permit: the isolation comes off, the area is handed back, the authorisation ends. It is doing exactly the job it was designed to do.
What it was never designed to do is say whether the job got finished. So the shift ends with everyone on the floor knowing the pump is not done — and nobody downstream able to see it.
Everyone on shift knows. Nobody downstream can see it.
02Two honest reports that disagree
By morning there are two reports, and they contradict each other.
The supervisor writes maintenance ongoing, because he watched the crew leave with the job half-done. The manager writes permit closed, because that is what the register says and the register is not wrong.
Same pump. Same day. Nobody lied.
That is worth sitting with, because the instinct is to look for who got it wrong, and there is nobody. Two people read two accurate records and drew opposite conclusions, and the disagreement will now be resolved by whoever is more senior or more available — not by whoever was closer to the work.
03One misreading, met four times
A permit records permission. It never records the work. Everything downstream treats the one as the other.
You can see the asymmetry in how the two are handled. The permit gets a number, a register, an audit trail and a retention period. The work gets a verbal confirmation and a signature closing the document that authorised it.
So you chase answers, you argue records, and you redo finished work. Rework nobody expected. A handover that reads finished when it is not. An audit that passes on paper. A contractor cleared but never competent for that particular job.
It looks like four problems. Most plants fund four fixes, and each one is defensible on its own. It is one problem, met four times — and a fix that leaves the misreading in place buys you the same problem again under a new name.
04Eighty-six
You might think the answer here is more AI. In June 2026 an AI lab and a global IT firm announced their fix: tens of thousands of certified engineers, trained and embedded inside plants like this one, in sectors including manufacturing.
Six weeks later, that firm's chief executive told analysts they had certified eighty-six.
The certificate takes ninety days. Knowing your plant takes years.
That is not a criticism of the eighty-six, and it is not really about either company. It is the same category error at a larger scale: a certificate records that somebody is permitted to be sent in. It says nothing about what they can do once they are standing in your unit. A plant hiring on the certificate is making exactly the mistake the permit makes.
The map was always on the floor.
05Capture, not reporting
If that is your operation, the problem is capture, not reporting.
It is a tempting mistake to make, because the symptom always shows up at the reporting end — two reports disagreeing, an audit that cannot be reconciled, a number nobody trusts. So the fix gets aimed there: a better form, a stricter review, another column.
But every one of those reports is downstream of a record that was never made. No amount of formatting recovers a fact nobody wrote down while the pump was still open. The crew knew. The moment passed. Everything after that is reconstruction.
Capture the work as it happens — not the permission to start it — and the two reports stop disagreeing, because they are finally reading the same thing.
Take one closed permit from last week. Find the record that proves the work happened — not the one that proves it was allowed. If there is not one, you have found the gap. Then ask the harder version: how many of your reports measure permission, and call it work?
Sources: Anthropic, announcement of the DXC alliance, 11 June 2026. DXC chief executive, Q1 FY2027 earnings call, 31 July 2026. Anthropic Partner Academy 90-day certification, per the 11 June announcement.
The permit says closed. The question is whether the job was actually done, and the permit cannot answer it. Issue and close are both recorded. The work between them left no record of itself. Two accurate reports, two opposite conclusions, and nobody was wrong. Four problems get four budgets. They are one misreading, funded four times. Tens of thousands announced, eighty-six certified. A certificate is a permit, not a skill. Reports are downstream of a record nobody made. Capture where the work happens, not where it is reported.
Get the next piece.
Get the free field guide — The Handover Gap: three disasters, one lesson, and a checklist for your next shift. Plus the occasional piece worth your shift. No noise, no pitch.
Run a shift somewhere? I compare notes with operators and supervisors on how real floors handle handover and capture — what works, what quietly doesn't. No pitch; I'm not selling anything. Tell me how yours does it: [email protected]