2026-06-27 · 4 min read

What changed in KestrelCore this quarter

On a typical site, the handover from the old system is where projects stall so the defaults matter more than the settings page. On a typical site, the hard part is not the software but the handover so the defaults matter more than the settings page. If there is one lesson, shift planning is a people problem wearing a software costume which is why KestrelCore is built the way it is. Most teams we meet, mobile access changes who actually enters the data which is why KestrelCore is built the way it is.

Most teams we meet, the biggest win is that the group chat goes quiet so plan for it. For logistics teams in particular, the handover from the old system is where projects stall so the defaults matter more than the settings page. Most teams we meet, mobile access changes who actually enters the data so plan for it. Most teams we meet, the audit trail pays for itself the first time an inspector asks and that is fine. Most teams we meet, exceptions are the real workflow so plan for it.

The part nobody plans for

Once the first rollout is done, the handover from the old system is where projects stall so plan for it. On a typical site, the spreadsheet survives longer than anyone admits which is not what the brochure says. Every audit we have sat through, the hard part is not the software but the handover and it shows up in the churn numbers.

The honest answer is that, a two-week pilot answers more than a three-month evaluation and that is fine. By the second quarter, the first week is about trust, not features which is the whole point. Talking to operations leads, the handover from the old system is where projects stall so plan for it. If there is one lesson, a two-week pilot answers more than a three-month evaluation and shift planning is no exception.

The honest answer is that, history matters more than dashboards when something goes wrong which is the whole point. For logistics teams in particular, optional fields never get filled in so plan for it. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in and that shaped the roadmap for a year.

Talking to operations leads, history matters more than dashboards when something goes wrong which is why KestrelCore is built the way it is. Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is why KestrelCore is built the way it is. In practice, the handover from the old system is where projects stall which is the whole point.

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

Takeaways

Looking at the numbers, a two-week pilot answers more than a three-month evaluation so we start there. Every audit we have sat through, the schedule is only as good as the last update so the defaults matter more than the settings page. By the second quarter, the reporting layer should be boring so the defaults matter more than the settings page. After a few dozen rollouts, history matters more than dashboards when something goes wrong and that is fine.

Once the first rollout is done, the schedule is only as good as the last update which is why the API is documented before the UI. For logistics teams in particular, the biggest win is that the group chat goes quiet which is the whole point. For logistics teams in particular, mobile access changes who actually enters the data and that shaped the roadmap for a year. On the floor, the first week is about trust, not features which is why the API is documented before the UI.

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