After the record 2023 wildfire season: The Question Utilities Should Be Asking
When the record 2023 wildfire season dominated the headlines in 2023, utilities felt the pressure shift. The era of arguing for funding is giving way to a harder era of accounting for it.
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.
The records that settle questions
For utilities, 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.
The cost of the gap, in plain numbers
The cost of a records gap rarely shows up as a single budget line. It shows up as a week lost reconciling a draw package, a crew sitting because a drawing version was unclear, a funder pausing a disbursement while someone hunts for an approval email. None of these are catastrophes alone. Stacked across a year, they are the difference between a project that finishes on plan and one that quietly slips by a quarter.
Where the hours actually go
Re-reading email threads to confirm a decision made weeks ago
Comparing two drawings to figure out which is current
Re-creating a meeting note because the original is on someone's laptop
Chasing a signature that was sent, signed, and then misfiled
Reassembling a chain of change orders to answer one funder question
The cost isn't only the missing document. It's the meeting to look for it, the second meeting to recreate it, and the slow erosion of trust every time someone has to say 'let me get back to you on that.'
Consider how this plays out for utilities 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 record 2023 wildfire season 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:
Which version of the budget is the real one
Whether a scope change was ever formally approved
The minutes where direction actually changed
Closeout proof of what was delivered and who signed for it
The records that settle questions
A generic scenario, played out two ways
Picture a mid-sized capital project — a community facility, a depot, a water upgrade; the specifics don't matter. Halfway through construction, a regulator asks a routine question about a design change. In the first version, the team spends three days pulling the answer from four systems and two inboxes. The answer is right, but the project loses a week. In the second version, the same question is answered in twenty minutes, because the decision, the approval, the revised drawing, and the related cost are already linked in one place.
Nothing in that second version is heroic. The team didn't work harder. They worked inside a system that recorded the decision once and made it findable forever.
These are the records that turn a hard question into a two-minute answer:
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.
The contract and its change orders. The original plus every amendment, in order, with nothing living only in an email thread.
Invoices matched to the contract. Each dollar paid, tied to the commitment that authorized it.
The decision record. Who approved what, when, and on what basis — captured as it happened, not reconstructed under pressure.
How to start: a practical week one
Pick one live project. Not the easiest, not the hardest. The one with the most active decisions this month.
Decide what "a record" means. Approvals, signed contracts, current drawings, meeting minutes that change scope, and the linked costs. Anything else is optional for week one.
Move the records into one place. Not five places that sync. One place, with names and dates attached.
Use it as the first answer, every time. When a question comes in, the answer lives in the system or it gets put there. No parallel folders.
Review at the end of the week. Where did you have to hunt? That is the next gap to close.
Week two is not a redesign. It is the same five steps, repeated, with one more record type added. By week six, the team stops looking for things, because the things are where they belong.
The way out is not more effort. It's a single place where the decision, the document, and the work are the same object.
This is the problem XNM-VISION was designed around: one source of truth for regulated assets and long approval chains, ingesting from the inboxes and folders you already use, so nothing has to be reassembled later.
What changes the result for utilities 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 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.
Why this matters now
The pressure on capital teams isn't going to ease. Funders ask for more proof, faster. Regulators ask sharper questions. Insurers price risk on the quality of records, not just the quality of work. A project that can't show its decisions pays more for everything around it, even when the work itself is excellent.
How XNM-VISION helps
XNM-VISION keeps capital projects and the records that prove them in one auditable system. Approvals, versions, contracts, change orders, and the meeting notes that explain the change — each with a name and a date, each searchable, each linked to the cost line it touches. When a question comes, the answer is already assembled.
Want to see what one source of truth looks like for your projects? Talk to us — it's a short conversation.
