Anatomy of an Overrun: When Capital projects Outrun the Paperwork
When LNG Canada's first cargo dominated the headlines in 2025, joint ventures felt the pressure shift. The era of arguing for funding is giving way to a harder era of accounting for it.
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.
Funded is not the same as finished
Joint ventures rarely fail for lack of effort. They fail because the proof is scattered — a sign-off here, an invoice there, a change order in a thread no one can find under pressure.
It compounds over time. Every handoff between joint ventures and their partners is a chance for a version to fork, an approval to go unrecorded, or a commitment to survive only in someone's memory.
Step back and the pattern is almost mechanical. Money arrives, ambition rises, the project grows — and the volume of decisions grows with it, faster than any inbox or folder can keep straight. For joint ventures, the failure is rarely dramatic; it is a slow accumulation of small, unrecorded moments that only add up to a problem when someone with authority starts asking questions. LNG Canada's first cargo is making that someone show up sooner, and more often. The teams that feel calm about it are not working harder — they simply never let the record and the work drift apart in the first place.
The usual suspects, every time:
The decision record — who approved what, when, and on what basis
Invoices matched to the contract that authorized them
The procurement justification, documented at the time
Version history proving which drawing was current on a given day
The records that settle questions
If you keep nothing else in a single system, keep these:
Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.
Approvals and sign-offs. Every gate with a name and date attached, visible to everyone the decision touches.
The contract and its change orders. The original plus every amendment, in order, with nothing living only in an email thread.
Meeting minutes and direction. Especially anything that changed scope, schedule, or budget.
The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.
The fix isn't 'try harder.' It's to stop keeping the record separate from the work, so the proof accumulates on its own.
That is exactly what XNM-VISION is built to do. It keeps capital projects and the records that prove them in one auditable system — approvals, versions, contracts, and change orders, each with a name and a date attached.
What changes the result for joint ventures is not another database. It's that XNM-VISION captures the record as a by-product of the work, ingesting from the inboxes and folders you already use — so being ready costs no extra effort.
LNG Canada's first cargo raised the ceiling on what's possible. Whether joint ventures reach it comes down to something unglamorous: whether the proof was there all along.
The cost of a missing minute
Most teams already understand the work. What slips is the connective tissue: who approved which version, which line item that invoice maps to, which minute authorised the substitution, which letter sets the obligation. None of it is unknowable. All of it is scattered.
The hidden tax shows up in small ways first. A team member spends an afternoon reconstructing a sequence of approvals from email threads. A vendor resubmits a deliverable because nobody can confirm which version was current. A reviewer asks for one document and gets four, each slightly different, none clearly authoritative.
A directive that was issued verbally and never written down
A version of a drawing that was superseded but is still being quoted
A funder condition nobody mapped to a deliverable
An invoice whose scope reference points to an old line item
A risk that was flagged in minutes but never tracked to closure
The fix is not heroic. It is structural. When the record of the decision lives in the same place as the work product the decision authorised, the team stops re-litigating the past and gets back to running the present.
How XNM-VISION changes the daily routine
Plain language matters here. "Audit-ready" is not a special posture you adopt before a review. It is what the file looks like on an ordinary Wednesday when nothing in particular is happening.
Capture the decision where it happens. A note in the minute, a change in scope, an approval against a version — all in the file, not in someone's inbox.
Bind the document to the decision. The drawing, the invoice, the report sit alongside the approval that made them current.
Make the obligation visible. Every funder condition, regulatory commitment, and contractual deliverable has a named owner and a due date everyone can see.
Keep the trail walkable. A reviewer can move from question to answer in clicks, not interviews.
The shift is not from manual to automated. It is from scattered to single. One place, one current version, one trail that holds up when somebody asks.
What good looks like, in a single Wednesday
On the right Wednesday, the team is not preparing for anything in particular. They are doing the work. A change request comes in and is logged against the right line item. A deliverable is uploaded and the version is clear. A funder asks a question and the answer is two clicks away. That is the bar.
When the records stop hunting you, the work itself gets easier. Decisions get made faster because the context is right there. Reviews stop being events and start being checkpoints.
This is the gap XNM closes for capital teams. Learn how in our overview of XNM-VISION.
