# Privilege review cost per document on Mac: where lawyers lose time in 2026

> Privilege review cost per document is labor, not a price list. Learn how to time a batch, price it, and cut log time with a 502(d) order and safer redaction.

URL: https://www.lazur.app/for/lawyers/problems/privilege-review-cost-per-document
Updated: 2026-11-07

Privilege review cost per document is the time a person spends reading one document, deciding whether it is privileged, and logging that decision. No study that prices privilege review per document turned up in our research. This page shows how to build that number from your own timing, where the money goes, and fixes you can use this week.

## Quick answer

- Per-document cost is minutes per document, times your cost per minute. Build it from your own timing.
- No study that prices privilege review per document turned up in our research. Measure a real batch.
- A Rule 502(d) order and an agreed log format cut review you do not need.
- Preview can leave hidden text in a redacted PDF. Test every file with a search and a paste.
- Lazur explains, points, dictates and drafts. It does not decide privilege or click for you.

## What privilege review cost and log time costs you

- **Reviewer hours on every document.** Every document in the set needs a person to read enough of it before a privilege call. Multiply your minutes per document by the number of documents, then by your cost per minute. That product is the cost you pay before a single log entry exists.
- **Partner second looks.** Hard calls often go up the chain. Track partner minutes on their own line, at the partner's rate, so they do not hide inside the reviewer total. Those are the files with the most risk, so they are also the ones where time matters most.
- **Log writing time.** Each log entry takes minutes to write well, and the description must match the document. Logs written late, after a deadline, often need a second pass. Time the log as its own cost, separate from the review.
- **Mistaken production and clawback work.** If privileged material goes out by mistake, you spend time on notices, clawback letters and checks of what the other side already read. A 502(d) order and a clear clawback window reduce that fight, though they do not remove the duty to act on obvious signs.
- **Redaction that leaks text.** A redaction that leaves text in the file can expose the content it was meant to protect. The fix means re-redacting and re-producing, which takes more time than a test. Test each redacted file before it leaves your desk.
- **Burnout and workload.** The 2026 ABA-commissioned study found 47% of surveyed lawyers screened positive for high burnout. It does not link that figure to privilege review. Repeated reading is still a workload you can reduce, and reducing it helps the people doing it.

## Why it happens

1. **Every document needs a human read.** A person still reads documents before making a privilege call, and that reading is the main labor in the process. Software can sort and group files, but the decision about what a document says and who it went to still lands on a reviewer. Every extra file adds reading time.
2. **Keyword searches are over-inclusive.** A 2019 arXiv study of privilege review notes that keyword searches are over-inclusive. A broad search sends more documents to a person, so more reading. The same study says little published research has confirmed how predictive modeling performs against keyword searches for privilege. Test the search terms on a sample before you run the whole set.
3. **Repeated content across custodians and threads.** The same email chain can sit in several mailboxes. Quoted replies repeat earlier messages inside each new one. Without deduplication and threading, a reviewer can read the same text again and again, and the cost grows with each copy.
4. **The log format is left open.** Rule 26(b)(5)(A) requires a description but sets no deadline and no log format. Teams that leave the format until the end of production then argue about detail. That argument costs time on both sides, and it happens when deadlines are closest.
5. **Mistakes that trigger rework.** Privilege mistakes often come from fast calls on unclear documents, and from redaction that does not remove hidden text. Each one can create extra rework, such as a notice to the other side or a clawback request. Rework adds reading and writing on top of the first pass.
6. **No shared privilege rules.** When reviewers apply different tests, the same kind of email gets different calls. Second looks then rise, and so does the time. A short written rule set, agreed before review starts, reduces that churn and gives reviewers one standard to apply.

## How to fix it

- **Get a Rule 502(d) order early.** Ask for a 502(d) order at the start of the case, with a clawback window and a clear standard. EDRM says these orders aim to reduce costly inquiries into inadvertence and into the reasonableness of review. You still must act on obvious signs of inadvertent production. Confirm the wording with the lawyer who runs the case.
- **Set the log format at the Rule 26 conference.** Propose fields and any category logging before the first production. Rule 26(f)(3)(D) now asks parties to state their views on privilege issues, including the timing and method for logging. Put the agreement in writing, then check your judge's standing order for anything extra.
- **Time a sample, then change one thing.** Measure minutes per document on a sample batch, change one process, and time the same kind of batch again. One change at a time shows what worked. Skip the big reorganization until you know which step costs the most.
- **Thread and deduplicate before the read.** Ask your vendor or IT team what threading and deduplication they can run before review. Group an email with its quoted replies and its attachments, then review the family as one unit under a written rule. Put that rule in the review protocol so every reviewer applies it.
- **Use Outlook search to narrow, then check.** Search for lawyer names, firm domains and phrases such as 'legal advice' to shrink the set before reading. Then check the hits against the actual messages. Search narrows the work. A lawyer still makes the privilege call on each message that remains.
- **Compare log versions in Word.** When a colleague revises the log, use Word's compare tool rather than rereading the whole file. In Word for Mac, choose Review > Compare. Read only the changes, then confirm the final entries against the source documents.
- **Redact with Sanitize and test the output.** Use a redaction tool that removes hidden text, such as Acrobat's Redact tool with Sanitize on. Macworld says Sanitize is on by default. After redacting, search for each removed word and copy from the redacted area. Send only the files that pass both checks.
- **Dictate log entries with fn.** Hold fn and speak each log description, then correct names by hand. Add names the dictation tool gets wrong to your personal dictionary. Dictation suits short, repetitive text like log entries. Check each entry against its document before you save it.

## What privilege review cost per document measures

Privilege review cost per document is the labor you spend on one file before you can call it privileged or not. That labor covers opening the file, reading enough of it, checking the author and recipients, and recording the decision. Labor has a price, so the cost is time multiplied by the rate of the person doing the work. Reading is usually the biggest share of that time.

![A lawyer reading printed documents at a desk during privilege review](https://lfobmih1tpj3sgpo.public.blob.vercel-storage.com/content-images/problem/privilege-review-cost-per-document/privilege-review-cost-per-document-1-26573d.jpg)

Treat any per-document number you see as a claim to test. Vendors and firms often price review by the hour, by the gigabyte, or by the batch. Converting that into a per-document figure takes arithmetic you can do yourself. No study that prices privilege review per document turned up in our research, so the sections below build the number from your own timing.

## How to work out your own cost per document

Start with a sample, not a guess. Pick a batch that looks like the rest of the set, such as a few email threads and a few attachments. Time the whole batch with a stopwatch app, or ask Lazur to start a timer. Count the documents, then divide the minutes by the count. The result is minutes per document for that batch.

Convert minutes to money next. Divide your hourly cost by 60 to get the cost of one minute. Multiply that by minutes per document. Run the same arithmetic on a second batch from a different custodian. Two batches that look alike can still differ, and a single batch hides that.

Here is a worked example with a real figure. The U.S. Bureau of Labor Statistics lists a May 2025 median lawyer wage of $159,670 a year, or $76.76 an hour. At that rate, one minute of a lawyer's time is worth about $1.28 in salary terms. Multiply that by your measured minutes per document. Then swap in your firm's billed rate, because clients pay billed rates, not salaries.

| Measure | How to record it | What it tells you |
| --- | --- | --- |
| Minutes per document | Stopwatch on a sample batch, divided by the document count | Your baseline before any change |
| Cost per minute | Hourly rate divided by 60 | Turns time into money |
| Hard calls per batch | Count files sent to a partner for a second look | Shows where judgment costs time |
| Log writing minutes | Time spent writing log descriptions for the same batch | Shows the cost of the log, separate from review |

_A simple tracker for each review batch._

## Mistakes that make the number look better or worse than it is

- Timing only the easy documents. Time a mix of short emails and long attachments, or the average flatters you.
- Counting families as one document. An email with an attachment is at least two review items. Pick your unit and write it down.
- Leaving out second looks. A partner reviewing your hard calls adds time that a reviewer's timer never shows.
- Mixing salary and billed rates on one sheet. Label which rate you used, so two batches can be compared.
- Forgetting the log. Writing descriptions takes its own time. Track it on a separate line.

## What privilege review costs beyond the hourly rate

The hourly rate is only part of the bill. A RAND study called Where the Money Goes looked at where e-discovery production money goes. A CloudNine summary says RAND found review for relevance, responsiveness and privilege was about 73% of production costs. Processing was about 19%, and collection about 8%. The same summary says outside counsel services were about 70% of total production costs.

Read those figures with care. They come from a secondary summary, not the RAND report itself. Another summary gives a different split, with review at 69% and collection at 12%. The study also covers large companies, not all litigation, and it covers review in general, not privilege alone. Check the original before you quote these numbers in a memo.

- **73%** Share of e-discovery production cost spent on review, per RAND 2012 (secondary summary) ([source](https://cloudnine.com/ediscoverydaily/electronic-discovery/ediscovery-trends-where-does-the-money-go-rand-provides-some-answers/))
- **$76.76** Median lawyer hourly wage, May 2025, from the BLS Occupational Outlook Handbook ([source](https://www.bls.gov/ooh/legal/lawyers.htm))
- **47%** Lawyers who screened positive for high burnout in the 2026 ABA-commissioned study ([source](https://www.nclap.org/when-demands-equal-distress-an-updated-understanding-of-lawyer-mental-health-and-well-being/))

Cost is not only money. A 2026 study commissioned by the American Bar Association, run with Krill Strategies, surveyed about 37,000 actively licensed lawyers. It found 47% screened positive for high burnout, and 16% met the severe burnout threshold. The study does not measure privilege review. It does show how heavy the work feels across the profession. Any change that cuts reading you do not need deserves a test for that reason alone.

## Why privilege review takes so long

Three things slow privilege review down. First, a person still reads documents before making a call. Second, keyword searches cast a wide net. A 2019 study of privilege review notes that keyword searches are over-inclusive, which sends more files to a human. Third, the same material repeats. An email chain can sit in several custodians' mailboxes, and each copy gets read again.

## Where the time goes inside a document set

Email threads are a common source of repeated reading. A thread holds earlier messages, quoted replies and signature blocks. Any one message can name a lawyer in the cc line, which makes the privilege call harder than the topic suggests. Attachments add more work. An email and its attached memo are separate review items, but the memo often carries the privilege claim on its own.

- Quoted replies inside a long thread, read again in every message
- Attachments that match a parent email and need a family decision
- Duplicates of the same message across custodians
- Signature blocks and disclaimers that name counsel but carry no legal advice
- Forwarded messages that move a privileged email to a wider audience

## Use a Rule 502(d) order to cut the review you do not need

A Rule 502(d) order can cut review you would otherwise do, without buying software. Federal Rule of Evidence 502(d) lets a federal court order that a privilege is not waived by disclosure connected with the litigation. The order also covers other federal and state proceedings. If a privileged document slips out, you have a clawback path instead of a fight about whether you were careless.

EDRM says a 502(d) order aims to scale back costly inquiries into inadvertence and into the reasonableness of privilege review. It quotes the Advisory Committee: 'The rule does not require the producing party to engage in a post-production review.' The duty does not vanish, though. The producing party must still act on obvious signs of inadvertent production. You can skip a deep re-review. You cannot ignore an obvious privileged email from the general counsel.

Negotiate the clawback timing too. EDRM's sample order gives 40 days to claw back used documents and 60 days for partially used ones. These windows are examples from one sample order, not rules for your case. No source here gives a dollar or hour figure for the savings, so time a batch before and after the order. Confirm the wording with the lawyer who runs your case, and follow your court's local rules.

## Agree on a privilege log format before you start logging

Rule 26(b)(5)(A) says a party that withholds privileged material must expressly make the claim. It must also describe the withheld documents in a way that lets other parties assess the claim without revealing protected content. The rule sets no deadline and no log format. That gap is where log time piles up, since nothing in the rule caps the detail.

The December 1, 2025 amendments changed the conversation. Rule 26(f)(3)(D) now requires the discovery plan to state the parties' views on privilege issues. That includes the timing and method for complying with Rule 26(b)(5)(A), and whether to seek a Rule 502 order. Rule 16(b)(3)(B)(iv) lets a scheduling order set that timing and method. Raise the log format at the Rule 26(f) conference, not after the first production.

Put your proposal in writing. Name the fields you want, such as date, author, recipients, document type and privilege basis. Ask whether some groups of documents can be logged by category instead of one entry each. Category logging is a method to propose, not a rule the court imposes, so get the other side's agreement in writing and check your court's local rules.

## Technology-assisted review helps responsiveness first

Technology-assisted review has the strongest support for responsiveness review. In a 2011 study, Grossman and Cormack used data from the TREC 2009 Legal Track Interactive Task. They reported that two technology-assisted review teams beat manual review on recall, precision and F1. Humans inspected only a small fraction of the collection.

Privilege is a different question. Privilege turns on who said what to whom, and whether legal advice was the purpose. A 2019 arXiv study compared keyword searches with predictive modeling for privileged documents. Its abstract says little published research has confirmed how predictive modeling performs against keywords for privilege. Read the full paper before you rely on any result from it.

So test before you trust. Run a small set through your tool, have two reviewers check the same calls, and log the disagreements. Write the method down so you can explain it to a court. If a tool sees client documents, your firm's policy on AI and client data applies first.

## Redact produced PDFs on a Mac without leaking hidden text

![Lawyer working on a laptop in an office, reviewing email and case files](https://lfobmih1tpj3sgpo.public.blob.vercel-storage.com/content-images/problem/privilege-review-cost-per-document/privilege-review-cost-per-document-2-3193ac.jpg)

Redaction is where a privilege mistake becomes public. Preview has a Redact tool, added in macOS Big Sur. Open the PDF, choose View > Show Markup Toolbar, then use the Redact button. Preview removes the text under each marked area. The catch is what stays inside the file. One practitioner's test found hidden text survived printing to PDF or exporting from Preview, and Acrobat's Sanitize tool recovered it.

Treat that as a warning to test, not a settled result. The post is one test, and it does not name the macOS version it used. Your file, your macOS version and your PDF software can behave differently. The only reliable check is the one in the testing section below.

## Redaction steps for Preview and Acrobat on Mac

1. Select the original PDF in Finder and press ⌘D to make a copy. Keep the original out of any shared folder.
2. Open the copy in Preview. Choose View > Show Markup Toolbar, then click Redact.
3. Mark each area that must go. Check every page, including any scanned pages inside the file.
4. Save the result under a new name, then close the file.
5. For a production that matters, open the same file in Acrobat and use the Redact tool. Macworld lists Edit > Redact Text & Images. Make sure Sanitize is on, since Macworld says it is on by default. Apply the redactions and save, because Adobe says they become permanent only then.

## Test a redacted PDF before it leaves your desk

Test the output, not the tool. Open the redacted PDF, press ⌘F, and search for a word you removed. If the search finds it, the text is still in the file. Then select an area you redacted and copy it. Paste into a plain text editor. If text appears in your paste, the redaction failed. Repeat the search in a second app, such as Chrome, which can open PDFs in a tab.

A black box drawn on top of text is not a redaction. Adobe's guide says redactions take effect when you apply them and save. Sources also disagree on whether Acrobat redaction needs a paid Creative Cloud plan. Macworld says it does, and Adobe's page is silent on the question. Check Adobe's current plan details before you rely on it.

## Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. Hold ⌥⌘ to ask about anything on screen, and Lazur answers out loud. Ask where something is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. It does not click for you or operate other apps.

For this work, the useful parts are explaining, pointing, dictating and drafting. Hold fn and Lazur dictates clean text at the cursor in any app. It can draft a clawback reminder or a meet-and-confer note for you to review. It does not decide whether a document is privileged, and a draft from Lazur is not legal advice.

Privacy comes first. Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. Your firm's rules still decide what you may share, so check them before you ask Lazur about a privileged document. Pro has a 3-day trial with no credit card, then costs $18 a month. See [pricing](https://www.lazur.app/pricing).

## Dictate log entries in Word without retyping them

Log entries are short, specific and repetitive, which suits dictation. Keep each description factual. Name the author, recipients, date and document type, and state the privilege basis, such as a request for legal advice. Do not describe the privileged content itself, because the log must not reveal what it protects. If Word opens in Reviewing mode first, see [how lawyers turn it off](https://www.lazur.app/for/lawyers/problems/word-opens-in-reviewing-mode).

1. Open the log in Word and click the cell for the next entry.
2. Hold fn and speak the description in full sentences.
3. Read the cell back. Correct names and dates by hand, because dictation can mishear proper names.
4. Add names you use often to your personal dictionary so they come out right next time.
5. Check the entry against the document itself, not your memory of it.
6. Turn on Track Changes with ⇧⌘E if a colleague must edit the log, so every change shows.

## Compare log versions instead of rereading them

When a colleague edits the log, read the changes, not the whole file. In Word for Mac, choose Review > Compare, pick the original and the revised file, and read only what changed. A step-by-step guide is at [how to compare two Word documents on a Mac](https://www.lazur.app/for/lawyers/problems/compare-two-word-documents-on-mac). Save each version with a date in the file name, so the comparison has a clear starting point.

## Narrow the email set in Outlook before anyone reads

Search narrows the set, and it does not make the call. In Outlook, search by a lawyer's name, a firm's domain, or words such as 'privileged' and 'legal advice'. Check the results against how your team writes. A search for the word 'legal' finds many messages with no legal advice in them. For more, see [Outlook for lawyers on Mac](https://www.lazur.app/for/lawyers/outlook).

## What to do next

Start with the timing sample, because every other number depends on it. Then read the 502(d) and log-format rules before your next meet-and-confer. Redact a test file and check it with a search and a paste before anything goes out. None of this needs a new tool to start, and each step gives you a number you can defend.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Where is the Redact button in Preview?”: Lazur circles the Redact control in the Markup toolbar and labels it, so you can click it yourself. (Points at it)
- “Where is the Redact button in Preview?”: Lazur circles the Redact control in the Markup toolbar and labels it.
- “Walk me through turning on Track Changes in this Word file.”: Lazur guides you one click at a time and waits for each click before it continues.
- “Explain who is copied on this Outlook thread.”: Lazur answers out loud about what the thread shows. The privilege call stays with you or your lawyer.
- “Hold fn and dictate the next log entry.”: Dictated text appears at your cursor in Word, so you can check it before you save.
- “Draft a clawback reminder for opposing counsel.”: Lazur drafts the text. A lawyer reviews it before anything goes out.
- “Research how courts treat 502(d) clawback windows in my district.”: Lazur runs the search in its own Chrome tabs and returns a summary and a report. Check each source yourself.
- “Remind me Friday to send the log to the team.”: Lazur adds the reminder to Apple Reminders.

## A plan you can start this week

- **Day 1: Time a real sample batch.** Pick a batch that looks like the rest of the set. Ask Lazur to start a timer, review the batch, and stop the timer when you finish. Divide the minutes by the document count to get minutes per document.
- **Day 2: Price the batch.** Divide your hourly cost by 60 to get cost per minute. Multiply it by minutes per document. Record the result and your log writing minutes on one line in your tracker.
- **Day 3: Read the log rules.** Read Rule 26(b)(5)(A) and Rule 26(f)(3)(D), then your court's local rules and your judge's standing orders. Note any rule about logs, clawbacks or 502(d) orders.
- **Day 4: Draft the proposal.** Draft a clawback clause and a log format with the fields you want. Send the draft to your supervising lawyer. Do not send it to opposing counsel until that lawyer approves it.
- **Day 5: Test one redaction.** Redact one test PDF in Preview, then search for a removed word with ⌘F and copy from the redacted area. If that test fails, repeat it in Acrobat with Sanitize on, if your firm licenses Acrobat.

## FAQ

### What is a typical privilege review cost per document?

No public study we found gives a sourced per-document figure. Build your own from a timed sample: minutes per document, times your cost per minute. The BLS median lawyer wage of $76.76 an hour is a salary figure, not a billing rate, so use your firm's rate for client-facing numbers.

### Does a Rule 502(d) order remove the need for privilege review?

No. The Advisory Committee note quoted by EDRM says the rule does not require post-production review. You still must act on obvious signs of inadvertent production. The order aims to reduce costly inquiries into how careful the review was.

### Does Preview redaction remove hidden text?

Not reliably, according to one test. The Eclectic Light Company found hidden text stayed in a file after printing to PDF or exporting from Preview, and Acrobat's Sanitize tool recovered it. That was one test, and the macOS version was not stated. Test your own output before you send it.

### Can technology-assisted review handle privilege calls?

The strongest published evidence covers responsiveness, using TREC 2009 Legal Track data. A 2019 arXiv study says little published research has confirmed how predictive modeling performs against keyword searches for privilege. Test any tool on a sample and have two people check the disagreements.

### What does FRCP 26(b)(5)(A) require in a privilege log?

It requires an express claim and a description of withheld documents that lets other parties assess the claim without revealing privileged information. The rule sets no deadline and no log format. Your court's local rules or your judge's orders may add detail.

### Can Lazur review documents for privilege?

No, not as the decision maker. Lazur explains what is on screen, points at buttons, dictates text and drafts text for you to review. Privilege calls stay with a lawyer. Check your firm's policy on AI and client data first.

### Does Lazur click buttons in Word or Acrobat for me?

No. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. It does not click buttons or operate other apps for you.

### Is my document sent to AI providers?

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer your question, and they are not stored. Content is never used to train AI models. Your employer's rules still decide whether you may share client material.

### Is there a free trial?

Yes. Pro has a 3-day trial with no credit card. The trial starts when you first open the app. Pro costs $18 a month, or $15 a month billed annually. The pricing page has the current details.

## Sources

1. [When Demands Equal Distress: An Updated Understanding of Lawyer Mental Health and Well-being](https://www.nclap.org/when-demands-equal-distress-an-updated-understanding-of-lawyer-mental-health-and-well-being/), North Carolina Lawyer Assistance Program, checked 2026-11-07
2. [eDiscovery Trends: Where Does the Money Go? RAND Provides Some Answers](https://cloudnine.com/ediscoverydaily/electronic-discovery/ediscovery-trends-where-does-the-money-go-rand-provides-some-answers/), CloudNine eDiscovery Daily, checked 2026-11-07
3. [Occupational Outlook Handbook: Lawyers](https://www.bls.gov/ooh/legal/lawyers.htm), U.S. Bureau of Labor Statistics, checked 2026-11-07
4. [Rule 26. Duty to Disclose; General Provisions Governing Discovery](https://www.law.cornell.edu/rules/frcp/rule_26), Cornell Law School Legal Information Institute, checked 2026-11-07
5. [December 2025 Privilege Protection Amendments to Fed. R. Civ. P. 16 and 26](https://edrm.net/2026/03/december-2025-privilege-protection-amendments-to-fed-r-civ-p-16-and-26/), EDRM, checked 2026-11-07
6. [Rule 502. Attorney-Client Privilege and Work Product; Limitations on Waiver](https://www.law.cornell.edu/rules/fre/rule_502), Cornell Law School Legal Information Institute, checked 2026-11-07
7. [Tailor FRE 502(d) Orders to the Case](https://edrm.net/2025/01/tailor-fre-502d-orders-to-the-case/), EDRM, checked 2026-11-07
8. [Technology-Assisted Review in E-Discovery Can Be More Effective and More Efficient Than Exhaustive Manual Review](https://grossman.uwaterloo.ca/grossman-publications/jolt-2011/), Maura R. Grossman (University of Waterloo), checked 2026-11-07
9. [An Empirical Study of the Application of Machine Learning and Keyword Terms Methodologies to Privilege-Document Review Projects in Legal Matters](https://arxiv.org/abs/1904.01722), arXiv, checked 2026-11-07
10. [How effective and safe is Preview's redaction tool?](https://eclecticlight.co/2020/12/11/how-effective-and-safe-is-previews-redaction-tool/), The Eclectic Light Company, checked 2026-11-07
11. [How to easily redact text in a PDF on your Mac](https://www.macworld.com/article/344869/how-to-redact-text-in-a-pdf-with-the-preview-app-adobe-acrobat-and-pdfpen.html), Macworld, checked 2026-11-07
12. [How to redact a PDF on a Mac step-by-step](https://www.adobe.com/acrobat/hub/how-to-redact-pdf-on-mac.html), Adobe, checked 2026-11-07