A reporting estate is not a bridge that stands once built. Leave it untended and it degrades: refreshes break, definitions drift, trust erodes. Why care beats rescue.

Analytics is a garden, not a project

Analytics gets treated like a project. Scope it, build it, launch it, move on. But a reporting estate is not a bridge that, once built, stands on its own. It is closer to a garden. Leave it untended and it does not stay as it was. It degrades. Refreshes break. Definitions drift away from the business. Uncertified reports breed. And trust, the only thing that makes any of it worth having, quietly erodes.

In practice, this is where our data strategy and leadership work comes in, and The Spreadsheet That Became A System Nobody Maintains covers useful related ground.

The decay is slow enough to ignore right up until the day someone asks whether a number can be trusted and nobody in the room is sure. That is the moment the rot announces itself, and by then it is expensive.

The handover party is when the rot begins

The trouble starts with the framing. A project has an end. You celebrate the launch, the team disperses, the budget closes. But the business carries on changing the day after go-live, and nothing is tending the estate to keep pace. The handover party is, far too often, the precise moment the rot begins, because everyone's attention leaves at once.

It rarely fails all at once. It accumulates in recognisable ways. A source system is upgraded, a field renamed, a refresh fails, and nobody owns fixing it, so a report goes stale. A new product line launches, the sales team reorganises, and the old measures quietly stop meaning what they used to while still showing the old numbers. Everyone adds their own report, none certified, until nobody can say which is the real one. The one person who understood the model leaves, and the capability to maintain it walks out with them. One wrong number, left unfixed, and people start checking by hand again, then stop using the reports at all.

The signs, if you look for them

You can spot it early. Refresh failures that sit for days because nobody jumps on them. The question "is this number right" creeping back into meetings. Shadow spreadsheets reappearing as people route around the reports. Reports with no named owner that nobody will defend or retire. Usage sliding down while the report count climbs up. None of those is dramatic on its own. Together they are an estate going quietly to seed.

Care is far cheaper than rescue

The economics are stark. A small, steady amount of maintenance, watching refreshes, fixing breaks promptly, keeping definitions current, retiring the dead, costs a fraction of the ground-up rebuild that neglect eventually forces. And it avoids the worst cost of all, a run of decisions made on numbers nobody quite trusts. Rescue is the most expensive kind of work, because by the time anyone is called the trust is already gone, and trust takes far longer to rebuild than numbers do.

Good continuity is not mysterious. It is a short list of habits done reliably: monitoring and alerting on refreshes so a break is caught before anyone downstream notices; a named owner accountable for the estate's health, not just its launch; a change process so the model moves when the business moves; periodic pruning and recertification; and a small standing capacity for fixes and modest enhancements, so requests are handled rather than piling up into the next big project.

Build for handover, run for life

None of this argues against building things well or handing them to your own people. Build for handover always: documented, understood, owned in-house. But accept that something has to tend the garden afterwards, whether that is your own team with the time and the skills, or a light ongoing arrangement with a partner.

So look at your estate this week and ask one thing: when a refresh last broke, how long did it sit, and who owns fixing the next one. If you cannot name the owner, the garden is already going over. This is exactly why our Analytics Acceleration Programme has a Continuity stage rather than a finish line, and why a fractional data lead so often pays for itself. The estate that is built and then abandoned is the one everyone gets called back to rebuild, at several times the cost of the care that would have prevented it. The full picture is in our Why Analytics Projects Rot guide.

If any of this sounds familiar, talk to us about your data.

Related reading

• Consolidating multiple Business Central companies in one model
• Why Your Self-Service BI Rollout Collapsed
• Why The AAP Is Not A Traditional Retainer