Anatomy of an Overrun: When Capital projects Outrun the Paperwork

Through 2025, health authorities 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.

And the bill always comes due at the worst moment: mid-build, mid-audit, or mid-dispute, when the missing piece is suddenly the only piece that matters.

What Bill C-5 and the new Major Projects Office actually changes

For health authorities, 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.

For health authorities juggling facility projects under strict compliance, the gap is structural, not personal. No amount of diligence closes a gap that is built into how the tools are wired together.

It helps to name the real adversary, because it is not incompetence. For health authorities, 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. Bill C-5 and the new Major Projects Office 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.

The usual suspects, every time:

• The current drawing, versus three that look almost identical

• The signed copy, versus the draft everyone kept editing

• The retention proof that you kept what you must keep

• The single thread that explains why a number changed

Make ready your resting state

Here is what belongs in one place, with a name and a date on every item:

1. Approvals and sign-offs. Every gate with a name and date attached, visible to everyone the decision touches.

2. Version history. Proof of which drawing, spec, or policy was current on any given day.

3. Procurement justification. Why this vendor, this price, this process — documented at the time, not rationalized after.

4. Meeting minutes and direction. Especially anything that changed scope, schedule, or budget.

5. Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.

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.

This is the problem one auditable system was designed around: one source of truth for facility projects under strict compliance, ingesting from the inboxes and folders you already use, so nothing has to be reassembled later.

Crucially, one auditable system doesn't ask health authorities 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 this actually looks like on a Monday morning

Picture a project lead opening the week with three questions on the table: where did last week's variance come from, did the change order get countersigned, and what does the funder need by Thursday. In a healthy system, each answer is one click away. In a fragmented one, each answer is a half-day of forwarded emails and phone calls. The difference is not effort. It is whether the record was captured at the moment the work happened, or stitched together afterwards from memory.

The teams that handle this calmly tend to share a few quiet habits. They treat the project's documents the way an accountant treats the ledger: every entry has a date, an author, and a place it belongs. They resist the temptation to keep "working copies" on personal drives. And they retire the version control conversation almost entirely, because there is only ever one current version and the older ones are visible but clearly marked.

The hidden cost of a brittle paper trail

Every hour spent reconstructing what happened is an hour not spent moving the project forward. Multiply that across a portfolio and the drag becomes structural. Worse, when the reconstruction is too costly, teams quietly stop doing it — and a small reporting gap turns into a slow erosion of trust with funders, councils, and partners. None of this shows up as a line item, but it shows up in the timeline.

1. Name the system of record. Pick one place where the truth lives, and make it the only place people are asked to look first.

2. Capture decisions where they happen. A decision made in a meeting belongs in the record before the meeting ends, not three days later in someone's notebook.

3. Make retrieval boring. If finding a document requires expertise, the document is effectively missing. Search, tag, and filter until the boring answer is the easy one.

A short, practical test

Pick any project that closed in the last twelve months. Ask one question: if a funder requested the full file tomorrow morning, how many people would you need to involve to produce it before noon? If the answer is more than two, the record is doing too much work in too many heads.

This is where XNM-VISION earns its keep. It is not a replacement for judgment or for the people who run the work. It is the discipline that keeps the record and the work moving together, so that the question "can you prove it?" stops being a fire drill and becomes a non-event.

We take apart a failure like this every week. Closing exactly this gap is why we built XNM-VISION.