Privacy and preparation
Legal process exception dataset without privileged advice
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
A legal process exception dataset records administrative exceptions, such as rejected invoice lines, approval bypasses or incomplete intake, as process facts: what happened, when, under which rule version, with whose authority and how it ended. It leaves out the advice given about them. Counsel approves the field list and reviews samples before collection, and excluded records are logged by category without their content.
Document stack
Legal process exception
Key takeaways
- Privilege protects communications, not the underlying facts, so process facts can usually be separated from advice.
- Confidentiality duties under Model Rule 1.6 are broader than privilege and matter most for law firms.
- Use structured fields with a named source of authority and a screen rule; exclude free text by default.
- Measure each exception against the rule version in force on the event date and record missing evidence as unknown.
- Litigation, investigations, regulator requests and legal holds stay out by default.
How can legal administrative exceptions be documented without privileged advice?
Record the process facts of each exception, meaning what happened, when, under which version of which rule, who had authority, which route the item took and how it ended, and leave out the legal reasoning anyone gave about it. Counsel approves the field list and reviews a sample before anything is collected, and every excluded record is logged by category.
This works because the line the law draws runs between facts and communications. In Upjohn Co. v. United States, the Supreme Court said the attorney-client privilege protects disclosure of communications, not disclosure of the underlying facts, and that a fact is one thing and a communication concerning that fact is another. An invoice rejected on a given date for a billing guideline breach is a fact; the email in which counsel explains whether to appeal it is a communication.
A legal process exception dataset built this way captures how legal work actually flows through intake, contracting, billing and approvals, including every point where it left the expected path. That is useful to people building legal operations tools and agents, and it can be assembled without putting advice into the record set.
Which legal operations exceptions are administrative, and which carry advice?
Most exceptions in legal operations are administrative at their core, but nearly every one has an advice layer attached in notes, emails or comments. The table separates the two for the exception types teams see most often and sets a default for each.
Billing exceptions are the easiest place to start because the codes are already standardized. The LEDES Oversight Committee maintains the UTBMS code sets used in legal e-billing, including activity codes such as A101, plan and prepare for, so a rejected line item can be described by its codes, dates and the guideline rule it broke without quoting the narrative.
| Exception type | Process facts to keep | Advice layer to exclude | Default |
|---|---|---|---|
| Outside counsel invoice rejected or reduced | Invoice and line IDs, UTBMS task and activity codes, guideline rule ID, dates, adjustment type, appeal outcome | Billing narratives describing the work, counsel's appeal reasoning | Include after screen |
| Contract routed outside the approval matrix | Contract type, value band, required and actual approver roles, matrix version, dates | Legal comments on risk or negotiating position | Include after screen |
| Signature by someone without delegated authority | Signer role, delegation record version, ratification date and approver role | Advice on enforceability | Include after screen |
| Matter opened before intake was complete | Missing intake fields, conflict check status timestamps, release date | Conflict analysis and any waiver discussion | Include status only |
| Template deviation in an NDA or standard agreement | Template version, clause IDs changed, approval route, turnaround in days | Redline comments and negotiation notes | Include clause IDs only |
| Deadline or docket correction | Rule set version, original and corrected dates, who corrected it by role | Analysis of which rule applies | Counsel decides per matter |
| Legal hold issued, changed or released | None by default | Hold notices, scope decisions, custodian lists | Exclude |
| Regulator or litigation-related request | None by default | Everything | Exclude |
Where is the line between a process fact and a protected communication?
Privilege is only one of the protections in play, and it is narrower than the others. Federal Rule of Evidence 502 deliberately defines attorney-client privilege and work-product protection by reference to applicable law rather than redefining them, so whether a given record is protected depends on the jurisdiction and the facts, and counsel makes that call.
Professional confidentiality is broader. ABA Model Rule 1.6(a) bars a lawyer from revealing information relating to the representation of a client without informed consent or another listed basis, and the comment explains that it covers all information relating to the representation, whatever its source, not only matters communicated in confidence. For a law firm, even a nonprivileged billing fact about a client matter falls inside that duty; for an in-house legal team, the company is the client, which changes who has to agree.
Keep four questions separate when you decide what can be collected: whether the team has access to the record, whether privilege or work product protects it, whether confidentiality duties or contracts restrict its use, and whether the company actually has the right to license it. A yes to the first answers none of the others, and removing names does not answer the last one.
What should the counsel-screened process record collection specification include?
The specification is the contract between legal operations and counsel about what a record may contain. Every field below is structured, comes from a named system of record and has a screen rule; free text is excluded unless counsel approves a specific field after sampling it.
At a glance
What should the counsel-screened process record collection specification include
| Field | Definition | Source of authority | Screen rule |
|---|---|---|---|
| exception_id | Stable pseudonymous ID for one exception event | Generated at collection | No matter names, client names or numbers that reveal them |
| exception_type | Controlled value from the exception catalogue | Catalogue approved by counsel | Values only from the approved list |
| governing_rule_ref | ID and version of the guideline, policy, matrix or template that was breached | Policy library or guideline repository | Reference only; never the text of advice about the rule |
| object_ref | Pseudonymous contract, invoice or matter reference with its version or amendment number | CLM, e-billing or matter system | Version chain kept; titles and parties removed |
| event_dates | Created, flagged, escalated, resolved | System audit timestamps | System dates only, not dates typed into notes |
| actor_roles | Roles of requester, approver, signer, reviewer | Directory and delegation records | Roles, not names |
| route_taken | Ordered list of steps and queues the item passed through | Workflow or audit log | Queue names generalized if they reveal a client |
| outcome_code | Approved, rejected, reduced, ratified, withdrawn, escalated | System of record | Coded value; reasons only from a coded list |
| evidence_refs | IDs of the approval, delegation or audit records that support each field | Same systems | IDs only; documents stay in place |
| screen_status | Counsel screen result and date, or the exclusion category | Counsel review log | Required before the record leaves legal |
How should counsel screen the records before collection?
Screen the specification first, then a sample, then the exclusions, and do all of it before any export leaves the legal team's systems. Fixing a leak after collection is far harder than not collecting it.
The exclusion record can borrow its logic from litigation practice. Federal Rule of Civil Procedure 26(b)(5)(A) asks a party withholding material as privileged to describe the nature of what it withholds in a way that, without revealing protected information, lets others assess the claim, and the committee notes accept description by category when items are numerous. An exclusion log that says how many records of each category were removed and why, without their content, gives reviewers and any later licensee a defensible picture of what is missing.
Do not rely on being able to undo a mistake. Rule 502(b) limits waiver for inadvertent disclosures made in a federal proceeding or to a federal agency when reasonable steps were taken to prevent and promptly correct them; a data project is neither, so counsel should assume no comparable safety net and screen accordingly.
- Step 1: counsel approves the exception catalogue and the field specification.
- Step 2: legal operations runs the extraction on a small sample from each exception type and system.
- Step 3: counsel reviews the sample for advice leaking through codes, queue names or reference fields.
- Step 4: matters and categories flagged for exclusion are removed at the source, and the exclusion log records counts by category.
- Step 5: a second sample from the full run is reviewed before release, and the screen status is written to every record.
Worked example: a rejected outside counsel invoice line
This example is illustrative and invented; it shows how one billing exception becomes a record, not a real matter. An outside firm submits an invoice in which one line bills time to a task the company's guidelines treat as non-billable overhead. The e-billing system rejects the line, the firm appeals, and the line is paid at a reduced rate.
| Field | Value in the record | Where it came from | What was left out |
|---|---|---|---|
| exception_type | invoice_line_rejected | Exception catalogue | Nothing |
| governing_rule_ref | Billing guidelines version 7, rule 4.2 | Guideline repository | The guideline commentary written by counsel |
| object_ref | INV-pseudonym-0193, line 12, UTBMS activity A101 | E-billing system | Firm name, matter name, timekeeper names and the narrative |
| event_dates | Submitted day 0, rejected day 2, appealed day 9, resolved day 23 | System audit timestamps | Dates mentioned in emails |
| actor_roles | Billing reviewer, legal operations manager, deputy general counsel | Delegation records | Names and the deputy general counsel's appeal reasoning |
| outcome_code | reduced | E-billing system | The negotiated explanation |
| screen_status | Approved by counsel, sample batch 3 | Counsel review log | Not applicable |
| Exception | A second line on the same invoice cites a litigation strategy call | Counsel sample review | Excluded as category litigation-related; counted in the exclusion log |
Which source, amendment or authority controls each exception?
The rule that applies is the version in force on the event date, not today's version, so the record has to carry version references and the source of authority for each one. A contract approval exception judged against this year's approval matrix will look like a breach when it was compliant at the time, or the reverse.
At a glance
Which source, amendment or authority controls each exception
When the controlling evidence is missing, say so in the record. A delegation of authority that cannot be found, an amendment that was signed but never loaded into the contract system, or a guideline revision with no effective date are themselves useful facts about the process. Mark them as unknown rather than inferring them from later documents, and keep the gap visible to whoever uses the data.
- Guidelines and policies: version ID and effective date range from the policy library.
- Contracts: the amendment chain, with each amendment's effective date and the version the exception was measured against.
- Authority: the delegation or signature matrix version in force on the event date.
- Workflow: the system audit log, not reconstructed timelines from email.
- Missing evidence: an explicit unknown value with a reason code.
When should legal records stay out even if they look administrative?
Exclude by category whenever the administrative facts would reveal strategy, an investigation or a client's affairs, and stop the project for a fresh counsel review if a sample shows advice leaking through structured fields. Matters in active litigation, investigations, regulator correspondence and legal holds stay out by default.
Law firms face an additional constraint. Because Model Rule 1.6 covers information relating to a client's representation, a firm's matter administration data generally needs a basis such as client informed consent before it can be shared, and that is a question for the firm's own counsel and its clients. ABA Formal Opinion 512, issued in July 2024, advises lawyers to obtain clients' informed consent before entering information relating to a representation into self-learning generative AI tools and says boilerplate consent in an engagement letter is not adequate. In-house teams should still check what outside firms' engagement terms say about billing data.
Where licensing fits once counsel has screened the records
A counsel-screened exception record set, with versions, authority and outcomes, documents how legal work moves through a company in a form that contains no advice. Whether it can be licensed is a separate question about ownership, client and vendor contracts and confidentiality duties, and screening for privilege does not settle it.
Once counsel has screened the records, SourceX can take a company through qualification, rights review, contracting, preparation and delivery of a licensed dataset. The process opens with a short company assessment that asks for no data, and no records move until the company has approved the scope and terms and signed the agreement.
Frequently asked questions
What is a legal process exception?
It is any point where a legal operations item left its expected path, such as an invoice line rejected under billing guidelines, a contract approved by the wrong role, or a matter opened before intake was complete. The exception itself is a process event with dates, rule versions and an outcome. The advice anyone gave about it is a separate record.
Is a contract approval log privileged?
Usually the log entries are process facts, such as who approved what and when, which privilege generally does not protect on their own. Comments attached to the approval can contain legal advice and may be privileged. Counsel should review the actual fields and a sample, because the answer depends on the content and the applicable law.
Can a law firm use its matter administration data for AI?
Only with care and usually with client consent. ABA Model Rule 1.6 covers all information relating to a client's representation, not just privileged communications, so billing and workflow facts about client matters fall within the duty. The firm's own counsel should decide the basis for any use, and ABA Formal Opinion 512 addresses consent for generative AI tools specifically.
How is an exclusion log different from a privilege log?
A privilege log is a litigation document that describes withheld items so the other side can assess a privilege claim. An exclusion log borrows the idea for a data project: it records how many records of each category were removed and why, without their content. It is not filed with anyone, but it shows a reviewer what is missing and on what basis.
Should free-text notes be included in a legal exception dataset?
Not by default. Notes are where advice, strategy and client details leak into otherwise administrative records. Keep structured fields and coded reasons, and add a free-text field only when counsel has reviewed a sample of it and approved its inclusion with a specific screen.
Sources
- In Upjohn Co. v. United States (449 U.S. 383), the Supreme Court held that the privilege protects disclosure of communications, not disclosure of the underlying facts. Source
- Federal Rule of Evidence 502 defines attorney-client privilege and work-product protection by reference to applicable law and limits waiver for inadvertent disclosure in federal proceedings when reasonable steps were taken to prevent and promptly rectify it. Source
- Federal Rule of Civil Procedure 26(b)(5)(A) requires a party withholding privileged material to describe its nature without revealing protected information, and the committee notes allow description by category for voluminous items. Source
- ABA Model Rule 1.6(a) bars a lawyer from revealing information relating to the representation of a client unless the client gives informed consent, the disclosure is impliedly authorized, or paragraph (b) permits it. Source
- The comment to Model Rule 1.6 explains the rule applies to all information relating to the representation, whatever its source, not only matters communicated in confidence. Source
- ABA Formal Opinion 512 (July 2024) advises informed client consent before inputting information relating to a representation into self-learning generative AI tools and says boilerplate engagement-letter consent is not adequate. Source
- The LEDES Oversight Committee publishes the revised UTBMS activity codes used in legal e-billing, including A101, plan and prepare for. Source
See if your company qualifies
A short company assessment. No data uploads are needed.