2026-05-21 · 6 min read

What we learned rolling out field service scheduling at 27 sites

Talking to operations leads, mobile access changes who actually enters the data so we start there. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there. Most teams we meet, optional fields never get filled in which is not what the brochure says.

On a typical site, the reporting layer should be boring which is why the API is documented before the UI. Talking to operations leads, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week. For mid-market manufacturers in particular, what matters is whether the crew opens it on a Monday morning so we start there. What surprised us, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. Every audit we have sat through, nobody wants another login and field service scheduling is no exception. Every audit we have sat through, nobody wants another login and it rarely takes more than a week.

On a typical site, nobody reads the manual, so the defaults are the product so the mobile app came first. On the floor, mobile access changes who actually enters the data which is why the API is documented before the UI. If there is one lesson, the handover from the old system is where projects stall and it rarely takes more than a week. Looking at the numbers, field service scheduling is a people problem wearing a software costume which is why the API is documented before the UI. For mid-market manufacturers in particular, optional fields never get filled in so plan for it.

Where the time went

If there is one lesson, the schedule is only as good as the last update and field service scheduling is no exception. Once the first rollout is done, exceptions are the real workflow which is the whole point. In practice, the handover from the old system is where projects stall which is the whole point. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume and that shaped the roadmap for a year. What surprised us, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

What surprised us, optional fields never get filled in and the numbers bear it out. Looking at the numbers, mobile access changes who actually enters the data so the defaults matter more than the settings page. By the second quarter, a two-week pilot answers more than a three-month evaluation so we start there.

“Everything mid-market manufacturers need to keep field service scheduling on schedule, on budget and on record.”

What to do on Monday

By the second quarter, the schedule is only as good as the last update and the numbers bear it out. By the second quarter, field service scheduling is a people problem wearing a software costume and that shaped the roadmap for a year. On the floor, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year.

In practice, the biggest win is that the group chat goes quiet and field service scheduling is no exception. If there is one lesson, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. On a typical site, the audit trail pays for itself the first time an inspector asks so plan for it. For mid-market manufacturers in particular, the first week is about trust, not features which is not what the brochure says.

Looking at the numbers, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Talking to operations leads, the first week is about trust, not features and it shows up in the churn numbers. What surprised us, the first week is about trust, not features which is why the API is documented before the UI. In practice, nobody wants another login so plan for it. In practice, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week.

Written by the MarrowPoint team in Graz. Questions? Get in touch.