Workflow

Build a privilege log that survives a challenge

Turns withheld documents into entries that actually describe the basis, flags the five categories that draw a motion to compel, and separates the documents that should be redacted from the ones that should be withheld.

About 25 minintermediateLitigation, In-house

Your prompt6,625 characters

Still to fill in: The withheld documents, Forum and any protocol, The matter and who the lawyers are

RoleYou are a litigator who has lost documents on a log rather than on the privilege, because the entries said "email regarding legal advice" and a magistrate could not assess anything from that. You write entries that let the other side test the claim without learning the advice, and you treat withholding an entire partly privileged document as the easiest mistake to lose on. You never state the privilege standard from memory, because it varies and because the log is where the variance bites.What I needTurn the withheld set below into a defensible log for Forum and any protocol, and tell me what will draw a motion.InputsWithheld set: The withheld documents Forum and protocol: Forum and any protocol The matter and the lawyers: The matter and who the lawyers are Deadline and volume: Deadline and volume House conventions: House conventions for logsHow to work this1. Fix the rules of the exercise before logging anything: what form the log takes in Forum and any protocol (document by document, categorical, metadata-only), what fields are required, whether a protocol or stipulation supersedes the default, and whether any category is excluded from logging at all. Mark each of these [CONFIRM - local rule, protocol, or order]. Getting the form wrong costs more than getting an entry wrong. 2. For every document, decide the withholding basis separately from the description: attorney-client, work product, common interest, joint defense, or a statutory protection. Where a document carries two bases, say which fact supports which, because a challenge to one should not take both. 3. Write descriptions that actually describe. The entry must let the claim be assessed without revealing the advice: the subject-matter category, the role of every participant including whether each is a lawyer, and whether counsel was sending or receiving. Apply House conventions for logs to the wording. An entry that would fit any withheld document in any case is the entry that draws the motion. 4. Flag the five categories that attract challenges, listing the affected control numbers under each: a document with no lawyer among its participants; a lawyer copied on what is otherwise a business thread; an attachment withheld because its parent is privileged rather than on its own footing; anything whose recipients include a third party outside the privilege; and anything created before the date The matter and who the lawyers are establishes litigation was anticipated, where work product is the basis. 5. Separate withholding from redaction, explicitly. Identify every document that is partly privileged and should be produced redacted rather than withheld in full, because an over-withheld document is the easiest thing to lose and the fastest way to lose credibility on the rest of the log. 6. Produce a gap report for the reviewers alongside the log: which entries lack the metadata needed to defend them, which basis codes are inconsistent with the metadata, and which documents a human has to open again before the log goes out. 7. Do not state the elements of privilege, the work product standard, the effect of copying a third party, or any waiver rule. Where the answer turns on one, mark it [CONFIRM - governing law] and name what the reviewer has to establish.Close with these four sections, every time, without being askedAssumptions I made. Every role I inferred, every basis I assigned from metadata alone, and every date I treated as the anticipation date. Mark each [verify] or [safe]. Where I assumed a participant was a lawyer from a name or a domain, say so; that assumption carries the entry. Where this is weakest. The two or three entries most likely to be challenged successfully. Name them by control number and say what the challenge would be, not that the log is generally defensible. What only you can decide. Options with tradeoffs, never a bare flag. At minimum: whether to log categorically where the protocol permits it. Categorical logging saves most of the work and invites a dispute about the category's boundaries that can reopen the whole set, while a document-by-document log is expensive and much harder to attack. Also yours: whether to produce the over-withheld documents in redacted form now, which concedes that the original call was wrong and removes the strongest thing the other side has to argue with. What would make this materially better. Ranked: the ESI protocol text, the document that establishes when litigation was anticipated, a list of who at the client is a lawyer and who is not, and the parent-attachment relationships for the withheld attachments.Output formatOpen with the form-and-fields block, every item marked [CONFIRM]. Then the log itself in the required fields, one row per document or per category. Then the five challenge categories, each listing the affected control numbers and what the challenge would be. Then the withhold-versus-redact list. Then the reviewer gap report as a task list: control number, what is missing, who has to look at it. Then the four sections.Never do this- If an entry would fit any withheld document in any case, it is too generic. "Email regarding legal advice" is the sentence this prompt exists to prevent. - No hedging filler. "Arguably privileged" is not a basis code. Assign the basis or send it back for a second look. Do not tell me to consult an attorney; I am the attorney signing this log. - Never state the elements of privilege, the work product standard, or any waiver rule, and never cite a case or a rule. Everything legal is [CONFIRM - governing law]. Never invent a participant, a date, a role, or a control number that is not in my input. - Where the metadata does not tell you whether a participant is a lawyer or whether counsel was giving advice, say you do not know and put it in the gap report. Do not assign a basis to keep the log complete. - Do not pad the entries. A description that says what is needed to assess the claim and stops is the correct length. Length is not value.Before you answer- Does every entry name the role of every participant and say whether counsel was sending or receiving? - Did I state any element of privilege or any waiver rule rather than marking it [CONFIRM]? - Is every partly privileged document on the redact list rather than the withhold list? - Did I invent a participant, a date, or a control number? - Would this log be useless in a different matter? It should be.

The run walks turn one, the pressure test, the follow-up, and a check on what came back. The Cockpit adds driver's-seat tunes. Your values come with either one.

Pressure-test it

Makes the AI switch hats and attack its own answer.

A motion to compel arrives with your log attached as Exhibit A and four entries highlighted. Read the whole log as the magistrate judge deciding that motion: which entries tell you nothing you could assess, which basis code is contradicted by the metadata sitting in the same row, and which single entry would make you order the document produced rather than order an in camera review? Then tell me which entries I fix before the deadline and which I let go.

Go deeper

Pushes the work further once the basics are right.

Logs are built by reviewers and defended by partners, and the gap is where the entries go wrong. Write the reviewer instruction for this set: the basis codes with the fact each one requires, three model entries drawn from this matter's own documents, the five situations where a reviewer stops and escalates rather than coding, and the one-line rule for deciding withhold against redact.

4Check what came backPaste the answer here and work a checklist against this prompt's own rules.

Before you run it

What to gather first

The withheld set with its metadata: author, recipients, copies, date, type
Who the lawyers are, inside and outside, so roles can be stated
The forum and any ESI protocol or stipulation governing the log
When litigation was actually anticipated, and what document establishes it
Whether a categorical log is permitted or agreed

Watch for

What a log must contain, and whether categorical logging is permitted, varies by forum, by protocol, and sometimes by judge. Nothing here establishes the requirement; the rule and the order do.
The model cannot tell whether a participant is a lawyer or whether a communication sought legal advice. Every basis it assigns from metadata alone is a guess a human has to confirm.
Over-withholding is the most common way a log is lost. A partly privileged document withheld in full costs you the document and the court's confidence in the rest of the log.
A log entry can itself waive privilege if it describes the advice rather than the subject matter. Read every description for what it gives away.
Do not paste privileged document text. Metadata and subject lines are usually enough to build a log, and the content is the thing you are protecting.

What comes back

A form-and-fields block with every requirement marked [CONFIRM], the log in the required fields, the five challenge categories each listing affected control numbers and the challenge, the withhold-versus-redact list, a reviewer gap report as a task list, and the four closing sections.

See an example of what you’ll get

Form and fields. [CONFIRM - the ESI protocol at Dkt. 41 and any standing order.] I have assumed a document-by-document log for pre-complaint materials and categorical logging for post-complaint communications with outside counsel, on the basis of what you described. If the protocol permits categorical treatment more broadly, roughly 600 entries come off this exercise. Fields assumed: control number, date, type, author with role, recipients with roles, copies with roles, basis, description. [CONFIRM - whether this forum requires the subject line, and whether attachments must be logged separately from parents.] Log (excerpt) | Control | Date | Type | Author (role) | Recipients (roles) | Basis | Description | |---|---|---|---|---|---|---| | PRIV-00012 | 2026-02-03 | Email | M. Farrow (in-house counsel) | D. Reyes (VP Engineering) | AC | Counsel providing legal analysis to the business owner concerning the scope of the departing employee's confidentiality obligations | | PRIV-00013 | 2026-02-03 | Attachment (.docx) | M. Farrow (in-house counsel) | Same | AC | Draft analysis prepared by counsel, transmitted with PRIV-00012 | | PRIV-00047 | 2026-01-22 | Email | D. Reyes (VP Engineering) | S. Okonjo (VP Sales), cc M. Farrow (in-house counsel) | See gap report | Business discussion of customer-account transitions; counsel copied | | PRIV-00188 | 2026-02-19 | Email | J. Keller (outside counsel) | M. Farrow, T. Lin (in-house counsel) | AC/WP | Outside counsel providing legal advice and impressions concerning anticipated claims; prepared after the Feb 11 hold notice | | PRIV-00203 | 2026-02-24 | Email | M. Farrow (in-house counsel) | D. Reyes; A. Sethi (Ridgeline Partners, financial advisor) | See challenge category 4 | Counsel communication transmitted to a non-employee third party | Challenge categories 1. No lawyer among the participants (14 documents: PRIV-00061 to 00074). Every one is an internal thread between business people. Work product is the only available basis and it requires a fact about who directed the work. Unless a lawyer directed these, they are producible. Highest exposure on this log. 2. Lawyer copied on a business thread (31 documents, including PRIV-00047). The cc does not make a business email privileged, and a magistrate reading this log will find these first because the metadata shows it. Each needs a human read for whether legal input was actually sought. 3. Attachments riding on their parents (6 documents, including PRIV-00013). PRIV-00013 stands on its own footing because counsel prepared it. The other five are business documents attached to privileged emails and are almost certainly producible as attachments. 4. Third-party recipients (3 documents, PRIV-00203, 00204, 00219). All three include Ridgeline Partners. [CONFIRM - governing law on whether a financial advisor falls inside the privilege here and what the common-interest requirements are.] Whatever the answer, these three need a decision rather than a basis code. 5. Pre-anticipation work product (22 documents dated before Feb 11). You identified the Feb 11 hold notice as the anticipation date, but the Jan 28 demand letter is the better date and it is the one the other side will use against you. Either way, work product claimed for anything before the earlier of the two needs a fact, not a code. Withhold against redact (9 documents). PRIV-00047, 00052, 00088, 00091, 00103, 00129, 00147, 00160, 00171. Each is a business thread with one embedded paragraph of legal input. Produce redacted. Withholding these in full is the thing most likely to cost you credibility on the 2,000 entries that are fine. Reviewer gap report | Control | What is missing | Who looks at it | |---|---|---| | PRIV-00047 and 30 others | Whether legal input was sought or counsel was merely copied | Second-level reviewer, document open | | PRIV-00061 to 00074 | Who directed the work, and when | Farrow or Lin, from memory and calendar | | PRIV-00203, 00204, 00219 | Ridgeline's engagement terms and whether counsel directed their work | Partner decision, not a reviewer call | | 6 attachments | Parent-child relationships, which the export does not carry | Vendor re-export | --- Assumptions I made. That Farrow and Lin are the only in-house lawyers and that everyone else named is not a lawyer [verify: I inferred roles from the names you gave me and one wrong inference invalidates every entry it appears in]. That Ridgeline Partners is an outside financial advisor rather than an affiliate [verify]. That the Feb 11 hold notice is the date you intend to assert for anticipation [safe, you told me, though see below]. Where this is weakest. PRIV-00203 is the single most vulnerable entry: it shows counsel sending to a named third party on the face of the log, which is an invitation. Second, the 22 pre-Feb-11 work product entries are weak in a specific way, because your own hold notice is dated Feb 11 and the demand letter is dated Jan 28. The other side will argue you anticipated litigation on Jan 28 and are claiming work product from an earlier date than your own documents support, or the reverse, depending on which helps them. Pick the date now and make the log consistent with it. Third, the 14 no-lawyer documents in category 1 have no basis on the face of the log at all. What only you can decide. Whether to log the 600 post-complaint outside-counsel communications categorically. Categorical logging removes most of the remaining work and hits the deadline comfortably, and it invites a fight about where the category's edges sit that can reopen the entire set if you lose it. Document-by-document costs roughly a week of reviewer time you do not have and is very hard to attack. Second, and more immediate: whether to produce the nine over-withheld documents in redacted form now or wait to be challenged. Producing now concedes the original call was wrong on nine documents and removes the best argument the other side has about the log's reliability; waiting preserves the position and means any challenge is argued against a log that a magistrate has already been told over-withholds. What would make this materially better. Ranked by impact: (1) The ESI protocol text, which decides whether 600 entries exist at all. (2) A definitive list of who at the client holds a law licence, which underpins every role assignment above. (3) The decision on the anticipation date, Jan 28 or Feb 11, which resolves 22 entries and has to be made before the log goes out rather than in response to a motion. (4) The parent-child export for the attachments.

Why this prompt is built the way it is

## Framework 1. **Fix the rules before logging anything:** the form the log takes, the required fields, any protocol or stipulation that supersedes the default, and the deadline. Confirm, never assert. 2. **State the basis separately from the description,** and where a document carries two bases, say which fact supports which. 3. **Write entries that permit assessment:** subject-matter category, the role of every participant, and whether counsel was sending or receiving. 4. **Flag the five categories that draw motions:** no lawyer on it; a lawyer copied on a business thread; an attachment riding on its parent; anything shared with a third party; anything predating the litigation the log implies was anticipated. 5. **Separate withholding from redaction.** 6. **Produce the reviewer gap report,** not only the log. 7. **Never state the privilege, work product, or waiver standard.**