Build a privilege log from the document set
Key facts
- Human involvement
- RedLawyer-led
- How AI is used
- From the mail and document-system export, extract each item's author, recipients, date, custodian and document type, group email threads and near-duplicates, and list the candidates where a lawyer on the named legal-team list appears or the document is already marked privileged. The tool writes no line of the log: the lawyer decides each claim and words every description, and the tool then checks the finished log for blank fields, entries that conflict across one thread and documents in the set that appear on no line.
- What the lawyer must review
- The lawyer decides each privilege claim on the dominant-purpose test and reads back their own descriptions to confirm none discloses the advice or the instructions it was sought on, that the ground stated fits the document, and that nothing privileged has gone into the production set.
- 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 | Supporting preparation only. Potential support includes extracting and organising information and identifying points for review. Confirm the tool’s capability and permitted scope. The tool writes nothing into the document. Substantive advice, judgement and any restricted content remain with the responsible human. |
| Lawyer | Perform the substantive analysis and decisions. Independently check any permitted supporting work and approve the exact output for its intended use. |
Checklist
- Confirm that the actual tool, feature and processing terms permit use of this information, including access, retention, training and disclosure conditions.
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Resolve exceptions and record the responsible lawyer’s approval of the exact output and intended use.
Forms and precedents for this task
| Form or precedent | Kind | AI use | Summary |
|---|---|---|---|
| Compulsory regulator notice response checklist (ASIC s 33 and ACCC s 155 notices) | Checklist | AI use Red | A step-by-step checklist for an in-house team that receives a compulsory notice from ASIC or the ACCC: triage, preservation, scope negotiation, search records, privilege schedule, signed response and close-out. |
Signed-in accounts can read the full text of each one. All precedents.