The Records Test: Could Developers Prove It Tomorrow?
LNG Canada's first cargo made one thing clear in 2025: getting capital projects approved is no longer the bottleneck. Delivering them — and being able to show your work — is.
This matters because the cost of a lost record is rarely the record. It's the six weeks, the redone work, and the credibility you spend reconstructing something you already had.
Make ready your resting state
For developers, the trouble starts when the record of the work and the work itself drift apart. Approvals live in inboxes, contracts live on someone's drive, and the field never sees either.
Look closer at any developers and the same fault line appears: the people doing the work and the people who must answer for it are reading from different copies. One has the latest drawing; the other has last month's.
It helps to name the real adversary, because it is not incompetence. For developers, the adversary is entropy — the natural tendency of a busy project to scatter its own evidence across people, tools, and time until no single place holds the whole truth. Every reorganization, every staff change, every 'we'll clean it up later' feeds it. LNG Canada's first cargo did not create this problem, but it raised the cost of it, because more scrutiny means more moments when scattered evidence has to be pulled back together at speed. Structure is the only thing that reliably beats entropy.
These are the records that go missing first:
An approval sitting in one person's inbox, with no backup and no clock anyone else can see
A contract on a personal drive that the field crew never opens
A change order buried in an email thread
A verbal 'go ahead' that left no trace
The decision wasn't wrong — it was invisible
Here is what belongs in one place, with a name and a date on every item:
Procurement justification. Why this vendor, this price, this process — documented at the time, not rationalized after.
Meeting minutes and direction. Especially anything that changed scope, schedule, or budget.
Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.
Closeout and retention. What was delivered, who signed for it, and proof you kept what you must keep.
The contract and its change orders. The original plus every amendment, in order, with nothing living only in an email thread.
You don't solve this with another reminder or another folder. You solve it by making the record a by-product of doing the work, not a second job.
XNM-VISION closes that gap for developers. Every decision, document, and dollar lives in one place, captured as the work happens, so 'audit-ready' is your resting state rather than a sprint.
Crucially, XNM-VISION doesn't ask developers to change how they work. It sits on top of the sources you already have, turning scattered effort into one auditable trail without a migration project.
The lesson repeats across every sector. You don't survive scrutiny by preparing for it. You survive by never being in a position that needs preparing.
What changes when the record catches up to the work
There's a small operational shift hiding inside every well-run capital program: the record stops being a thing you produce after the fact and becomes a thing that exists at the moment the decision is made. That sounds like a minor distinction. It is not. It is the difference between an audit that takes two days and an audit that swallows two weeks, and between a successor team that inherits clarity versus one that inherits a forensics project.
Picture a generic scenario familiar to anyone running a multi-site program. A scope change is agreed in a corridor on a Tuesday. The cost is small, the rationale is sound, and everyone shakes hands. Six months later, an internal review asks who authorised the variation and on what basis. The answer exists in someone's memory, in a deleted thread, and in two non-identical email forwards. Nothing was hidden. Nothing was malicious. The record simply never caught up to the work, and now it has to be reconstructed at three times the cost of having captured it in the first place.
The fix is not more discipline. The fix is removing the friction between doing and recording, so the two happen as one motion.
Practical steps to close the gap this quarter
Pick one project as your pilot. Not the easiest, not the hardest. The one whose paperwork would embarrass you most if it surfaced unannounced.
Inventory the artifacts that already exist. You almost certainly have more than you think; the problem is reachability, not absence.
Define the resting state in one page. What lives where, who can see it, and what 'current' means for each artifact type.
Move new decisions through the resting state first. If it isn't captured there, it didn't happen. The cultural shift sticks faster than people expect.
Run a dry-audit at 60 days. Ask a stranger to find five things in ten minutes. If they can, you have a system. If they can't, you have a folder.
None of this requires a new philosophy of work. It requires acknowledging a quiet truth: in 2025, the constraint on capital delivery is not money, and it is not ambition. It is the ability to prove, in a calm voice, what was decided and why. Teams that organise around that proof spend less time defending themselves and more time building.
Why this matters now
Funders, boards, and oversight bodies are getting faster, and the cycle time of their questions is shrinking. What used to be an annual conversation is now a quarterly one; what used to be a quarterly one is now a phone call on a Thursday afternoon. The teams that thrive in this environment are not the ones with the biggest binders. They are the ones who can pull a single page in under a minute and stand behind every line on it.
This is also where the XNM-VISION records engine quietly earns its keep: it does not ask teams to remember to file things; it captures the artifact, the version, and the reason at the moment of the decision, so the resting state is always one step ahead of the next question.
Want to see what one source of truth looks like for your projects? Talk to us — it's a short conversation.
