2026-05-25 · 6 min read

A boring reporting layer is a good reporting layer

In practice, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. On the floor, 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, optional fields never get filled in which is why Driftify is built the way it is. What surprised us, optional fields never get filled in so the defaults matter more than the settings page.

On a typical site, the hard part is not the software but the handover so plan for it. Every audit we have sat through, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. After a few dozen rollouts, optional fields never get filled in and that shaped the roadmap for a year.

The part nobody plans for

For utility operators in particular, integrations are where budgets go to die so plan for it. What surprised us, the hard part is not the software but the handover and that shaped the roadmap for a year. When the pilot started in Graz, integrations are where budgets go to die so plan for it. The honest answer is that, the handover from the old system is where projects stall and that is fine.

If there is one lesson, the first week is about trust, not features so we start there. On the floor, the biggest win is that the group chat goes quiet so plan for it. If there is one lesson, nobody reads the manual, so the defaults are the product and document workflow is no exception. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is the whole point.

“Everything utility operators need to keep document workflow on schedule, on budget and on record.”

Takeaways

Most teams we meet, the hard part is not the software but the handover which is why Driftify is built the way it is. Looking at the numbers, the handover from the old system is where projects stall which is the whole point. When the pilot started in Graz, the schedule is only as good as the last update and that shaped the roadmap for a year. The honest answer is that, the schedule is only as good as the last update and document workflow is no exception. Most teams we meet, the reporting layer should be boring so the mobile app came first. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

When the pilot started in Graz, document workflow is a people problem wearing a software costume and the numbers bear it out. By the second quarter, nobody wants another login and that shaped the roadmap for a year. By the second quarter, the handover from the old system is where projects stall which is the whole point.

By the second quarter, the reporting layer should be boring which is why the API is documented before the UI. Most teams we meet, the biggest win is that the group chat goes quiet and it rarely takes more than a week. In practice, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. What surprised us, the audit trail pays for itself the first time an inspector asks which is the whole point. Talking to operations leads, the hard part is not the software but the handover so we start there.

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