Legal Services Offshore research · legal-support-governance

Where does privilege review time accumulate in a production log?

A time-observation design for privilege review that separates reading, redaction, escalation, and log writing without turning the result into a reviewer ranking.

Published · 4 sources

Where does privilege review time accumulate in a production log? research illustration

Research context

This research brief is designed for legal operations planning. Use the findings to ask better workflow questions. Test any proposed process against the firm’s jurisdiction, professional duties, systems, and client commitments. Treat every local result as a starting point for review rather than a universal benchmark.

Question and scope

This study asks where privilege review time accumulates during a document production. It treats the review as a set of observable stages: reading a document, applying a privilege category, redacting, escalating a question, and writing the log entry. The scope is one review team and a fixed document set. The result describes that setting and should not be read as a productivity benchmark.

The unit is one document-review interaction that can be timed. A document opened and closed without a decision is still an event if it consumed review time. Documents that were never assigned are outside the scope. Record the inclusion rule before observing.

Record whether the review session happened before or after the production deadline was set. A session under deadline pressure may show a different stage distribution. Report the timing with the result. That variable helps separate a process issue from a scheduling issue.

Definitions and evidence standard

Define each stage before timing. Reading includes opening and reviewing the document. Coding includes selecting the privilege category and recording the basis. Redaction includes applying the redaction and checking the image. Escalation includes stopping, writing the question, and routing it to the lawyer. Log writing includes completing the production and privilege fields.

Use a time record that the reviewer can complete without disrupting the work. A start and stop timestamp per stage is more reliable than a daily estimate. If the review tool logs activity, use the log and check a sample against the reviewer's note. Do not infer time from the page count alone.

Record whether the reviewer worked from a native file or a rendered image. A native file may show metadata and comments that an image hides. Report the file type with the stage time. The tool affects the review and should not be pooled silently.

Sampling and measurement

Select review sessions across document types and reviewer experience. Freeze the sample before looking at the times. If the team uses more than one privilege category set, report them separately. A training session should be excluded or labeled because it measures learning rather than routine work.

Measure the total time per stage, the median time per document, and the share of documents escalated. Add the number of log entries corrected after review. Report the count of documents and sessions behind each median. A median from a small sample is a description, not a stable estimate.

If a document is escalated, record the question and the lawyer's response separately from the active review time. The wait may be longer than the work. Report both so the team can see whether the bottleneck is judgment or availability. Record the source and the date with the entry.

If a document is escalated, record the question and the lawyer's response separately from the active review time. The wait may be longer than the work. Report both so the team can see whether the bottleneck is judgment or availability. Keep the evidence beside the decision in the file.

Findings and interpretation

Present the stage distribution before suggesting a cause. A large escalation share may mean the privilege categories are unclear. A large log-writing share may mean the fields are poorly designed or duplicated. A large redaction share may reflect the document type. Read a sample of documents behind each stage.

Compare the stages with the lawyer's response time for escalations. A reviewer may wait because the question is unclear or because the lawyer is unavailable. Report the wait separately from the active work. The finding should suggest a specific support change, such as a category guide or a faster escalation route.

Compare the stage distribution with the number of privilege categories in the guide. A long category list may increase coding time without improving accuracy. Report the count beside the median. A simpler guide is easier to test and train.

Compare the escalation rate with the number of privilege categories. A long category list may produce more questions even when the documents are similar. Report the count beside the rate. A simpler guide is easier to test.

Limitations

Timing a review can change how a reviewer works. The observation may add a pause at each stage or encourage a reviewer to skip a careful check. The study also cannot see the legal judgment behind a privilege call. Treat the result as a description of observed sessions, not a measure of review quality.

The document set may not represent the full production, and the window may include a training or a surge. If the category set changed during the window, the stages may not be comparable. Record these limits with the result. Record the source and the date with the entry.

If a document is escalated and later returned with a decision, record the round trip. The wait may be a larger cost than the review itself. Report the round-trip count with the stage times. Keep the evidence beside the decision in the file.

Practical next step

Choose one change that matches the largest avoidable stage, such as a category guide, a log template, or an escalation queue. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same stage definitions. Test it on a comparable set of sessions.

Keep the before and after observations separate so the comparison is honest. Record the sessions that were excluded and why. Review the result with the reviewers and the lawyer who owns the production. If the change does not help, record that result too.

Test the revised guide on one document type before applying it to the whole production. A guide for emails may not fit contracts. Record the type and the result. The next round can compare the same stages.

Comparing document types

Different document types carry different reading and redaction demands. An email may take less time to read than a contract but more time to assess for privilege. Report the count and the median for each type, and label small groups as descriptive only. Record the source and the date with the entry.

If one type dominates the escalation time, check whether the category guide gives enough examples for that type. A type that looks slow may simply carry the most judgment. Compare the process, not the reviewer. The next study can test a type-specific guide before applying it to the whole review.

Keep the review timings and document samples in a restricted workspace. Publish only the aggregate stages and document-type counts. If a client asks for the result, describe the method and the support change rather than sharing content. Keep the evidence beside the decision in the file.

Keep the review timings and document samples in a restricted workspace. Publish only the aggregate stages and document-type counts. If a client asks for the result, describe the method and the support change rather than sharing content. Ask the named owner to confirm the record.

What the evidence does not show

The study does not establish that a faster stage is a better stage. It also does not measure whether a privilege call was correct. Those are quality questions that need a separate sample. Time is one input to planning, not a verdict on the review.

Do not use the result to promise a client that a production will finish by a certain date or that every document will be reviewed in a certain way. Do not publish document content or reviewer identities. Keep the sample size, the stage definitions, and the review decisions with the result. Record the source and the date with the entry.

Ask the lawyer which stage most often delays a production decision. The answer may differ from the reviewer's view. Record both perspectives with the result. The support change should address the stage that actually controls the deadline.

Using the result in a client conversation

A client may ask how the firm plans a privilege review, and the study supports a careful answer. Describe the window, the number of sessions, the stage distribution, and the support change that was tested. Do not say that the review will be faster or cheaper in every matter. Explain that the measure covers observed work and that the lawyer reviews the substantive calls.

If the client asks for a commitment, offer a process commitment such as a category guide, a log template, and a named escalation owner. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. Record the source and the date with the entry.

Keep the timings and document samples in a restricted workspace. Publish only the aggregate stages and document-type counts. If a client asks for the result, describe the method and the support change rather than sharing content. Keep the evidence beside the decision in the file.

Sources and method

Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.

  1. U.S. Courts, Federal Rules of Civil Procedure
  2. American Bar Association, Model Rules of Professional Conduct
  3. GAO, Standards for Internal Control in the Federal Government
  4. NIST Cybersecurity Framework 2.0

Related research

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.