Inputs and outcomes can be clearly described while the handoff between them remains ambiguous. One party produces evidence, another reviews it, and a third is expected to act.
The middle of that chain deserves its own governance.
Make the transition explicit
Record what is being handed over, which version applies, the purpose of the transfer and who is receiving it. Distinguish receipt from acceptance, and acceptance from authorisation to proceed.
Preserve unresolved conditions and the identity of the person responsible for resolving each one. A document transfer should not silently change its evidence status.
My note on evidence-state transitions identifies five useful questions: what is the current state, what authority does the source actually have, who owns the next response, what permits the transition, and where may the record be used?
These are questions to make explicit at a handoff, not a universal approval ladder. Different institutions may use different status names and review procedures. The receiving institution needs to understand the meaning, not merely import the label.
A fictional handoff between three teams
Calling the report simply “accepted” would lose the most important part of the technical conclusion: accepted for what, by whom and with which exclusion?
Equally, the report can be useful while a concern remains open. The task is to preserve the boundary of that use—not to force every record into an all-or-nothing status.
Keep source authority separate from destination authority
The field team can explain the observations it collected. The panel can assess the questions within its remit. The decision owner can consider actions within a separate mandate. None of those roles should be inferred solely from possession of the same document.
A source may be authoritative for a particular record without being authorised to decide the proposed activity. A receiving organisation’s review does not rewrite the origin of the evidence or convert the sender into the approver.
At the receiving end, state the permitted use and identify any additional review still needed. An internal discussion, a public statement and a consequential commitment may ask different things of the same evidence.
Keep a return path
A receiving reviewer needs a way to request clarification, return incomplete material or record a disagreement. The response should remain connected to the original submission.
In the fictional example, the location discrepancy goes back to the field-record owner with a precise question: which boundary and visit does the comparison describe? The request includes the report version, the reviewer’s concern and the agreed response point. Receipt of that request should also be acknowledged.
If the answer is late, the record should show the next escalation route. Silence should not make an excluded comparison available for unrestricted use.
Treat a corrected submission as a new review event
Suppose the field team submits R-12:v3 with the location corrected. Retain R-12:v2 and show which observation changed. Connect the revision to the outstanding question rather than uploading an unrelated replacement file.
The panel then records whether its earlier limitation still applies. The decision owner checks any dependent instruction or paper. A new upload does not retrospectively expand the scope of the earlier assessment.
Even when the correction leaves the conclusion unchanged, record that it was considered. A short statement of “reviewed; no change to the limited conclusion, for these reasons” is more informative than a silent replacement.
Keep the handoff small enough to use
The working handoff can be concise: identify the record and version, current state, intended use, receiving reviewer, unresolved conditions and response route. Link supporting material rather than copying it into multiple disconnected records.
Where a receiving organisation uses another system, agree how identifiers, review limitations and corrections will remain visible. A successful file transfer is only the transport step; it does not settle the receiving institution’s use of the contents.
The companion article A metric should not travel alone examines what must survive when a handoff involves a calculated indicator rather than a report.
The next useful question
Ask the receiving person to explain what they have received, what they may use it for and what they must do if it changes. Compare that answer with the sender’s record.
If those answers differ, resolve the handoff before treating the evidence as accepted for the next decision.
About this version
This archive article was expanded on 24 September 2026 with a worked example and additional review questions drawn from the author’s linked public writing. Its original publication date is not recorded. The date shown identifies this revision, not an inferred first publication. Scenarios and identifiers are fictional.
Fracture → Signal → Spine → Assurance