Litigation Task Codes
The ABA litigation task codes (L100 through L500), five matter phases with original guidance on when each code applies, the patterns reviewers see, and what invoice review checks.
UTBMS litigation task codes classify legal work by matter phase, describing where in the case lifecycle each piece of work belongs.
Where activity codes describe how time was spent, task codes describe where in the case lifecycle it belongs. This is the structure that makes phase budgeting, budget-to-actual tracking, and cross-matter benchmarking possible, so coding accuracy here determines how much a legal department's analytics can actually say. The ABA original set has five phases and 29 task codes; the eDiscovery codes (L600 series) supplement it as a sixth phase. Every code is searchable alongside all sets at the UTBMS code database.
Phase-level accuracy is the foundation of spend analytics, which is why litigation coding sits at the core of a legal spend management program: clean phase data is what lets a department compare firms on the same work, spot phases that drift, and budget the next matter from the last one.
What are litigation task codes used for?
Litigation task codes answer a single question for every line on a bill: which phase of the matter does this work belong to. Each timekeeper line pairs a task code (the phase) with an activity code (the kind of work), so one entry tells the reviewer both where and how.
The value shows up in aggregate. When phases are coded consistently, a department can see how fees distribute across assessment, discovery, motions, and trial, compare that shape across firms and matters, and notice when a phase runs heavier than the work should require. When coding is loose, that entire layer of insight disappears.
What does each litigation task code cover?
The opening and ongoing management phase. It runs the life of the matter, which makes it the natural landing spot for time that belongs elsewhere, so its share of total fees is a coding-quality indicator in itself.
L110: Fact Investigation/DevelopmentABA (1997)
Gathering and developing the facts of the case, including witness interviews, document collection from the client, and factual chronology work.
When to use this code: Use for factual development work, typically concentrated early in the matter and revived when new facts emerge.
Patterns reviewers commonly see: Fact investigation entries continuing at steady volume deep into a matter, which can indicate either genuinely evolving facts or early-phase work that was deferred. Also overlap with L310 and L320 once formal discovery begins, since the boundary is where firms differ most in coding practice.
What invoice review checks: Expect a front-loaded curve. When L110 stays flat across the matter timeline, read narratives to understand what changed factually, and compare against the discovery codes to see whether the same work is being classified two ways.
L120: Analysis/StrategyABA (1997)
Developing and refining case strategy, evaluating claims and defenses, and advising on direction.
When to use this code: Use for genuine strategic analysis. Senior timekeeper concentration here is normal and appropriate.
Patterns reviewers commonly see: L120 functioning as a general-purpose code for time that resists classification, since almost any litigation work can be described as strategic. Firms vary widely in how much of a matter lands here, and high concentration usually reflects coding habits rather than an unusually strategic case.
What invoice review checks: Benchmark L120 as a percentage of matter fees across your panel. Wide variance between firms handling similar matters is a coding-consistency conversation, and consistency is what makes your phase analytics trustworthy.
L130: Experts/ConsultantsABA (1997)
Identifying, retaining, and working with experts and consultants outside the formal expert discovery process.
When to use this code: Use for expert selection and early consulting work. Once expert discovery begins, L340 takes over for disclosure and deposition work.
Patterns reviewers commonly see: The L130 and L340 boundary applied inconsistently within one matter, which splits expert-related cost across two phases and understates both.
What invoice review checks: Read L130 and L340 together when evaluating total expert-related fees, and pair them with E119 expense entries for the complete expert cost picture.
L140: Document/File ManagementABA (1997)
Organizing and managing case files and documents outside formal document production.
When to use this code: Use narrowly. Substantive document organization with legal judgment qualifies; routine file maintenance is overhead under most guidelines regardless of task code.
Patterns reviewers commonly see: Administrative work carrying attorney or paralegal rates under this code, paralleling the A110 pattern on the activity side. The task code does not change the overhead classification in guidelines.
What invoice review checks: Apply the same test as A110: if the narrative describes clerical work, the guideline overhead provision governs. L140 paired with A110 on the same line is a strong indicator the entry warrants that read.
L150: BudgetingABA (1997)
Preparing and revising matter budgets and staffing plans.
When to use this code: Use for budget preparation where guidelines permit billing it. Many clients designate budget preparation as non-billable, treating it as part of the engagement relationship.
Patterns reviewers commonly see: Billable budgeting time where your guidelines designate it non-billable, and repeated budget revision entries that track the budget cycle rather than case developments.
What invoice review checks: The guideline designation resolves most questions here. Where budgeting is billable, volume should correlate with genuine scope changes in the matter.
L160: Settlement/Non-Binding ADRABA (1997)
Settlement analysis, negotiation, mediation, and other non-binding resolution efforts.
When to use this code: Use for resolution-directed work at any point in the matter. Spikes around mediation sessions and serious negotiation windows are the expected shape.
Patterns reviewers commonly see: Sustained L160 volume with no corresponding settlement activity visible to the client, which is usually a coding drift question rather than a work question.
What invoice review checks: L160 should correlate with events the legal department knows about. It is also one of the most decision-useful codes you have: matters with early L160 concentration and late resolution are where resolution strategy reviews pay for themselves.
L190: Other Case Assessment, Development and AdministrationABA (1997)
Phase work that fits no more specific L100-series code.
When to use this code: Minimal expected usage given how broad the named codes in this phase already are.
Patterns reviewers commonly see: L190 absorbing routine case administration at meaningful volume, which removes that work from any analyzable category.
What invoice review checks: Track catch-all usage by firm across all phases as a single coding-hygiene metric. The L190, L250, L390, and L440 family tells one story about how carefully a firm codes.
The pleadings and motion practice phase. Work here maps to court filings, which gives review an external reference point: the docket.
L210: PleadingsABA (1997)
Drafting and responding to complaints, answers, counterclaims, and amendments.
When to use this code: Use for pleadings work. Volume concentrates early and should track the docket.
Patterns reviewers commonly see: Pleadings hours out of proportion to the complexity of the filing, particularly on answer-and-affirmative-defenses work that follows established firm patterns.
What invoice review checks: The docket is the reference. Hours per pleading can be benchmarked across matters, and repeat matter types give you internal baselines quickly.
L220: Preliminary Injunctions/Provisional RemediesABA (1997)
Work on temporary restraining orders, preliminary injunctions, attachments, and similar emergency or provisional relief.
When to use this code: Use for provisional remedy work. Genuinely intensive when it happens, and time-compressed by nature.
Patterns reviewers commonly see: Little in the coding itself. The intensity is real; the review question is usually staffing breadth during the emergency window.
What invoice review checks: Post-event review works better than line-item review here. Compare team size and hours against the scope of the emergency once it resolves, and feed the result into staffing expectations for the next one.
L230: Court Mandated ConferencesABA (1997)
Preparation for and attendance at scheduling conferences, status conferences, and other court-required appearances.
When to use this code: Use for court-mandated conference work, including required meet-and-confer sessions tied to those conferences.
Patterns reviewers commonly see: Preparation time that exceeds the conference itself by a wide multiple for routine status appearances, and multiple attendees at conferences that call for one.
What invoice review checks: Conference length is verifiable from the docket and minute entries, which anchors both the attendance time and a reasonableness read on preparation.
L240: Dispositive MotionsABA (1997)
Motions to dismiss, summary judgment motions, and other case-dispositive motion work.
When to use this code: Use for dispositive motion practice. Often the largest single work product investment in the pre-trial life of a case.
Patterns reviewers commonly see: Summary judgment efforts that begin without a strategy conversation with the client, given the investment involved, and research or drafting volume spread across many timekeepers on a single brief.
What invoice review checks: L240 is a budgeting checkpoint more than a line-item review target. A phase-level estimate before briefing starts turns the eventual invoice review into a variance discussion instead of a surprise.
L250: Other Written Motions and SubmissionsABA (1997)
Non-dispositive motion practice not covered elsewhere, such as motions to compel filed outside discovery, motions in limine filed pre-trial, and procedural motions.
When to use this code: Use for miscellaneous motion work in the pre-trial phase.
Patterns reviewers commonly see: This code absorbing motion work that belongs in more specific categories, particularly discovery motions that belong under L350, which shifts cost between phases.
What invoice review checks: Read narratives against the docket. Motion practice always leaves a paper trail, so classification questions resolve quickly.
L260: Class Action Certification and NoticeABA (1997)
Certification briefing, class definition work, and notice administration in class action matters.
When to use this code: Use in class actions for certification and notice work. Irrelevant to most portfolios, central to some.
Patterns reviewers commonly see: Notice administration costs flowing through fees rather than through third-party administrators at cost, where an administrator is the contemplated structure.
What invoice review checks: For departments with class action exposure, L260 phase budgeting and administrator cost separation are the two structural reviews that matter.
Typically the most expensive phase of litigation and the one where task coding pays its way. Discovery codes plus E118 expenses give a legal department its clearest view of where litigation cost actually accumulates.
L310: Written DiscoveryABA (1997)
Drafting and responding to interrogatories, requests for production, and requests for admission.
When to use this code: Use for written discovery work in both directions, propounding and responding.
Patterns reviewers commonly see: Response drafting hours on discovery sets that follow standard patterns for the matter type, and written discovery entries appearing after the discovery cutoff on the scheduling order.
What invoice review checks: The scheduling order gives discovery codes a time boundary that automated rules can enforce. Within the window, benchmark hours per discovery set against comparable matters.
L320: Document ProductionABA (1997)
Collection, review, and production of documents, including privilege review.
When to use this code: Use for document review and production work. On document-heavy matters this becomes the single largest fee category in the case.
Patterns reviewers commonly see: Attorney-rate review of documents suited to staff attorney, contract reviewer, or technology-assisted workflows; review rates per document that vary widely across firms; and first-level review layered under multiple rounds of re-review. Read alongside E118, since the fee and vendor sides of document review are one economic decision.
What invoice review checks: This is where review economics live. Track documents-per-hour and cost-per-document where your eBilling and eDiscovery data allow it, and treat the review staffing model as a negotiable engagement term, because it is.
L330: DepositionsABA (1997)
Preparing for, taking, and defending depositions.
When to use this code: Use for deposition work. Preparation, attendance, and follow-up all belong here, paired with the appropriate activity codes.
Patterns reviewers commonly see: Preparation multiples well above the deposition length for routine witnesses, and second-chair attendance at depositions that call for one examiner.
What invoice review checks: Deposition length is documented by the transcript, which anchors both attendance and a preparation-ratio review. Prep-to-deposition ratios by witness type become a useful internal benchmark quickly.
L340: Expert DiscoveryABA (1997)
Expert disclosures, expert reports, and expert depositions.
When to use this code: Use once the matter enters formal expert discovery. Earlier expert selection and consulting belongs under L130.
Patterns reviewers commonly see: Report drafting time on the firm's side that parallels substantial drafting billed by the expert, which raises the question of who is writing the report.
What invoice review checks: Read L340 with L130 and E119 for the full expert cost picture. The fee-side drafting volume against the expert's own invoice tells you how the work was actually divided.
L350: Discovery MotionsABA (1997)
Motions to compel, protective order motions, and other discovery dispute work.
When to use this code: Use for discovery motion practice, including the meet-and-confer work the motions require.
Patterns reviewers commonly see: Sustained discovery motion volume, which is expensive in itself and usually signals a case-management dynamic worth a strategic conversation beyond the invoice.
What invoice review checks: L350 concentration is decision-useful data. Matters where discovery disputes consume a material share of fees are candidates for a different resolution posture, and the code makes that visible early.
L360: Onsite InspectionsABA (1997)
Inspections of premises, property, equipment, or other physical evidence conducted as part of discovery.
When to use this code: Use for site and physical inspections in the discovery phase, including preparation for and attendance at the inspection.
Patterns reviewers commonly see: Multiple timekeepers attending inspections that require one, and travel time folded into inspection entries, which parallels the A109 travel pattern.
What invoice review checks: Inspections are scheduled events with defined durations, so attendance and preparation review both anchor to the event itself.
L390: Other DiscoveryABA (1997)
Discovery work that fits no more specific L300-series code, such as third-party discovery logistics.
When to use this code: Limited expected usage given the coverage of the named discovery codes.
Patterns reviewers commonly see: Material volume here, which most often turns out to be work that belongs under L310 through L350 and is coded quickly rather than precisely.
What invoice review checks: Fold into the catch-all hygiene metric alongside L190, L250, and L440, tracked by firm.
The phase where daily burn rates peak. Few matters reach it, but the ones that do reward advance phase budgeting more than any other stage.
L410: Fact WitnessesABA (1997)
Preparing fact witnesses for trial testimony.
When to use this code: Use for trial-stage fact witness preparation.
Patterns reviewers commonly see: Preparation sessions repeated across trial continuances, which is a real cost of calendar movement worth attributing to the continuance rather than the witness work.
What invoice review checks: Witness preparation hours per witness is a benchmarkable figure. Continuance-driven repetition should be visible in the timeline and factored into how you evaluate the total.
L420: Expert WitnessesABA (1997)
Preparing expert witnesses for trial testimony.
When to use this code: Use for trial-stage expert preparation, distinct from expert discovery work under L340.
Patterns reviewers commonly see: The same dual-billing dynamic as A108 and E119: firm preparation time alongside expert-invoiced preparation time for the same sessions.
What invoice review checks: Read against the expert's invoice for the trial period. The combined figure is the real cost of putting the expert on the stand.
L430: Written Motions and SubmissionsABA (1997)
Trial-stage written motion practice, including motions in limine, trial briefs, and proposed findings.
When to use this code: Use for trial-phase written work.
Patterns reviewers commonly see: Motion in limine volume growing well beyond the evidentiary issues that matter, since these motions multiply easily and each carries drafting, response, and argument cost.
What invoice review checks: Count and scope of in limine motions against the issues genuinely in dispute. A pre-trial conversation about which motions to bring is the control point; the invoice just reports the outcome.
L440: Other Trial Preparation and SupportABA (1997)
Trial preparation not covered by the witness and motion codes, including trial logistics, exhibit preparation, and war room support.
When to use this code: Use for general trial preparation. Legitimately broad in the final weeks before trial.
Patterns reviewers commonly see: Support staff and logistics time at professional rates, and L440 absorbing work with more specific homes during the pre-trial surge.
What invoice review checks: In the trial window, phase-level budget tracking outperforms line-item review. Set the trial-phase budget with staffing named in advance, then manage variance.
L450: Trial and Hearing AttendanceABA (1997)
Attendance at trial and substantive hearings.
When to use this code: Use for time in the courtroom during trial and hearings, paired with A109 on the activity side.
Patterns reviewers commonly see: Courtroom attendance by team members without trial-day roles, which guidelines often address through staffing plans or pre-approval for attendance beyond the trial team.
What invoice review checks: Trial days are documented, so attendance review is factual: who was there, for how long, against the staffing plan agreed before trial.
L460: Post-Trial Motions and SubmissionsABA (1997)
Post-verdict motion practice, including motions for judgment, new trial motions, and fee petitions.
When to use this code: Use for post-trial work at the trial court level. Appellate work moves to the L500 series.
Patterns reviewers commonly see: The L460 and L510 boundary once notices of appeal are filed, which affects whether your appeal-phase economics are readable.
What invoice review checks: The notice of appeal is a clean dividing line on the docket. Coding on either side of it should follow the docket, and usually does once raised.
L470: EnforcementABA (1997)
Post-judgment enforcement work, including collection efforts, judgment liens, and enforcement proceedings.
When to use this code: Use for enforcing a judgment after entry, distinct from post-trial motion practice under L460.
Patterns reviewers commonly see: Enforcement cost accumulating past the point the recoverable amount supports it, which is an economics question the code makes visible.
What invoice review checks: Track enforcement fees against amounts actually collected. The ratio is the single most decision-useful number in this code.
A phase with different economics: fewer timekeepers, deeper work products, and outcomes that turn on a small number of briefs. Often staffed by different lawyers, sometimes a different firm, which makes its cost independently benchmarkable.
L510: Appellate Motions and SubmissionsABA (1997)
Appellate motion practice, procedural filings, and record designation.
When to use this code: Use for appellate work other than merits briefing and argument.
Patterns reviewers commonly see: Record preparation and procedural work volume, which varies with record size but follows predictable patterns per court.
What invoice review checks: Procedural appellate work benchmarks well across appeals in the same court system. Two or three data points give you a usable baseline.
L520: Appellate BriefsABA (1997)
Researching and drafting merits briefs on appeal.
When to use this code: Use for merits briefing, the center of gravity of any appeal.
Patterns reviewers commonly see: Brief-drafting hours distributed across many timekeepers, since appellate writing concentrates naturally in one or two hands, and total hours per brief against the issues presented.
What invoice review checks: Hours per brief is one of the most benchmarkable figures in litigation billing. Fixed-fee and capped arrangements also work unusually well for appellate briefing precisely because the work product is well-defined.
L530: Oral ArgumentABA (1997)
Preparing for and presenting oral argument.
When to use this code: Use for argument preparation and presentation, including moot sessions.
Patterns reviewers commonly see: Moot court sessions with large internal audiences all billing attendance, which is the A105 multi-attendee pattern in appellate form.
What invoice review checks: Argument length is public and preparation practices are well understood. A staffing conversation before the argument cycle sets expectations better than adjustments after it.
How should legal departments use litigation task codes in invoice review?
Litigation review works best at two levels. Line by line, confirm the task code matches the narrative and that catch-all phases like L120 analysis and strategy are not absorbing work that belongs in a specific phase. In aggregate, benchmark each phase as a share of total fees across firms handling comparable matters, since the shape of the curve says more than any single entry.
Both levels depend on the eBilling platform capturing phase codes cleanly and running the comparisons automatically, which is where legal technology implementation matters: phase budgets, budget-to-actual alerts, and cross-matter benchmarks should be system features, not spreadsheets a reviewer rebuilds each month.
How do Litigation Task Codes support legal spend management?
Litigation Task Codes only deliver value inside a program that enforces them. Our legal spend management and enterprise legal management hubs cover how coded invoices become spend control, and our guides to matter budgets, outside counsel spend benchmarks, and what to put in outside counsel billing guidelines go deeper on the review programs, guidelines, and eBilling rules that put UTBMS coding to work.
Bottom Line
Litigation task codes are the backbone of legal spend analytics. When phases are coded accurately, phase budgeting, budget-to-actual tracking, and cross-firm benchmarking all become possible; when they are not, the data cannot support any of it. The recurring review themes are a front-loaded assessment phase that stays flat too long, a strategy phase that grows into a catch-all, and a discovery phase whose share signals scope.
Accurate phase coding is what turns a pile of invoices into a spend program that can actually compare, budget, and forecast.
Frequently asked questions
What is the difference between litigation task codes and activity codes?
Task codes (the L-series) describe the phase of the matter the work belongs to, such as case assessment or discovery. Activity codes (the A-series) describe the kind of work, such as drafting or reviewing. Each time entry carries both, so one line tells the reviewer where in the case the work sits and what kind of work it was.
How many litigation phases are there?
The ABA original set defines five phases: case assessment and administration (L100), pre-trial pleadings and motions (L200), discovery (L300), trial preparation and trial (L400), and appeal (L500). The LOC eDiscovery codes (L600 series) act as a sixth phase and have their own reference page.
Which litigation codes are the most common sources of review questions?
The case assessment phase (L110 and L120) is where work that belongs elsewhere tends to accumulate, because almost any litigation task can be described as assessment or strategy. Reviewers watch the assessment phase for a flat curve deep into a matter and benchmark the strategy code as a share of total fees across firms.
How should litigation task codes be used in invoice review?
Check line by line that the task code matches the narrative and that catch-all phases are not absorbing specific work, then review phase distribution in aggregate against comparable matters. Each code below lists the patterns reviewers commonly see and what invoice review checks, so the test is concrete at both levels.
How do UTBMS codes relate to outside counsel billing guidelines and legal spend management?
UTBMS codes are the shared vocabulary that outside counsel billing guidelines and a legal spend management program depend on. Guidelines define what each code should and should not contain, the eBilling system enforces those rules, and consistent coding is what makes spend analytics and cross-firm benchmarking possible. Without agreed codes, guidelines cannot be enforced and spend data cannot be compared.
About this reference
UTBMS code sets are standards published by their respective bodies, including the ABA, the LEDES Oversight Committee, UTBMS.com, the CBA, DRI, the Judiciaries of England and Wales, and the Yerra Global KM Expert Group. All copyrights and trademarks are the property of their respective owners; Swiftwater & Company is not affiliated with or endorsed by any of them.
Code identifiers follow the published standards, while all descriptions and annotations are original Swiftwater commentary, developed with human expertise, proprietary consulting knowledge, and AI assistance.
This is general reference material, not legal advice. Standards are revised over time, so confirm the current version with the originating body before implementing.
Next Step
Ready to talk to a legal operations practitioner who has actually done it?
Start with the free CURRENT Assessment to benchmark your spend program, or use legaltechcalculator.com to build the cost case for the eBilling rules that enforce these codes.
Book a Discovery CallNo commitment and no pitch deck, just a direct conversation with a legal operations practitioner.