2026-07-18 · 8 min read

Why the spreadsheet always wins the first month

Looking at the numbers, the hard part is not the software but the handover so the mobile app came first. If there is one lesson, the handover from the old system is where projects stall so we start there. In practice, the hard part is not the software but the handover which is why the API is documented before the UI. By the second quarter, mobile access changes who actually enters the data which is why Copperhq is built the way it is.

Talking to operations leads, mobile access changes who actually enters the data and that shaped the roadmap for a year. Every audit we have sat through, history matters more than dashboards when something goes wrong and shift planning is no exception. On the floor, the reporting layer should be boring which is the whole point. The honest answer is that, the hard part is not the software but the handover which is the whole point.

What actually happened

The honest answer is that, the reporting layer should be boring which is the whole point. Every audit we have sat through, the biggest win is that the group chat goes quiet so we start there. For logistics teams in particular, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Once the first rollout is done, nobody wants another login which is why Copperhq is built the way it is. On a typical site, exceptions are the real workflow and that is fine.

In practice, optional fields never get filled in which is not what the brochure says. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. If there is one lesson, integrations are where budgets go to die so the defaults matter more than the settings page. Looking at the numbers, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, the schedule is only as good as the last update which is why the API is documented before the UI.

By the second quarter, 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, nobody reads the manual, so the defaults are the product which is why Copperhq is built the way it is. On a typical site, history matters more than dashboards when something goes wrong so we start there. In practice, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

If there is one lesson, the schedule is only as good as the last update so the defaults matter more than the settings page. Most teams we meet, shift planning is a people problem wearing a software costume so we start there. On the floor, the hard part is not the software but the handover and that is fine.

“Plan, dispatch and reconcile in one place. Copperhq connects to the systems you already run and stays out of the way.”

Where this leaves us

Talking to operations leads, history matters more than dashboards when something goes wrong and it rarely takes more than a week. For logistics teams in particular, the reporting layer should be boring which is not what the brochure says. What surprised us, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. On the floor, optional fields never get filled in and the numbers bear it out.

Looking at the numbers, history matters more than dashboards when something goes wrong which is not what the brochure says. What surprised us, the schedule is only as good as the last update and that is fine. On a typical site, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Once the first rollout is done, mobile access changes who actually enters the data which is why Copperhq is built the way it is. Once the first rollout is done, the reporting layer should be boring so the defaults matter more than the settings page. On the floor, the hard part is not the software but the handover and that shaped the roadmap for a year.

On a typical site, the biggest win is that the group chat goes quiet and that is fine. In practice, history matters more than dashboards when something goes wrong which is not what the brochure says. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week.

Written by the Copperhq team in Porto. Questions? Get in touch.