The Gold Standard · Anthropology
Make the decision path visible
A disclosure review board can issue a sound correction, replace the canonical release and still lack evidence that a consequential recipient stopped using the old record. Addresses bounce, teams change, shared mailboxes go unattended and an acknowledgement may confirm receipt without confirming replacement.
The gold standard treats contact failure as a decision risk. It ranks recipients by consequence, tries proportionate alternate routes, verifies action at critical control points and keeps unresolved exposure visible until it is bounded or repaired.
Choose the route closest to your decision
Chapter contents
Chapters 1–3
Chapters 4–6
Chapters 7–9
Chapters 10–12
CHAPTER 1 OF 12 · DEFINE ACKNOWLEDGEMENT
1. Define the acknowledgement that the decision needs
Specify whether the recipient must confirm receipt, identify the controlling version, replace a stored copy, amend a briefing or reconsider a decision.
A reply saying received is not evidence that the superseded record left the workflow. Match the acknowledgement to the risk.
CHAPTER 2 OF 12 · DEFINE ACKNOWLEDGEMENT
2. Distinguish delivery evidence from corrective action
Separate sent, delivered, opened, understood, replaced and applied. Record timestamps and the evidence supporting each state.
Automated delivery receipts help with routing, but they cannot prove that a person used the corrected record.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · DEFINE ACKNOWLEDGEMENT
3. Rank recipients by consequence and urgency
Classify recipients by their ability to make, recommend, automate or repeat a material decision. Prioritise pending appeals, controlled repositories and downstream publishers.
A dormant archive and an officer preparing a decision should not receive the same escalation effort or deadline.
| State | Evidence |
|---|---|
| Delivered | System accepted message |
| Received | Recipient confirms notice |
| Replaced | Old copy removed or marked |
| Applied | Decision path updated |
CHAPTER 4 OF 12 · RECOVER CONTACT
4. Use alternate routes without widening disclosure
Try verified organisational contacts, case-system alerts, repository notices, supervisors or data stewards. Share only the minimum needed to identify the correction.
Do not resend protected information through a less secure channel merely because the preferred channel failed.
CHAPTER 5 OF 12 · RECOVER CONTACT
5. Set escalation clocks and ownership
Give each consequence tier a response window, named owner and next action. Escalate missed deadlines to someone who can pause use or control the affected workflow.
A contact queue without an owner can create the appearance of activity while exposure continues.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · RECOVER CONTACT
6. Worked example: the analyst left before acknowledging replacement
A corrected proxy-record extract is sent to an analyst who prepared a pending appeal brief. The address bounces because the analyst has left, and the shared project folder still contains the old attachment.
The correction owner alerts the case manager, places a supersession notice beside the file, replaces the controlled copy and asks the new brief owner to confirm the governing version before submission. Changed-context check: if the analyst received the record only for an abandoned exploratory task and no decision or shared output survives, the team may close after documenting that absence rather than reconstructing a nonexistent decision.
| Failure | Next route |
|---|---|
| Bounce | Verified organisational contact |
| No reply | Case owner or supervisor |
| Unknown holder | Repository or publication notice |
| High consequence | Pause decision gate |
CHAPTER 7 OF 12 · CONTROL EXPOSURE
7. Escalate unresolved high-consequence recipients
Where contact cannot be restored, pause affected publication or decision steps, flag the case record and notify the authority responsible for accepting residual risk.
Do not infer safety from silence. Unreachability removes evidence; it does not establish that the old version is unused.
CHAPTER 8 OF 12 · CONTROL EXPOSURE
8. Reconsider decisions when acknowledgement cannot be obtained
Use dissemination, access and citation records to identify decisions that may have relied on the superseded release. Reopen those that meet the materiality threshold.
Independent review is especially useful when the original decision owner is unavailable or has an interest in closure.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · CONTROL EXPOSURE
9. Protect privacy during repeated outreach
Use identifiers, dates, section references and secure contact routes. Keep failed-address logs and recipient lists under appropriate access control.
Repeated attempts can themselves reveal sensitive participation or case relationships if notices are over-detailed.
| Field | Record |
|---|---|
| Holder | Known or possible recipient |
| Copy | Version and location |
| Decision | Potential use |
| Control | Restriction or review |
CHAPTER 10 OF 12 · CLOSE HONESTLY
10. Record residual exposure as a bounded statement
State who remains unreachable, what they may hold, which decisions are exposed, what controls were applied and when the risk will be reviewed.
Avoid the label fully corrected when a material use path remains unresolved.
CHAPTER 11 OF 12 · CLOSE HONESTLY
11. Test the process with a changed recipient map
Simulate staff departure, expired contractor access, a closed mailbox and a forwarded attachment. Confirm that authoritative repositories and decision gates still surface the correction.
Transfer check: a process that works only for current internal staff has not demonstrated control over realistic dissemination.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · CLOSE HONESTLY
12. Audit acknowledgement quality and repeat failure
Track bounce rate, time to responsible owner, action-confirmation rate, unresolved high-consequence recipients, stale-copy rediscovery and repeated contact gaps.
The gold standard closes what can be proved, limits what cannot and leaves a visible route for later evidence to trigger repair.
| Measure | Warning |
|---|---|
| Bounce rate | Contact data stale |
| Action gap | Receipt without replacement |
| Late escalation | Exposure persists |
| Stale rediscovery | Propagation incomplete |
Frequently asked questions
Is an email delivery receipt enough?
No. It shows a routing event, not that the recipient identified, replaced or applied the corrected version.
How many contact attempts are required?
Use proportionate, risk-based routes and deadlines; high-consequence gaps need escalation or a pause rather than endless identical messages.
Can an unreachable recipient prevent all closure?
Not always. Closure can be bounded when the remaining exposure, attempted routes, safeguards and review trigger are explicit.
Should a correction notice repeat the sensitive passage?
No. Use controlled identifiers and a secure route to the replacement without redisclosing protected detail.
Continue through verified routes
Core routes
Anthropology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Corrective re-release propagation, cached copies and decision reconsideration
- Redaction disputes, disclosure review boards and corrective re-release
- Evidence deadlocks and decisions under residual uncertainty
- Evidence asymmetry and independent review