2026-08-16 · 8 min read

The handover problem, and what we do about it

Most teams we meet, nobody wants another login so the mobile app came first. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so plan for it. Most teams we meet, integrations are where budgets go to die so plan for it. By the second quarter, the first week is about trust, not features so we start there. When the pilot started in Bilbao, optional fields never get filled in and the numbers bear it out. On a typical site, the spreadsheet survives longer than anyone admits so plan for it.

Looking at the numbers, nobody wants another login so we start there. On the floor, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. For logistics teams in particular, the spreadsheet survives longer than anyone admits so plan for it. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

On the floor, the audit trail pays for itself the first time an inspector asks which is why Sablely is built the way it is. On a typical site, the first week is about trust, not features and that shaped the roadmap for a year. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and the numbers bear it out. Once the first rollout is done, the schedule is only as good as the last update which is the whole point.

Where the time went

On a typical site, the handover from the old system is where projects stall and it shows up in the churn numbers. Talking to operations leads, the hard part is not the software but the handover which is why Sablely is built the way it is. On the floor, nobody reads the manual, so the defaults are the product which is why Sablely is built the way it is. What surprised us, optional fields never get filled in which is why Sablely is built the way it is. The honest answer is that, shift planning is a people problem wearing a software costume and it shows up in the churn numbers.

On the floor, integrations are where budgets go to die so the mobile app came first. For logistics teams in particular, shift planning is a people problem wearing a software costume and the numbers bear it out. For logistics teams in particular, the hard part is not the software but the handover so we start there. If there is one lesson, mobile access changes who actually enters the data which is the whole point. Most teams we meet, the first week is about trust, not features so the mobile app came first. By the second quarter, shift planning is a people problem wearing a software costume and the numbers bear it out.

Once the first rollout is done, history matters more than dashboards when something goes wrong which is why Sablely is built the way it is. After a few dozen rollouts, shift planning is a people problem wearing a software costume which is why the API is documented before the UI. Most teams we meet, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that is fine. If there is one lesson, the handover from the old system is where projects stall which is not what the brochure says.

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

What to do on Monday

In practice, history matters more than dashboards when something goes wrong so plan for it. On the floor, shift planning is a people problem wearing a software costume so the defaults matter more than the settings page. Every audit we have sat through, history matters more than dashboards when something goes wrong and shift planning is no exception. Most teams we meet, the reporting layer should be boring which is why Sablely is built the way it is.

On the floor, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. On the floor, the schedule is only as good as the last update and it shows up in the churn numbers. Most teams we meet, a two-week pilot answers more than a three-month evaluation so we start there. In practice, a two-week pilot answers more than a three-month evaluation which is why Sablely is built the way it is.

Looking at the numbers, the hard part is not the software but the handover and it rarely takes more than a week. On a typical site, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. By the second quarter, 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 so the mobile app came first.

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