Insurance Defense Billing Guidelines: Staying Compliant
Block billing bans, staffing rules, pre-approval thresholds and non-billable categories quietly shrink insurance defense invoices. Here is how guideline breaches become write-downs, and the daily habits that keep your billing intact.
Insurance defense work is the only corner of legal billing where the person paying the invoice has written a rulebook about how you are allowed to describe your own work, and where breaking a formatting rule costs you the same money as not doing the work at all. Every panel carrier issues billing guidelines. Most firms read them once during onboarding, file the PDF somewhere on a shared drive, and never look at them again until the first reduction report lands and someone has to explain why eleven thousand dollars of recorded time turned into eight thousand of approved time.
The frustrating part is that almost none of those reductions are disputes about whether the work was necessary. They are disputes about whether the entry was written in a form the auditor can approve. A partner who took a deposition and drafted a motion in the same afternoon did real work. If both tasks land in one 6.4 hour line reading "prepare for and attend deposition; work on motion for summary judgment; correspondence," the auditor cannot allocate that time to a task code, cannot confirm the motion drafting was done at the right rate by the right timekeeper, and cannot verify it fell inside an approved budget. So the line gets cut, and the firm eats the difference.
Insurance defense billing compliance is therefore not a legal skill. It is an operational one. It lives in how the timekeeper records the entry at the moment of the work, in whether the guideline is visible on the matter instead of buried in an email thread, and in whether your system can stop a non compliant invoice from leaving the building. Firms that treat it as a monthly cleanup exercise lose money permanently. Firms that treat it as a capture habit almost never see a reduction report at all.
The Guidelines Are a Contract Term, Not Etiquette
The first mental shift is understanding what a billing guideline actually is. When a carrier appoints you to its panel, the engagement almost always incorporates the guideline document by reference. The guidelines are a term of the retainer, which means a breach is not rudeness, it is non conformance with the agreement under which you are being paid. That is exactly why the reduction is applied unilaterally rather than negotiated. The carrier is not arguing about the value of your work, it is pointing at a term you agreed to and declining to pay the part that falls outside it.
That framing matters because it changes who inside your firm needs to know the rules. If guidelines were etiquette, only the billing partner would need to read them. Because they are contract terms, every timekeeper who touches the matter is capable of breaching them, including the paralegal who logs three tasks in one entry and the associate who spends four hours on legal research nobody pre approved. The tripartite relationship between insurer, insured and defense counsel is governed differently across US states, and the position in England and Wales, Canada and Australia differs again on questions like who your client actually is and what independent professional judgment you owe. Confirm the ethical framework in your own jurisdiction, because a guideline that conflicts with your duty to the insured does not override that duty.
Why Block Billing Is the First Thing an Auditor Strikes
Block billing is the single most reduced practice in insurance defense, and it is reduced because it defeats the audit itself. An auditor's job is to allocate every tenth of an hour to a task, confirm the task was performed by a permitted timekeeper at a permitted rate, and check that it was inside an approved activity. A block entry combining four activities makes all three checks impossible at once. Faced with an entry they cannot decompose, most audit systems apply a flat percentage reduction to the whole line rather than trying to guess the split. You lose time on the compliant work as well as the questionable work.
The fix is unglamorous and completely mechanical. One task, one entry, one time value, one clear verb describing what was produced. "Draft opposition to motion to compel, section on proportionality" survives an audit. "Case work" does not. Timekeepers resist this because it feels like more administration, but recording four separate entries at the moment of the work takes less time than one reconstructed block entry at month end, and it is the only version that gets paid in full. When time capture happens inside the matter as the work happens, the granularity is free. When it happens from memory on the twenty eighth, granularity is expensive, which is precisely why block billing keeps reappearing.
Staffing Restrictions and the Cost of the Wrong Timekeeper
Most panel guidelines restrict who may perform which work, and they do it in two directions at once. Upward, they prevent partner rates being applied to tasks a junior associate or paralegal should have handled, which is why document review, indexing, deposition summarising and routine calendaring done at partner rates are so frequently reduced to a lower rate or refused outright. Downward, they often bar administrative work from being billed at all, no matter who did it. The result is a narrow band of appropriate seniority for each task, and stepping outside it in either direction costs money.
The second staffing rule that catches firms out is the limit on attendance. Many guidelines cap the number of timekeepers who may bill for the same event, so two attorneys attending the same deposition, hearing or mediation without prior written approval produces a reduction for the second one automatically. The same applies to internal conferences, where some carriers will pay only one side of an intra firm discussion. None of this is unreasonable from the carrier's perspective, but it means staffing decisions are billing decisions, and they need to be made before the calendar entry is created rather than discovered when the invoice comes back short. Assigning tasks to the right person from the start is far cheaper than arguing about it afterwards.
| Feature | Guideline-safe practice | What gets written down |
|---|---|---|
| Time entries | One task per line with the deliverable named | Multiple activities blocked into one figure |
| Staffing | Task assigned to the lowest appropriate timekeeper | Partner rate applied to review or summarising |
| Attendance | One biller per event unless approved in writing | Two attorneys billing the same deposition |
| Approvals | Written consent captured on the matter before spend | Expert retained first, approval requested later |
Pre-Approval Thresholds and the Silent Write-Down
Pre approval thresholds are where the largest single reductions come from, because the amounts involved are not tenths of an hour, they are experts, vendors, investigators, extended research and travel. Almost every set of guidelines names a spending figure above which written consent is required, and a list of categories requiring consent at any amount. The threshold varies by carrier and by programme, which is exactly why firms get it wrong: the number that applies to one panel does not apply to the next, and a habit formed on one relationship silently breaches another.
What makes these reductions so painful is that they are not recoverable through explanation. If a carrier requires written approval before retaining an accident reconstruction expert and the retention happened first, the invoice for that expert is refused on procedural grounds regardless of how central the expert turned out to be at trial. The discipline that prevents this is boring and effective. Approval requests go out in writing, the reply is saved to the matter rather than to an individual inbox, and the spend does not start until the reply exists. Storing that approval as a document on the matter itself, with a comment recording what was approved and by whom, means the person who has to defend the line item in six months is not searching an email archive. Casely records a comment field on every document capturing what changed and why, which turns a scattered approval trail into something you can produce in one click.
The Non-Billable Categories Nobody Reads Until It Is Too Late
Every guideline document has a section listing work the carrier will not pay for, and it is the section most timekeepers skip. It usually covers file opening and file closing administration, conflict checking, preparing and reviewing your own invoices, internal staffing and training, secretarial and clerical work, time spent responding to audit queries, and general legal research on matters the carrier considers within the panel firm's assumed competence. Some guidelines also exclude travel time entirely, others allow it at a reduced percentage, and others allow it only when productive work is impossible.
The trap here is not malice, it is habit. A paralegal who has always billed matter setup on private client work will bill it on a defense file without thinking. An associate who bills for reading the guidelines will find that entry refused, sometimes with a pointed comment. The solution is to make the non billable list a property of the matter rather than a fact somebody has to remember. When a matter is opened under a panel programme, the firm should know at the point of time entry which categories are not billable to that carrier, and the timekeeper should be recording them as non billable rather than recording them as billable and hoping. Time recorded honestly as non billable still gives you accurate utilisation data. Time refused by an auditor gives you nothing but a smaller cheque.
- Do you know the pre-approval threshold for every panel you are on, without looking it up?
- Can you produce the written approval for any expert or vendor on any open defense matter in under a minute?
- Does every timekeeper on defense files know which categories are non-billable to that carrier?
- Are your entries granular enough that an auditor could allocate each one to a single task code?
How a Guideline Breach Actually Becomes a Write-Down
Understanding the mechanics of the reduction helps you prevent it. The invoice arrives at the carrier or at its third party bill review vendor, usually in an electronic format, and it is passed through automated rules before any human reads it. Those rules flag rate mismatches against the approved rate schedule, entries above a maximum duration for their task code, duplicate attendance, block billing patterns, categories on the exclusion list, and spend above threshold without a matching approval record. Flagged lines are reduced, and a reduction report comes back with codes rather than sentences.
At that point the firm has a short window to appeal, and the appeal succeeds only if you can produce evidence, not explanation. Evidence means the original granular entry, the approval email, the staffing rationale, and the budget the work fell under. Firms that reconstruct time at month end have no evidence, because the record they are appealing from is the same vague entry that triggered the flag. This is why most write-downs are never appealed at all. The economics of chasing a three hundred dollar reduction across a two week appeal process rarely work, so the money is quietly written off, and nobody at the firm ever calculates the annual total. That uncalculated total is usually the reason a defense practice with strong volume shows weak realisation.
The Task Code Problem Hiding Under Electronic Billing
Most carriers require electronic invoice submission, and the dominant format in the US market is LEDES 1998B, which carries a task code and an activity code on every line. The codes are not decoration. They are how the carrier's system rolls up spend by phase and compares your matter to every other matter on the panel. A firm that codes everything to a single generic task looks like an outlier the moment the data is aggregated, and outliers get audited more closely, more often.
The practical consequence is that coding discipline and narrative discipline are the same discipline. If your entry names one task clearly, the code follows obviously. If your entry blocks four tasks together, someone in billing has to pick a code, and they will pick the one that covers the largest share, which distorts your phase data and makes future budget conversations harder to win. Native support for the export format matters here, because firms that rebuild LEDES files by hand introduce errors in exactly the fields the automated rules check first. Casely supports LEDES 1998B export directly, and because hourly, flat fee, contingency and blended arrangements are all native rather than bolted on, a defense matter billed under a blended panel rate exports without a manual rebuild.
Habits That Keep Invoices Intact
The firms that almost never receive reduction reports share a small set of habits, and none of them are heroic. Time is entered the same day, inside the matter, at task level. Staffing is decided when the task is created, not when the calendar reminder fires. Approval requests are sent before spend starts and stored on the matter. The guideline document itself lives attached to the matter so a new associate can read it in ten seconds rather than asking a partner. Invoices get a compliance read before submission rather than after rejection, and that read looks for block entries, excluded categories and unapproved spend, in that order.
The other habit is treating each panel as a distinct set of rules rather than blending them into one vague sense of what carriers want. Thresholds differ, rate schedules differ, attendance rules differ, and the excluded category list differs. Firms that run several panels need the rules to be visible on the matter, because human memory averages across programmes and the average is wrong for every one of them. A matter stage tracker configured for the defense workflow helps here, because it puts the compliance step in the same place as the litigation step. When the stepper shows that a matter has moved into expert discovery, the approval requirement is not a thing someone has to remember, it is the next visible action on the file.
- 01Open the matter under the correct panel programme with its guideline attached
- 02Assign each task to the lowest appropriate timekeeper before work begins
- 03Record time the same day, one task per entry, with the deliverable named
- 04Request and store written approval on the matter before any threshold spend
- 05Run a compliance read on the draft invoice before it is submitted
Building the Guidelines Into the Matter, Not the Memo
Everything above fails if compliance depends on people remembering things. The durable version puts the rules where the work happens. That means the panel guidelines are a document on the matter, the approved rate schedule is on the matter, the approval correspondence is on the matter, and the budget is on the matter, all reachable by any timekeeper who opens the file. It also means the connection between related matters is explicit, so a coverage file and its underlying defense file are linked with the reason stated rather than living as two unrelated records that happen to share a name.
Access control matters more in defense work than firms expect, because a panel firm frequently acts for multiple insureds and occasionally faces situations where one file must be walled from another. A wall that only hides menu items is not a wall. Casely enforces ethical walls at the server and data access layer, so a walled user cannot reach a restricted matter through search, through the calendar, or through a forwarded link. Combined with per firm AES-256 document encryption, that gives you an answer when a carrier's own information security questionnaire arrives, which on most panels it eventually does.
What to Do When a Reduction Lands Anyway
Some reductions are wrong, and those are worth appealing properly. Start by separating the codes into two piles: reductions caused by how the entry was written, and reductions caused by disagreement about whether the work was necessary. The first pile is a process failure on your side and the appeal will usually fail, so learn from it and move on. The second pile is a substantive disagreement, and it is winnable when you have the underlying record. Produce the granular entries, the approval, the staffing reason and the outcome the work produced, and make the argument in one message rather than three.
Then close the loop internally, because the same reduction code appearing twice in a quarter is a training problem, not an accident. Track reductions by timekeeper and by code, so you can see whether one associate is block billing, whether one practice group keeps missing approval thresholds, or whether a particular carrier's rules have changed since you last read them. A defense practice that reviews reduction codes monthly stops repeating the expensive ones within a quarter. A practice that only looks at the net cheque never finds out which habit is costing it money.
The Compounding Value of Getting This Right
Insurance defense is a volume business with thin margins, and the difference between a healthy panel practice and a struggling one is rarely the hourly rate. It is the percentage of recorded time that survives to become collected revenue. Every guideline breach is a small, permanent haircut on work you already performed, and because each one is individually too small to fight, they accumulate invisibly. Firms that fix capture at the point of entry rather than at the point of billing recover that margin without working an extra hour.
The tooling question is simply whether your system makes the compliant behaviour the easy behaviour. Time should be recordable at task level in seconds, the guideline and approval trail should sit on the matter rather than in someone's inbox, unbilled time should convert into an itemised draft in one click so nobody is reconstructing a month from memory, and the export format the carrier requires should be native rather than reassembled by hand. If you want to see how that fits together for a defense practice, start with legal billing software built for matter level time capture, or look at how legal e-billing software handles carrier submissions without a manual rebuild.
None of this replaces judgment about the case, and none of it overrides your professional duties to the insured, which vary meaningfully between US states, England and Wales, the Canadian provinces and the Australian states. Confirm those obligations locally and never let a billing guideline push you into a position your own regulator would not recognise. Within that boundary, though, compliance is a solved operational problem. Record the work properly the day you do it, get approval in writing before you spend, staff the task at the right level, and the invoice you send is the invoice you get paid.
WRITTEN BY
Sounak D.
Writes about legal practice operations, billing, and the day-to-day mechanics of running a firm on Casely.
More about the team