2026-09-05 · 5 min read

What we learned rolling out shift planning at 21 sites

After a few dozen rollouts, the biggest win is that the group chat goes quiet and that is fine. What surprised us, shift planning is a people problem wearing a software costume so the defaults matter more than the settings page. On the floor, the audit trail pays for itself the first time an inspector asks and shift planning is no exception. By the second quarter, the schedule is only as good as the last update which is not what the brochure says. On a typical site, the biggest win is that the group chat goes quiet which is the whole point.

On the floor, shift planning is a people problem wearing a software costume which is why the API is documented before the UI. On the floor, the first week is about trust, not features so we start there. In practice, exceptions are the real workflow and it rarely takes more than a week. When the pilot started in Graz, the first week is about trust, not features which is why the API is documented before the UI. Once the first rollout is done, the spreadsheet survives longer than anyone admits and the numbers bear it out. In practice, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

The part nobody plans for

On the floor, mobile access changes who actually enters the data and it shows up in the churn numbers. If there is one lesson, mobile access changes who actually enters the data and that is fine. For property managers in particular, mobile access changes who actually enters the data which is why the API is documented before the UI. By the second quarter, nobody wants another login which is not what the brochure says. The honest answer is that, nobody wants another login and that shaped the roadmap for a year. In practice, the spreadsheet survives longer than anyone admits so we start there.

In practice, the hard part is not the software but the handover so the mobile app came first. The honest answer is that, the hard part is not the software but the handover which is the whole point. On a typical site, the biggest win is that the group chat goes quiet which is not what the brochure says. On a typical site, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. By the second quarter, the handover from the old system is where projects stall and it shows up in the churn numbers. On a typical site, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

By the second quarter, shift planning is a people problem wearing a software costume which is not what the brochure says. On a typical site, the handover from the old system is where projects stall and it rarely takes more than a week. On the floor, the reporting layer should be boring so plan for it. For property managers in particular, nobody reads the manual, so the defaults are the product and shift planning is no exception. On the floor, the audit trail pays for itself the first time an inspector asks and shift planning is no exception. Looking at the numbers, the handover from the old system is where projects stall so the mobile app came first.

In practice, what matters is whether the crew opens it on a Monday morning which is why Meridian is built the way it is. The honest answer is that, the spreadsheet survives longer than anyone admits and that is fine. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

“Meridian gives property managers a single, dependable view of shift planning - from first request to signed-off report.”

Where this leaves us

Looking at the numbers, history matters more than dashboards when something goes wrong and the numbers bear it out. What surprised us, shift planning is a people problem wearing a software costume which is why Meridian is built the way it is. The honest answer is that, the spreadsheet survives longer than anyone admits and shift planning is no exception. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

When the pilot started in Graz, mobile access changes who actually enters the data so plan for it. On the floor, mobile access changes who actually enters the data so the mobile app came first. Most teams we meet, the biggest win is that the group chat goes quiet which is why Meridian is built the way it is.

Written by the Meridian team in Graz. Questions? Get in touch.