Home / Research / Billing operations

How much billing rework comes from unclear partner instructions?

A study protocol for measuring rework caused by ambiguous partner instructions, including definitions, sampling, coding, and reporting limits.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How much billing rework comes from unclear partner instructions?
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 much billing rework is caused by partner instructions that lack a needed detail. The unit is a rework event, meaning a billing task that had to be repeated, corrected, or escalated because the original instruction was unclear. The purpose is to distinguish an instruction problem from a rate, guideline, or system problem. The result is an operational estimate, not an evaluation of any partner's communication style.

Scope the study to one billing team and a defined period, such as one quarter or two billing cycles. Include instructions delivered in person, by email, by message, or through a task system. Exclude work that was redone because the client changed a requirement after the instruction was given. State the team, the matters, and the instruction channels included so the estimate is not applied outside its scope.

Defining an unclear instruction

An instruction is unclear when a reasonable billing specialist cannot complete the requested action without asking a follow-up question or making an assumption that later proves wrong. The ambiguity may concern scope, amount, rate, narrative, timing, or approval authority. Record the specific missing element rather than labeling the whole instruction as vague. A precise definition makes the coding repeatable.

Distinguish an unclear instruction from an incomplete record. If the partner gave a clear direction but the supporting document was missing, that is a records problem. If the partner said to make the invoice reasonable without naming the amount or standard, that is an instruction problem. The two can occur together, so record the primary cause and any secondary cause separately.

Rework events and the unit of analysis

Count one rework event each time the original task must be revisited because of the instruction gap. A single instruction may generate several events if it affects multiple invoices or timekeepers. Record the event at the point of correction, not at the end of the month when the memory has faded. The event should have a start time, an end time, and a clear description of the repeated work.

Use the billing task as the primary unit and the matter as a secondary unit. The task-level view shows where the time goes, while the matter-level view shows whether the problem concentrates in particular engagements. Report both so a leader can see the operational cost and the relationship context. Do not average across dissimilar task types without showing the mix.

Evidence sources

Use the original instruction, the follow-up question, the corrected task, and the final approval as the core evidence. The follow-up question is often the clearest proof that a detail was missing. If the correction happened without a question, record the assumption that was made and how it was discovered. Link each source to the rework event so a second reviewer can verify it.

Add the billing system timestamps and the queue history where available. These records show when the task was opened, changed, and closed. Do not rely on a recollection that the instruction was confusing. The evidence standard should let an analyst confirm the event from the file without interviewing the people involved.

Sampling and observation

If the volume is manageable, review every rework event in the period. If not, sample by partner, matter type, and instruction channel so the sample reflects the population. Draw the sample before reviewing outcomes to avoid selecting only the most dramatic cases. Record the sampling frame and the inclusion rules in the study file.

Ask the billing specialists to log potential events during the period using a short form. The form should capture the instruction, the missing detail, the action taken, and the time spent. Keep the form short enough that people complete it in the moment. A long form produces late, reconstructed entries that are less reliable.

Coding the cause

Use a small cause list: missing amount, missing scope, missing rate basis, missing narrative standard, missing approval, conflicting instruction, and other. Define each code with an example and an exclusion. Add a secondary code when more than one detail was missing. The coding should point to a specific fix, such as a template field or a confirmation step.

Have a second reviewer code a sample and compare the results. Report the agreement rate and resolve disagreements by returning to the evidence. If a code cannot be applied consistently, revise the definition before continuing. The coding scheme is part of the measurement, not an afterthought.

Measuring time and cost

Measure active time per rework event, not elapsed time. Active time includes rereading the instruction, asking the question, rebuilding the task, and rechecking the result. Waiting for a response is a separate measure because it affects cycle time but not staff effort. Report both so the team can see the difference between a slow answer and a costly correction.

Multiply the observed time by the number of events to estimate total effort for the period. Report the median and the range rather than a single average, because a few complex events can distort the mean. Do not convert time to a dollar cost unless the firm provides an approved labor rate and the method for applying it. The protocol measures effort, not price.

Analysis and reporting

Report the number of rework events, the share of instructions affected, and the active time per event. Break the results down by cause, partner group, matter type, and instruction channel. A high rate in one channel may point to a template or a meeting habit rather than an individual. Show the count behind each rate so a small sample is visible.

Compare the cost of the rework with the cost of the prevention step. A short confirmation template may prevent several events at a low cost, while a new meeting may add time without solving the cause. Report both sides of the comparison. The output should identify one or two specific changes, not just a ranking of causes.

Limits and sources of error

Self-reported logs can be incomplete or rounded, and people may underreport events that felt routine. Pair the log with a sample of direct observation or system timestamps to check for bias. Report the share of events with estimated time. A precise number based on coarse logs is misleading.

The study may overrepresent partners who give many instructions or matters with heavy billing activity. Report the mix and avoid comparing partners on a raw count without adjusting for volume. The purpose is to improve the instruction process, not to rank individuals. Keep the limitations beside the result.

Retention and privacy

Store the instruction evidence and the time logs in a controlled billing folder. Remove client names and matter numbers from the analysis file when they are not needed. If an example is used in training, redact the client and the individual partner. Follow the firm's records policy for the retention period.

Limit access to the study team and the billing manager. Do not circulate a list of partners with the highest rework counts outside the management context. The study is about process design, not personal performance. Aggregate the results before sharing them more broadly.

Applying the result

If missing amounts dominate, add an amount field to the standard instruction template. If missing scope dominates, require the matter and phase to be named before the task is accepted. If conflicting instructions dominate, add a confirmation step that resolves the conflict before work begins. The fix should match the most common cause.

Test the change on a small sample in the next cycle and compare the event rate with the baseline. A drop in one cause with no increase in another is evidence that the change worked. If the rate does not move, examine whether the instruction channel or the matter mix changed. Record the result and set the next review date.

Review cadence

Repeat the study each quarter while instruction templates are being changed, then move to a semiannual cycle. Keep the cause definitions and the event rule stable so the trend is comparable. Report any change in the instruction channels or the matter mix beside the result. A measure that changes its method every cycle cannot show whether the process improved.

Review the findings with the billing manager and a partner group that gives many instructions. Ask which missing detail causes the most rework and which template change is practical. Set one change and a follow-up date before the next cycle. The review should end with a named owner, not a general agreement that communication matters.

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. Federal Trade Commission data security guidance
  6. United States Department of Labor work hours 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