What this review measures
This design counts saved reports whose original or de facto owner is no longer able to maintain them, and records what still depends on those reports. It does not measure report quality or usage. The practical question is narrower: when a person leaves a role, how many saved reports keep running without anyone accountable for their logic, access, or failures? That count is a useful proxy for maintenance risk. It also gives a team a concrete list to work through rather than a vague warning about documentation debt.
Define the report population
Start with a written scope: the workspace, the folder, or the dashboard set being reviewed. Record the export date and the person who pulled the list. Decide whether personal reports, shared reports, and scheduled subscriptions all count, and write the rule. If the tool exposes an owner field, capture it; if it does not, note that the owner must be inferred. The population should be stable and reproducible. A review that silently changes scope between months cannot show whether the situation is improving.
Capture the reported owner
Export the owner field exactly as the tool records it, including service accounts, shared team identities, and blank values. A shared team identity is not a person and should be flagged. Record the report name, the folder, the data source, the last modified date, and whether the report is scheduled. Keep the original values; do not normalize a blank owner into a plausible name. The owner field is the first evidence, but it is not the whole answer, because a report can list a departed person and still be maintained informally by someone else.
Establish who is still present
Compare each named owner with the current team roster or directory. Record whether the person is active, has changed roles, or has left. Do not treat a role change as a departure without checking whether the new role still covers the report. If the directory is unavailable, use the team's own list and state the limitation. The comparison should be done at a fixed date so the result is reproducible. Record the source of the roster and the date it was checked.
Identify the de facto maintainer
For reports with a departed or ambiguous owner, ask who actually updates or fixes them. Record the name and the evidence, such as a recent change log entry or a message thread. If no one can be identified, mark the report as unmaintained rather than guessing. The de facto maintainer may be outside the original team, which itself is a finding about hidden dependencies. This step is qualitative, so record how the answer was obtained and who provided it.
Check what still depends on the report
For each unmaintained report, check whether a dashboard, subscription, alert, or downstream report still reads it. Record the dependent asset and its owner. A stale report that nothing reads is a cleanup candidate; a stale report feeding an executive dashboard is a live risk. The dependency check turns the ownership count into a risk statement. Without it, the team sees a long list of orphaned reports and no way to prioritize the work.
Measure the share without an active owner
Report the number of reports in scope, the number with an active named owner, and the number with no active owner or only a shared identity. Report counts alongside percentages and break them down by folder or dashboard. Do not describe the result as an industry benchmark or a target. It describes this workspace at this time. If the sample is small, say so. The value is in the trend across repeated reviews and in the specific list of reports that need attention.
Look for the creation pattern
Group the results by who created the reports and when. A cluster of orphaned reports from one period may indicate a project that ended without a handoff. A cluster from one creator may indicate personal report-building that was never shared. Look also for reports created by a departed person shortly before they left, because those are the most likely to lack documentation. The pattern points to a process fix, such as requiring an owner at creation or a handoff check before offboarding.
Choose a repair for the riskiest reports
Prioritize the unmaintained reports that feed live dashboards or alerts. For each, decide whether to assign an owner, archive the report, or rebuild it from a maintained source. Record the decision and the owner. Prefer archiving a report that no one reads over assigning a nominal owner who will never look at it. A small number of reports with real owners and current definitions is more useful than a large inventory with names attached for appearance.
Retest after the repair
Rerun the same export and the same comparisons after the repair cycle. Report what changed, what remains, and whether new orphaned reports appeared. Compare the result with the earlier review and note any pattern that persisted. A repair that reduces the unowned share without slowing report creation is a real improvement. A repair that simply renames owners without changing the creation process will be undone by the next project.
Document limits and data handling
The review depends on the accuracy of the owner field and the team roster. It cannot prove that an active owner actually understands the report, and it does not measure whether the report is correct. State those limits in the method note. The export may include report names that reveal commercial plans, so restrict access and avoid publishing the full list. Delete the working extract when the review is complete. A repeatable ownership review is one that another analyst can run without reconstructing the scope or the roster source.
Sources
- https://www.nist.gov/cyberframework
- https://www.census.gov/data/developers/guidance/api-user-guide.html
- https://knowledge.hubspot.com/records/understand-original-source-properties
- https://www.w3.org/TR/NOTE-datetime
- https://www.ftc.gov/business-guidance/privacy-security