WorkflowLegal Operations & Litigation

eDiscovery Document Review & Privilege Log

eDiscovery document review where the agents explain every call, your reviewers decide, and the privilege log holds up on first serve

A privilege log that holds up on first serve, every entry tied to its passage.

See one case, screen by screen ↓
demo10%of the 186,240-document review set needed a person: 18,600 documents, every privilege candidate among them
demo1,108descriptionsof 3,091 log entries rewritten by the privilege checker before the log was served
demo95.7%estimated recall, measured by an elusion sample of 2,401 documents, not assumed
target0entriessent back after service: every log line re-read against Rule 26(b)(5)(A) first
In short

What is eDiscovery Document Review & Privilege Log?

eDiscovery document review software that reviews documents for relevance and privilege and drafts the privilege log, each call cited. Eight agents code the review set, check each other's privilege calls, write the log row by row as reviewers decide and watch productions for slips. Review attorneys make every privilege call, and the supervising attorney signs the log and every production.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

Why review costs the most and the privilege log fails first

Every document that answers the other side's requests for production has to be reviewed, then produced, withheld or redacted. Each withheld or redacted document needs a privilege log entry that lets the other side assess the claim under Rule 26(b)(5)(A): date, author, every recipient and their affiliation, the privilege asserted and a description that does not give the advice away. Review is most of what eDiscovery costs, and the log is usually written at the end, in bulk, from tags and metadata.

That is where it breaks. A reviewer calls an email privileged because the general counsel is on it and misses the outside PR firm on the cc line. Descriptions come out as "email re legal advice". Since 1 December 2025 the timing and method of the log belong in the Rule 26(f) discovery plan and can be written into the scheduling order, so the log is measured against what the parties agreed. A log the other side cannot assess brings a motion to compel, a re-review and, where a third party was left off, an argument that the privilege was waived.

typical$0.50–$1.00a documentfor traditional review by people, before the privilege log, QC and second-level review
demo147of 214documents with a third party on them moved to produce or redact on the sample matter: privilege did not hold
Where a production volume's review days goestimated
By hand20 days
With the solution5.2 days
  • Building batches and tracking pace against the production date1 → 0.2 d
  • First-pass responsiveness and privilege coding8 → 1 d
  • Second-level privilege review and third-party waiver checks4 → 2 d
  • Writing and cleaning up the privilege log3 → 0.5 d
  • QC sampling and reviewer re-checks2 → 0.5 d
  • Redactions, Bates numbering and sign-off2 → 1 d

Estimated split for one rolling production volume on a mid-size matter, by hand and with the solution.

How it works

How a document moves

Eight agents code, check each other and write the log as reviewers decide; the supervising attorney signs.

What comes in
Documents in186,240 · 38 custodians, after de-duplication
Agents at work
Batch plannerback-plans to the date
Then
First-pass reviewerrelevance + privilege
Then
Privilege checkerwaiver + log read
Log writerrow at decision
Then
Redaction agent
QC samplerrecall measured
Then
Production agentBates + serve
Clawback agent502(d) watch
A person decides
Supervising attorneyapproves notes, signs log and production
What comes out
Signed privilege log
Bates production
Defensibility pack
One case, step by step

One privilege call, from the agents' first read to a signed log

Arden Components, Inc. v. Kestrel & Vane Industrial Ltd., in the District of Delaware. Kestrel & Vane is answering 24 requests for production from a review set of 186,240 documents across 38 custodians, and Volume 3 is due Friday 23 October. The agents read, cite and propose; the review attorney decides; the supervising attorney approves and signs. Here is how one email goes, screen by screen, in the working solution.

  1. 01Wednesday, 11:40

    Two days to Volume 3, and one call waiting for her

    Hannah Cole · Review attorney

    Today shows 45 of 46 batches closed and the eight release gates for Volume 3. Under "Needs you", Hannah has one item: batch 14 has a call waiting, because the checker flagged a possible waiver. Below, the agents' latest work is listed: the checker's flag, the batch planner's forecast, the QC sampler's elusion sample.

    “Batch 14: 1 call waiting for you · KV-0031942 · the checker flags a possible waiver: outside PR firm on counsel's advice”

  2. 02Batch 14

    The batch, the document and the log on one screen

    First-pass reviewer

    Batch 14 is a second-level privilege batch of 64 documents from the Okafor and Marchetti threads. KV-0031942, "RE: Arden termination — statement and next steps", is open in the middle with its passages numbered. The first-pass reviewer coded it responsive to RFP 7, 8 and 23 at 0.96 and privileged, attorney-client, at 0.91: "General Counsel gives advice in ¶2 of her 17 Mar message." Under the document, the batch's privilege log is being written as each call is made.

    The header names every participant's role: Sofia Marchetti, attorney · Leah Brennan, third party.

  3. 0311:31 · 6.1 seconds

    A second agent argues with the first

    Privilege checker

    The checker reads the thread: 3 messages, 3 people, 2 domains. Leah Brennan is not counsel. The engagement register shows Halden Brook Communications was engaged by Corporate Communications on 6 Nov 2023 for media relations, with no Kovel letter. Attorney-client privilege is likely waived; work product is tested separately, because Arden's notice of 11 March made litigation foreseeable and ¶2 is counsel's assessment of litigation risk. It recommends producing with one redaction, at 0.87, with each source cited.

    “Hand to the review attorney — A privilege call is never final until a person makes it.”

  4. 04Her decision

    She overturns the first pass, with a reason

    Hannah Cole · Review attorney

    The screen says it plainly: "Agents disagree: first pass withhold, checker produce with one redaction." Hannah chooses Overturn, then "Produce with one redaction", then reason code TP-1, "Third party on the communication — no Kovel engagement", and adds a note for the record. Her decision rewrites the log row and is logged with her name.

  5. 0511:41

    The log row is rewritten in front of her

    Log writer

    Paragraph 2 becomes a redaction box: "REDACTED — WORK PRODUCT · PRIV-02980 · Protocol §4.4". The row that read "Withheld · Attorney-client · Email re legal advice" now names Leah Brennan, Halden Brook Communications (outside PR consultant; third party), and its description passes ESI Order ¶11. The attachment, the holding-statement draft, follows its parent and is produced in full. Batch 14 is complete, and so is review for Volume 3: 46 of 46 batches.

    “Email chain forwarding counsel's 17 Mar 2024 assessment of litigation risk following Arden's 11 Mar 2024 notice of breach, prepared in anticipation of litigation; shared with an outside communications consultant (Halden Brook Communications) for a holding statement.”

  6. 06The same minute

    Her overturn becomes a written rule, with its effect previewed

    Privilege checker

    It is Hannah's second Halden Brook overturn in the matter, so the checker drafts protocol note PN-12: halden-brook.com is a third party, and work product is tested for counsel's litigation assessments after 11 Mar 2024. The preview finds 318 documents in the Volume 4 queue across 9 batches: 37 calls would change, 29 privileged to produce and 8 to redact as work product. The 64 decided Volume 3 documents from the same firm show 0 conflicts.

    “Wait for the supervising attorney — Nothing changes until Elena Brandt approves.”

  7. 07In her queue

    The supervising attorney approves the note, with the evidence beside it

    Elena Brandt · Supervising attorney

    PN-12 waits on Quality with its numbers: 318 documents, 37 calls, 0 conflicts. Beside it is how the review is measured: estimated recall 95.7% from an elusion sample of 2,401, reviewer agreement 96.5%, and the agents' privilege calls overturned 11.2% of the time in batch 1 and 3.1% in batch 46 as approved notes reached the first pass. Jonah Weiss is at 93.4%, and his batch 9 can be re-checked with one click.

    “Overturns fall as approved protocol notes reach the first-pass reviewer. Nothing is retrained in the dark: every change traces to a note.”

  8. 08Before she signs

    The log is read the way opposing counsel will read it

    Privilege checker

    Elena runs the opposing-counsel read on log v3: 3,091 entries checked against Rule 26(b)(5)(A) and ESI Order ¶11, every participant checked for a role and affiliation, and descriptions compared with what courts have sent back. The result: 0 entries at high risk, 41 medium and 3,050 low. The medium ones use thread or attachment wording that the order allows, and a reviewer accepted each one.

    “No entry at high risk. … The log is ready for sign-off.”

  9. 0911:45 · signed

    She signs the log by name

    Elena Brandt · Supervising attorney

    The sign-off shows what she is approving: 3,091 entries, 2,604 withheld and 487 redacted, all 3,091 re-read by the checker, 1,108 rewritten, and the method, ESI Order ¶11, document by document. She picks reason code AP-1, "Meets ESI Order ¶11 and Rule 26(b)(5)(A)", and types her name. Volume 3 then shows 7 of 8 release gates passed; her approval of the production opens only when every gate has passed.

    “I have reviewed the log and the checker's read. I approve it for service with Volume 3.”

  10. 10After production

    A slip in Volume 2 is caught inside the 502(d) window

    Clawback agent

    The clawback agent keeps comparing what was produced with every later privilege decision. On 20 Oct it found that KVI-0104377 to KVI-0104379, produced in Volume 2, are a 98.6% near-duplicate of a withheld memo. Under ¶3 of the Rule 502(d) order, notice is due Tuesday 27 Oct, 6 days away. The notice to opposing counsel is drafted for Elena to sign; the agent never contacts the other side itself.

    “Notice due Tue 27 Oct · 6 days left · found Tue 20 Oct 16:40 by the clawback agent”

Who it’s for

Built for everyone whose name is on the review.

The same matter, seen by four of the people who carry it — what a production week looked like, and what it looks like now.

HC
Hannah ColeeDiscovery review attorney · privilege batches
Review attorney
Before
“I can make the call. I just need to see who was really on the thread, and why the machine thinks what it thinks.”
Now
Sees the passage behind each agent's call, every participant's role and the log row being written, and decides with a reason code.
EB
Elena BrandtSenior Counsel, Litigation · signs the log and every production
Supervising attorney
Before
“My name goes on that log. If the other side can pick it apart, it isn't finished.”
Now
Approves protocol notes with their effect previewed, reads the log as opposing counsel will, then signs the log, each production and each clawback notice.
OA
Owen AchterbergLitigation support manager · batches, pace and settings
Litigation support manager
Before
“Tell me on Tuesday that Friday is in trouble, not on Thursday night.”
Now
The batch planner back-plans to the production date and proposes a re-balance when a reviewer's pace slips; he approves it.
GL
Grace LiuLitigation paralegal · productions and clawbacks
Paralegal
Before
“When a privileged page slips out, the clock on the clawback is days, not weeks.”
Now
Gets clawback notices drafted with the 502(d) clock started and every copy found, and productions assembled behind release gates with their evidence.
Built on the engine

8 agents. Each with one job, and hard limits.

Eight agents code, check each other and write the log as reviewers decide; the supervising attorney signs.

Batch planner

Builds batches by custodian, thread and family, assigns them by load and skill, and back-plans review to the production date, proposing a re-balance when a batch falls behind.

  • Never changes a deadline
  • A re-balance needs the litigation support manager
First-pass reviewer

Codes every document for responsiveness, request by request, and for privilege, highlights the passage behind each call and gives a confidence.

  • A privilege call is never final
  • Cites a passage for every call; below 0.90, and every privilege candidate, goes to a person
Privilege checker

Re-reviews every privilege call and log line: tests waiver against the engagement register, tests work product separately, proposes the narrowest treatment, rewrites descriptions, runs the opposing-counsel read and drafts protocol notes from overturns.

  • Recommends only; never overrides a reviewer
  • A protocol note changes nothing until it is approved
Log writer

Writes the log row at the moment of decision: date, author, every recipient with their affiliation, basis, treatment and a description, logging threads and attachments as the ESI order says.

  • Never logs a document no person decided
  • Never describes the advice itself
Redaction agent

Proposes each redaction box with its basis: privilege, work product, personal data under FRCP 5.2, or third-party pricing under the protective order.

  • Never burns in a box a reviewer has not accepted
QC sampler

Draws elusion and reviewer samples at the confidence in Settings, estimates recall, spots reviewer drift and re-queues a batch for a re-check.

  • Never changes a decision; it reports and re-queues
Production agent

Numbers, endorses and assembles each volume with load file, privilege log and cover letter, checks Bates continuity and families, and serves by secure link.

  • Never serves without the supervising attorney's signature
Clawback agent

Watches produced volumes against later decisions and near-duplicates of withheld documents, starts the Rule 502(d) clock, finds every copy and drafts notices and sequestration certificates.

  • Never contacts the other side
  • Counsel signs every notice
Supervising attorney

Signs the log and every production. The agents propose; a named person decides.

Ask in plain words

Ask about any document, log entry or deadline

Ask in plain words about a control number, a Bates range, the log or the next production — or tell it what to draft. Every answer points to its source and opens the screen it is about.

Why was KV-0031942 flagged?

The first-pass agent coded it attorney-client privileged (0.91) because Sofia Marchetti gives advice in ¶2 of her 17 Mar message. The privilege checker then found Leah Brennan, Halden Brook Communications, on the cc line. Halden Brook was engaged by Corporate Communications on 6 Nov 2023, not through counsel, and has no Kovel letter (ENG-0112). So attorney-client privilege is likely waived, but ¶2 can still be protected as work product. Its recommendation: produce with one redaction, confidence 0.87. The call is yours.

Which log entries would the other side challenge?

One entry is at high risk: KV-0031942. Its description, "Email re legal advice", does not let Arden assess the claim under Rule 26(b)(5)(A). It also leaves out Leah Brennan of Halden Brook, a third party on the thread, which ESI Order ¶11(b) requires. 41 more entries are medium risk.

Draft the clawback notice for KVI-0104377

KVI-0104377 to KVI-0104379 were produced in Volume 2 on 25 Sep. They are a 98.6% near-duplicate of withheld KV-0019220, Wexford Lane's draft termination memo. Under Rule 502(d) Order ¶3, notice is due within 7 days of discovery (20 Oct), so by Tue 27 Oct. The notice asks Corbin & Ashe to sequester and certify within 5 days. Elena Brandt signs it.

How much is left before Volume 3?

One call. 45 of 46 batches are closed. Batch 14 has KV-0031942 waiting for Hannah Cole, plus its attachment, which follows it. After that, the open gates are 618 personal-data redactions to accept and Elena Brandt's sign-off of log v3. Volume 3 is due Fri 23 Oct.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayDays to the next production, its release gates, what needs each person, what the agents did overnight and the team's pace.
The review screenThe batch, the document with the passage behind each call numbered, the log being written underneath, and the agents' calls with You decide.
The privilege checker at workThread, attorney list and engagement register read; attorney-client and work product tested separately; the narrowest treatment recommended, with its sources.
Overturn with a reasonThe treatment, the reason code and a note for the record; the decision rewrites the log row and is logged with the reviewer's name.
The log row, rewrittenThe paragraph redacted as work product with its basis, and the log row naming every recipient and affiliation in words the other side can assess.
A protocol note from an overturnThe overturn written as a rule, with its effect previewed on the documents still to review — waiting for the supervising attorney.
Quality, measuredThe protocol note waiting for approval, estimated recall from an elusion test, reviewer agreement and the agents' overturn rate by batch.
Batches and the back-planEvery batch with its custodians, reviewer, pace and plan, the burn-down to the production date and the batch planner's re-balances.
The opposing-counsel readThe cumulative privilege log read against Rule 26(b)(5)(A) and the ESI order, each entry scored for challenge risk before sign-off.
Waiver checks and the engagement registerEvery document with a third party on it, what the checker found and recommends, beside the register of who counsel engaged and how.
Sign the privilege logEntries, checker re-reads and challenge risk summed up, the method, a reason code and the supervising attorney's typed name.
Clawback watchA produced near-duplicate of a withheld memo with its 502(d) clock and drafted notice, and the other side's clawback with every copy found and locked.
Thresholds and samplingConfidence for a person to review, challenge risk, the clawback near-duplicate threshold, QC and elusion samples, pace and batch alerts.
Governance

Built for defensibility: cited, decided, signed, on the record.

Agents propose, attorneys decideNo privilege call is final until a review attorney makes it. Uphold, overturn and escalate each need a reason code, and every decision is recorded with the reviewer's name.
Every call cites its passage and its authorityEach call shows the highlighted passage and the protocol section, ESI order clause, engagement record, Rule 26(b)(5)(A) or Rule 502 provision it rests on.
Two agents, then a personPrivilege is screened by the first pass, re-reviewed by the checker against the engagement register, and decided by a reviewer; the supervising attorney re-checks a sample of every reviewer's decisions.
Overturns become rules in the openAn overturn can become a written protocol note with its effect previewed. It changes nothing until the supervising attorney approves it, and every call it changes traces back to the note and the overturn.
Signed by the supervising attorneyThe privilege log, each production and each clawback notice are approved with a reason code and a typed name. A production cannot be approved until every release gate has passed.
An audit trail you can defendEvery action by people and agents is recorded in order and never edited, and exports as a defensibility pack with the search terms, custodians, hashes, coding decisions, reviewer identity and protocol notes.
Configuration

Your protocol and your orders, not ours

The rules and thresholds the agents follow are settings for each matter. Changes to the review rules are logged and need the supervising attorney.

SettingDefaultChoose from
Privilege candidates always go to a personAlways onCannot be turned off: an agent never makes a privilege call final
First-pass confidence for a person to review0.90Set per matter; below it, responsive calls go to a reviewer
Code not responsive automaticallyOn, at 0.95 or aboveOn · Off; these are seen only if they fall in a QC sample
Families follow the parent (FM-1)OnOn · Off; the checker can show a different basis for an attachment
Thread loggingPer ESI Order ¶11(c)Per ESI Order ¶11(c) · Every message separately
High challenge risk0.70The score at which a log entry blocks sign-off
Near-duplicate threshold for the clawback watch95%Produced pages compared with withheld documents
Reviewer QC sample · elusion sample2.5% · 95% confidence, ±2%Share of each reviewer's decisions re-checked · confidence and margin
Connections

Works with the systems your review already runs on

Microsoft 365 mail, Teams and OneDrivethrough the legal hold export, custodian by custodian
Document managementmatter workspaces and versions
Legal hold systemcustodians and acknowledgments
Processing from forensic imagesde-duplication, text and metadata
Matter management and e-billingbudget and reviewer time
Secure production deliveryproductions served by link, with receipts
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0entries
sent back after service: every log line re-read against Rule 26(b)(5)(A) first
3,091 of 3,091 entries checked
1,108 descriptions rewritten
estimated
90%
of documents never need a first pass by hand: about $84k–$168k avoided on one matter
First pass by hand186,240 docs
With agents18,600 docs
estimated
95.7%
estimated recall, measured by an elusion sample, not assumed

“demo” = seen in the working solution, on its sample matter · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (ComplexDiscovery / EDRM 2025 pricing surveys — $0.50–$1.00 a document for traditional review, often more). Rules: FRCP 26(b)(5)(A); FRCP 16(b)(3)(B)(iv) and 26(f)(3)(D) as amended 1 Dec 2025; FRE 502(d). People, companies, firms, matters and documents named on this page are fictional — characters and sample data in the working solution.

Questions

What litigation and legal operations teams ask us.

What is eDiscovery Document Review & Privilege Log?

eDiscovery document review software that reviews documents for relevance and privilege and drafts the privilege log, each call cited. Eight agents code the review set, check each other's privilege calls, write the log row by row as reviewers decide and watch productions for slips. Review attorneys make every privilege call, and the supervising attorney signs the log and every production.

How does the AI document review decide privilege, and who makes the final call?

The first-pass reviewer codes each document for responsiveness by request and for privilege, with the passage behind each call and a confidence. The privilege checker then re-reviews every privilege call. Neither makes a call final: a review attorney upholds, overturns or escalates each one with a reason code.

How does it catch a privilege waiver, such as an outside PR firm on the cc line?

The privilege checker reads every participant against the attorney list and your engagement register: who counsel engaged, when, and under which letter — Kovel, common interest or ordinary business. Where a third party is present, it tests attorney-client privilege and work product separately and recommends the narrowest treatment, such as producing with one paragraph redacted.

Will our privilege log hold up under Rule 26(b)(5)(A) and our ESI order?

Every entry is written at the moment of decision with the date, author, every recipient and their affiliation, the basis and a description, then re-read by the privilege checker against Rule 26(b)(5)(A) and the method in your ESI order. Before sign-off it reads the whole log the way opposing counsel will and scores each entry's challenge risk. The target is zero entries sent back after service; on the sample matter, the checker rewrote 1,108 of 3,091 descriptions before the log was served.

How do we know the review found what it should?

Recall is measured, not assumed. The QC sampler draws an elusion sample from what was coded not responsive — on the sample matter, 31 responsive in 2,401, for an estimated recall of 95.7% — and re-checks a share of every reviewer's decisions, so drift shows up while there is time to fix it.

What happens if a privileged document is produced by mistake?

After every volume, the clawback agent compares what was produced with later privilege decisions and with near-duplicates of withheld documents. When it finds a slip, it starts the clock in your Rule 502(d) order, lists every copy by Bates number and drafts the notice for counsel to sign. When the other side claws back, it finds and locks every copy, including deposition exhibit folders, and drafts the certification.

Do attorneys stay in control?

Yes. The agents recommend; review attorneys decide every privilege call with a reason code. A protocol note drawn from an overturn changes nothing until the supervising attorney approves it, and only the supervising attorney can sign the log, approve a production or send a clawback notice. The agents never contact opposing counsel.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your review protocol, orders, attorney list, engagement register and a sample of past logs — and it goes live once every quality gate has passed. We will walk you through it on a sample of your own review set first.

See it on
your matter.

We'll run eDiscovery Document Review & Privilege Log on a sample of your own review set, protocol and past privilege logs.