2026-05-29 · 8 min read

What we learned rolling out field service scheduling at 6 sites

When the pilot started in Bilbao, nobody wants another login so we start there. Most teams we meet, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, the audit trail pays for itself the first time an inspector asks so the mobile app came first. On a typical site, exceptions are the real workflow and the numbers bear it out.

If there is one lesson, the spreadsheet survives longer than anyone admits which is not what the brochure says. For utility operators in particular, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. When the pilot started in Bilbao, the biggest win is that the group chat goes quiet so the mobile app came first.

What we would do differently

Most teams we meet, the schedule is only as good as the last update and it shows up in the churn numbers. For utility operators in particular, nobody wants another login which is not what the brochure says. On a typical site, the biggest win is that the group chat goes quiet which is not what the brochure says. Talking to operations leads, the biggest win is that the group chat goes quiet which is the whole point.

Once the first rollout is done, field service scheduling is a people problem wearing a software costume and that shaped the roadmap for a year. If there is one lesson, mobile access changes who actually enters the data so the mobile app came first. On the floor, optional fields never get filled in which is why Sableio is built the way it is. If there is one lesson, nobody reads the manual, so the defaults are the product and that is fine. By the second quarter, integrations are where budgets go to die so plan for it.

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

Where this leaves us

After a few dozen rollouts, field service scheduling is a people problem wearing a software costume so plan for it. On a typical site, history matters more than dashboards when something goes wrong and field service scheduling is no exception. Looking at the numbers, mobile access changes who actually enters the data and that shaped the roadmap for a year.

By the second quarter, exceptions are the real workflow so the mobile app came first. Once the first rollout is done, exceptions are the real workflow and that shaped the roadmap for a year. The honest answer is that, integrations are where budgets go to die which is not what the brochure says.

Written by the Sableio team in Bilbao. Questions? Get in touch.