Build a chain-of-custody log from the capture papers
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- From the capture notes, list who held the device or file, when, and what hashes or export logs exist, marking gaps.
- What the lawyer must review
- Do not let the log invent a custodian
- Treat a broken chain as going to weight
- Written for / version
- US
Open a jurisdiction version of this task to see which instruments apply: US
Who does what
| Role | What they do |
|---|---|
| Assistance | From the capture notes, list who held the device or file, when, and what hashes or export logs exist, marking gaps. |
| Lawyer | Set the scope, supervise the work closely, verify every part relied on, resolve omissions and exceptions, and approve the exact output. |
Checklist
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Verify every relied-on citation, figure and name against the source document.
- The responsible lawyer approves the exact version before use.
Forms and precedents for this task
| Form or precedent | Kind | AI use | Summary |
|---|---|---|---|
| NSW gate before compelled or suppressed material enters a generative AI program | Checklist | AI use Yellow | A gate, under Supreme Court Practice Note SC Gen 23 paragraph 9A, before subpoenaed, suppressed, or compulsion material is entered into any generative AI program, including a closed one. |
| Letter asking that devices and native files be preserved | Letter | AI use Red | Letter asking a party or a non-party to keep devices, accounts and native files so that an authenticity question can still be investigated, without claiming that the letter is a court order. |
Signed-in accounts can read the full text of each one. All precedents.
Sources
Confirm the required checking with the responsible lawyer before work starts. The checking approach does not establish permission to use AI.