One Source of Truth: The Case for Provincial agencies in 2025

Through 2025, provincial agencies watched stubborn construction-cost inflation 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.

What's really at risk isn't tidiness. It's whether a funder, an auditor, or a partner can look at your project and trust that it was run the way you say it was.

Funded is not the same as finished

A short readiness check

Before chasing new tools, it is worth running a quick honesty test on the current state. The questions below are intentionally blunt. If three or more answers are uncomfortable, the cost of the status quo is almost certainly higher than the cost of fixing it.

1. One canonical source. Is there a single place where the live version of every contract, drawing and decision lives?

2. A clean audit trail. Can you show, for any decision, who approved it, when, and on what basis?

3. Easy hand-off. If the lead leaves tomorrow, can a replacement be productive within a week?

4. Honest status. Does leadership see the same project status the team sees, in real time?

For provincial agencies, 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.

It compounds over time. Every handoff between provincial agencies 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.

There is a reason this keeps happening even to careful provincial agencies. The tools that hold the work — email, shared drives, spreadsheets, a project app or two — were each built to do one job well, not to keep a single, time-stamped record of what was decided and why. So the record becomes a manual chore bolted onto the real work, and it is the first thing to slip when multi-year capital plans across many sites gets busy. In a year shaped by stubborn construction-cost inflation, that one dropped chore is exactly what returns, months later, as a finding, a dispute, or a number nobody can explain.

Here is where the proof tends to hide:

• 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

Where the proof goes to hide

If you keep nothing else in a single system, keep these:

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

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

3. The contract and its change orders. The original plus every amendment, in order, with nothing living only in an email thread.

4. The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.

5. Closeout and retention. What was delivered, who signed for it, and proof you kept what you must keep.

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 multi-year capital plans across many sites, ingesting from the inboxes and folders you already use, so nothing has to be reassembled later.

What changes the result for provincial agencies is not another database. It's that one auditable system 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.

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 a 90-day fix actually looks like

1. Week 1 — pick one project. Choose a live file with real stakes, not a pilot in a corner. Real stakes force real decisions.

2. Weeks 2–3 — consolidate the record. Pull contracts, drawings, change orders and approvals into one place and label the live versions.

3. Weeks 4–8 — wire in approvals. Move sign-offs out of email and into the record. Every approval leaves a timestamp and a name.

4. Weeks 9–12 — rehearse the audit. Pretend a funder is at the door and run a dry export. If it is clean, repeat the pattern on the next project.

Ninety days is enough to prove the pattern on one file. It is not enough to boil the ocean, and that is the point. Capital teams do not need a transformation programme — they need one project that is visibly easier to run, so the next one can copy it.

This is the gap XNM closes for capital teams. Learn how in our overview of XNM-VISION.