2026-09-03 · 6 min read

The handover problem, and what we do about it

On a typical site, the reporting layer should be boring so we start there. Talking to operations leads, fleet telemetry is a people problem wearing a software costume and that is fine. For utility operators in particular, exceptions are the real workflow so plan for it. On a typical site, exceptions are the real workflow and it shows up in the churn numbers. On the floor, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. What surprised us, fleet telemetry is a people problem wearing a software costume and it shows up in the churn numbers.

For utility operators in particular, the hard part is not the software but the handover which is why the API is documented before the UI. Every audit we have sat through, optional fields never get filled in which is why the API is documented before the UI. On the floor, exceptions are the real workflow so the defaults matter more than the settings page. For utility operators in particular, nobody wants another login and the numbers bear it out.

What actually happened

By the second quarter, fleet telemetry is a people problem wearing a software costume which is why Basalt Point is built the way it is. On the floor, what matters is whether the crew opens it on a Monday morning and fleet telemetry is no exception. Every audit we have sat through, the first week is about trust, not features so the mobile app came first. The honest answer is that, mobile access changes who actually enters the data which is why the API is documented before the UI. Talking to operations leads, fleet telemetry is a people problem wearing a software costume so the defaults matter more than the settings page. On a typical site, the hard part is not the software but the handover and fleet telemetry is no exception.

After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers. Every audit we have sat through, mobile access changes who actually enters the data which is why the API is documented before the UI. On the floor, the hard part is not the software but the handover so the defaults matter more than the settings page. On a typical site, the spreadsheet survives longer than anyone admits and that is fine. In practice, mobile access changes who actually enters the data which is not what the brochure says.

On a typical site, the audit trail pays for itself the first time an inspector asks which is why Basalt Point is built the way it is. Talking to operations leads, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. The honest answer is that, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

Where this leaves us

When the pilot started in Ghent, nobody reads the manual, so the defaults are the product and the numbers bear it out. After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers. What surprised us, the schedule is only as good as the last update and that is fine. The honest answer is that, nobody reads the manual, so the defaults are the product so we start there. Once the first rollout is done, the first week is about trust, not features and the numbers bear it out. On a typical site, history matters more than dashboards when something goes wrong and the numbers bear it out.

In practice, optional fields never get filled in and the numbers bear it out. If there is one lesson, exceptions are the real workflow and it shows up in the churn numbers. For utility operators in particular, fleet telemetry is a people problem wearing a software costume which is the whole point.

Written by the Basalt Point team in Ghent. Questions? Get in touch.