DSP 04 / ORIGINAL EDITORIAL
Who gets to correct the record
Published project stories need a correction path for the people, places, and work they describe.
A project profile can become inaccurate even when it began in good faith. Teams change, conditions shift, language dates, and a public summary can reveal more than participants expected.
Name the accountable editor
Every dispatch needs an owner who can review a correction, preserve the request, update the public record, and explain material changes. A generic inbox without an operating process is not enough.
Separate correction from erasure
Some issues need a visible correction note. Others require removing personal, unsafe, or improperly shared material. The policy should distinguish editorial history from a participant's safety and privacy needs.
Close the loop
Tell the requester what changed, what did not change, and how to appeal. Record the decision without publishing private correspondence or turning the correction page into a dispute archive.
TAKE TO THE FIELD
Questions before transfer
- Who can request a correction?
- What evidence is needed?
- Which changes receive a public note?
- What requires immediate removal?
A field publication earns trust through visible correction operations.