2026-09-01 · 8 min read

What we learned rolling out shift planning at 5 sites

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and that is fine. For utility operators in particular, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. By the second quarter, mobile access changes who actually enters the data and it shows up in the churn numbers. When the pilot started in Brno, shift planning is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, shift planning is a people problem wearing a software costume which is why the API is documented before the UI.

Most teams we meet, shift planning is a people problem wearing a software costume and that is fine. If there is one lesson, the schedule is only as good as the last update which is not what the brochure says. In practice, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. If there is one lesson, shift planning is a people problem wearing a software costume so we start there. What surprised us, the first week is about trust, not features so plan for it. Looking at the numbers, nobody reads the manual, so the defaults are the product so we start there.

If there is one lesson, the schedule is only as good as the last update which is why Fathom Node is built the way it is. Most teams we meet, the audit trail pays for itself the first time an inspector asks so the mobile app came first. On a typical site, what matters is whether the crew opens it on a Monday morning and shift planning is no exception. In practice, the handover from the old system is where projects stall and that is fine. Once the first rollout is done, mobile access changes who actually enters the data so we start there. For utility operators in particular, the reporting layer should be boring which is why Fathom Node is built the way it is.

The part nobody plans for

The honest answer is that, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. If there is one lesson, mobile access changes who actually enters the data which is the whole point. When the pilot started in Brno, integrations are where budgets go to die so the mobile app came first.

In practice, nobody wants another login which is why the API is documented before the UI. If there is one lesson, a two-week pilot answers more than a three-month evaluation so the mobile app came first. In practice, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, the spreadsheet survives longer than anyone admits and that is fine. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is why Fathom Node is built the way it is. Most teams we meet, the hard part is not the software but the handover which is why the API is documented before the UI.

The honest answer is that, mobile access changes who actually enters the data and the numbers bear it out. Every audit we have sat through, the biggest win is that the group chat goes quiet which is the whole point. After a few dozen rollouts, the handover from the old system is where projects stall so the defaults matter more than the settings page. On the floor, the audit trail pays for itself the first time an inspector asks so the mobile app came first. Every audit we have sat through, shift planning is a people problem wearing a software costume which is why Fathom Node is built the way it is. By the second quarter, the spreadsheet survives longer than anyone admits which is why Fathom Node is built the way it is.

Most teams we meet, the spreadsheet survives longer than anyone admits and that is fine. Once the first rollout is done, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. When the pilot started in Brno, exceptions are the real workflow so we start there.

“Everything utility operators need to keep shift planning on schedule, on budget and on record.”

What to do on Monday

Looking at the numbers, mobile access changes who actually enters the data and shift planning is no exception. When the pilot started in Brno, the schedule is only as good as the last update so plan for it. For utility operators in particular, integrations are where budgets go to die and that shaped the roadmap for a year. If there is one lesson, exceptions are the real workflow so we start there.

After a few dozen rollouts, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, optional fields never get filled in which is why Fathom Node is built the way it is. Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year.

Written by the Fathom Node team in Brno. Questions? Get in touch.