Add scorecard items
Record each domain, system, product, dataset, or critical element with its owner and relative weight.
Assess domains, systems, data products, datasets, or critical data elements using seven quality dimensions, weighted priorities, thresholds, trends, ownership, issue counts, and accountable actions.
Create a repeatable scorecard that connects measurement to ownership and action.
Record each domain, system, product, dataset, or critical element with its owner and relative weight.
Enter seven dimension scores, a target threshold, prior-period score, open issues, and the next action.
Review weighted results, RAG status, trend, target gap, weakest dimensions, and prioritised actions.
Use the scorecard as a governance and prioritisation aid, not as a substitute for source-system profiling, statistical validation, audit evidence, or professional judgement.
Define each dimension, sampling period, population, tolerance, and evidence source before scoring. Keep the definition stable across reporting periods.
A trend may reflect a real control change, a different sample, a revised rule, or improved issue detection. Record the reason for material movement.
Assign one owner, a due date, expected outcome, and validation evidence. Re-score only after the remediation has been tested.
It is the weighted average of item-level scores. Each item score is the arithmetic mean of seven data quality dimensions, and each item contributes according to its relative weight.
Use a consistent relative scale based on business criticality, regulatory impact, customer impact, financial exposure, or operational dependency. A critical dataset might receive a weight of 5 while a lower-impact dataset receives 1.
No. The calculation divides by the total weight, so any positive and consistent relative scale works.
Green means the score meets or exceeds its target. Amber means it is below target by no more than 10 points. Red means it is more than 10 points below target.
The tool compares the current item score with the entered prior-period score. Movement greater than 0.4 points is improving, below −0.4 is declining, and movement within that range is stable.
Yes, but interpret the portfolio carefully. Mixed item types can be useful for executive oversight, while operational teams may prefer separate scorecards by type for more comparable results.
Use documented profiling rules, reconciliations, validation tests, control logs, issue registers, source-to-target checks, service-level measurements, and representative samples.
Duplicate names can cause ambiguous ownership, double counting, and export problems. Use distinct names or qualify them with the system, domain, region, or product.
It may mean no issues are open, but it may also indicate incomplete issue capture. Confirm that monitoring, triage, and logging processes are operating before treating zero as assurance.
No. Import plain values only. The expected columns are Type, Name, Owner, the seven dimension scores, Weight, Target, Prior, Issues, and Action.
No external API is used. Browser-based import and export stay local. Form submission is processed by the page itself unless the site owner later adds secure storage.
No. It is a management aid based on user-supplied information. It does not independently verify controls, evidence, regulatory compliance, or certification readiness.