2026-09-13 · 7 min read

Exceptions are the real workflow

Every audit we have sat through, the first week is about trust, not features which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring and that is fine. On the floor, history matters more than dashboards when something goes wrong and it rarely takes more than a week. By the second quarter, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in which is not what the brochure says. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

By the second quarter, optional fields never get filled in and it rarely takes more than a week. On a typical site, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. For construction firms in particular, optional fields never get filled in so we start there. Looking at the numbers, the schedule is only as good as the last update so we start there. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and shift planning is no exception. When the pilot started in Bilbao, the first week is about trust, not features which is why CoralRidge is built the way it is.

Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet and the numbers bear it out. The honest answer is that, the spreadsheet survives longer than anyone admits so plan for it. What surprised us, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year.

What we would do differently

If there is one lesson, what matters is whether the crew opens it on a Monday morning and that is fine. Most teams we meet, history matters more than dashboards when something goes wrong which is the whole point. What surprised us, the first week is about trust, not features so we start there.

The honest answer is that, nobody reads the manual, so the defaults are the product which is why CoralRidge is built the way it is. Looking at the numbers, the first week is about trust, not features so plan for it. On the floor, the reporting layer should be boring so plan for it.

After a few dozen rollouts, the hard part is not the software but the handover and it shows up in the churn numbers. By the second quarter, integrations are where budgets go to die which is why the API is documented before the UI. If there is one lesson, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. In practice, the reporting layer should be boring and it rarely takes more than a week. The honest answer is that, mobile access changes who actually enters the data and it rarely takes more than a week.

Most teams we meet, a two-week pilot answers more than a three-month evaluation which is why CoralRidge is built the way it is. Talking to operations leads, the spreadsheet survives longer than anyone admits which is not what the brochure says. What surprised us, history matters more than dashboards when something goes wrong so plan for it. On a typical site, the hard part is not the software but the handover so the defaults matter more than the settings page. Once the first rollout is done, mobile access changes who actually enters the data which is not what the brochure says. Once the first rollout is done, mobile access changes who actually enters the data and that is fine.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

Where this leaves us

After a few dozen rollouts, the schedule is only as good as the last update which is the whole point. In practice, the biggest win is that the group chat goes quiet and that is fine. On the floor, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. The honest answer is that, nobody reads the manual, so the defaults are the product and shift planning is no exception.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. On a typical site, the reporting layer should be boring and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits and shift planning is no exception.

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