Evidence

How to build an evidence packet another person can actually review

A strong evidence packet is not a dump of files. It is an ordered set of documents with an index, a chronology and a reason for each item being included.

Reviewed 27 August 2026

The person reviewing your paperwork usually does not share your memory of what happened. A useful evidence packet lets that person understand the matter without guessing which screenshot matters, which invoice is current or why two documents appear to contradict each other.

Start with a one-page index

Give every document a stable number such as A01, A02, A03. The index should include the number, document name, date, source and a short statement of relevance. “Email” is a poor label; “A07 — Email from retailer confirming replacement promised — 14 May 2026” is much easier to review.

Do not renumber everything every time a new document arrives. If you expect additions, use categories or leave gaps in numbering. Stability matters because your letter can refer to “A07” without that reference becoming wrong later.

Keep chronology separate from the document index

An index answers “what documents are here?” A chronology answers “what happened and when?” They are related but not interchangeable. Your chronology can cite evidence numbers beside each event: “14 May — replacement promised (A07).” That makes factual claims traceable.

Prefer original context over cropped fragments

A screenshot may be necessary, but preserve enough context to show the sender, date and surrounding message. Keep the original file where possible. If you annotate a copy, retain an unaltered original as well. If a document contains unrelated private information, use a redacted working copy only where appropriate and keep the original securely.

Use a gap log

A mature file admits what is missing. Create a short list called “evidence to obtain”. Examples might include a receipt, an original decision, an itemised invoice, a submission confirmation or a complete email thread. A gap log prevents you from accidentally describing a missing record as if you already have it.

Check for duplicates and contradictions

Duplicates make a packet look larger without making it stronger. Keep one best copy unless two versions prove something important. If two records differ, do not hide the difference. Note it and, if possible, explain which one is current and how you know.

A practical packet order

1. Cover sheet with matter name and reference number.
2. Index.
3. Short chronology.
4. The decision, notice or form that triggered the work.
5. Core evidence grouped by issue, not by random download order.
6. Correspondence and proof of submission.
7. Supporting material and any gap list.

Use the evidence packet builder to create a browser-local first draft of the index.

---

Finish with a verification check

• Have you preserved the original notice, form or transaction record?
• Can every important factual statement be traced to a document or dated note?
• Have you distinguished official deadlines from your own planning dates?
• Have you checked the current official route before submitting?
• Have you saved proof of what you sent and when?