After Bill C-5 and the new Major Projects Office: The Question Audit teams Should Be Asking
Through 2025, audit teams watched Bill C-5 and the new Major Projects Office move money and attention toward big builds. The capital is the easy part. The hard part shows up later, in whether you can prove what you decided and when.
The quiet truth is that most overruns aren't decisions gone wrong. They're decisions that went fine but couldn't be proven, defended, or found in time.
Where the proof goes to hide
For audit teams, 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.
The cost isn't only the missing document. It's the meeting to look for it, the second meeting to recreate it, and the slow erosion of trust every time someone has to say 'let me get back to you on that.'
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 audit teams, 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. Bill C-5 and the new Major Projects Office 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:
Which version of the budget is the real one
Whether a scope change was ever formally approved
The minutes where direction actually changed
Closeout proof of what was delivered and who signed for it
What Bill C-5 and the new Major Projects Office actually change
Put plainly, an audit-ready project keeps these together from day one:
Closeout and retention. What was delivered, who signed for it, and proof you kept what you must keep.
The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.
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.
Procurement justification. Why this vendor, this price, this process — documented at the time, not rationalized after.
What changes the outcome isn't heroics at audit time. It's removing the gap between doing the work and recording it.
XNM-VISION closes that gap for audit teams. 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 audit teams 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.
Funding gets you to the starting line. Records are what carry you across it. In a year defined by Bill C-5 and the new Major Projects Office, that distinction is the whole game.
What this looks like in practice
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.
Picture a typical week on a mid-sized capital file. A change directive is issued in a Tuesday meeting, a revised drawing arrives Thursday from the engineer, an invoice referencing the new scope lands the following Monday, and a funder requests proof of approval three weeks later. Four different people touched four different systems. The decision was sound. The trail is not.
Approvals living in email rather than against the document
Two slightly different copies of the same contract on two shared drives
A meeting decision that nobody translated into a change order
A regulatory obligation tracked in a spreadsheet that one person updates
A vendor submittal accepted in conversation but never recorded
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.
A quieter way to run the file room
Multiply that across a portfolio and the picture gets sharper. The overrun is not the surprise; the surprise is how predictable it was once you could see the gaps. The same three or four records keep going missing across files, across years, across teams.
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.
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.
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.
None of this is glamorous. That is the point. The teams that look unflappable at review are the ones that made the boring choices early and stuck with them.
We take apart a failure like this every week. Closing exactly this gap is why we built XNM-VISION.
