1
Describe the issue
Record what happened, where it occurred, the affected assets, business impact, evidence, and recurrence context.
Data governance tool
Turn data issues into controlled, accountable action
Capture the issue, quantify priority, assign ownership, track aging and SLA exposure, and document the evidence required for defensible closure.
Transparent scoringNo external data transferDeterministic results
How it works
Use one consistent record to support triage, ownership, remediation, validation, and reporting.
2
Calculate and assign
Apply severity and urgency ratings, confirm the accountable owner, due date, SLA expectation, and dependencies.
3
Remediate and close
Track aging, implement corrective action, validate the outcome, and close only when measurable criteria are satisfied.
Create or assess a data issue
Required fields are marked with an asterisk. Your entries remain on this page after validation errors.
Methodology and responsible use
The tool uses a simple, explainable priority model intended for consistent operational triage.
Method
Severity measures the magnitude of impact. Urgency measures the required speed of response. Multiplying the two values creates a score from 1 to 16. Aging uses calendar days. SLA thresholds are guidance defaults and should be aligned to your organisation’s risk appetite, regulatory duties, and operating model.
Limitations
The tool does not verify facts, estimate financial loss, determine legal obligations, or assess technical root cause. It cannot detect omitted dependencies, unreported impact, duplicate issues across separate browser sessions, or changing conditions after calculation.
Using the result
Use the score to support triage, not to replace accountable judgement. Review high-impact issues with relevant data owners, business owners, technology teams, risk, privacy, security, compliance, or legal specialists where applicable.
Closure discipline
Close an issue only after the defined validation method confirms the closure criteria, supporting evidence is retained, residual risk is accepted by an authorised owner, and recurrence prevention has been considered.
Related tools
Strengthen issue management with connected governance, quality, and accountability practices.
Frequently asked questions
What is a data issue register?
It is a controlled record of data defects and weaknesses, including impact, severity, urgency, ownership, remediation, evidence, validation, and closure decisions.
How is priority calculated?
Priority equals severity multiplied by urgency. Both inputs use a 1–4 scale, creating a transparent score from 1 to 16.
What is the difference between severity and urgency?
Severity reflects how serious the impact is. Urgency reflects how quickly action is required. A serious issue may not always be immediate, and an urgent issue may have limited impact.
What do the SLA thresholds mean?
They are default target response or remediation windows: 2 days for P1, 5 for P2, 15 for P3, and 30 for P4. Organisations should tailor them to their own obligations and risk appetite.
How is aging calculated?
Aging is the number of calendar days from detection to the calculation date. For closed issues, it runs from detection to the closed date.
When is an issue overdue?
An open issue is overdue when its due date is earlier than the current date. Closed and accepted-risk issues are not marked overdue by this tool.
What evidence should be recorded?
Useful evidence includes reproducible queries, affected records, screenshots, logs, reconciliations, test results, ticket references, approvals, and validation outcomes.
What makes good closure criteria?
Criteria should be specific and testable, such as a rule passing for an agreed period, affected records corrected, controls implemented, owner approval obtained, and residual risk accepted.
Can I import and export records?
Yes. The page supports local CSV import for field population and local CSV or JSON export for the generated record. Review imported values before submission.
Does the tool prevent duplicate issue IDs?
It validates the ID format but cannot compare against other browser sessions or an enterprise repository without secure storage. Check uniqueness against your authoritative register.
Does this replace professional judgement?
No. The output supports consistent triage but does not replace legal, regulatory, security, privacy, safety, technical, or business judgement.
Is any information transmitted externally?
No external API is used. Calculations, import, and export operate locally unless the deployed website is deliberately extended with secure server-side storage.