Unused Reports Are a Governance Smell. Here’s the Cleanup

Zero views is a signal. Refreshing ghosts is how capacity and trust both leak.

One quiet page can be a product miss. An estate of quiet pages is a governance miss. The usage log is telling you the certified layer never happened, the attic never got emptied, and refresh still treats everything as live.

This is the estate, not the empty Tuesday, not the funeral

Nobody opens the dashboard is about one report that lost the meeting because it was wrong in grain, slow, untrusted, or ownerless. Fix that page or kill it.

How to retire a dashboard is the ritual for one file: owner, replacement, date, announcement. You will use that ritual. This piece is about noticing the smell across the tenant, and the cleanup list that goes beyond a one-off funeral.

Dashboard sprawl is a tax is the inventory slogan. This post is the signal that slogan missed: usage near zero, refresh still on, and endorsement still looking official. Ghosts with a schedule.

If you cannot say which reports the company actually runs, you do not have governance. You have hosting.

What the smell actually is

Usage is not a vanity metric. It shows which products take part in decisions.

A handful of analyst clicks is not a meeting. A report that only the author opens is a working paper that escaped. A certified badge on a file nobody has opened in a quarter is a lying label.

Ghosts cost money even when seats are assigned. Unused licenses covers the invoice side, and this covers the workspace side. You can have full seats and still refresh a museum.

The smell shows up as a cluster:

Refresh of the unviewed. Gateways, capacity, and 6 a.m. collisions eat the morning window with jobs nobody needed, as in the 7 a.m. surprise.

Endorsement without an audience. Promoted and certified only mean “safe” if people can find the live one. A wall of badges is camouflage.

Twins of the live pack. The certified app is quiet because the old name still works. Adoption failed at the front door, estate-wide.

No owner on the long tail. Authors left and bookmarks remain. Access that was fine for a project is not fine two years later. See hidden costs of Power BI governance.

Pull the usage you have and ask the EA who builds the pack. If both are quiet on a file, that is data. It is not a reason to keep the schedule “just in case.”

What an unviewed estate costs

1. Capacity leaks on ghosts. Unused reports still refresh, still fail, and still page someone at dawn. You buy headroom to feed the attic. Premium capacity is not a strategy, and turning jobs off is the cheaper capacity plan.

2. Trust leaks from the label. If “certified” includes files nobody uses, the word means nothing. People keep the emailed workbook, and the next certified page inherits the shrug.

3. Risk sits where nobody looks. Old RLS, stale vendor lists, and columns that should have died with a project all linger. Review follows usage, so unviewed means unreviewed.

4. The live product stays buried. Navigation becomes a scavenger hunt, and the steward’s app looks empty because thirty other doors still open. Sprawl was the tax. Ghosts are how the tax compounds after the build.

5. Analysts rebuild instead of pointing. Copying feels safer than trusting a quiet catalog, so drift continues and you pay to explain two truths: why reports show different numbers.

6. Roadmaps get funded on fiction. Leaders add pages and tools on top of an unused foundation. The estate looks busy in a workspace list, but the meetings never moved.

Open the activity data. If the meeting owners are not there, the file failed, even if a handful of clicks still land.

The cleanup list (estate level)

Do this as one pass, then keep it as hygiene. Individual funerals still use the ritual. The pass is how you build the queue.

1. Inventory with usage, not with pride. For each report, list the workspace, last view by a consumer (not the author), refresh on or off, endorsement, and named owner. No owner plus no views is the first pile. Author-only views is the second. Real usage with no owner is a rescue, not a funeral.

2. Split the piles in writing. Ghosts have near-zero consumer use for a cycle with refresh still on. Twins have usage but duplicate a certified decision. Live reports are the ones the meeting actually opens. Only live reports stay in the app people are told to use. Ghosts and twins get dates.

3. Turn refresh off before you argue taste. For ghosts, the first win is the morning window. A dark report that still refreshes is the smell, so disable the schedule. Keep the file visible with a banner if you must. Capacity comes back before the political fight starts.

4. Strip lying labels. Remove certified and promoted from anything that is not live and owned. Endorsement is a promise, and an unused report is a broken one. Recertify only the thin layer, as in certified models vs the wild west.

5. Queue funerals instead of declaring a mass grave. Each ghost still needs an owner, a replacement or a “decision dead” note, and a date, following the ritual post. Batch announcements by domain. Do not delete a tenant on a Friday, and do not recertify everything as a substitute for retirement.

6. Close the hose. Cleanup without intake is a season. Stop commissioning a page per question, and put standing executive asks in the model, as in questions that should never be ad-hoc. Review usage monthly like incidents. A copy with a new name is a resurrection, so send it through commissioning, not nostalgia.

Change leadership is how the live door becomes the default, as in data project management. If nobody can say which decisions the estate serves, you need a roadmap before a purge. A Quickstart can be the one live loop you point people to while the attic goes dark. Ongoing conscience is managed advisory.

What good looks like

You can name the reports the ELT actually runs, and it is a short list. Refresh jobs match that list plus a labeled sandbox with no endorsement.

Certified means used and owned. Unused means dark, then gone, and the attic does not refill every quarter.

Frequently asked questions

What if something unused is needed once a year? Then it is not a daily product. Label it and refresh it on a calendar that matches the use, or run it as a working paper with an owner. Do not keep a daily job for an annual question.

Should we delete everything with zero views this month? No. Prove neglect or replacement, then use the ritual. Silent takedowns are how zombies come back by Monday.

Is low usage always a failure? For an executive pack, yes. For a steward’s diagnostic page, maybe not. The smell is an estate of unviewed, unowned, still-refreshing files wearing a badge. One quiet diagnostic is not the signal.

Get started

Stop refreshing ghosts and calling it a program. Read the usage, darken the attic, and keep the live layer honest.

Want to know which reports are still eating the morning window with nobody home? Book a session with Alluvium. We will split ghosts, twins, and live reports, and name the first jobs that should already be off. To check the models behind the live layer, request a free Model Health check.