After the widening municipal infrastructure deficit: The Question Health authorities Should Be Asking
Through 2023, health authorities watched the widening municipal infrastructure deficit 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.
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.
What the widening municipal infrastructure deficit actually changes
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.
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.
Picture the opposite, just for a moment. A capital project where every approval, version, and dollar lands in one place as it happens, each stamped with a name and a date, visible to everyone the work touches. When a funder calls or an auditor schedules a review, nothing has to be reconstructed — the answer is already there, assembled by the act of doing the work. For health authorities, that is not a fantasy or a bigger budget; it is a different default. And in an era defined by the widening municipal infrastructure deficit, that default is quietly becoming the line between the teams that deliver and the teams that stall.
These are the records that go missing first:
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
In practice: what the daily workflow looks like
On a typical week, a portfolio manager opens the workspace, scans a single status strip, and sees which projects moved, which decisions are waiting, and which records are flagged for review. The work itself produces the proof: every upload, approval, and dollar lands in the same place as it happens, so the record assembles itself instead of being chased down on Friday afternoons.
The shift is small in feel but large in effect. Teams stop asking each other for the latest version, because the latest version is the one they are looking at. They stop emailing PDFs for sign-off, because the gate, the name, and the timestamp are already attached to the item being approved.
When something does go wrong — a vendor disputes a quantity, a funder asks for a backup, a council member questions a change — the answer is one click away, with the supporting trail intact. The cost of being right drops from days to minutes.
A few practical patterns we see repeatedly:
A single status strip that flashes when something past-due, sensitive, or new arrives
Per-project folders that hold drawings, contracts, change orders, and invoices in one stack
Tiered visibility, so council, staff, contractors, and funders each see what they should
An audit log that records every read, edit, approval, and delete with a hash-chained timestamp
Where the proof goes to hide
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.
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.
Closeout and retention. What was delivered, who signed for it, and proof you kept what you must keep.
Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.
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 the XNM-VISION records engine 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.
Crucially, the XNM-VISION records engine 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 money will keep flowing toward big builds. The teams that win the next decade won't be the ones who got funded — they'll be the ones who could prove, on any given Tuesday, exactly how the work was run.
How XNM-VISION helps a capital portfolio stay defensible
XNM-VISION was built around one stubborn idea: the system of record and the system of work should be the same system. When the two are separated, the record is always behind, always partial, and always expensive to reassemble. When they are joined, the record is a free byproduct of getting the work done.
That joining shows up in small, daily mechanics. A purchase order is matched to a contract at creation, not at year-end. An invoice is reconciled against the line items it cites, not against a memory of what was agreed. A change order is signed inside the project workspace, with a stamped version of the drawing it modifies.
If your team is starting from a patchwork of tools, three moves usually move the needle the fastest:
Name one owner per project record. Someone whose job includes the simple act of putting the document where it belongs.
Move approvals out of email. Anything that needs a sign-off should be approved in the same place the work lives, with a name and a timestamp attached.
Reconcile money at the line item. Match each invoiced dollar to the contract clause that authorized it, while the memory of the work is still warm.
None of this requires heroics. It requires a default that protects you on the days you don't have time to be careful — which is most days, on most capital portfolios.
Want to see what one source of truth looks like for your projects? Talk to us — it's a short conversation.
