Evidence Register and Claim review

Evidence Register

The Evidence Register organises deterministic, pseudonymised excerpts created from approved documents or pasted text. It shows items needing review first and keeps each item traceable to its source document and page where available.

• An evidence type is an organisational label, not a legal classification.
• A missing item can reflect extraction, pseudonymisation or classification limits.
• Inspect document detail when you need to understand the indexed pseudonymised chunks.

Build the review

Claim review combines the latest structured profile with the current pseudonymised Evidence Register. The build creates an immutable review snapshot and makes no external AI or embedding call.

• Refresh the review when the profile or evidence has changed.
• An out-of-date review blocks further decisions until it is refreshed.
• Questions without candidate evidence remain visible as gaps for professional review.

Review one question at a time

Start with Needs review. Open a claim, then one question, and inspect each candidate excerpt in context. Accepted candidates collapse from the active queue but remain available under All claims.

1. 1Accept when the excerpt is useful evidence for that review question.
2. 2Reject when it is not useful or is incorrectly linked.
3. 3Reset when the candidate needs to return to the review queue.
4. 4Use a short note to record why the review state was chosen when that will help later checking.

What the statuses mean

Needs review, accepted and rejected record your workflow decision about a candidate relationship. Acceptance does not prove a fact, establish an element, determine legal sufficiency or predict the tribunal outcome.

Check the underlying document, public sources, current law and professional judgement before relying on a reviewed candidate.