One Source of Truth: The Case for Health authorities in 2024
The push to close the First Nations infrastructure gap by 2030 made one thing clear in 2024: getting capital projects approved is no longer the bottleneck. Delivering them — and being able to show your work — is.
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.
The records that settle questions
Most health authorities are managing facility projects under strict compliance across email, spreadsheets, and three or four tools that don't talk to each other. The information exists. It just can't be assembled when it counts.
Look closer at any health authorities 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.
Consider how this plays out for health authorities in practice. A decision gets made in a meeting, refined over a few emails, approved with a nod, and then executed by a crew who never saw any of it written down. Months later — often once the push to close the First Nations infrastructure gap by 2030 has put every project under a brighter light — someone asks a question that should be easy: show me where this was approved, and by whom. The work itself was sound. The trail behind it was not. And it is precisely in that gap, between a good decision and a provable one, that budgets quietly disappear and schedules slip.
These are the records that go missing first:
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
What this looks like on a real project
Picture a mid-sized capital program a year into delivery. Three contractors are on site, two engineering firms are still issuing revisions, and a funder has just asked for a status update before the next disbursement. The work itself is going well. The proof of how it has been going is scattered across three inboxes, two shared drives, and a paper file in the project trailer.
Nothing about that scene is unusual. It is, in fact, the default state of most capital projects that have grown faster than their record-keeping. The team is not careless. They are simply doing what works in the moment — sending an email, saving a PDF, marking up a drawing — without a clean way to make the moment count later.
The cost shows up at the worst possible time: during an audit, a dispute, or a leadership change. Someone asks a precise question, and the answer requires reconstructing a conversation that happened six months ago between two people, only one of whom is still on the team.
A funder request that used to take a week of stitching together now takes an afternoon
A new team member can see what was decided and why, without asking three people
A dispute moves from memory and tone to the record and the timeline
A leadership change does not reset the project's institutional knowledge to zero
Funded is not the same as finished
Here is what belongs in one place, with a name and a date on every item:
Version history. Proof of which drawing, spec, or policy was current on any given day.
The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.
Procurement justification. Why this vendor, this price, this process — documented at the time, not rationalized after.
Approvals and sign-offs. Every gate with a name and date attached, visible to everyone the decision touches.
Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.
None of this is a discipline problem. Diligent people lose records every day. It's a structure problem — and structure is fixable.
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 health authorities 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.
The push to close the First Nations infrastructure gap by 2030 raised the ceiling on what's possible. Whether health authorities reach it comes down to something unglamorous: whether the proof was there all along.
How XNM-VISION changes the working day
The shift XNM-VISION makes is small but compounding. Instead of a folder where documents land and an inbox where decisions live, the record and the work share a single object. Approving a change order, attaching a revised drawing, and noting the reason all happen in the same place — and they stay together.
That removes a class of work that nobody enjoyed anyway: the weekly reconciliation between what is actually happening and what the file shows. When the file is the work, reconciliation is not a task. It is a property of the system.
What teams notice first is that meetings get shorter. The opening ten minutes that used to be spent agreeing on what version of reality everyone is looking at simply disappear. The dashboard is the version of reality. Disagreements move to the decision itself, where they belong.
Practical steps to take this quarter
None of this requires a rebuild. The teams that get the most out of a single source of truth tend to do the same handful of things in their first ninety days:
Pick one program to start with. Do not try to migrate everything at once. Choose the project where the cost of disorder is highest and the team is most willing to change one habit.
Move the live record into the system first. Approvals, decisions, current versions, and the schedule. The archive can follow. Today's work is what changes the outcome.
Name an owner for every record class. Contracts, change orders, invoices, drawings, minutes. One name per class, with a clear backup, removes ninety percent of the orphan documents.
Set a weekly five-minute review. Not a meeting — a glance at what is missing, what is overdue, and what is sitting in one person's inbox. The discipline is small. The compounding is large.
The reason this matters is not abstract. Capital projects live and die on the ability to defend a sequence of decisions against people who were not in the room when the decisions were made. The teams that can do that — calmly, on demand — keep their funding, their reputation, and their schedule.
The teams that cannot do that spend their energy re-litigating the past instead of building the next thing. Over a multi-year program, that energy adds up to entire quarters of lost momentum.
We take apart a failure like this every week. Closing exactly this gap is why we built XNM-VISION.
