2026-06-12 · 4 min read

What we learned rolling out shift planning at 4 sites

On a typical site, the hard part is not the software but the handover and the numbers bear it out. Once the first rollout is done, mobile access changes who actually enters the data and it rarely takes more than a week. By the second quarter, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

What surprised us, the first week is about trust, not features and it shows up in the churn numbers. What surprised us, exceptions are the real workflow and it shows up in the churn numbers. For construction firms in particular, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. What surprised us, the reporting layer should be boring and the numbers bear it out. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Talking to operations leads, nobody reads the manual, so the defaults are the product so plan for it.

Where the time went

What surprised us, nobody wants another login so plan for it. When the pilot started in Bilbao, the hard part is not the software but the handover and that shaped the roadmap for a year. What surprised us, mobile access changes who actually enters the data and that is fine.

When the pilot started in Bilbao, the reporting layer should be boring and that shaped the roadmap for a year. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so we start there. What surprised us, the first week is about trust, not features so plan for it. What surprised us, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

On the floor, integrations are where budgets go to die and the numbers bear it out. On a typical site, the spreadsheet survives longer than anyone admits which is not what the brochure says. What surprised us, the handover from the old system is where projects stall so the mobile app came first. When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits so we start there.

“CoralRidge gives construction firms a single, dependable view of shift planning - from first request to signed-off report.”

Takeaways

Once the first rollout is done, integrations are where budgets go to die which is the whole point. What surprised us, the biggest win is that the group chat goes quiet and shift planning is no exception. Talking to operations leads, the schedule is only as good as the last update and the numbers bear it out. By the second quarter, nobody wants another login and it shows up in the churn numbers.

By the second quarter, the spreadsheet survives longer than anyone admits which is not what the brochure says. When the pilot started in Bilbao, shift planning is a people problem wearing a software costume and it rarely takes more than a week. On the floor, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

On the floor, the reporting layer should be boring and that is fine. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. For construction firms in particular, history matters more than dashboards when something goes wrong which is the whole point.

Written by the CoralRidge team in Bilbao. Questions? Get in touch.