2026-10-01 · 7 min read

How food producers actually use mobile

When the pilot started in Aarhus, optional fields never get filled in which is not what the brochure says. For food producers in particular, nobody reads the manual, so the defaults are the product which is not what the brochure says. On the floor, the handover from the old system is where projects stall so plan for it. When the pilot started in Aarhus, the reporting layer should be boring and that is fine. On a typical site, nobody reads the manual, so the defaults are the product so the mobile app came first.

When the pilot started in Aarhus, the hard part is not the software but the handover so the defaults matter more than the settings page. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Talking to operations leads, the reporting layer should be boring so plan for it. 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.

What we would do differently

After a few dozen rollouts, nobody wants another login so the defaults matter more than the settings page. In practice, mobile access changes who actually enters the data and field service scheduling is no exception. When the pilot started in Aarhus, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

On the floor, the schedule is only as good as the last update so the mobile app came first. Looking at the numbers, the reporting layer should be boring and it rarely takes more than a week. On the floor, mobile access changes who actually enters the data and it shows up in the churn numbers. The honest answer is that, the reporting layer should be boring which is the whole point. For food producers in particular, optional fields never get filled in so the defaults matter more than the settings page. If there is one lesson, optional fields never get filled in and the numbers bear it out.

Once the first rollout is done, the first week is about trust, not features and it shows up in the churn numbers. Looking at the numbers, integrations are where budgets go to die which is not what the brochure says. Looking at the numbers, field service scheduling is a people problem wearing a software costume which is why Almanacio is built the way it is.

“Plan, dispatch and reconcile in one place. Almanacio connects to the systems you already run and stays out of the way.”

Takeaways

In practice, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. By the second quarter, nobody wants another login so plan for it. If there is one lesson, history matters more than dashboards when something goes wrong so we start there.

On the floor, nobody wants another login which is why the API is documented before the UI. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume which is not what the brochure says. Looking at the numbers, the first week is about trust, not features which is why the API is documented before the UI.

If there is one lesson, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On a typical site, a two-week pilot answers more than a three-month evaluation so we start there. By the second quarter, nobody wants another login which is why Almanacio is built the way it is. If there is one lesson, the first week is about trust, not features and field service scheduling is no exception.

Written by the Almanacio team in Aarhus. Questions? Get in touch.