Turn a Bulk Document List into a Privilege Log in One Prompt Session

The task

You're a litigator or paralegal who just finished a responsiveness pass and now has a stack of documents flagged "withhold — privileged." You need to turn that pile into a defensible privilege log before the production deadline. This piece gives you a prompt chain that takes pasted document metadata and returns a Rule 26(b)(5)-compliant log plus a QC pass — no file uploads, no new SaaS.

Before AI

A paralegal opens each withheld doc, copies the metadata into a spreadsheet, drafts a one-line description that doesn't accidentally reveal the privileged content, picks the right privilege basis, and flags anything odd for the associate. On a 100-document batch, that's roughly a full day of billable time, and the descriptions drift in style by hour four.

The news hook: with OpenAI's Decisions API push into cheaper bulk legal review, the "we can't afford to automate this" argument is getting weaker. But most teams don't need a new API — they need a prompt that actually works in the chat window they already pay for. A privilege log is created during the course of discovery to identify and describe documents that are responsive to a discovery request, but are withheld from production on the basis of attorney-client privilege, work-product protection, or another privilege.

The workflow

The chain has three steps: generate the log, run a privilege-waiver QC pass, then produce a cover memo for the supervising attorney. Paste your metadata table into Step 1 and let the chain run.

Step 1 — Generate the metadata-plus privilege log

A metadata-plus log is the format most courts now accept: objective fields pulled from the document, plus one short description. The metadata-plus format exports objective metadata, author, recipient, date, subject, file type, and adds one short description field.

You are a senior litigation paralegal drafting a Rule 26(b)(5) privilege log in the metadata-plus format. The user will paste a tab- or pipe-delimited table of withheld documents. Columns may include: DocID, Date, Author, Recipients, CC, Subject/Title, FileType, Custodian, and a short Notes field describing why it was flagged.

For each row, produce one log entry with these columns, in this order:
1. DocID
2. Date (YYYY-MM-DD)
3. Author (name, title if given)
4. Recipients (names; mark external parties with [EXT])
5. CC/BCC
6. Document Type (Email, Memo, Draft Agreement, Handwritten Note, etc.)
7. Privilege Asserted — pick from: Attorney-Client, Work Product, Attorney-Client + Work Product, Common Interest, Joint Defense
8. Description — one sentence, max 25 words. Describe the SUBJECT MATTER and PURPOSE of the communication (e.g., "Email reflecting legal advice from outside counsel regarding draft indemnity provisions in Vendor MSA") WITHOUT revealing the substance of the advice itself. Never quote the document. Never state the legal conclusion given.

Rules:
- If an attorney is on the communication, name them and note "(counsel)" after their name the first time they appear.
- If no attorney appears on the face of the document, do NOT assert Attorney-Client unless Notes indicates the document reflects or was prepared at the direction of counsel — in that case, use the description to say so.
- Work Product requires anticipation of litigation. If Notes doesn't support that, don't assert it.
- If a row is ambiguous or missing a key field (no author, no date, no recipients), still output the row but put "⚠ REVIEW" in the Privilege Asserted column and explain the issue in the Description.
- Output as a markdown table. Nothing else — no preamble, no closing commentary.

Here is the metadata table:

DocID | Date | Author | Recipients | CC | Subject | FileType | Custodian | Notes
NSC-00142 | 2025-03-04 | Rhea Alvarado (GC) | Jon Petrov (CEO); Mia Chen (CFO) | - | RE: Draft response to Westlake demand letter | Email | Petrov | GC advising on litigation response strategy
NSC-00143 | 2025-03-04 | Jon Petrov (CEO) | Rhea Alvarado (GC) | Mia Chen (CFO) | RE: RE: Draft response to Westlake demand letter | Email | Petrov | CEO reply to GC seeking further advice
NSC-00144 | 2025-03-05 | Rhea Alvarado (GC) | outside-counsel@brantford-llp.com | Jon Petrov (CEO) | Westlake — litigation hold scope | Email | Alvarado | GC looping in outside counsel re anticipated Westlake suit
NSC-00151 | 2025-03-07 | Mia Chen (CFO) | finance-team@nsc.example | - | Q1 close checklist | Email | Chen | Flagged by reviewer — attachment referenced legal reserve estimate from GC
NSC-00158 | 2025-03-09 | - | - | - | Scanned handwritten note re Westlake | PDF | Petrov | No metadata; found in CEO folder labeled "Westlake-privileged"
NSC-00163 | 2025-03-11 | Daniel Osei (Brantford LLP, outside counsel) | Rhea Alvarado (GC); Jon Petrov (CEO) | - | Memo: assessment of Westlake claims | DOCX | Alvarado | Outside counsel work product memo prepared after demand letter received
NSC-00170 | 2025-03-12 | Rhea Alvarado (GC) | Jon Petrov (CEO) | - | Settlement authority request | Email | Alvarado | GC seeking board authority; attaches draft term sheet
NSC-00181 | 2025-03-15 | Jon Petrov (CEO) | spouse@personal.example | - | Rough week | Email | Petrov | Personal email; reviewer unsure why flagged — mentions "the lawsuit thing"

Step 2 — QC pass for waiver and over-designation risks

The log is only as good as its weakest entry. One email to a spouse or a vendor can waive the whole thread. Your privilege log should provide sufficient information to allow the other party to assess the privilege claim, including establishing all of the elements of attorney-client privilege or work product protection. This step pressure-tests each row.

You are now switching roles to opposing counsel reviewing the privilege log you just produced. Your job is to find entries you would challenge in a meet-and-confer or motion to compel.

Go through the log row by row and output a QC table with these columns:
1. DocID
2. Risk Level — High / Medium / Low / None
3. Issue — pick from: Possible Waiver (third party on comm), No Attorney Visible, Work Product Without Litigation Trigger, Description Too Vague, Description Reveals Substance, Over-Designation (looks like business advice, not legal), Missing Metadata, Personal Comm Not Privileged, Other
4. Recommendation — specific fix (reword description, downgrade privilege basis, remove from log and produce, split entry, confirm with custodian, etc.)

Rules:
- Only flag rows with a real issue. If a row is clean, omit it from the QC table.
- At the end, below the table, add a "Batch-level flags" bullet list for anything that affects multiple entries (e.g., "Thread NSC-00142/143 — confirm no non-privileged forward exists before logging").
- Be concrete. "Reword to..." is better than "revise description."
- Do not reproduce the full log. Only output the QC table and the batch-level flags.

Step 3 — Cover memo for the supervising attorney

The associate or partner signing the log needs a one-page orientation, not the full table. This prompt converts the QC output into a reviewable memo.

Draft a short cover memo to the supervising attorney who will sign off on this privilege log. Use this structure, nothing more:

**TO:** Supervising Attorney
**FROM:** Reviewing Paralegal
**RE:** Privilege Log — [infer matter name from the data, e.g., "Westlake Matter"] — Batch for Review
**DATE:** [today]

1. **Batch summary** — one sentence: how many entries, date range, primary custodians, privilege bases asserted (with counts).
2. **Items requiring your decision** — bulleted list of every High-risk and Medium-risk item from the QC pass, each with: DocID, the issue in plain English, and the recommended action. Keep each bullet under two lines.
3. **Items I recommend removing from the log and producing** — bulleted list, with one-line rationale each. If none, say "None."
4. **Open questions for the client / custodian** — bulleted list of factual questions you need answered before the log can be finalized (e.g., "Was outside counsel engaged before or after March 4?"). If none, say "None."

Write in a direct, professional tone. No hedging language ("it may be the case that..."). No restating of the log. Keep the whole memo under 350 words.

Gotchas

• The model will cheerfully assert Attorney-Client on an all-business email if an attorney is cc'd. The Step 1 rules push back on this, but spot-check anyway — presence of counsel ≠ legal advice.
• Handwritten notes and scans with no metadata (like NSC-00158 in the sample) will be guessed at. The prompt flags them with "⚠ REVIEW" but a human has to actually open the file. There is no shortcut here.
• Thread deduplication is not handled. If your source data has the same email chain logged five times with different reply counts, you'll get five log entries. Dedupe upstream.
• Format choice matters legally. Rules around privilege logs have changed over time, so it's important to know what your choices are today. There are four common formats, and metadata-plus is not accepted everywhere — check the governing case management order or local rule before using this chain. The ABA's overview of privilege log types is a reasonable starting point.
• Never paste actual client documents or PHI into a consumer chat tool. This workflow is designed to run on metadata only — the DocID, dates, senders, and subject lines you'd normally see in your review platform's export. If subject lines themselves are privileged, redact before pasting.
• The log is a draft. The rule doesn't require a document-by-document log, and a thin one can waive the privilege it's meant to protect. An attorney still signs it, and an attorney still owns the privilege calls.

Time saved

A manual metadata-plus log runs roughly 2–3 minutes per entry once a paralegal is in rhythm — call it ~4 hours for a 100-doc batch, plus a second pass for QC. This chain produces the first draft and the QC table in a single sitting; realistic attorney/paralegal review time afterward is around 45–60 minutes for the same batch. Conservative estimate: ~3 hours saved per 100-doc batch, with the bigger win being consistency of description language across the log.

What we got when we ran it

We executed every prompt above, in order, against the sample input (model: claude-sonnet-4-6). Outputs below are real and unedited apart from length truncation.

Step 1 output

| DocID | Date | Author | Recipients | CC/BCC | Document Type | Privilege Asserted | Description | |-----------|------------|-------------------------------|--------------------------------------------------------------|----------------------|---------------|----------------------------------|-----------------------------------------------------------------------------------------------| | NSC-00142 | 2025-03-04 | Rhea Alvarado, General Counsel (counsel) | Jon Petrov, CEO; Mia Chen, CFO | — | Email | Attorney-Client + Work Product | Email from General Counsel advising on litigation response strategy in connection with Westlake demand letter. | | NSC-00143 | 2025-03-04 | Jon Petrov, CEO | Rhea Alvarado (counsel), General Counsel | Mia Chen, CFO | Email | Attorney-Client | Email from CEO to General Counsel seeking further legal advice regarding response to Westlake demand letter. | | NSC-00144 | 2025-03-05 | Rhea Alvarado (counsel), General Counsel | outside-counsel@brantford-llp.com [EXT] | Jon Petrov, CEO | Email | Attorney-Client + Work Product | Email from General Counsel to outside litigation counsel transmitting instructions regarding anticipated Westlake litigation hold scope. | | NSC-00151 | 2025-03-07 | Mia Chen, CFO | finance-team@nsc.example | — | Email | ⚠ REVIEW | Underlying email appears non-privileged; privilege may attach only to attached document reflecting legal reserve estimate prepared at GC's direction — attachment must be reviewed separately to confirm. | | NSC-00158 | 2025-03-09 | — | — | — | Handwritten Note (PDF scan) | ⚠ REVIEW | Author, date, and recipients are absent; cannot confirm privilege basis from available metadata — document requires attorney review before privilege can be asserted. | | NSC-00163 | 2025-03-11 | Daniel Osei, Brantford LLP, outside counsel (counsel) | Rhea Alvarado (counsel),

…output truncated at 250 words.

Step 2 output

| DocID | Risk Level | Issue | Recommendation | |-----------|------------|-------|----------------| | NSC-00142 | Medium | Work Product Without Litigation Trigger | Log asserts Work Product, but Notes says "demand letter" received — confirm a specific, concrete anticipation of litigation existed at this date (not merely a business dispute). If only a demand letter exists with no litigation threat, downgrade to Attorney-Client only. | | NSC-00143 | Medium | Possible Waiver (third party on comm) | Mia Chen (CFO) appears in CC. CFO is a non-attorney business officer. Confirm she was included for purposes of obtaining or transmitting legal advice, not for a business purpose. If the latter, waiver argument is viable. Add one clause to description clarifying her role in the privileged communication. | | NSC-00144 | Low | Other | Recipient field lists a raw email address (outside-counsel@brantford-llp.com) rather than a named attorney. Opposing counsel will argue the log fails to identify the recipient as an attorney. Replace with full name, title, and firm of the Brantford LLP attorney who received the email. | | NSC-00151 | High | Missing Metadata; Over-Designation (looks like business advice, not legal) | The logged entry is the email itself, which appears to be a routine finance operations communication. The privilege claim rests entirely on an unlogged attachment. The attachment must be broken out as a separate log entry with its own DocID, author, and privilege basis. The parent email should be removed from the log and produced, or produced with the

…output truncated at 250 words.

Step 3 output

TO: Supervising Attorney FROM: Reviewing Paralegal RE: Privilege Log — Westlake Matter — Batch for Review DATE: 2025-07-14 --- 1. Batch Summary This batch contains eight entries spanning 2025-03-04 through 2025-03-15, with primary custodians Petrov, Alvarado, and Chen; privilege bases asserted are Attorney-Client (2), Attorney-Client + Work Product (3), and entries flagged for review (3). --- 2. Items Requiring Your Decision - NSC-00142 (Medium): Work Product assertion rests on a demand letter alone — confirm litigation was concretely anticipated by March 4 or downgrade to Attorney-Client only. - NSC-00143 (Medium): CFO Mia Chen appears in CC without explanation — confirm she was included to facilitate legal advice, not for a business purpose, or waiver is arguable. - NSC-00144 (Low): Outside counsel recipient is identified only by email address — replace with full name and title before serving the log. - NSC-00151 (High): Privilege attaches to the attachment only, not the parent email — break into two entries, produce the parent email, and log the attachment separately with its own DocID and privilege analysis. - NSC-00163 (Low): Description is marginally vague — reword to specify that outside counsel evaluated the legal merits of claims in the Westlake demand letter in anticipation of litigation. - NSC-00170 (Medium): GC may have been acting in a corporate-officer capacity rather than a legal-advisor capacity — confirm her role and assess the attached term sheet for independent privilege treatment before retaining both on the log. --- 3. Items I Recommend Removing from the Log and Producing

…output truncated at 250 words.

---

This content is for informational purposes only and is not legal advice. Confirm confidentiality, privilege, and jurisdictional rules before using any AI tool with client matters.