A client changes its outside counsel guidelines. The billing team uploads the new document, reruns an older pre-bill, and receives a different set of violations.
Which rules should have applied to those entries? Without an applicability record, the team cannot explain the change.
AI OCG review needs versioned rules, explicit applicability, approved exceptions, and traceable findings. The aim is to apply the correct client instructions to the correct work—not to make the newest guideline document automatically override every earlier decision.
Separate the document from the executable rule
An outside counsel guideline document is source material. A rule used by software is an interpretation of that material for a defined situation.
Store the original document and location behind each rule. Identify the client, matter scope, rule owner, approved interpretation, and the date or condition under which it applies.
Dates require care. A rule could depend on when work was performed, when a matter opened, or another agreed condition. Do not assume invoice date controls. Have the responsible billing and legal owners establish applicability from the relevant agreement and client instructions.
Create an applicability record
The following is a suggested implementation template, not a universal client billing standard.
| Record element | Example of what to capture |
|---|---|
| Rule identity | Stable rule ID plus version |
| Source | Guideline document version and section |
| Scope | Named client and covered matters |
| Applicability | Approved date basis and effective period |
| Interpretation | Exact condition the review checks |
| Exception | Approval reference, scope, and expiry |
| Release | Reviewer, approval date, and deployment version |
Preserve the source wording alongside the interpreted rule. When an instruction is ambiguous, mark it unresolved and route it for clarification rather than converting uncertainty into an automatic rejection.
Make exceptions narrow and visible
An exception for one matter should not suppress the rule for every matter belonging to that client. Bind each exception to its authorized scope and keep evidence of approval.
Avoid free-text notes that the AI must reinterpret every time. Structured fields can capture the relevant matter, activity, condition, and expiry while retaining the original approval material for human inspection.
When an exception expires or is withdrawn, stop applying it to new eligible work according to the approved policy. Preserve its historical application record.
Illustrative example: revised travel guidance
A hypothetical client changes its travel-billing instructions for specified matters. A pre-bill includes entries from before and after the approved effective date, plus a matter with a documented exception.
The review service first resolves applicability. It checks each entry against the relevant rule version and exception state, then returns a finding containing the source section and the reason for the flag.
It does not rewrite time narratives to conceal a violation. Nor does it silently remove charges. The billing reviewer decides the appropriate correction or escalation.
The example demonstrates system design, not a statement of what any actual client's billing rules permit.
Test changes against a fixed review set
Before activating a new rule, test entries that should pass, should be flagged, and should require human interpretation. Include boundary dates, multiple matters, expired exceptions, and missing data.
Compare the old and new results. Every changed finding should have an explainable cause, such as a revised applicability condition or an intentional rule change. A large unexplained difference should stop release.
Keep rule tests separate from model-output evaluations. A correctly selected rule can still be applied incorrectly to a time entry; both layers need review.
Explain every finding to the reviewer
A useful finding includes the entry reference, the applicable rule version, source location, matched evidence, exception evaluation, and recommended review action. Missing facts should appear as missing facts, not confirmed noncompliance.
ABA Formal Opinion 512 discusses lawyer oversight and reasonable fees in the context of generative AI. It does not prescribe this OCG architecture. Have qualified owners review the system's interpretations and billing decisions.
Frequently asked questions
Should a revised guideline automatically be applied to an older invoice?
No. Determine applicability from the approved client instructions, agreement, and relevant date basis. If an older invoice needs a new review, retain the original result and record the new rule version and reason separately. Do not silently rewrite the earlier decision.
What if an exception appears to conflict with a later guideline?
Route the conflict to the authorized billing and legal owners. Record their interpretation, the affected matters, and the applicable period before activating a changed rule. The system should not guess that either the exception or the newer document always takes precedence.
Should missing entry information be classified as a confirmed billing violation?
Distinguish an information gap from evidence of a rule breach. Identify what is missing, which rule cannot be evaluated, and who must resolve it. A reviewer can then request clarification without treating an incomplete record as proven noncompliance.
Can AI rewrite a time narrative just to make a flagged charge pass?
The review workflow should not conceal the underlying work or evade client instructions. Preserve the original entry and route any correction through the authorized billing process. A rule finding supports review; it is not permission to alter the facts or make an unsupported billing decision.
Keep appeals linked to the original review
If a client challenges an invoice, reproduce the rule version and evidence used at review time. Later clarification should create a new decision record rather than erase the old one.
Start by testing whether your current system can explain one disputed entry using the exact rules that applied when it was reviewed. Discuss that requirement when scoping LuMay Legal Agents.
