Skip to main content
DefenceFile
Help centre

Evidence workflow · 4 min

Build the evidence register

How to turn source files into a reviewable register with ownership, status, replacement lineage, and board-pack blockers.

Help baseline: 2026-06-15

evidence registersource metadatahuman reviewreplacement lineageboard pack

Start with source facts

A useful register keeps the original source name, type, upload date, review status, and linked principle visible before anyone relies on the board-pack view.

  • Keep draft evidence separate from approved evidence.
  • Keep rejected evidence visible until a replacement closes the lineage.
  • Show whether an item is included in source-register and board-pack traces.

Use human review as the control point

Named review decisions make the workflow inspectable. They do not certify reasonable procedures or replace legal judgment, but they help a buyer see who approved, rejected, or requested changes.

  • Ask reviewers to leave decision notes that explain the operational reason.
  • Treat stale, rejected, and unreviewed evidence as separate blockers.
  • Export the review digest when handing work to advisers or governance teams.

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