2026-08-12 · 6 min read

Permissions are a product decision

On the floor, optional fields never get filled in which is not what the brochure says. When the pilot started in Ghent, the hard part is not the software but the handover which is why the API is documented before the UI. Once the first rollout is done, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. On a typical site, mobile access changes who actually enters the data and that is fine.

What surprised us, what matters is whether the crew opens it on a Monday morning so plan for it. In practice, what matters is whether the crew opens it on a Monday morning so we start there. What surprised us, the schedule is only as good as the last update so the mobile app came first. By the second quarter, the schedule is only as good as the last update and the numbers bear it out. After a few dozen rollouts, the schedule is only as good as the last update and the numbers bear it out.

What we would do differently

Talking to operations leads, what matters is whether the crew opens it on a Monday morning so plan for it. In practice, the audit trail pays for itself the first time an inspector asks and that is fine. Once the first rollout is done, mobile access changes who actually enters the data and that is fine. Looking at the numbers, the handover from the old system is where projects stall which is not what the brochure says.

Every audit we have sat through, nobody reads the manual, so the defaults are the product and that is fine. On the floor, the handover from the old system is where projects stall which is why the API is documented before the UI. Every audit we have sat through, the spreadsheet survives longer than anyone admits which is not what the brochure says. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

By the second quarter, optional fields never get filled in and that is fine. By the second quarter, the reporting layer should be boring and it rarely takes more than a week. Talking to operations leads, optional fields never get filled in and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Talking to operations leads, integrations are where budgets go to die and that shaped the roadmap for a year.

The honest answer is that, exceptions are the real workflow and it rarely takes more than a week. On the floor, exceptions are the real workflow so the defaults matter more than the settings page. In practice, nobody wants another login which is why the API is documented before the UI.

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

What to do on Monday

After a few dozen rollouts, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, fleet telemetry is a people problem wearing a software costume so the mobile app came first. Talking to operations leads, the reporting layer should be boring and that is fine. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is not what the brochure says.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is the whole point. Most teams we meet, the hard part is not the software but the handover which is why Almanac Cloud is built the way it is. Once the first rollout is done, integrations are where budgets go to die and it shows up in the churn numbers.

Talking to operations leads, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. On the floor, the schedule is only as good as the last update so plan for it. For property managers in particular, the schedule is only as good as the last update which is why the API is documented before the UI.

Written by the Almanac Cloud team in Ghent. Questions? Get in touch.