Privacy and preparation
How to record a privilege exclusion without reproducing privileged content
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Record a privilege exclusion as a decision, not as a copy: give each excluded item or batch an opaque ID, the counsel-approved screen rule and its version, the reviewer and approver, the date, a count and a topic drawn from a fixed vocabulary. Leave out subject lines, file names, excerpts and the advice itself. The log proves the screen ran and held without becoming a second privileged document.
Record timeline
Record a privilege exclusion
Key takeaways
- An exclusion log documents the decision and its authority; the excluded material and any summary of it stay out.
- Privilege log practice under Rule 26(b)(5)(A) is the right model, but a data project has no court, no opposing party and no automatic clawback.
- Subject lines, file names, matter names and participant lists can reveal privileged content on their own, so they need their own screen.
- Topics come from a short vocabulary counsel approves in advance, never from free text a reviewer types.
- When even a count would reveal something sensitive, keep a sealed entry with counsel and put only its ID in the dataset log.
How do you record a privilege exclusion without reproducing what was excluded?
You record the decision and its basis, never the content. Each entry says which screen rule applied, who applied it and who approved it, when, to how many items, and under which coarse topic, using an identifier that cannot be traced back to a subject line or file name without access to counsel's own file.
That separation matters because the exclusion log travels further than the excluded material. It goes to a licensee's reviewers, to auditors and to whoever maintains the dataset next year. If the log carries an email subject such as a draft settlement position or a file name that names an investigation, the screen has leaked what it was meant to protect, and the log has become a privileged document in its own right.
The rest of this page sets out the log as a field specification counsel can adopt, shows where metadata leaks, and covers what to do when the log cannot safely say anything at all.
Why borrow from the privilege log, and where does the comparison end?
Litigators already solve a close cousin of this problem. Federal Rule of Civil Procedure 26(b)(5)(A) requires a party withholding material as privileged to describe it in a way that, without revealing the protected information, lets others assess the claim, and the committee note accepts that voluminous items may be described by category rather than one by one.
Rule 26(f)(3)(D) asks parties to settle the timing and method of that logging early, and Rule 16 lets a scheduling order fix them, because logs produced at the end of a process cause disputes. The Sedona Conference Commentary on Privilege Logs (2024) goes further and prefers a log of objective metadata plus a short topic description over long narrative entries.
The comparison ends at purpose. A privilege log persuades an adversary and a judge that withholding is justified. An exclusion log persuades a licensee, an auditor and your own team that the dataset does not contain the withheld class at all. Nobody is entitled to challenge an individual entry, so the log can be coarser than a litigation log, but it must be more rigorous about proving completeness: counts in, counts out and counts excluded have to reconcile.
What should the counsel-designed exclusion evidence log contain?
Ten fields are enough for most collections. Counsel designs the permitted values before review starts, and reviewers choose from them rather than writing prose.
Two companion records sit beside the entries. The first is the rule book: each screen rule's code, version, effective date and the plain-language test a reviewer applies, approved by counsel and kept with the log. The second is a reconciliation sheet per source container, which states the items returned by the scope query, the items excluded by rule, the items sealed and the items staged. If those four numbers do not balance, the log is not finished, however tidy the entries look.
Keep names of reviewers and approvers in counsel's file and use role codes in the shared log. The licensee needs to know that a qualified person approved each rule, not who that person is.
| Field | What it records | Permitted values | Never write here |
|---|---|---|---|
| Entry ID | Opaque identifier for one item or one batch | Random or sequential ID with no meaning | Hashes of subject lines or file names that could be matched |
| Source system and container | Where the item sat before exclusion | System name and a container code from the inventory | Matter names, mailbox owner names, folder titles |
| Screen rule and version | Which counsel-approved rule caused the exclusion | Rule code such as PRIV-02 with version and effective date | The reasoning applied to this item |
| Exclusion basis | The category of protection asserted | Attorney-client, work product, confidentiality duty, legal hold, other counsel direction | Any description of the advice |
| Topic | Coarse subject from a fixed vocabulary | For example contract negotiation, employment, regulatory, dispute, corporate | Free text, party names, dates of events discussed |
| Count and unit | How many items the entry covers | Integer plus unit: message, thread, file, record | Size or length details that hint at content |
| Reviewer and approver | Who applied the rule and who signed off | Role codes, with names held in counsel's file | Personal notes or comments |
| Decision date | When the exclusion was decided | ISO date | Dates taken from the excluded item |
| Amendment link | Whether a later decision changed this one | Entry ID of the superseding entry, or none | Why counsel changed its mind |
| Disposition | What happened to the excluded copy | Never extracted, removed before staging, deleted from working copy | Where a privileged copy is kept |
Where does the metadata itself give the privileged content away?
Most leaks in exclusion logs come from fields that look harmless. A subject line can state the advice. A file name can name a dispute that is not public. A participant list of the general counsel, the chief financial officer and one employee, on one date, can disclose an internal investigation without a single word of content.
The Sedona commentary flags a related trap: when a log is built only from the top message of an email chain, earlier privileged messages inside the chain can be withheld without appearing on the log at all. For a data project the risk runs the other way too. A thread kept because its top message is routine can carry a privileged reply further down.
- Screen subject lines, file names, folder paths and calendar titles with the same rules as bodies, and drop them from the log rather than editing them.
- Treat each message in a thread as its own unit, and record thread-level exclusions with a count of messages.
- Replace participant lists with role counts only when counsel agrees that the combination of roles is not itself revealing.
- Round small counts into bands, such as fewer than five, wherever an exact count of one or two would identify an event.
- Keep attachment exclusions linked to their parent entry so the reconciliation still adds up.
Who decides what is excluded, and how is that authority recorded?
Counsel decides the rules and approves the hard calls; reviewers apply the rules. The log shows that chain by recording a rule code and version on every entry, a reviewer role and an approver role, and an amendment link when counsel later changes a decision.
The rules work best when they follow the line the Supreme Court drew in Upjohn: privilege protects communications, not the underlying facts. A rule can therefore keep a contract's executed terms and approval dates in scope while excluding the legal advice exchanged about them. Where facts and advice sit in the same message, the rule should exclude the message and leave the fact to be collected from a system of record, such as the contract repository.
Version every rule. When counsel tightens PRIV-02 halfway through, entries decided under version one remain valid records of what was done, and a re-screen of the earlier batch gets its own entries pointing to the old ones. That trail is what lets someone later answer which rule was in force when a given batch left the building.
Worked example (illustrative): screening a contract repository
This example is invented to show the log in use. A company's legal operations team plans to license a set of executed vendor contracts, their approval records and their renewal dates. Counsel writes three rules: PRIV-01 excludes any message or comment with in-house or outside counsel as author or recipient; PRIV-02 excludes drafts marked as counsel work product; HOLD-01 excludes anything under a legal hold.
Illustrative counts: the scope query returns 4,200 contract records and 31,000 associated comments. Reviewers exclude 2,900 comments under PRIV-01, 410 drafts under PRIV-02 and 60 contract records under HOLD-01. The log carries about a dozen batch entries, each with a topic code and a count, rather than thousands of item lines, and the reconciliation shows 4,140 contracts and 28,100 comments staged.
One exception changes the record. A reviewer finds that 14 comments written by a paralegal relay counsel's advice word for word. Counsel issues PRIV-01 version two, which adds relayed advice, and a new entry records the 14 items with an amendment link to the original batch. The exclusion log never says what the advice was, only that the rule changed and when.
When even a count would reveal too much, what goes in the log?
Sometimes the existence of an exclusion is the sensitive fact. A single excluded thread under the topic regulatory, dated in a quiet quarter, can tell an informed reader that an inquiry happened. In those cases the dataset log should carry a sealed entry: an ID, the decision date and the word sealed, with the full entry kept in counsel's own file under privilege.
Sealed entries are an exception, not a habit. If more than a handful are needed, the collection boundary is probably wrong, and the better decision is to remove the whole container or date range from scope and record that as one ordinary entry. Counsel should also decide whether licensees are told that sealed entries exist, which is usually the honest default.
What does the log do when privileged material slips through?
It gives you the evidence of reasonable care and a starting point for removal. Federal Rule of Evidence 502(b) protects against waiver for inadvertent disclosure in a federal proceeding or to a federal agency when the holder took reasonable steps to prevent it and promptly acted to fix it. A data license is not a federal proceeding, so a team should not assume that safety net exists, and Rule 502(e) adds that an agreement between parties about disclosure binds only those parties unless a court order adopts it.
That makes the contract and the log carry the weight. The license should require prompt notice, return or deletion of identified items and deletion from derived training sets where feasible. The log should record the incident as a new entry, linked to the batch that missed it, with the rule change that would have caught it.
Law firms carry an added duty. ABA Model Rule 1.6(c) asks lawyers to make reasonable efforts to prevent inadvertent or unauthorized disclosure of information relating to a representation, a category wider than privilege. For a firm, the log is part of how it shows those efforts, and state versions of the rule may differ.
When should the log stop a collection instead of describing it?
Stop when the log cannot be kept honestly. Each of these signals means counsel should narrow the scope or pause before more records are screened.
- Counsel cannot express the screen as rules a trained reviewer can apply consistently.
- Exclusions dominate a container, so what remains is a skewed sample of the work and hard to describe without the excluded part.
- The reconciliation does not close: items in minus items staged minus items excluded leaves an unexplained remainder.
- Sealed entries keep growing, which signals the scope includes matters that should not be near a dataset.
- The records contain client information held by a law firm, where consent and professional duties need their own analysis before any screen is designed.
Licensing a legal dataset with its exclusion record attached
A clean exclusion log does not create a right to license the remaining records; ownership, client and vendor contracts and confidentiality terms still need their own review. What it does is let a licensee see that privileged material was screened out under named rules, by named roles, with numbers that add up.
Where a legal operations team wants to license the remaining records, SourceX covers rights review, preparation and contracting for selected business records used in AI. It begins with a short company assessment that needs no data, and because no records are delivered before the company approves scope and terms and signs, counsel's screen and exclusion log can be finished first.
Frequently asked questions
What is a privilege exclusion log?
It is a record of each decision to keep privileged or otherwise protected material out of a dataset. Each entry names the screen rule and version, the reviewer and approver roles, the date, a count and a coarse topic. It deliberately leaves out the excluded content and any description of the advice.
Is a privilege exclusion log itself privileged?
It should not need to be, and designing it so it reveals nothing protected is the point. If an entry would only make sense by describing the advice, it belongs in counsel's own file as a sealed entry. Counsel should confirm the status of both records for the specific facts.
How detailed should each exclusion entry be?
Detailed enough to reconcile counts and identify the rule, and no more. Batch entries by rule, container and topic usually work better than per-item lines. Per-item entries make sense only when a licensee or auditor needs to trace a specific removal.
Can I list the email subject lines of excluded messages?
No. Subject lines often state the advice or name a dispute, which is the content you are excluding. Use an opaque entry ID and a topic code from counsel's vocabulary instead.
Does Rule 502 protect a company that accidentally licenses privileged emails?
Not automatically. Rule 502(b) addresses disclosures in federal proceedings or to federal agencies, and a commercial data license is neither. Plan for contractual notice, return and deletion, and keep the exclusion log as evidence of the care taken.
Sources
- Federal Rule of Civil Procedure 26(b)(5)(A) requires a party withholding privileged material to describe it without revealing protected information, and the committee note allows description by category for voluminous items. Rule 26(f)(3)(D) asks the parties' discovery plan to address privilege claims, including the timing and method for complying with Rule 26(b)(5)(A). Source
- Rule 16 allows a scheduling order to set the timing and method for complying with Rule 26(b)(5)(A), building on the parties' Rule 26(f) discussion. Source
- Federal Rule of Evidence 502(b) limits waiver for inadvertent disclosures in federal proceedings or to federal agencies, and 502(e) makes party agreements binding only on the parties unless a court order adopts them. Source
- In Upjohn Co. v. United States, the Supreme Court held that privilege protects communications, not the underlying facts. Source
- ABA Model Rule 1.6(c) requires lawyers to make reasonable efforts to prevent inadvertent or unauthorized disclosure of information relating to a representation. Source
- The Sedona Conference Commentary on Privilege Logs (2024) prefers metadata plus topic logs and warns that logs built from top-level email metadata can miss privileged messages earlier in a chain. Source
See if your company qualifies
A short company assessment. No data uploads are needed.