Targets not measurable
Target Over-Achievement Anomalies
An indicator reporting 400% of target is rarely a triumph - it usually means the target was set too low or the data is wrong.
Why Over-Achievement Anomalies Matter
Implausibly high over-achievement is a quiet red flag that the AGSA reads as weak target-setting or unreliable data rather than exceptional performance. Targets set far below realistic capacity, or actuals inflated by counting errors, both produce anomalous over-achievement that undermines the usefulness of the indicator. AuditPro Core flags indicators reporting anomalous over-achievement so the cause is investigated before the figure is published.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Indicators flagged
16
>200% of target
6
Data error confirmed
4
Targets recalibrated
9
▲ 9
Achievement as % of target
Over-achievement review
| Indicator | Target | Actual | Verdict |
|---|---|---|---|
| Ind P | 100 | 340 | Sandbagged target |
| Ind Q | 50 | 134 | Data error |
| Ind R | 200 | 424 | Genuine |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Over-achievement as a signal
Massive over-achievement signals that the target was not a genuine stretch. Targets are meant to be achievable yet meaningful, and routine large beats suggest they were neither.
Weak target-setting
Setting targets far below realistic capacity guarantees easy over-achievement and flatters performance. The FMPPI achievability test exists partly to prevent this.
Data error risk
An anomalous actual can equally stem from a counting or unit error - double-counting, wrong denominators or mis-keyed figures - which is a reliability problem.
Usefulness impact
Either cause damages the usefulness of the indicator, because a target that is trivially beaten provides no real measure of performance against intent.
How AuditPro Core Bridges the Gap
- Anomaly detection: indicators reporting implausible over-achievement are flagged against expected ranges.
- Exception workflow: flagged indicators route for investigation into target-setting or data error before publication.
- Traceability to source: the anomalous actual links to its evidence so a data error can be distinguished from a weak target.
- Continuous monitoring: repeat over-achievers are tracked to drive better target-setting next cycle.
Key Takeaways
- Large over-achievement usually signals a weak target or a data error, not excellence.
- Targets set below realistic capacity fail the FMPPI achievability test.
- Tracing the actual to evidence separates a counting error from a soft target.
- Either cause undermines the usefulness of the indicator and warrants correction.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.