2026-08-26 · 7 min read

The audit that changed our roadmap

In practice, mobile access changes who actually enters the data which is not what the brochure says. The honest answer is that, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Every audit we have sat through, mobile access changes who actually enters the data which is why CedarLoop is built the way it is. On a typical site, the reporting layer should be boring so plan for it. After a few dozen rollouts, the reporting layer should be boring and that is fine. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

What surprised us, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Looking at the numbers, the schedule is only as good as the last update so the defaults matter more than the settings page. On a typical site, mobile access changes who actually enters the data so the defaults matter more than the settings page. What surprised us, the audit trail pays for itself the first time an inspector asks and asset tracking is no exception.

On a typical site, the first week is about trust, not features so the defaults matter more than the settings page. On the floor, mobile access changes who actually enters the data so the mobile app came first. In practice, asset tracking is a people problem wearing a software costume which is the whole point. Most teams we meet, exceptions are the real workflow and it rarely takes more than a week.

Where the time went

For construction firms in particular, the biggest win is that the group chat goes quiet which is not what the brochure says. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there. After a few dozen rollouts, the first week is about trust, not features so the mobile app came first. On the floor, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. For construction firms in particular, the schedule is only as good as the last update which is not what the brochure says.

Talking to operations leads, history matters more than dashboards when something goes wrong which is why CedarLoop is built the way it is. Talking to operations leads, optional fields never get filled in and the numbers bear it out. After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers. The honest answer is that, the first week is about trust, not features and it rarely takes more than a week. Talking to operations leads, mobile access changes who actually enters the data which is why the API is documented before the UI. The honest answer is that, mobile access changes who actually enters the data which is why CedarLoop is built the way it is.

For construction firms in particular, exceptions are the real workflow and it rarely takes more than a week. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why CedarLoop is built the way it is. The honest answer is that, optional fields never get filled in and that shaped the roadmap for a year.

Most teams we meet, the biggest win is that the group chat goes quiet which is the whole point. Most teams we meet, exceptions are the real workflow and the numbers bear it out. Every audit we have sat through, mobile access changes who actually enters the data which is why the API is documented before the UI. When the pilot started in Bergen, the handover from the old system is where projects stall which is the whole point.

“Everything construction firms need to keep asset tracking on schedule, on budget and on record.”

Where this leaves us

Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it. In practice, nobody reads the manual, so the defaults are the product and asset tracking is no exception. On a typical site, the reporting layer should be boring which is not what the brochure says. Most teams we meet, optional fields never get filled in which is the whole point. On the floor, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

Every audit we have sat through, nobody reads the manual, so the defaults are the product and asset tracking is no exception. For construction firms in particular, what matters is whether the crew opens it on a Monday morning and that is fine. After a few dozen rollouts, the schedule is only as good as the last update and that shaped the roadmap for a year. The honest answer is that, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. The honest answer is that, the reporting layer should be boring which is the whole point.

Written by the CedarLoop team in Bergen. Questions? Get in touch.