Home / Research / Budgets

How often do matter budgets change after the first prebill?

A budget revision study that counts changes after the first prebill, codes the reasons, and reports the effect on client communication and approval.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How often do matter budgets change after the first prebill?
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 matter budget changes after the first prebill is prepared. The unit is a budget revision event, defined as a change to the approved amount, phase allocation, or staffing plan that is recorded after the first prebill. The purpose is to understand how stable the budget is during the billing cycle and whether clients are informed before the change appears on an invoice. The result describes the process, not the accuracy of any individual estimate.

Scope the study to matters with a written budget and at least one prebill in the period. Include revisions requested by the client, the partner, or the billing team. Exclude routine accrual updates that do not change the approved budget. State the matter types, the clients, and the period included so the result is not generalized beyond the sample.

Defining a budget change

A budget change occurs when the total approved amount, the phase allocation, or the staffing plan changes in a way that affects the client's expectation or the firm's approval. A change from one timekeeper to another may be a staffing change even if the total stays the same. Record the type of change and the date it was approved. The definition should match the fields the firm actually maintains.

Distinguish a formal revision from a forecast update. A formal revision changes the approved budget and usually requires client communication or internal approval. A forecast update changes the expected spend without changing the approved amount. Both are useful, but they answer different questions. Report them separately so a routine forecast does not look like a budget breach.

Baseline and revision records

Capture the baseline budget, the approval date, and the source document before the first prebill. Record the phase amounts and the assumptions that matter for the work. If the baseline is only a total number, note that limitation because it prevents a phase-level analysis. A baseline without a date cannot support a timing comparison.

For each revision, record the prior amount, the new amount, the reason, the approver, and the client communication date. Link the revision to the prebill or invoice that triggered it. If the revision was discussed verbally, record the date and the participants. The record should let a reviewer reconstruct the sequence without guessing.

Sampling

Sample matters across practice areas, matter sizes, and clients with different budget requirements. Include matters with no revisions so the denominator reflects the full population. Draw the sample before reviewing the revision history to avoid selecting only the most volatile matters. Report the sampling frame and the number of matters in each stratum.

If the firm has few budgeted matters, extend the period rather than reducing the evidence standard. Track matters that close during the window and matters that remain open at the end. Report open matters separately because their revision history is still developing. Dropping them would bias the result toward shorter matters.

Data collection

Use the budget record, the prebill history, the matter management system, and client correspondence as the primary sources. Record the date each revision was approved and the date the client was told. The gap between the two is a useful measure of communication lag. If the client was never told, mark that as a missing communication rather than assuming it happened.

Collect the data at defined milestones: first prebill, mid-matter review, and closing. A single end-of-matter review may miss revisions that were later reversed. The milestone approach captures the state the reviewer actually saw. Keep the collection dates so the timeline is clear.

Coding the reasons

Use codes such as scope change, staffing change, rate change, client request, estimate error, and other. Define each code with an example and require a note for the other category. Add a secondary code when more than one reason applies. The coding should point to a specific prevention or communication step.

Distinguish a revision caused by new information from one caused by an error in the original estimate. A scope change is often legitimate and predictable, while an estimate error may point to a template or review gap. Report the two separately so the firm does not treat every revision as a failure. The cause should be based on evidence, not on alater recollection.

Analysis

Report the share of matters with at least one revision, the median number of revisions, and the median time from the first prebill to the first revision. Include the share of revisions communicated to the client before the next invoice. A revision that is approved internally but never communicated creates a client surprise even if the number is correct. Report the count of matters behind each share so a small sample is visible.

Break the results down by matter type, client, and reason. A high revision rate in one practice area may reflect the nature of the work, while a high rate in another may reflect a weak intake estimate. Compare only matters with similar scope and duration. The analysis should describe the pattern, not rank the partners.

Reporting

Report the revision rate, the timing, the reasons, and the communication lag together. A high rate with early client communication is a different problem from a low rate with late communication. Show the number of matters behind each rate. The report should make the operational trade-off visible.

Present the results to the billing manager, the budget owner, and a relationship partner. Ask which revisions were avoidable and which were legitimate. Set one change to the intake estimate or the client communication routine. The report should lead to a decision, not just a description.

Limits and sources of error

Budget records are often incomplete, especially when the original estimate was verbal or stored in a separate spreadsheet. A missing revision is not proof that no change occurred. Report the completeness of the source before drawing conclusions. Name the owner of the budget record and the system where it is maintained.

Matter duration and scope complexity confound comparisons across practice areas. A long matter has more opportunity for revision, and a fixed-fee matter may have no budget revisions at all. Report the context beside the rate and avoid comparing unlike matters. The purpose is to improve the process, not to judge the estimate in isolation.

Privacy and retention

Store the budget history in the controlled matter record and keep the study file separate from the live budget. Remove client names and matter details from the analysis file when they are not needed. If an example is shared, use a role label and a rounded amount. Follow the firm's records policy for the retention period.

Limit access to the study team and the budget owner. Do not circulate a partner-level revision list outside the management context. Aggregate the results before sharing them more broadly. The same care applies to client communications quoted in the study.

Applying the result

If estimate errors dominate, add a phase-level check to the intake budget and a second review before the first prebill. If scope changes dominate, build a client communication step into the change approval. If communication lag dominates, add the client notice date to the revision record and review it weekly. The fix should match the most common reason.

Test the change on a defined group of matters and compare the revision rate and communication lag with the baseline. A lower rate of avoidable revisions is the direct result, while earlier client notice is the service result. Report both. Set a follow-up date and keep the definitions stable so the comparison is valid.

Review cadence

Repeat the study annually and after a major rate change, practice group reorganization, or budget template revision. Keep the baseline and revision definitions stable so the comparison is meaningful. Report the matters that crossed a material threshold separately from routine forecast updates. A change in the client mix should be noted beside the rate.

Review the findings with the budget owner, the billing manager, and a relationship partner. Ask which revisions were avoidable and which communication step would have helped the client most. Set one change and a follow-up date. The next study should test whether that change reduced avoidable revisions without hiding legitimate scope changes.

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. U.S. Government Accountability Office Green Book
  3. Legal Electronic Data Exchange Standard
  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