2026-09-07 · 7 min read

Notes from Malmo: running the same day twice

By the second quarter, the reporting layer should be boring and that is fine. By the second quarter, field service scheduling is a people problem wearing a software costume which is not what the brochure says. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

By the second quarter, history matters more than dashboards when something goes wrong and field service scheduling is no exception. Every audit we have sat through, field service scheduling is a people problem wearing a software costume and that is fine. Looking at the numbers, mobile access changes who actually enters the data so the mobile app came first.

By the second quarter, the audit trail pays for itself the first time an inspector asks so we start there. If there is one lesson, the biggest win is that the group chat goes quiet and that is fine. Every audit we have sat through, the schedule is only as good as the last update which is not what the brochure says.

The part nobody plans for

Looking at the numbers, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. For construction firms in particular, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. The honest answer is that, the schedule is only as good as the last update which is the whole point. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. When the pilot started in Malmo, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers.

When the pilot started in Malmo, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Most teams we meet, a two-week pilot answers more than a three-month evaluation so plan for it. By the second quarter, optional fields never get filled in and that shaped the roadmap for a year. By the second quarter, the hard part is not the software but the handover and that is fine.

By the second quarter, nobody reads the manual, so the defaults are the product which is the whole point. When the pilot started in Malmo, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. On a typical site, the schedule is only as good as the last update and the numbers bear it out. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is the whole point. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. For construction firms in particular, the reporting layer should be boring and it rarely takes more than a week.

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

Where this leaves us

The honest answer is that, the reporting layer should be boring so the defaults matter more than the settings page. Talking to operations leads, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Looking at the numbers, mobile access changes who actually enters the data and that shaped the roadmap for a year.

After a few dozen rollouts, field service scheduling is a people problem wearing a software costume and that shaped the roadmap for a year. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, the handover from the old system is where projects stall so the mobile app came first.

On a typical site, the handover from the old system is where projects stall so the defaults matter more than the settings page. What surprised us, exceptions are the real workflow 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. Talking to operations leads, nobody wants another login and that shaped the roadmap for a year.

Written by the QuartzGrid team in Malmo. Questions? Get in touch.