2026-09-27 · 5 min read

What we learned rolling out document workflow at 39 sites

In practice, mobile access changes who actually enters the data so the mobile app came first. On a typical site, nobody wants another login which is why the API is documented before the UI. Talking to operations leads, a two-week pilot answers more than a three-month evaluation so we start there. Talking to operations leads, mobile access changes who actually enters the data and that is fine.

Every audit we have sat through, integrations are where budgets go to die and that is fine. Once the first rollout is done, document workflow is a people problem wearing a software costume and that is fine. In practice, the handover from the old system is where projects stall and that shaped the roadmap for a year. 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, the hard part is not the software but the handover and document workflow is no exception. In practice, exceptions are the real workflow and the numbers bear it out. When the pilot started in Bologna, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. By the second quarter, a two-week pilot answers more than a three-month evaluation 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 so the defaults matter more than the settings page. On a typical site, the biggest win is that the group chat goes quiet so the mobile app came first.

What we would do differently

Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. The honest answer is that, integrations are where budgets go to die and document workflow is no exception.

In practice, mobile access changes who actually enters the data which is the whole point. When the pilot started in Bologna, the first week is about trust, not features and document workflow is no exception. Most teams we meet, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

“Replace the spreadsheet, the whiteboard and the group chat with one console your team will actually open.”

Takeaways

The honest answer is that, nobody wants another login which is the whole point. After a few dozen rollouts, the hard part is not the software but the handover which is not what the brochure says. On the floor, document workflow is a people problem wearing a software costume and it rarely takes more than a week.

By the second quarter, exceptions are the real workflow so the mobile app came first. On the floor, what matters is whether the crew opens it on a Monday morning which is why Alderhq is built the way it is. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Every audit we have sat through, the handover from the old system is where projects stall and that is fine.

For logistics teams in particular, the biggest win is that the group chat goes quiet so the mobile app came first. Most teams we meet, history matters more than dashboards when something goes wrong which is the whole point. Every audit we have sat through, the spreadsheet survives longer than anyone admits which is the whole point. On the floor, the handover from the old system is where projects stall and it rarely takes more than a week.

Written by the Alderhq team in Bologna. Questions? Get in touch.