Too many reports and no clear answers.
A request arrives for another dashboard. There may already be three versions of it, and nobody knows which to trust. Reperta finds the overlaps and helps you decide what is worth keeping.
Sound familiar?
The dashboard that already exists, somewhere.
Teams rebuild answers because finding the existing report is harder than creating another.
Nobody wants to delete the wrong one.
Without knowing what depends on a report, every retirement feels risky.
Every copy needs maintaining.
One definition change means tracking down every copy and every owner.
How Reperta helps
- 1
See the overlap
Copies and near-copies are grouped together by structure and calculation.
- 2
Know what matters
Ownership, recent use and dependencies show which reports the business really relies on.
- 3
Agree what stays
Owners record keep, fix, retire or rebuild for each report, with the reason written down.
Copies grouped together, with a suggested keeper. Duplicate and near-duplicate reports in families, with the version to keep for the owner to confirm.
Northwind: three versions of one board pack
The Northwind FY26 board pack had two duplicate copies, FINAL and FINAL v2. One review settled which to keep and which to retire.
What you get
- Every copy and near-copy, grouped into families
- Ownership and dependencies next to each one
- A recorded decision for every report
- Less to maintain once owners agree what goes
Questions
Does a duplicate mean we should delete it?
Owners check the purpose and what depends on it first. Reperta gives them the evidence to decide quickly.
Can you tell whether a report is used?
Where your sources record usage, Reperta shows it. Where they do not, the report is listed for its owner to confirm.
Related guides
The reporting transformation checklist: what to settle before you commit
Eight questions every sponsor should have answered before a reporting transformation is scoped, from what exists and who owns it to what retires and how sign-off works.
Read the guideKeep, fix, retire or rebuild: a decision framework for reports
A simple framework for deciding what each report deserves, the evidence to ask for behind every verdict and how to get owners to commit.
Read the guideOther places teams start
All use cases- Conflicting numbersOne agreed definition for every metric
- AI-built dashboardsFaster dashboards still need agreed numbers
- Ongoing reporting healthStay right as reporting changes
- Spreadsheet reportingFind the workbooks the business runs on
- Fixing known problemsTurn findings into fixes that stick
- ModernisationDecide what to keep, fix, retire or rebuild
- Moving to Power BIMove what matters and leave the rest behind
- Retiring SSRSSwitch off the old server without surprises
Bring the number nobody can explain.
Book a 30-minute demo. We will show you how Reperta finds what is behind it, fixes it and keeps it right.