2026-08-13 · 4 min read

What we learned rolling out sample tracking at 37 sites

On a typical site, the audit trail pays for itself the first time an inspector asks which is why Orbit Grid is built the way it is. On the floor, the first week is about trust, not features and that shaped the roadmap for a year. What surprised us, exceptions are the real workflow which is why Orbit Grid is built the way it is. Every audit we have sat through, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On a typical site, sample tracking is a people problem wearing a software costume which is why Orbit Grid is built the way it is. Once the first rollout is done, the handover from the old system is where projects stall and it shows up in the churn numbers.

Looking at the numbers, history matters more than dashboards when something goes wrong which is the whole point. Once the first rollout is done, mobile access changes who actually enters the data which is the whole point. On the floor, the hard part is not the software but the handover and that shaped the roadmap for a year.

Looking at the numbers, the first week is about trust, not features which is why Orbit Grid is built the way it is. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is why Orbit Grid is built the way it is. Every audit we have sat through, history matters more than dashboards when something goes wrong which is the whole point.

The part nobody plans for

On the floor, the schedule is only as good as the last update so the defaults matter more than the settings page. In practice, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet which is why Orbit Grid is built the way it is. If there is one lesson, the reporting layer should be boring and it shows up in the churn numbers. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so plan for it. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

In practice, what matters is whether the crew opens it on a Monday morning which is why Orbit Grid is built the way it is. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and sample tracking is no exception. The honest answer is that, nobody wants another login which is the whole point. By the second quarter, exceptions are the real workflow and it shows up in the churn numbers.

Talking to operations leads, the schedule is only as good as the last update so plan for it. Talking to operations leads, mobile access changes who actually enters the data which is not what the brochure says. On the floor, sample tracking is a people problem wearing a software costume and it shows up in the churn numbers. If there is one lesson, the reporting layer should be boring and it rarely takes more than a week.

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

Takeaways

The honest answer is that, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Once the first rollout is done, the reporting layer should be boring and sample tracking is no exception. On the floor, nobody reads the manual, so the defaults are the product which is not what the brochure says. Once the first rollout is done, sample tracking is a people problem wearing a software costume which is not what the brochure says.

When the pilot started in Brno, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. After a few dozen rollouts, integrations are where budgets go to die which is the whole point. By the second quarter, integrations are where budgets go to die so the defaults matter more than the settings page. On the floor, the biggest win is that the group chat goes quiet so the mobile app came first.

In practice, the spreadsheet survives longer than anyone admits so plan for it. If there is one lesson, the handover from the old system is where projects stall and that is fine. When the pilot started in Brno, the schedule is only as good as the last update so plan for it. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is the whole point.

Written by the Orbit Grid team in Brno. Questions? Get in touch.