2026-08-14 · 7 min read

Exceptions are the real workflow

On the floor, the hard part is not the software but the handover so plan for it. By the second quarter, history matters more than dashboards when something goes wrong and that is fine. In practice, the biggest win is that the group chat goes quiet and it rarely takes more than a week. In practice, the handover from the old system is where projects stall and that is fine. For distribution centres in particular, the biggest win is that the group chat goes quiet so plan for it.

By the second quarter, nobody wants another login which is why LumenPath is built the way it is. By the second quarter, the first week is about trust, not features and that shaped the roadmap for a year. The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. If there is one lesson, exceptions are the real workflow so we start there. In practice, the handover from the old system is where projects stall and field service scheduling is no exception. The honest answer is that, the schedule is only as good as the last update and field service scheduling is no exception.

If there is one lesson, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. When the pilot started in Leeds, a two-week pilot answers more than a three-month evaluation which is why LumenPath is built the way it is. Most teams we meet, the handover from the old system is where projects stall which is why LumenPath is built the way it is. In practice, mobile access changes who actually enters the data and field service scheduling is no exception.

What we would do differently

By the second quarter, the reporting layer should be boring and that is fine. On a typical site, exceptions are the real workflow which is the whole point. Every audit we have sat through, the biggest win is that the group chat goes quiet which is not what the brochure says. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

When the pilot started in Leeds, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. What surprised us, mobile access changes who actually enters the data so the mobile app came first. For distribution centres in particular, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

“Everything distribution centres need to keep field service scheduling on schedule, on budget and on record.”

What to do on Monday

Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. After a few dozen rollouts, history matters more than dashboards when something goes wrong which is not what the brochure says. By the second quarter, the hard part is not the software but the handover and it rarely takes more than a week. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume so plan for it. After a few dozen rollouts, the hard part is not the software but the handover which is why LumenPath is built the way it is.

For distribution centres in particular, the reporting layer should be boring so the mobile app came first. For distribution centres in particular, nobody reads the manual, so the defaults are the product which is the whole point. For distribution centres in particular, integrations are where budgets go to die and that is fine. The honest answer is that, the schedule is only as good as the last update which is the whole point. In practice, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

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