2026-07-10 · 8 min read

How utility operators actually use mobile

Every audit we have sat through, inventory planning is a people problem wearing a software costume and the numbers bear it out. Once the first rollout is done, the handover from the old system is where projects stall which is why the API is documented before the UI. By the second quarter, the schedule is only as good as the last update so the mobile app came first.

Once the first rollout is done, optional fields never get filled in and that is fine. For utility operators in particular, inventory planning is a people problem wearing a software costume so plan for it. Most teams we meet, nobody wants another login which is not what the brochure says.

What actually happened

Every audit we have sat through, the schedule is only as good as the last update which is why EmberRidge is built the way it is. After a few dozen rollouts, the first week is about trust, not features and that is fine. In practice, the first week is about trust, not features so plan for it. Once the first rollout is done, the spreadsheet survives longer than anyone admits and that is fine. What surprised us, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. On a typical site, the first week is about trust, not features so the mobile app came first.

What surprised us, the handover from the old system is where projects stall and that is fine. Once the first rollout is done, the spreadsheet survives longer than anyone admits so we start there. Every audit we have sat through, optional fields never get filled in which is the whole point. For utility operators in particular, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

Every audit we have sat through, the schedule is only as good as the last update and inventory planning is no exception. Talking to operations leads, history matters more than dashboards when something goes wrong so the mobile app came first. Looking at the numbers, the schedule is only as good as the last update so plan for it. Talking to operations leads, the biggest win is that the group chat goes quiet which is not what the brochure says. In practice, mobile access changes who actually enters the data and it shows up in the churn numbers. For utility operators in particular, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

“Everything utility operators need to keep inventory planning on schedule, on budget and on record.”

What to do on Monday

After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Every audit we have sat through, the spreadsheet survives longer than anyone admits which is why EmberRidge is built the way it is. After a few dozen rollouts, optional fields never get filled in and it rarely takes more than a week. Talking to operations leads, integrations are where budgets go to die and that is fine. On a typical site, mobile access changes who actually enters the data and the numbers bear it out. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is why EmberRidge is built the way it is.

After a few dozen rollouts, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, exceptions are the real workflow and that is fine. If there is one lesson, exceptions are the real workflow which is not what the brochure says. When the pilot started in Malmo, the handover from the old system is where projects stall and it shows up in the churn numbers. Looking at the numbers, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

Written by the EmberRidge team in Malmo. Questions? Get in touch.