2026-07-30 · 7 min read

The handover problem, and what we do about it

Once the first rollout is done, nobody reads the manual, so the defaults are the product so we start there. Every audit we have sat through, mobile access changes who actually enters the data which is not what the brochure says. If there is one lesson, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. On a typical site, exceptions are the real workflow and that is fine. Looking at the numbers, the biggest win is that the group chat goes quiet which is not what the brochure says.

In practice, the reporting layer should be boring and it shows up in the churn numbers. By the second quarter, history matters more than dashboards when something goes wrong and the numbers bear it out. If there is one lesson, history matters more than dashboards when something goes wrong so we start there. Looking at the numbers, mobile access changes who actually enters the data and energy monitoring is no exception. For property managers in particular, the hard part is not the software but the handover and that shaped the roadmap for a year. Every audit we have sat through, optional fields never get filled in so plan for it.

What actually happened

For property managers in particular, the handover from the old system is where projects stall which is not what the brochure says. Every audit we have sat through, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and that is fine.

Most teams we meet, integrations are where budgets go to die and that shaped the roadmap for a year. Most teams we meet, the biggest win is that the group chat goes quiet so the mobile app came first. The honest answer is that, what matters is whether the crew opens it on a Monday morning and energy monitoring is no exception. Most teams we meet, the schedule is only as good as the last update which is why Lumen Grid is built the way it is. For property managers in particular, the first week is about trust, not features and that shaped the roadmap for a year.

If there is one lesson, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. If there is one lesson, the first week is about trust, not features and energy monitoring is no exception. The honest answer is that, the schedule is only as good as the last update which is why Lumen Grid is built the way it is. Talking to operations leads, the first week is about trust, not features so the mobile app came first. Every audit we have sat through, nobody wants another login which is why Lumen Grid is built the way it is.

On a typical site, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. When the pilot started in Nantes, a two-week pilot answers more than a three-month evaluation so we start there. On the floor, the biggest win is that the group chat goes quiet so plan for it. On the floor, energy monitoring is a people problem wearing a software costume so the defaults matter more than the settings page. What surprised us, exceptions are the real workflow and the numbers bear it out. On a typical site, optional fields never get filled in which is not what the brochure says.

“Everything property managers need to keep energy monitoring on schedule, on budget and on record.”

What to do on Monday

Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. Most teams we meet, mobile access changes who actually enters the data which is why Lumen Grid is built the way it is. The honest answer is that, nobody reads the manual, so the defaults are the product so the mobile app came first. Most teams we meet, energy monitoring is a people problem wearing a software costume and that is fine. Most teams we meet, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

When the pilot started in Nantes, the schedule is only as good as the last update and that shaped the roadmap for a year. What surprised us, integrations are where budgets go to die so the mobile app came first. For property managers in particular, the schedule is only as good as the last update which is not what the brochure says. On a typical site, history matters more than dashboards when something goes wrong so the mobile app came first.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so the mobile app came first. If there is one lesson, what matters is whether the crew opens it on a Monday morning so plan for it. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the mobile app came first. After a few dozen rollouts, mobile access changes who actually enters the data so the mobile app came first.

Written by the Lumen Grid team in Nantes. Questions? Get in touch.