2026-07-29 · 6 min read

What we learned rolling out field service scheduling at 39 sites

Once the first rollout is done, the first week is about trust, not features and it rarely takes more than a week. What surprised us, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. On the floor, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. On the floor, the hard part is not the software but the handover and the numbers bear it out. Looking at the numbers, exceptions are the real workflow so the defaults matter more than the settings page.

Looking at the numbers, nobody wants another login which is not what the brochure says. In practice, history matters more than dashboards when something goes wrong and field service scheduling is no exception. Talking to operations leads, the spreadsheet survives longer than anyone admits and the numbers bear it out. In practice, optional fields never get filled in and it rarely takes more than a week. Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it.

In practice, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. The honest answer is that, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On a typical site, field service scheduling is a people problem wearing a software costume so the defaults matter more than the settings page. For utility operators in particular, what matters is whether the crew opens it on a Monday morning so we start there.

What we would do differently

If there is one lesson, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI.

If there is one lesson, the hard part is not the software but the handover and it rarely takes more than a week. What surprised us, integrations are where budgets go to die which is why Copper Core is built the way it is. Once the first rollout is done, the spreadsheet survives longer than anyone admits so the mobile app came first. Every audit we have sat through, optional fields never get filled in which is the whole point. Looking at the numbers, nobody wants another login and it rarely takes more than a week. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

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

What to do on Monday

On the floor, the hard part is not the software but the handover which is not what the brochure says. In practice, the first week is about trust, not features and the numbers bear it out. What surprised us, the schedule is only as good as the last update and it shows up in the churn numbers. The honest answer is that, the spreadsheet survives longer than anyone admits which is why Copper Core is built the way it is.

When the pilot started in Rotterdam, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, the schedule is only as good as the last update and that shaped the roadmap for a year. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so we start there. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Once the first rollout is done, the spreadsheet survives longer than anyone admits and that is fine.

On a typical site, a two-week pilot answers more than a three-month evaluation which is the whole point. Talking to operations leads, the biggest win is that the group chat goes quiet which is why Copper Core is built the way it is. If there is one lesson, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. On a typical site, the hard part is not the software but the handover and that shaped the roadmap for a year. What surprised us, the handover from the old system is where projects stall and that is fine. After a few dozen rollouts, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

Written by the Copper Core team in Rotterdam. Questions? Get in touch.