Home / Research / Narrative quality

How often do billing narratives omit the business purpose of the task?

A narrative audit that tests whether a billed entry explains why the work was necessary, not just what activity occurred.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How often do billing narratives omit the business purpose of the task?
Table of contents

Method note: this brief proposes a source-led review approach. It does not claim that private client or firm data has been collected.

Question and scope

This protocol asks how often a billed time narrative omits the business purpose of the task. The unit is a billed time line, and the measure is whether a reader can identify why the task was necessary and how it advanced the matter. The study covers narratives on invoices issued during the period, not the quality of the legal work. It does not evaluate whether the time spent was reasonable.

Scope the study to matters with at least one narrative entry above the firm's minimum billing threshold. Include invoices that were paid, adjusted, and still open so the denominator reflects the full workload. Exclude fixed-fee lines and cost-only lines, and record the number excluded. State the billing system, the narrative standard, and the owner of the analysis.

Defining the event

Define a purpose gap as a narrative that describes an activity but not the reason it was needed at that stage. Reviewed documents is an activity, while reviewed the production to identify documents responsive to the court order states a purpose. A short entry can still have a purpose, and a long entry can still lack one. Write two examples and one boundary case before coding.

Distinguish a purpose gap from a vague verb and from a missing narrative. A vague verb may still be clear in context, while a missing narrative is a blank field with a separate code. Keep the categories separate because the repair differs. Code the primary issue and note any secondary issue.

Population and denominator

The population is every narrative time line on an included invoice. Report the number of invoices, the number of lines, the number excluded, and the number in the final sample. Count lines rather than invoices, because one invoice can contain entries from several timekeepers. If a line was revised after the invoice, use the version that the client received.

Report the purpose gap rate by line and by billed value. A small number of high-value lines can carry most of the client exposure, so the value measure matters. Keep both measures in the report. The value measure should use the billed amount, not a notional rate.

Evidence sources

Use the invoice narrative, the contemporaneous time note, the task code, and the client guideline as the primary evidence. Compare the narrative with the note and record the date each was observed. If the note is missing, mark the line as incomplete rather than inferring the purpose from the matter name. The evidence log should let a second reviewer repeat the match.

Rank the sources so reviewers know what to trust first. A contemporaneous note is stronger than a later summary, and the client guideline is stronger than an internal assumption about what the client wants. Record the evidence type for each line so the analysis can separate a documentation gap from a genuine purpose gap. A task code without a note is the weakest source for a purpose question.

Sampling

Sample across timekeepers, task types, and clients so one matter does not define the result. Include entries that were paid without a question, because payment is not proof that the narrative was clear. Draw the sample before reading the narratives so the selection is not biased toward the disputed lines. If the population is small, review every line and extend the period.

Stratify the sample by entry length and by whether the client guideline requires a purpose statement. A short entry may pass more often because it is easier to read, while a long entry may hide the purpose in detail. Report the gap rate for each stratum rather than pooling them. The reader should be able to see where the standard breaks down.

Coding the record

Use a short code list that points to a specific repair. Code each line as clear purpose, activity only, generic wording, missing narrative, or unknown. Add a note for the task type and the stage of the matter. Keep the code list short enough that two reviewers can apply it consistently.

Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the narrative and the source note, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on what counts as a purpose, stop and fix the definition before continuing.

Measuring the variable

Measure the purpose gap rate by line, by billed value, and by task type. Report the median and the range for the narrative length so a few long entries are visible. Measure the share of lines that pass a blind reader test, where a reviewer who does not know the matter tries to state the purpose. Keep the raw counts with the analysis file.

Do not convert the gap to a dollar figure without an approved fee and collection data. The study measures narrative quality, not profitability. If the firm wants a revenue view, run it as a separate analysis with the finance owner. A precise dollar figure built on an incomplete narrative set is less useful than a clear line count.

Analysis and reporting

Report the overall gap rate, the rate by task type, and the number of lines behind each figure. Show the share of billed value affected and the most common wording pattern. Compare only groups with similar client requirements and matter types. Include the lines that were clear so the report shows the full distribution.

Give the reader one table that answers the main question and put the coding detail in an appendix. Write the finding in plain language before presenting the technical definition. Include the cases that contradict the pattern rather than hiding them in an average. A report that cannot be acted on is just another record of the past.

Limits and sources of error

A missing note is not proof that no purpose existed, and a later summary is not proof that the purpose was clear at the time. Report the completeness of the evidence before drawing a conclusion. Small samples, changing client guidelines, and reviewer disagreement can all limit interpretation. A short entry may be perfectly clear to a reader who knows the matter.

Avoid comparing groups that differ in client sophistication or matter complexity. A client that reviews every line may receive fuller narratives than one that does not. Describe the context beside the rate and avoid ranking individual timekeepers. The purpose is to improve the record, not to judge professional worth.

Privacy and retention

Store the narratives, source notes, and client guidelines in a controlled folder with access limited to the study team. Remove client names, matter details, and privileged content from the analysis file when they are not needed. If an example is shared, use a role label and redact the client and the specific matter. Keep privileged material in a separate restricted location.

Do not circulate a client-level or timekeeper-level list about narrative quality outside the management context. Aggregate the results before sharing them more broadly, and check that a small group cannot be re-identified. The same rule applies to screenshots of the billing system and to quoted entries. Privacy is part of the method, not an afterthought added at the end.

Applying the result

Choose one change that matches the most common gap. If activity-only entries dominate, add a purpose prompt to the time-entry form with a short example. If long entries hide the purpose, add a review question at the prebill. If the guideline is unclear, ask the client for a sample of an acceptable narrative.

A lower gap rate is not the only useful outcome. Faster client approval and fewer questions can improve the process even when the rate stays similar. Report the direct result and the service result separately. Stop the change if it produces longer narratives without a clearer purpose.

Review cadence

Repeat the audit each quarter and after any change to the time-entry form, the client guideline, or the billing system. Keep the definitions and the unit stable so periods can be compared. Report the lines that were excluded or still open beside the main rate. Review the coding guide after the first repetition and keep the changes visible.

Review the result with the billing manager and the attorney who supervises the timekeepers, not only with the preparer. Ask which fix is easiest to sustain and which gap causes the most client questions. Set one change and a follow-up date, then check whether the change held. The next audit should test the repair, not just repeat the same count.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. American Bar Association Model Rules of Professional Conduct
  2. Legal Electronic Data Exchange Standard
  3. U.S. Government Accountability Office Green Book
  4. Internal Revenue Service recordkeeping guidance
  5. U.S. Bureau of Labor Statistics
  6. Federal Trade Commission data security guidance

Put the guidance to work

Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.

Discuss your workflow