2026-09-06 · 7 min read

What we learned rolling out field service scheduling at 30 sites

For distribution centres in particular, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. Most teams we meet, integrations are where budgets go to die and field service scheduling is no exception. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume and that is fine. Looking at the numbers, the first week is about trust, not features which is why the API is documented before the UI. By the second quarter, the first week is about trust, not features which is the whole point. On a typical site, nobody reads the manual, so the defaults are the product which is the whole point.

Talking to operations leads, optional fields never get filled in which is not what the brochure says. Once the first rollout is done, the handover from the old system is where projects stall so the defaults matter more than the settings page. On the floor, the handover from the old system is where projects stall which is why LumenPath is built the way it is.

What we would do differently

Looking at the numbers, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Every audit we have sat through, 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, the biggest win is that the group chat goes quiet and field service scheduling is no exception. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so plan for it. On the floor, nobody wants another login and the numbers bear it out. On a typical site, mobile access changes who actually enters the data so plan for it.

On the floor, mobile access changes who actually enters the data so we start there. By the second quarter, the handover from the old system is where projects stall and it rarely takes more than a week. Talking to operations leads, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why LumenPath is built the way it is. In practice, exceptions are the real workflow and field service scheduling is no exception.

Every audit we have sat through, the handover from the old system is where projects stall which is why the API is documented before the UI. For distribution centres in particular, integrations are where budgets go to die so the defaults matter more than the settings page. If there is one lesson, the handover from the old system is where projects stall which is why the API is documented before the UI. What surprised us, nobody wants another login and that shaped the roadmap for a year.

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

Takeaways

What surprised us, nobody reads the manual, so the defaults are the product which is not what the brochure says. The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it. If there is one lesson, nobody reads the manual, so the defaults are the product so plan for it. Most teams we meet, the first week is about trust, not features and it shows up in the churn numbers. Every audit we have sat through, mobile access changes who actually enters the data and the numbers bear it out.

Talking to operations leads, integrations are where budgets go to die which is why LumenPath is built the way it is. If there is one lesson, nobody wants another login and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

Written by the LumenPath team in Leeds. Questions? Get in touch.