One Source of Truth: The Case for Utilities in 2023
Through 2023, utilities watched the 2023 Fall Economic Statement 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.
Funded is not the same as finished
The pattern is familiar to utilities: each system holds a piece of the truth, no system holds all of it, and the gaps between them are exactly where projects quietly bleed.
It compounds over time. Every handoff between utilities 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.
It helps to name the real adversary, because it is not incompetence. For utilities, 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. The 2023 Fall Economic Statement 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.
Here is where the proof tends to hide:
A funder's reporting requirement nobody mapped to a document
An approval that exists but isn't visible to the work
A commitment made in a meeting and never written down
The one attachment that proves the whole timeline
Make ready your resting state
Put plainly, an audit-ready project keeps these together from day one:
Procurement justification. Why this vendor, this price, this process — documented at the time, not rationalized after.
Version history. Proof of which drawing, spec, or policy was current on any given day.
Closeout and retention. What was delivered, who signed for it, and proof you kept what you must keep.
Meeting minutes and direction. Especially anything that changed scope, schedule, or budget.
The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.
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.
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.
Crucially, XNM-VISION doesn't ask utilities 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 the 2023 Fall Economic Statement, that distinction is the whole game.
What this looks like on a real week
Picture a Tuesday morning where the program lead opens a single dashboard and sees, at a glance, which approvals are waiting, which drawings changed since Friday, and which invoices are about to come due. Nothing is hunted; nothing is forwarded; nothing waits for one person to come back from holiday. The act of opening the file is the act of being audit-ready.
Now picture the same Tuesday without that view. A coordinator pings three inboxes. A site lead is using last month's drawing because the latest version landed only on a desktop in head office. An invoice gets paid against a scope that quietly changed in a meeting nobody minuted. None of it is anyone's fault in particular; all of it is the consequence of letting the record live in a dozen places at once.
Approvals routed to a role, not a single inbox, so a vacation never stops the work
Drawings and specs versioned in one place, with the current revision marked and the history one click away
Invoices linked to the contract and the change order they belong to, so coding is never guesswork
Field notes and photos attached to the task they describe, not stranded on a phone
How to start without rebuilding everything
The instinct on hearing all this is to brace for a migration project, a six-month rebuild, and a fight with the IT calendar. That is the old way. The teams getting ahead are doing the opposite: they pick one live project, move its record into one place, and let the next project copy the pattern. The system grows with the work instead of waiting for the work to pause.
In practice that means: keep what already works on paper, pull the live decisions into a shared workspace, and let the older archives be loaded as time permits. The point is not perfection on day one. The point is that from day one, the next decision is captured the right way, with a name and a date, in the place everyone is already looking.
Pick one live project. A current build or program with active approvals, contracts, and invoices — not a finished one.
Map the five record types that matter. Approvals, decisions, versions, procurement, and minutes. Skip the rest until these five are real.
Move the next decision, not the last one. Start the discipline on tomorrow's approval; bring the back-catalogue in as you have time.
Show one stakeholder the difference. A funder, a board member, a partner agency — one person who used to wait, now answered in minutes.
Repeat on project two. Copy the workspace, change the names, and the pattern compounds.
What changes for the team is smaller than it sounds and bigger than it looks. The work is the same; the proof is built in. The next review is not a sprint; it is a click.
This is the gap XNM closes for capital teams. Learn how in our overview of XNM-VISION.
