2026-06-24 · 8 min read

Exceptions are the real workflow

After a few dozen rollouts, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. On the floor, the hard part is not the software but the handover which is why the API is documented before the UI. For food producers in particular, the schedule is only as good as the last update which is the whole point.

On the floor, the reporting layer should be boring so we start there. Most teams we meet, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Talking to operations leads, history matters more than dashboards when something goes wrong and the numbers bear it out. By the second quarter, the first week is about trust, not features which is not what the brochure says. After a few dozen rollouts, optional fields never get filled in which is the whole point. On the floor, mobile access changes who actually enters the data which is why the API is documented before the UI.

The part nobody plans for

For food producers in particular, the reporting layer should be boring and field service scheduling is no exception. On the floor, the schedule is only as good as the last update so we start there. If there is one lesson, nobody wants another login so the mobile app came first.

For food producers in particular, optional fields never get filled in and that is fine. What surprised us, the reporting layer should be boring and it shows up in the churn numbers. By the second quarter, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. What surprised us, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

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

Takeaways

If there is one lesson, nobody wants another login and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. The honest answer is that, nobody wants another login and that is fine.

After a few dozen rollouts, the first week is about trust, not features and that is fine. Once the first rollout is done, nobody wants another login which is why Lumen is built the way it is. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why Lumen is built the way it is. If there is one lesson, the reporting layer should be boring so we start there. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine.

Written by the Lumen team in Wroclaw. Questions? Get in touch.