2026-06-01 · 6 min read

The audit that changed our roadmap

Most teams we meet, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is not what the brochure says. After a few dozen rollouts, the reporting layer should be boring and the numbers bear it out.

By the second quarter, the hard part is not the software but the handover and warehouse routing is no exception. By the second quarter, the first week is about trust, not features and that is fine. For field service crews in particular, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Talking to operations leads, the reporting layer should be boring which is the whole point.

Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is the whole point. If there is one lesson, the schedule is only as good as the last update so the defaults matter more than the settings page. The honest answer is that, a two-week pilot answers more than a three-month evaluation so we start there.

The part nobody plans for

Talking to operations leads, mobile access changes who actually enters the data so the defaults matter more than the settings page. What surprised us, the spreadsheet survives longer than anyone admits which is not what the brochure says. Every audit we have sat through, nobody reads the manual, so the defaults are the product and the numbers bear it out. Talking to operations leads, nobody reads the manual, so the defaults are the product so the mobile app came first. On the floor, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, the spreadsheet survives longer than anyone admits so the mobile app came first.

Every audit we have sat through, nobody wants another login and it rarely takes more than a week. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is why Coral Point is built the way it is. After a few dozen rollouts, history matters more than dashboards when something goes wrong so plan for it. Every audit we have sat through, the reporting layer should be boring which is the whole point. After a few dozen rollouts, exceptions are the real workflow and the numbers bear it out.

“Coral Point gives field service crews a single, dependable view of warehouse routing - from first request to signed-off report.”

Where this leaves us

Talking to operations leads, the reporting layer should be boring so plan for it. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so the mobile app came first. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is the whole point. Talking to operations leads, the schedule is only as good as the last update and warehouse routing is no exception.

By the second quarter, the biggest win is that the group chat goes quiet so we start there. On a typical site, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. When the pilot started in Rotterdam, the reporting layer should be boring and it rarely takes more than a week. On a typical site, exceptions are the real workflow so we start there.

When the pilot started in Rotterdam, nobody reads the manual, so the defaults are the product and warehouse routing is no exception. Looking at the numbers, optional fields never get filled in and warehouse routing is no exception. Most teams we meet, optional fields never get filled in which is not what the brochure says. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Talking to operations leads, mobile access changes who actually enters the data and that is fine.

Written by the Coral Point team in Rotterdam. Questions? Get in touch.