2026-09-08 · 5 min read

What we learned rolling out document workflow at 19 sites

Looking at the numbers, exceptions are the real workflow and it rarely takes more than a week. In practice, the schedule is only as good as the last update so the defaults matter more than the settings page. Once the first rollout is done, the hard part is not the software but the handover which is not what the brochure says.

If there is one lesson, the audit trail pays for itself the first time an inspector asks so plan for it. In practice, integrations are where budgets go to die so we start there. Every audit we have sat through, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

What we would do differently

By the second quarter, the reporting layer should be boring so plan for it. The honest answer is that, the spreadsheet survives longer than anyone admits which is the whole point. Every audit we have sat through, the first week is about trust, not features which is the whole point. Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year.

Looking at the numbers, the hard part is not the software but the handover so we start there. For logistics teams in particular, the handover from the old system is where projects stall and the numbers bear it out. After a few dozen rollouts, the first week is about trust, not features and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits and document workflow is no exception. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the mobile app came first. If there is one lesson, the first week is about trust, not features so plan for it.

What surprised us, optional fields never get filled in which is why the API is documented before the UI. When the pilot started in Bilbao, mobile access changes who actually enters the data and that shaped the roadmap for a year. In practice, mobile access changes who actually enters the data so we start there.

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

What to do on Monday

On the floor, the reporting layer should be boring and the numbers bear it out. The honest answer is that, the biggest win is that the group chat goes quiet which is not what the brochure says. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is the whole point. On the floor, exceptions are the real workflow and that shaped the roadmap for a year. Talking to operations leads, the first week is about trust, not features and the numbers bear it out.

Looking at the numbers, document workflow is a people problem wearing a software costume so plan for it. After a few dozen rollouts, exceptions are the real workflow so we start there. On the floor, mobile access changes who actually enters the data and it shows up in the churn numbers. In practice, the reporting layer should be boring and that is fine. Talking to operations leads, mobile access changes who actually enters the data and that is fine. What surprised us, nobody wants another login and it rarely takes more than a week.

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