3 Signs Your Waste Reporting Is Fragile (and the One Root Cause Behind Them)

Most waste leaders can’t point to the day their reporting started feeling fragile — it just sort of got that way. Three signs give it away: one person can answer most reporting questions and only that person, the same KPI shows up with different numbers in different decks, and month-end gets harder rather than easier as the company grows. None of them is unusual, and none means anyone is doing a bad job. All three are signals that the data architecture underneath the reporting hasn’t kept up with the business — it’s held together by quiet, manual work that doesn’t scale. The fix isn’t a new tool or more effort; it’s a governed foundation that turns reporting from fragile into reliable.

What does it mean for reporting to be “fragile”?

Fragile reporting is reporting that still produces the numbers — until the day it doesn’t. It works, month after month, but only because a few people keep propping it up with manual effort nobody sees: an export here, a spreadsheet stitched to another spreadsheet there, a query only one person can run. Nothing looks broken from the outside. The decks go out. The board gets its package. The routes get reviewed.

What makes it fragile is that all of that rests on effort rather than architecture. Most waste leaders can’t point to the moment their reporting started feeling this way — it just sort of got that way, one urgent request at a time. The tell isn’t a dramatic failure. It’s a handful of small, familiar signs that the foundation underneath hasn’t kept pace with the company on top of it. Here are the three that show up most often.

Sign 1: One person can answer most reporting questions — and only that person

When a number looks off or leadership needs a new view by Friday, everyone routes it to the same person. They know the ERP, they wrote the SQL or the macros, they built the Power BI, and they understand the business well enough to know what every figure is supposed to mean. They’re genuinely great at it — which is exactly why the risk is easy to miss.

The reporting isn’t fragile because that person is doing anything wrong. It’s fragile because the whole operation lives in their head and on their laptop, which makes them a single point of failure. If they’re out during close, on vacation, or they leave, nobody else can run, fix, or explain the reports leadership depends on. That’s a business risk, not a personnel one — we go deeper on it in when one person holds your reporting together.

Sign 2: The same KPI shows different numbers in different decks

Revenue by location is one figure in the finance deck and another in the ops review. Two people pull “on-time service” and get different answers. The numbers aren’t wrong on purpose — they come from different sources, filtered different ways, and defined slightly differently by whoever built each report. Having dashboards is not the same as trusting them.

This is the quiet sign, because it doesn’t stop anyone from working — it just erodes confidence. Every meeting opens with a debate about whose number is right instead of what to do about it. The root cause is that there’s no single governed definition of each metric, so the same KPI gets recalculated by hand in a dozen places and drifts. It’s the same reason fixing ERP reporting starts with a roadmap, not a tool — you can’t buy your way to one version of the truth without deciding where it lives.

Sign 3: Month-end gets harder, not easier, as the company grows

You’d expect reporting to get easier with scale — more systems, more people, more practice. Instead, close takes longer every quarter. A new location adds another export. An acquisition adds another chart of accounts to reconcile by hand. The finance team loses the first week or two of every month assembling the same package they assembled last month, from scratch.

That’s the signature of manual work that doesn’t scale: effort grows with the business instead of staying flat. When the plumbing is automated and governed, adding a location is a configuration change, not a new spreadsheet. When it isn’t, every bit of growth lands on the same people as more hand-work — which is why finance teams lose the first two weeks of every month right when the company can least afford it.

Why do all three signs point to the same root cause?

Because they aren’t three separate problems — they’re three symptoms of one. The data leaders need lives in systems that were never built to talk to each other: the ERP runs routes and billing, payroll sits somewhere else, fuel and disposal somewhere else again. Nobody planned for those to come together into trusted reporting, so people bridged the gap by hand, one workaround at a time.

Each workaround was rational on its own. Stacked over a few years, they add up to a reporting layer that depends on one person’s memory (sign 1), recalculates every metric in isolation (sign 2), and grows more manual with every location added (sign 3). The company scaled; the architecture underneath the reporting didn’t. That’s the whole diagnosis — and it’s why adding effort or another BI tool doesn’t help. You’re just stacking more on the same foundation.

How do you fix fragile reporting?

You fix the foundation, not the symptoms. In practice that’s a governed source layer beside the ERP where data from every system is defined once, a shared model other people can build on, and a roadmap that sequences the work so value lands early instead of waiting on a big rebuild. Concretely, it’s three moves:

• One governed source layer instead of one-off extracts. The ERP, payroll, fuel, and disposal data lands in one place with clean lineage, so a route or location number means the same thing whoever pulls it — and no one is re-exporting by hand.
• Definitions that live in the architecture, not in someone’s head. Each KPI is calculated once, in a shared model, so the same figure feeds every deck. That’s what ends the “whose number is right” debate and takes reporting off any one person.
• A sequenced roadmap, not a rip-and-replace. The ERP stays the system of record and the BI tools stay in place. The foundation sits beside them and reads from them, so the highest-risk reports move first and each step lands on the last.

None of this throws away the work your team already does well. It gives that work an architecture to stand on — so reporting survives a vacation, agrees with itself across decks, and gets easier as you grow. That’s the difference between reporting held together with tape and reporting you can rely on. It’s also the same foundation that lets an operator finally see route profitability or automate month-end — capabilities that stay out of reach as long as everything runs by hand.