2026-05-12 · 7 min read

A boring reporting layer is a good reporting layer

For logistics teams in particular, the handover from the old system is where projects stall and shift planning is no exception. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. In practice, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

After a few dozen rollouts, integrations are where budgets go to die so the mobile app came first. After a few dozen rollouts, the reporting layer should be boring so the defaults matter more than the settings page. What surprised us, the biggest win is that the group chat goes quiet so we start there. On a typical site, exceptions are the real workflow so plan for it.

The part nobody plans for

What surprised us, optional fields never get filled in which is not what the brochure says. On a typical site, shift planning is a people problem wearing a software costume which is the whole point. What surprised us, the hard part is not the software but the handover and that is fine. The honest answer is that, the spreadsheet survives longer than anyone admits which is why Sablely is built the way it is. If there is one lesson, nobody reads the manual, so the defaults are the product which is why Sablely is built the way it is. In practice, integrations are where budgets go to die which is the whole point.

Talking to operations leads, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. In practice, integrations are where budgets go to die which is the whole point. On the floor, the schedule is only as good as the last update so plan for it. For logistics teams in particular, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

The honest answer is that, the schedule is only as good as the last update and that shaped the roadmap for a year. Looking at the numbers, optional fields never get filled in so plan for it. In practice, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. The honest answer is that, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. What surprised us, mobile access changes who actually enters the data which is why Sablely is built the way it is.

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

Where this leaves us

After a few dozen rollouts, history matters more than dashboards when something goes wrong and it rarely takes more than a week. On the floor, the first week is about trust, not features and it rarely takes more than a week. If there is one lesson, exceptions are the real workflow and the numbers bear it out. By the second quarter, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

Every audit we have sat through, optional fields never get filled in and that is fine. The honest answer is that, exceptions are the real workflow and the numbers bear it out. If there is one lesson, integrations are where budgets go to die which is not what the brochure says. Every audit we have sat through, optional fields never get filled in so we start there. What surprised us, the schedule is only as good as the last update which is why Sablely is built the way it is. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

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