Describe the correction
Capture record identifier, field, prior value, proposed value, source evidence, reason, and requested effective date. A correction log should explain what changed without relying on memory.
Check the blast radius
Look for reports, customer messages, linked records, and workflows that depend on the corrected field. Flag downstream impact before changing a value that may be used elsewhere.
Verify after the change
A second reviewer or owner should confirm the result for sensitive fields and record the check. Disputed corrections remain visible with their decision status rather than being overwritten.