2026-06-22 · 4 min read

The handover problem, and what we do about it

Every audit we have sat through, exceptions are the real workflow which is not what the brochure says. On a typical site, what matters is whether the crew opens it on a Monday morning which is the whole point. What surprised us, the reporting layer should be boring which is why the API is documented before the UI. The honest answer is that, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Looking at the numbers, the biggest win is that the group chat goes quiet which is why NimbusPoint is built the way it is.

Every audit we have sat through, exceptions are the real workflow and it rarely takes more than a week. Looking at the numbers, exceptions are the real workflow so the defaults matter more than the settings page. By the second quarter, the schedule is only as good as the last update which is not what the brochure says. Once the first rollout is done, optional fields never get filled in and asset tracking is no exception.

What we would do differently

What surprised us, nobody reads the manual, so the defaults are the product which is why NimbusPoint is built the way it is. Most teams we meet, history matters more than dashboards when something goes wrong which is the whole point. Once the first rollout is done, the hard part is not the software but the handover and that shaped the roadmap for a year.

Every audit we have sat through, exceptions are the real workflow so we start there. Every audit we have sat through, the hard part is not the software but the handover which is why the API is documented before the UI. Once the first rollout is done, the first week is about trust, not features and that shaped the roadmap for a year.

The honest answer is that, asset tracking is a people problem wearing a software costume and the numbers bear it out. For utility operators in particular, integrations are where budgets go to die which is not what the brochure says. On a typical site, integrations are where budgets go to die so we start there. For utility operators in particular, the hard part is not the software but the handover so the defaults matter more than the settings page. When the pilot started in Bologna, integrations are where budgets go to die and asset tracking is no exception.

“Plan, dispatch and reconcile in one place. NimbusPoint connects to the systems you already run and stays out of the way.”

Takeaways

In practice, mobile access changes who actually enters the data and that is fine. Looking at the numbers, mobile access changes who actually enters the data and that shaped the roadmap for a year. On the floor, what matters is whether the crew opens it on a Monday morning which is why NimbusPoint is built the way it is. Once the first rollout is done, the handover from the old system is where projects stall so plan for it. By the second quarter, the biggest win is that the group chat goes quiet and the numbers bear it out. By the second quarter, the first week is about trust, not features and asset tracking is no exception.

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Talking to operations leads, nobody wants another login and it rarely takes more than a week. Every audit we have sat through, exceptions are the real workflow and that shaped the roadmap for a year. When the pilot started in Bologna, the audit trail pays for itself the first time an inspector asks so plan for it.

Written by the NimbusPoint team in Bologna. Questions? Get in touch.