2026-08-24 · 4 min read

The audit that changed our roadmap

In practice, the spreadsheet survives longer than anyone admits so plan for it. In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. Every audit we have sat through, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

What surprised us, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. By the second quarter, mobile access changes who actually enters the data so plan for it. When the pilot started in Nantes, optional fields never get filled in and the numbers bear it out. When the pilot started in Nantes, what matters is whether the crew opens it on a Monday morning so we start there.

What we would do differently

On a typical site, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. If there is one lesson, the hard part is not the software but the handover which is why KestrelCore is built the way it is. On a typical site, exceptions are the real workflow and the numbers bear it out. On a typical site, a two-week pilot answers more than a three-month evaluation which is the whole point.

Every audit we have sat through, the spreadsheet survives longer than anyone admits so plan for it. On the floor, the spreadsheet survives longer than anyone admits which is the whole point. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Once the first rollout is done, the first week is about trust, not features and that is fine. In practice, the first week is about trust, not features and it rarely takes more than a week.

Most teams we meet, the biggest win is that the group chat goes quiet so plan for it. On the floor, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Talking to operations leads, 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, nobody wants another login and the numbers bear it out.

“Everything logistics teams need to keep shift planning on schedule, on budget and on record.”

Takeaways

When the pilot started in Nantes, a two-week pilot answers more than a three-month evaluation and that is fine. Every audit we have sat through, integrations are where budgets go to die so we start there. On the floor, the biggest win is that the group chat goes quiet and shift planning is no exception.

Once the first rollout is done, nobody wants another login so plan for it. The honest answer is that, the hard part is not the software but the handover so the defaults matter more than the settings page. For logistics teams in particular, the audit trail pays for itself the first time an inspector asks which is why KestrelCore is built the way it is.

If there is one lesson, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. After a few dozen rollouts, the hard part is not the software but the handover and that is fine. On the floor, exceptions are the real workflow and that shaped the roadmap for a year. What surprised us, optional fields never get filled in which is not what the brochure says.

Written by the KestrelCore team in Nantes. Questions? Get in touch.