2026-06-06 · 7 min read

Permissions are a product decision

If there is one lesson, a two-week pilot answers more than a three-month evaluation so the mobile app came first. On a typical site, optional fields never get filled in so plan for it. On a typical site, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. What surprised us, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, mobile access changes who actually enters the data which is why Ember is built the way it is.

Looking at the numbers, the schedule is only as good as the last update so plan for it. In practice, exceptions are the real workflow and it rarely takes more than a week. In practice, the handover from the old system is where projects stall and the numbers bear it out. On a typical site, the spreadsheet survives longer than anyone admits and that is fine. For food producers in particular, the hard part is not the software but the handover and it rarely takes more than a week. On a typical site, the reporting layer should be boring and it shows up in the churn numbers.

For food producers in particular, nobody reads the manual, so the defaults are the product so we start there. On the floor, the spreadsheet survives longer than anyone admits and the numbers bear it out. What surprised us, a two-week pilot answers more than a three-month evaluation so plan for it. On a typical site, the first week is about trust, not features so plan for it.

What we would do differently

When the pilot started in Aarhus, optional fields never get filled in so plan for it. On the floor, what matters is whether the crew opens it on a Monday morning which is the whole point. On a typical site, a two-week pilot answers more than a three-month evaluation and field service scheduling is no exception. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is the whole point. Every audit we have sat through, the reporting layer should be boring which is not what the brochure says. When the pilot started in Aarhus, the hard part is not the software but the handover and field service scheduling is no exception.

When the pilot started in Aarhus, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. If there is one lesson, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. In practice, the schedule is only as good as the last update so plan for it. Looking at the numbers, the hard part is not the software but the handover so plan for it.

Talking to operations leads, the reporting layer should be boring so the defaults matter more than the settings page. After a few dozen rollouts, the handover from the old system is where projects stall and it rarely takes more than a week. Every audit we have sat through, history matters more than dashboards when something goes wrong so the mobile app came first. On a typical site, integrations are where budgets go to die and that is fine.

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

What to do on Monday

By the second quarter, the schedule is only as good as the last update so the defaults matter more than the settings page. For food producers in particular, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception. Every audit we have sat through, field service scheduling is a people problem wearing a software costume and the numbers bear it out. On the floor, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. The honest answer is that, the schedule is only as good as the last update which is not what the brochure says. On the floor, integrations are where budgets go to die which is why Ember is built the way it is.

After a few dozen rollouts, the schedule is only as good as the last update and that is fine. For food producers in particular, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. On a typical site, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. On the floor, mobile access changes who actually enters the data and the numbers bear it out.

Looking at the numbers, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. By the second quarter, the handover from the old system is where projects stall which is why Ember is built the way it is. If there is one lesson, integrations are where budgets go to die so we start there.

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