Correction and rectification.
WHAT THE OBLIGATION IS
To keep data accurate, and correct it when told.
WHY IT MATTERS
Decisions are made on data, and wrong data produces wrong outcomes.
WHAT EXAMPLES LOOK LIKE
A wrong address preventing delivery An incorrect payment record A mistaken note affecting service
WHAT TO DO ON RECEIVING A CORRECTION REQUEST
Verify the correct information Update every system holding it Inform anyone you shared it with
WHY THAT LAST STEP
The error propagated.
WHAT TO DO IF YOU DISPUTE THE CORRECTION
Record the dispute alongside the data.
WHY
The person is entitled to have the disagreement noted.
WHAT TO BE CAREFUL WITH
Opinions recorded as facts.
WHAT THE DISTINCTION IS
A note that someone was rude is an opinion; a record that they called on a date is a fact.
WHAT TO DO ABOUT OPINIONS
Record them as such, and only where necessary.
WHY
They are the person's data and they can request them.
WHAT TO REVIEW
Where data is duplicated across systems.
WHY
Correction in one place leaves errors elsewhere.
WHAT TO BUILD
A single authoritative record, where possible.
WHAT TO RECORD
The request, and what was changed.
