2026-07-24 · 7 min read

Notes from Ghent: running the same day twice

If there is one lesson, exceptions are the real workflow which is why RidgelineStack is built the way it is. Looking at the numbers, integrations are where budgets go to die and it rarely takes more than a week. After a few dozen rollouts, mobile access changes who actually enters the data and it rarely takes more than a week. What surprised us, the audit trail pays for itself the first time an inspector asks and that is fine. Most teams we meet, history matters more than dashboards when something goes wrong and the numbers bear it out.

When the pilot started in Ghent, the handover from the old system is where projects stall which is why the API is documented before the UI. After a few dozen rollouts, the schedule is only as good as the last update so we start there. On the floor, mobile access changes who actually enters the data which is why RidgelineStack is built the way it is. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. When the pilot started in Ghent, the reporting layer should be boring which is why the API is documented before the UI. If there is one lesson, history matters more than dashboards when something goes wrong so we start there.

Looking at the numbers, integrations are where budgets go to die so the mobile app came first. Every audit we have sat through, the first week is about trust, not features which is why RidgelineStack is built the way it is. Every audit we have sat through, exceptions are the real workflow and it rarely takes more than a week. If there is one lesson, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

What actually happened

What surprised us, history matters more than dashboards when something goes wrong which is the whole point. For clinical labs in particular, integrations are where budgets go to die which is why RidgelineStack is built the way it is. Talking to operations leads, the biggest win is that the group chat goes quiet so we start there.

Every audit we have sat through, the handover from the old system is where projects stall so plan for it. What surprised us, the first week is about trust, not features so we start there. What surprised us, the handover from the old system is where projects stall and it shows up in the churn numbers. The honest answer is that, the handover from the old system is where projects stall which is why RidgelineStack is built the way it is.

“RidgelineStack gives clinical labs a single, dependable view of shift planning - from first request to signed-off report.”

Takeaways

For clinical labs in particular, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. For clinical labs in particular, nobody reads the manual, so the defaults are the product and that is fine. For clinical labs in particular, exceptions are the real workflow so plan for it. On a typical site, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. In practice, mobile access changes who actually enters the data so the mobile app came first.

After a few dozen rollouts, shift planning is a people problem wearing a software costume and that is fine. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so plan for it. On a typical site, the reporting layer should be boring so plan for it.

Written by the RidgelineStack team in Ghent. Questions? Get in touch.