Evidence workflow · 5 min
Resolve rejected evidence with replacements
How rejected evidence blocks export, how replacementForEvidenceId closes lineage, and how the review digest reports rework status.
Help baseline: 2026-06-15
rejected evidencereplacement lineageresolved_by_replacementUpload replacement evidencerework
Treat rejection as an open rework blocker
Rejected source evidence must be replaced or reworked before the board pack can be signed off. The review queue keeps rejected rows visible and links operators to Upload replacement evidence.
- Unresolved rejected evidence blocks board-pack export.
- Reviewer notes should explain what was wrong with the source and what replacement or rework is needed.
- Do not delete the rejected original just to clear the queue; keep the lineage inspectable.
Close the original with an approved replacement
A replacement closes the original only when the replacement evidence links back through replacementForEvidenceId and is approved by a named reviewer.
- The original rejected item is unresolved until the approved replacement exists.
- When closed, the lineage status becomes resolved_by_replacement and the replacement row is not_applicable with replacesEvidenceId.
- The review digest includes replacementForEvidenceId, reworkResolution, replacementEvidenceId, replacementTitle, and notes.
Boundary
DefenceFile help explains workflow operation. It does not provide legal advice, create privilege, certify scope, certify reasonable procedures, or guarantee that a statutory defence will succeed.
Request pilot review