Legal Services Offshore blog
Build a matter budget variance review before the client update
A variance review that compares the approved budget with recorded time and cost, explains the gap, and keeps the client message separate from the numbers.

Key takeaways
A matter budget review is useful only when the baseline is written down before the work begins. The review compares recorded time and cost with that baseline and explains the difference. Without a baseline, the review turns into a description of whatever was spent. The baseline should name the assumptions and the date it was approved.
The variance review and the client update are separate documents. The review explains the numbers for the lawyer, while the update communicates an approved message to the client. Merging them risks sending an unapproved explanation. Keep the working analysis and the client-facing note in separate files.
Record every variance with a cause that can be checked. A cause such as scope growth is only useful when it points to a dated instruction or a document. Record the source beside the amount. A variance without a source is an observation rather than a finding.
The review should end with a decision and an owner. The decision may be to absorb the difference, seek approval for more budget, or change the plan. Record who decided and when. A review that ends without a decision will be repeated next month.
Set the budget baseline before the review
Record the approved budget with its phases, its assumptions, and the person who approved it. The baseline should state what work is included and what is excluded. A budget that lists only a total cannot support a meaningful comparison. The reviewer needs the structure as well as the number.
Keep the baseline version that existed at the start of the period. A budget revised after the work was done cannot explain the variance. Record the revision date and the reason for any later change. Compare the period against the baseline that applied during the period.
Record the time and cost categories that the firm uses to report the matter. The categories should match the budget phases where possible. A mismatch produces a variance that is only a reporting artifact. Note the mapping in the working paper.
Confirm the exchange rate or the fee basis when the matter involves more than one currency or a fixed fee. Record the source and the date of the rate used. A rate change can create a variance that has nothing to do with the work. The reviewer should see the basis.
Compare actual time and cost to the approved plan
Export the recorded time and cost for the period and freeze the export before the review. Freezing the export prevents an entry from changing after the comparison. Record the export date and the person who produced it. A later reader should see the same figures the reviewer saw.
Compare each category with the baseline and record the difference in both amount and share. A large share on a small category can be more important than a small share on a large one. Record both so the reader can judge. Do not round away a difference that affects a decision.
Separate a timing difference from a real overrun. Work that moved into the next period is different from work that cost more than planned. Record the category and the evidence. The lawyer decides whether the timing difference needs a client note.
Record the unbilled time and the write-offs that affect the comparison. A budget comparison that ignores write-offs can show a variance that the client never sees. Record the amounts and the approval. The billing owner confirms the treatment.
Explain variance without changing the numbers
Write the explanation beside the recorded figure rather than editing the figure. The record should show what was spent and what the team believes caused it. Record the source of the explanation, such as a meeting note or an instruction. The explanation is analysis, not a correction.
Distinguish a cause the firm controls from one it does not. A court-ordered schedule change is different from an internal delay. Record the category and the evidence. The difference informs the next budget rather than assigning blame.
Note any scope change with the dated instruction that authorized it. A scope change without a written instruction is a question for the lawyer. Record the question and the person who can answer it. The review should not assume that a conversation changed the budget.
Keep the explanation short enough to review and specific enough to test. A paragraph that repeats the category name adds nothing. Point to the document, the date, and the amount. The next reviewer should be able to follow the reference.
Decide what goes into the client update
Draft the client update only after the lawyer has reviewed the variance. The update should use the explanation the lawyer approved. Record the approval and the date. A draft sent before approval can create a promise the firm did not intend.
Describe the status and the next step without predicting the final cost. A projection is a legal and commercial statement that belongs to the lawyer. Record any projection the lawyer approved and its basis. Keep the wording close to the approved version.
Record what the client asked for and what the firm agreed to send. A client request for a revised budget should go to the lawyer rather than to the support team. Record the request and the owner. The update should reflect the actual exchange.
File the approved update with the variance review so the numbers and the message stay together. A reader should see what was decided and what was communicated. Record the date sent and the channel. The pair is the record of the client conversation.
Keep the review note with the matter record
Store the baseline, the export, the variance schedule, and the approval in one place. A review spread across three folders is hard to reconstruct. Record the location in the matter index. The index should name the budget documents.
Record who prepared the review and who approved the conclusion. A review with no named reviewer is difficult to rely on. Record the role and the date. The names should match the firm's delegation record.
Restrict access to the review to the people who need the financial detail. The working paper may contain fee information that is not for the whole team. Record the access list and the review date. Remove access when the matter closes.
Check that the stored review opens after a system change. A file that no longer loads is not a record. Record a sample check and the date. Review old budget folders during the next records audit.
Check the next budget against the last variance
Use the variance categories from the last review when building the next budget. A repeated cause should change an assumption rather than appear again as a surprise. Record the change and the reason. The next baseline should reflect what the firm learned.
Record the assumptions that the team expects to test during the matter. A budget with no stated assumptions cannot be reviewed. Record the assumption and the date it will be checked. The reviewer should know which number is uncertain.
Review the variance process with the billing owner and the lawyer who owns the matter. Ask whether the categories still match how the work is recorded. Record the answer and any change. A process that fits one matter may not fit the next.
Set the date for the next variance review before the current one closes. A recurring date prevents the review from being skipped in a busy month. Record the date and the owner. The cadence should be visible to the whole matter team.
A supervised support lane can assemble the baseline, the time export, and the variance schedule while the lawyer approves the explanation and the client message. billing and time entry support.
Sources
- American Bar Association, Model Rules of Professional Conduct
Used for supervision, confidentiality, competence, and communication boundaries in legal support work.
- American Bar Association, Law Practice Management Resources
Used for the general matter management and client communication context that this review supports.
- GAO, Standards for Internal Control in the Federal Government
Used as a general reference for documented ownership, review evidence, and exception handling.
- NIST Cybersecurity Framework 2.0
Used for access control, monitoring, and recovery language around shared legal records.