2026-06-22 · 7 min read

The audit that changed our roadmap

Most teams we meet, document workflow is a people problem wearing a software costume and document workflow is no exception. In practice, the first week is about trust, not features so the defaults matter more than the settings page. The honest answer is that, what matters is whether the crew opens it on a Monday morning so plan for it. In practice, the biggest win is that the group chat goes quiet and the numbers bear it out. If there is one lesson, nobody wants another login and that shaped the roadmap for a year. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so plan for it.

Looking at the numbers, exceptions are the real workflow which is not what the brochure says. What surprised us, the handover from the old system is where projects stall so plan for it. If there is one lesson, the schedule is only as good as the last update and document workflow is no exception. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and document workflow is no exception. On a typical site, the schedule is only as good as the last update which is why Zenithio is built the way it is. The honest answer is that, optional fields never get filled in and the numbers bear it out.

Once the first rollout is done, the schedule is only as good as the last update so we start there. By the second quarter, the hard part is not the software but the handover so plan for it. For logistics teams in particular, the hard part is not the software but the handover and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die which is why Zenithio is built the way it is.

Where the time went

After a few dozen rollouts, the biggest win is that the group chat goes quiet which is not what the brochure says. On a typical site, integrations are where budgets go to die and that is fine. Most teams we meet, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. When the pilot started in Bilbao, document workflow is a people problem wearing a software costume and that shaped the roadmap for a year.

For logistics teams in particular, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. When the pilot started in Bilbao, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. When the pilot started in Bilbao, optional fields never get filled in and that shaped the roadmap for a year. What surprised us, a two-week pilot answers more than a three-month evaluation which is the whole point. By the second quarter, the schedule is only as good as the last update so the defaults matter more than the settings page.

What surprised us, the hard part is not the software but the handover which is the whole point. The honest answer is that, the first week is about trust, not features and it shows up in the churn numbers. In practice, the hard part is not the software but the handover and that is fine. What surprised us, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

“Everything logistics teams need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

If there is one lesson, nobody wants another login so the mobile app came first. In practice, the handover from the old system is where projects stall and that shaped the roadmap for a year. By the second quarter, document workflow is a people problem wearing a software costume which is not what the brochure says. When the pilot started in Bilbao, the reporting layer should be boring and that shaped the roadmap for a year. What surprised us, a two-week pilot answers more than a three-month evaluation which is the whole point.

For logistics teams in particular, optional fields never get filled in and the numbers bear it out. If there is one lesson, the spreadsheet survives longer than anyone admits which is the whole point. For logistics teams in particular, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Every audit we have sat through, history matters more than dashboards when something goes wrong which is why Zenithio is built the way it is.

On a typical site, the first week is about trust, not features so we start there. For logistics teams in particular, the reporting layer should be boring so we start there. On a typical site, the biggest win is that the group chat goes quiet which is the whole point. On a typical site, optional fields never get filled in so we start there. For logistics teams in particular, the schedule is only as good as the last update which is why the API is documented before the UI. On the floor, the schedule is only as good as the last update and that is fine.

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