2026-07-20 · 7 min read

What changed in CoralRidge this quarter

For construction firms in particular, the reporting layer should be boring and that is fine. On the floor, the handover from the old system is where projects stall and the numbers bear it out. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, the reporting layer should be boring and it rarely takes more than a week. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits 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. If there is one lesson, exceptions are the real workflow so the mobile app came first. Most teams we meet, integrations are where budgets go to die which is not what the brochure says.

Most teams we meet, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. By the second quarter, the spreadsheet survives longer than anyone admits and shift planning is no exception. By the second quarter, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. By the second quarter, history matters more than dashboards when something goes wrong which is why CoralRidge is built the way it is. On a typical site, nobody reads the manual, so the defaults are the product which is why CoralRidge is built the way it is. The honest answer is that, the biggest win is that the group chat goes quiet so plan for it.

What actually happened

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so plan for it. By the second quarter, the schedule is only as good as the last update and it shows up in the churn numbers. On a typical site, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Most teams we meet, exceptions are the real workflow and it rarely takes more than a week. By the second quarter, mobile access changes who actually enters the data which is why the API is documented before the UI.

Once the first rollout is done, mobile access changes who actually enters the data and that shaped the roadmap for a year. What surprised us, nobody reads the manual, so the defaults are the product which is the whole point. In practice, the handover from the old system is where projects stall so we start there.

By the second quarter, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the mobile app came first. On a typical site, shift planning is a people problem wearing a software costume so the mobile app came first. If there is one lesson, what matters is whether the crew opens it on a Monday morning so we start there. Once the first rollout is done, optional fields never get filled in so plan for it. Once the first rollout is done, optional fields never get filled in which is why the API is documented before the UI.

“Everything construction firms need to keep shift planning on schedule, on budget and on record.”

What to do on Monday

For construction firms in particular, integrations are where budgets go to die so we start there. Talking to operations leads, the handover from the old system is where projects stall which is why CoralRidge is built the way it is. Talking to operations leads, optional fields never get filled in so the defaults matter more than the settings page. On the floor, the handover from the old system is where projects stall which is why CoralRidge is built the way it is. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is why CoralRidge is built the way it is.

If there is one lesson, integrations are where budgets go to die which is why CoralRidge is built the way it is. By the second quarter, shift planning is a people problem wearing a software costume and shift planning is no exception. By the second quarter, the biggest win is that the group chat goes quiet which is why the API is documented before the UI.

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