Resources
How to Build an Outside Counsel Guideline Compliance Process
Build an OCG compliance process that organizes current guidelines, assigns rules correctly, checks time entries, and catches invoice-level issues before submission.
Julia Bodet
Growth
AI Summary
Store one current guideline for each client and connect it to the correct matters before creating billing rules.
Validate extracted rules before activation and apply them at the firm, client, or matter level.
Entry-level checks, invoice-level review, and matter setup address different types of requirements.
Rule suggestions still require human review, especially when client language depends on context.
Track correction volume, first-pass acceptance, client rejections, and time to invoice to measure whether the process is working.
Law firms rarely struggle to understand why Outside Counsel Guidelines (OCGs) matter. The harder problem is applying the right requirement to the right entry, matter, and invoice every month.
This guide assumes the firm already understands what OCGs contain. It focuses on the operating process: controlling guideline versions, turning clauses into usable rules, and deciding where each check belongs.
OCG Implementation Plan
Step 1: Inventory and ownership
Collect the current guideline, amendments, e-billing instructions, and matter list. Name the billing partner and administrator responsible for the client.
Step 2: Classification
Separate billing rules from matter controls and non-billing obligations. Map each requirement to the correct client and matters.
Step 3: Rule validation
Extract or draft a limited set of high-confidence rules. Test them against representative compliant and non-compliant entries. Resolve conflicts and document exceptions.
Step 4: Timekeeper briefing
Explain the rules that affect daily entry, including codes, narrative detail, prohibited terms, and block-billing requirements. Keep the guidance specific to the client.
Step 5: First-cycle review
Review the earliest entries before pre-bill. Record which suggestions were accepted, rejected, or overridden. Use those results to refine the rules before the first complete invoice.
Start with One Current Source for Every Client
OCG compliance begins before a rule is written. The firm first needs to know which document governs the work.
Guidelines are often stored in email, client folders, shared drives, billing-system notes, or individual partner files. One PointOne customer entered implementation with guidelines spread across 214 separate client folders. That structure is manageable only when each folder has a clear current version and owner.
For every document, record:
Client name and client number
Matters covered
Effective date
Date received
Version or amendment history
Responsible billing partner
Billing administrator or operational owner
Related e-billing instructions
Keep prior versions for audit history, but mark one version as current. An update should trigger a review of the rules already connected to that client and its matters.
Convert the Document into Structured Rules
A guideline document may contain hundreds of clauses, but not every sentence belongs in a billing rules engine.
Separate the document into three groups:
Billing rules: requirements that can be checked against a time entry or pre-bill.
Matter controls: approvals, rates, staffing limits, or budgets that belong in matter setup.
Operating obligations: security, conflicts, reporting, and communication requirements owned outside the billing workflow.
AI can accelerate rule extraction, but the resulting list still needs validation. A long guideline can produce hundreds of proposed rules, including duplicates, unclear clauses, or requirements that belong elsewhere. Extraction and activation should therefore remain separate steps.
For each proposed billing rule, confirm:
The source clause and current document version
Whether the rule applies firmwide, to one client, or to one matter
Whether it produces a clear and useful suggestion
Whether an exception or threshold applies
Who can approve or override the result
Apply Rules at the Correct Level
Rule scope prevents one client’s requirement from changing entries for everyone else.
Firm-level rules apply across the organization. These are appropriate for internal narrative standards, preferred abbreviations, capitalization, or other firmwide conventions.
Client-level rules apply to all matters for one client. Examples include prohibited language, default narrative requirements, or a client’s standard task-code policy.
Matter-level rules apply only to a particular engagement. A matter may have its own staffing plan, budget, billing increment, or exception to the client’s standard guideline.
More specific rules should be reviewed for conflicts with broader ones. A matter-level exception has little value if the timekeeper also receives a contradictory firm-level suggestion.
Decide Where Each Compliance Check Belongs
No single checkpoint can evaluate every OCG requirement.
Checkpoint | Best suited for | Examples |
|---|---|---|
Matter setup | Requirements that must be true before work is billed | Approved timekeepers, rates, staffing limits, budgets |
Time entry | Facts visible in one entry | Missing codes, prohibited phrases, required detail, time increments, potential block billing |
Pre-bill review | Patterns visible across entries or the full draft bill | Duplicates, inconsistent meeting time, cumulative task caps, cross-timekeeper issues, discounts |
Human review | Requirements that depend on legal or billing judgment | Whether staffing was reasonable, whether a narrative reveals confidential information, whether an exception applies |
This division matters in practice. Certain rules may not be resolved from one entry alone, such as collective analysis across multiple entries and certain financial adjustments. Therefore, those checks belong at pre-bill or with a reviewer rather than being presented as entry-level automation.
Separate Objective Checks from Judgment
Objective checks depend on identifiable data. The system can determine whether a code is missing, a rate exceeds a configured amount, a phrase appears, or a duration follows the required increment.
Other clauses are contextual. A reviewer may need to decide:
Whether a narrative provides enough detail
Whether a partner was the appropriate person for a task
Whether two attendees made separate contributions to the same meeting
Whether a communication includes information that should be redacted
Whether an exception in the guideline applies
Software can surface these entries, explain the relevant rule, and suggest a revision, but the decision is still made by the reviewer.
Use Block Billing as a Test Rule
A client may prohibit any entry containing more than one task. Another may allow combined tasks below a threshold. A third may permit related work to stay together. The rule therefore needs the client’s actual language, not a generic instruction to “prevent block billing.”
A practical block-billing rule should include:
The client or matter to which it applies
The client’s definition of a separate task
Any time or project threshold
Examples that should and should not be flagged
The person who decides close cases
Stage Rules Before Applying Them Broadly
Activating every extracted rule at once can create noisy or conflicting suggestions.
A safer rollout is:
Draft or extract the rule in plain language.
Assign its firm, client, or matter scope.
Keep it staged while an administrator tests representative entries.
Confirm that the suggestions match the intended guideline.
Activate a small group of clear rules.
Review accepted, rejected, and overridden suggestions.
Refine the wording before adding more.
PointOne’s current support guidance recommends beginning with a small number of clear rules and monitoring their behavior before broader activation. Firm administrators control rule creation, editing, activation, and scope.
Check Entries Before Reviewing the Full Bill
Entry-level review is the first chance to correct a problem. It works well for requirements visible in one record, such as a missing code, vague narrative, prohibited term, or incorrect increment.
The correction happens while the work is recent and before the entry reaches the month-end queue.
Reserve Pre-Bill Review for Invoice-Level Issues
Pre-bill review occurs after time is recorded and before the invoice reaches the client. It provides the context that one-entry checks cannot.
Reviewers can compare:
Entries from everyone who attended the same meeting
Similar narratives that may represent duplicate work
Total time against a task or research cap
Rates, discounts, write-downs, and expenses
The complete invoice against its submission deadline
This is also where a firm routes the draft through the people responsible for approval. Depending on the firm, the sequence may include an assistant, originating attorney, responsible billing partner, and billing administrator.
How PointOne Handles OCG Compliance
PointOne separates guideline management from the two stages where rules are applied.
PointOne Rules stores guidelines, extracts proposed billing requirements, and lets administrators create rules at the firm, client, or matter level. Active rules generate suggestions on applicable entries. Extraction should be validated, and suggestions remain advisory.
PointOne Time generates entries for attorney review and applies the relevant entry-level rules before release. The timekeeper can accept a suggestion, reject it, or edit the entry.
PointOne Review applies the relevant guidelines during pre-bill review and adds invoice-level context. PointOne Review supports configurable routing, inline edits, comments, permissions, and AI suggestions. It can identify cross-entry and cross-timekeeper issues that do not appear at the individual-entry stage. Reviewers can work through suggested changes, comments, approvals, and firm-specific routing in one workflow.
FAQs About OCG Compliance
What Should a Firm Do If Work Starts Before the OCGs Are Fully Configured?
Flag the matter for manual review, confirm the highest-risk terms first, and avoid treating an incomplete rule set as approval. Staffing, rates, billing deadlines, and prohibited charges should take priority because they can affect work from the first day of the engagement. The remaining rules can be tested and added in stages.
How Can a Firm Test a New OCG Rule Without Interrupting Billing?
Run the rule against a representative set of historical or staged entries before applying it broadly. Include examples that should pass, examples that should be flagged, and known exceptions. A billing administrator and the responsible lawyer should review the results before the rule becomes active.
Can the Same Rule Template Be Used for Multiple Clients?
A shared template can be a useful starting point for common requirements such as block billing or narrative detail. Each client’s language, thresholds, exceptions, and matter scope still need to be confirmed. Reusing an unverified rule can apply one client’s interpretation to another client’s work.
What Records Should a Firm Keep When It Challenges an Invoice Reduction?
Keep the applicable guideline version, engagement terms, time entry, invoice, reduction reason, prior approval, and correspondence with the client or e-billing reviewer. Recording the final outcome also helps the firm decide whether to clarify a rule, add an exception, or change its review process.
How Should OCG Compliance Be Handled When a Matter Moves to a New Firm or Team?
Treat the transition as a new implementation. Confirm the current guidelines, approved timekeepers, rates, budget, prior client approvals, and open billing deadlines. Do not assume that the former firm’s configuration or another team member’s understanding reflects the terms that now govern the matter.