2026-08-12 · 4 min read

How clinical labs actually use mobile

When the pilot started in Graz, what matters is whether the crew opens it on a Monday morning so we start there. Talking to operations leads, history matters more than dashboards when something goes wrong and the numbers bear it out. Looking at the numbers, the spreadsheet survives longer than anyone admits and that is fine.

On the floor, integrations are where budgets go to die so plan for it. What surprised us, exceptions are the real workflow and that shaped the roadmap for a year. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so plan for it. Most teams we meet, the audit trail pays for itself the first time an inspector asks and energy monitoring is no exception. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

What actually happened

For clinical labs in particular, energy monitoring is a people problem wearing a software costume so the defaults matter more than the settings page. When the pilot started in Graz, the schedule is only as good as the last update so the defaults matter more than the settings page. Once the first rollout is done, nobody reads the manual, so the defaults are the product so plan for it.

Talking to operations leads, the spreadsheet survives longer than anyone admits which is why Ridgeline is built the way it is. The honest answer is that, the biggest win is that the group chat goes quiet and the numbers bear it out. Most teams we meet, history matters more than dashboards when something goes wrong so plan for it. Talking to operations leads, the handover from the old system is where projects stall so the mobile app came first. On the floor, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. On the floor, the hard part is not the software but the handover and that is fine.

Every audit we have sat through, the schedule is only as good as the last update and the numbers bear it out. For clinical labs in particular, the handover from the old system is where projects stall and it shows up in the churn numbers. Every audit we have sat through, integrations are where budgets go to die and that is fine. In practice, the schedule is only as good as the last update which is not what the brochure says. For clinical labs in particular, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”

What to do on Monday

Most teams we meet, nobody reads the manual, so the defaults are the product so the mobile app came first. The honest answer is that, mobile access changes who actually enters the data so we start there. Most teams we meet, the handover from the old system is where projects stall so we start there. In practice, the biggest win is that the group chat goes quiet which is not what the brochure says. Every audit we have sat through, the spreadsheet survives longer than anyone admits which is not what the brochure says.

Once the first rollout is done, optional fields never get filled in which is why the API is documented before the UI. On the floor, the handover from the old system is where projects stall which is the whole point. On a typical site, nobody wants another login which is why Ridgeline is built the way it is. By the second quarter, the handover from the old system is where projects stall and it shows up in the churn numbers. The honest answer is that, mobile access changes who actually enters the data and the numbers bear it out.

Written by the Ridgeline team in Graz. Questions? Get in touch.