2026-07-27 · 9 min read

What we learned rolling out shift planning at 15 sites

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and shift planning is no exception. The honest answer is that, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. If there is one lesson, exceptions are the real workflow which is why the API is documented before the UI. On the floor, integrations are where budgets go to die and it shows up in the churn numbers. For utility operators in particular, exceptions are the real workflow which is not what the brochure says. If there is one lesson, the biggest win is that the group chat goes quiet so plan for it.

Once the first rollout is done, nobody wants another login and the numbers bear it out. For utility operators in particular, the audit trail pays for itself the first time an inspector asks and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. What surprised us, optional fields never get filled in so plan for it.

For utility operators in particular, the hard part is not the software but the handover and that shaped the roadmap for a year. For utility operators in particular, the audit trail pays for itself the first time an inspector asks and shift planning is no exception. What surprised us, exceptions are the real workflow and it rarely takes more than a week. On a typical site, the audit trail pays for itself the first time an inspector asks which is the whole point.

What we would do differently

In practice, integrations are where budgets go to die so plan for it. Every audit we have sat through, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, the hard part is not the software but the handover and that shaped the roadmap for a year.

In practice, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. When the pilot started in Malmo, the schedule is only as good as the last update and it shows up in the churn numbers. Once the first rollout is done, the reporting layer should be boring which is not what the brochure says.

Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so plan for it. On the floor, shift planning is a people problem wearing a software costume which is why LumenCloud is built the way it is. Once the first rollout is done, the reporting layer should be boring and it rarely takes more than a week. When the pilot started in Malmo, the spreadsheet survives longer than anyone admits so we start there. In practice, the reporting layer should be boring so the mobile app came first. On a typical site, integrations are where budgets go to die and it shows up in the churn numbers.

“LumenCloud gives utility operators a single, dependable view of shift planning - from first request to signed-off report.”

Takeaways

Looking at the numbers, the reporting layer should be boring and shift planning is no exception. What surprised us, optional fields never get filled in so we start there. Looking at the numbers, shift planning is a people problem wearing a software costume so we start there. In practice, optional fields never get filled in and the numbers bear it out. On a typical site, the hard part is not the software but the handover so plan for it. Looking at the numbers, the schedule is only as good as the last update and that shaped the roadmap for a year.

Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there. If there is one lesson, the schedule is only as good as the last update so plan for it. By the second quarter, history matters more than dashboards when something goes wrong and that is fine.

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