Problems do not wait for your next migration.
A definition was agreed. Months later, a new report brings back the old version. Reperta keeps watching, so you catch it early and fix it without starting over.
Sound familiar?
The inventory is already out of date.
Reporting changes every week. A one-off review describes the day it was done.
The agreed definition gets forgotten.
New reports quietly bring back a problem after everyone has moved on.
People move on.
Owners change roles, workbooks evolve and nobody remembers why a decision was made.
How Reperta helps
- 1
Set the baseline
The first discovery records what exists, how it is calculated and what was agreed.
- 2
Rescan on a schedule
Each run is compared with the last, so new copies and changed calculations stand out.
- 3
Act on what changed
Changes are shown against earlier decisions, so the right owner can review them quickly.

Every run, dated and comparable. Discovery runs show what was found, what changed since last time and what needs a decision.
Northwind: a baseline to measure against
Northwind Group's first discovery raised 163 findings across 47 reporting assets. Every later run is measured against that baseline, so progress and new problems are both visible.
What you get
- A reporting baseline with every decision attached
- Alerts when calculations change or copies appear
- A history of who agreed what, and why
- Health trends that keep each review focused
Questions
What does Reperta watch for?
New and changed reports, calculations that move away from the agreed definition, new conflicts and reports that lose their owner.
Can we start with one reporting problem?
Yes. Start with one number or one workbook, then keep using the same platform as the scope grows.
Related guides
An agreed KPI definition needs more than a glossary entry
Keep the reasoning, scope, source evidence and accountable owner together so the next reporting change does not restart the same argument.
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
- Dashboard sprawlKnow what you have before you build more
- 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.