It's 2:00 a.m. A storm just took out 180,000 customers. By sunrise you have your own crews, contractor crews and mutual-aid crews from three states rolling through your service territory.
They're doing heroic work. They're also logging their hours on paper timesheets, texting photos to a supervisor and handing in damage reports on clipboards.
Six months later, the regulator wants to see every hour, every truck and every invoice behind your storm cost recovery. Someone in finance opens a spreadsheet with 41 tabs and quietly updates their résumé.
Welcome to the most important industry in America, running on some of its least loved software.
A trillion-dollar grid, run on paper and Excel
Utilities aren't short on technology. You have smart meters, SCADA, outage management systems and an ERP that took years to implement.
But between those big systems sit hundreds of everyday jobs nobody built software for: storm invoices, inspections, vegetation patrols, contractor timesheets, rate case data, crew qualifications and interconnection requests. That's where the binders and spreadsheets live, and that's where the money and the risk hide.
When utility software goes wrong, it goes very public
Most industries get to fail quietly. Utilities fail in front of regulators, reporters and every customer with a mailbox:
- Los Angeles (LADWP). A new billing system's budget grew from $87 million to about $181 million. Some customers got wildly inflated bills, others got none. The fallout included a $67.5 million class settlement.
- Central Hudson, New York. After billing system failures, the state regulator reached a $64.59 million settlement, including shareholders paying more than $35.3 million spent on fixing the system.
- Jackson, Mississippi. A water meter and billing overhaul went so badly that Siemens paid back $89.8 million.
- Baltimore. After $133.6 million spent on water billing, the luxury Ritz-Carlton Residences went unbilled for years, about $2.3 million. Meanwhile one homeowner received an $81,000 water bill. (We assume they didn't have a pool.)
And it's not just billing. One utility found a spreadsheet error that overstated a revenue line by $23 million in its rates. Customers got bill credits. Somebody got a very long meeting.
In a regulated business, a spreadsheet isn't just a spreadsheet. It's evidence.
The jobs your big systems were never built for
Your ERP handles finance. Your billing system bills. Your asset system tracks assets. What falls between them is where your people lose their nights and weekends:
- Storm cost tracking. Crew hours, equipment, mutual-aid invoices and receipts, rebuilt by hand after the storm and defended line by line in the audit.
- Field inspections and work orders. Poles, transformers, pipelines and substations inspected on paper, then typed in later, if anyone has the time.
- Vegetation management. Millions of trees, thousands of line-miles, contractors everywhere and wildfire risk on the line. Proof of what was trimmed, where and when, usually lives in contractor spreadsheets.
- Rate case data. Hundreds of numbers pulled from a dozen systems into Excel, with formulas nobody wants to touch and an audit trail made of email.
- Interconnection requests. Developers email forms and studies, engineers track progress in trackers, and everyone asks "what's the status?" every week.
- Crew qualifications. Who's certified for what, and when it expires, tracked in binders and static spreadsheets.
- Know-how that walks out the door. Every retiring veteran takes decades of "here's what you actually do when this happens" with them.
The fix: focused, regulator-ready apps beside your core systems
You don't need another five-year core replacement. Keep your ERP, billing and asset systems as the systems of record. Build focused apps around them that capture work once, where it happens, and keep the proof forever:
- A storm cost tracker. Crews log hours, equipment and photos on their phones; mutual-aid invoices are matched to the work; finance gets an audit-ready package, not a 41-tab spreadsheet.
- Mobile inspections and work orders that work offline in the field, with photos, GPS and readings that flow straight into your asset and ERP systems.
- A vegetation program tracker showing every span, every contractor and every trim cycle on a map, with proof attached.
- A rate case workspace where every number has a source, a version and a history, so the next spreadsheet error never reaches a regulator.
- An interconnection portal where developers submit requests, upload studies and see their status without sending a single email.
- A crew qualification tracker that warns supervisors before a certification expires, not after an incident.
- A field knowledge library where your veterans record procedures with photos and video, searchable from any truck.
Why this works now (and why it didn't before)
Five years ago, each of these apps meant a long procurement, a large integrator and a project measured in years. That's why they never got built, and why the binders survived.
With Defender, a focused module like these is built in weeks. And because it's a regulated industry, it's built with the discipline auditors expect:
| What regulators and auditors ask for | What every Defender module includes |
|---|---|
| "Show us exactly what this system is supposed to do." | A complete requirements document, signed off by your team |
| "Who changed this number, and when?" | Roles, permissions and a full audit trail from day one |
| "How do you know it works?" | Automated tests that run after every change |
| "Where does the data live?" | Deployment to your own cloud or on-premise servers |
| "Who owns it?" | You. All source code, documents and decision records transfer to you |
The grid is being rebuilt. Rebuild the paperwork with it.
America is spending more than a trillion dollars to modernize the grid. It's worth spending a tiny fraction of that so the people doing the work aren't fighting binders and spreadsheets while they do it.
Pick the one process that keeps your team up during storm season or rate case season. We'll show you what it looks like as clean, auditable software, in weeks, not years.
The binders can finally go to the archive, where they belong.
