Define the correction at field level
Synthetic record R-121 has title “Monthly data” instead of the accepted “October data”. The period 2026-10 is correct; the customer note has no correction evidence. The approved remedy changes only title. Supplying an entire old record as replacement would risk overwriting unrelated content. This fixture describes the business change set, without claiming a particular API patch or locking feature.
| Field | Current value | Supported remedy | Change decision |
|---|---|---|---|
| Title | Monthly data | Accepted reference says October data | Change title only |
| Period | 2026-10 | Already matches reference | Keep |
| Customer note | Call after review | No change requested or evidenced | Keep |
Apply and check the documented change set
- Locate accepted correction evidence
- List affected fields
- Apply only supported replacement
- Compare affected and retained fields
If the field’s current value differs from the reviewed value, revisit the correction before applying it.
How many fields change in this remedy?
Show the worked answer
One: title. Period and customer note remain unchanged. This is not permission to replace the whole record.
Retain the current and expected values with the correction record. Recheck newer edits before applying the approved field change.