Legal Services Offshore blog

Build a privilege log that survives a second review

A privilege log routine that ties each entry to the document, the basis claimed, the author, and the reviewer who accepted it.

Build a privilege log that survives a second review editorial illustration
Defined workflowAttorney review gatesPractical escalation

Define the log's purpose before the first row

A privilege log can serve the court, the opposing party, and the firm's own review team, and those readers need different things. Write down the purpose of the log and the fields required by the applicable rules or agreement. Decide whether the log covers withheld documents only or also redacted documents. Record the version and date of the template so a later reviewer knows which standard was used.

Keep the template narrow enough to complete consistently. A log that asks for every possible detail invites free-text entries that cannot be compared. A log that asks for too little forces the reviewer back into the documents. Start with the document identifier, date, author, recipients, subject, privilege basis, and the reviewer who made the call. Add fields only when they change a decision or satisfy a stated requirement.

Tie every entry to one document and one version

Use the document identifier from the review platform rather than a file name that may change. Record the version reviewed and the date it was collected or produced. If a document has attachments, list the parent and each attachment as separate entries when the privilege claim may differ. Do not let one row stand in for a family of documents without saying so.

When a document is renumbered or re-produced, keep the earlier reference and add the new one. A reader should be able to move from the log row to the exact document that was reviewed. If the document cannot be located, mark the entry incomplete and route it for correction. A log that points to a missing file is not evidence of a privilege review, even if the description sounds complete.

Record the basis in facts, not conclusions

A bare entry that says attorney-client privilege tells the reader very little. Record who provided the legal advice, who requested it, and why the communication was made in confidence. For work product, record the litigation or anticipated litigation and the mental impression or strategy at issue. Use the firm's approved categories, but add a short factual note when the category alone would be ambiguous.

Do not overstate the claim to make the entry look stronger. If the basis is uncertain, say what is uncertain and route the question to the attorney. If the document contains both privileged and non-privileged material, record the redaction decision and the reviewer. The log should describe the basis without disclosing the very content the firm is trying to protect.

Run a second-pass consistency check

Before the log is used, sample entries across document types, authors, and reviewers. Check that the identifiers exist, the dates match the documents, the descriptions are consistent, and the claimed basis is the same for similar communications. Look for entries with no reviewer, entries copied from another matter, and rows that describe a document rather than a communication. Include at least one entry that was corrected after the first review.

Record each correction and the reason in a short change log. If the same field is wrong repeatedly, fix the template or the instruction before reviewing more documents. Have the attorney or senior reviewer confirm the final version and the date. A second review is not a formality; it is the step that turns a working list into a record the firm can defend.

Sources

  1. American Bar Association — Attorney-client privilege

  2. U.S. Courts — Federal Rules of Civil Procedure

  3. NIST Cybersecurity Framework 2.0

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.