Home / Blog / Prebill workflow

Prepare a prebill packet for a partner's fifteen-minute review

A packet design that puts the decision, the exceptions, and only the needed evidence in front of a partner who has fifteen minutes to review a prebill.

Legal Billing Assistant Editorial Team · Published · 8 min read

Editorial illustration representing Prepare a prebill packet for a partner's fifteen-minute review
Table of contents

Put the decision on the first page

A partner opening a prebill packet should see the decision before the detail. State the matter, the billing period, the total, and whether the packet recommends release, hold, or a specific correction. Put the recommendation at the top with the exceptions that drive it. The rest of the packet exists to support that first page, not to make the partner search for the point.

Name the person who prepared the packet and the person who owns the next decision. Include the date and the version so the partner knows which draft is in front of them. If the packet is a revision, say what changed since the prior version. A clear first page respects the partner's time and reduces the chance of approving the wrong draft.

Order exceptions by money and risk

Sort the exceptions by dollar impact first, then by client or regulatory risk. A large write-down request and a small missing receipt should not receive the same visual weight. Put the highest-value or highest-risk items at the top of the exception page with a one-line reason. The partner can then spend the available minutes on the items that matter most.

Group routine corrections separately so they do not crowd the decisions. A missing task code that the assistant can fix under a written rule does not need partner attention. State that the routine items were corrected and list them in an appendix for audit. Separating preparation from decision is the point of the packet. A short appendix is enough when the correction rule is written and the list is stable.

Attach only the evidence a partner will open

For each exception, attach the smallest evidence set that supports the decision. A rate question may need the engagement letter and the prior invoice, while a narrative question may need the time entry and the client guideline. Do not attach the full matter file in the hope that more is better. Excess evidence slows the review and makes the relevant fact harder to find.

Label each attachment with the exception it supports and the page or field to check. Use a consistent naming pattern so the partner can move from the packet to the evidence without guessing. If an attachment contains privileged or sensitive material, mark it and limit distribution. The packet should make the evidence easy to verify, not merely available.

Separate missing information from disagreement

Mark a record as incomplete when a required field or source is absent. Mark it as disputed when the information exists but the correct treatment is contested. The two statuses lead to different next steps and different owners. Combining them into one exception category causes the partner to spend time on a question that a matter team member could answer.

For incomplete records, name the person or system that can supply the missing item and the date it was requested. For disputed records, state the competing positions and the decision the partner is being asked to make. A short distinction on the exception page prevents the review from turning into an investigation. It also gives the assistant a clear follow-up path after the meeting.

Write the one-line recommendation carefully

The recommendation should state an action, not a sentiment. Write release the invoice, hold line twelve pending client approval, or reduce the charge to the approved rate. Avoid phrasing such as looks reasonable or seems fine, because it does not tell the partner what approval would do. A specific recommendation is easier to accept, reject, or modify.

Support the recommendation with the rule and the evidence, not with the assistant's confidence. If the rule is ambiguous, say which interpretation was used and who confirmed it. If no one confirmed it, say that the decision is still open. Honest uncertainty is more useful than a confident recommendation built on an unstated assumption. A recommendation that cannot name its rule is not ready for the packet.

Keep the review packet short enough to finish

Set a page budget for the packet and treat it as a design constraint. Most partner reviews can work with a one-page summary, a short exception list, and a small evidence appendix. If the packet exceeds the budget, move routine detail to a secondary file rather than shrinking the font. The partner should be able to finish the review in the time available.

Test the packet with the intended reviewer before the busy close period. Ask where they looked first, what they could not find, and which attachment they ignored. Use that feedback to reorder the pages and remove unnecessary material. A packet designed around actual reading behavior is more effective than one organized around the preparer's workflow.

Record the partner's decision in place

Capture the decision next to the exception it resolves, not in a separate email thread. Record the approver, the date, the action approved, and any condition attached to it. If the partner approves a range or delegates a follow-up, write the boundary explicitly. The record should let a later reviewer understand what was authorized without asking the partner again.

Send the decision record to the billing team and the matter owner the same day. Update the prebill status only after the record is saved. If the partner asks for a change that affects another matter or client, route it through the appropriate owner rather than applying it broadly. A decision recorded in place is easier to audit and harder to misapply.

Use the next packet to fix the template

After the review, note which exceptions recurred and why the template did not prevent them. A repeated missing field may call for a matter-opening check, while a repeated narrative issue may call for a timekeeper prompt. Assign one template or workflow change and a date to test it. The packet improves when each review produces a specific fix.

Compare the time spent preparing the packet with the time the partner spent reviewing it. If preparation is growing while review time stays flat, the packet may be carrying unnecessary detail. If review time is growing, the first page or the exception ordering may be weak. Use both numbers to guide the next redesign rather than guessing.

Common questions answered

How many exceptions should a packet include? Include every exception that requires a decision, but group routine corrections separately. If the decision list is long, order it by value and risk and summarize the remainder. The partner should not have to read every routine item to find the few that need judgment. A long list is acceptable when the priority is clear.

What if the partner wants the full file? Keep the full file available and link to it from the packet rather than attaching it by default. Note the specific documents that support each exception. If the partner asks for more, add the requested evidence for the next review. Respecting the page budget does not mean hiding the record.

Who prepares the recommendation? The billing support specialist can draft the recommendation from the written rule and the evidence. The supervising attorney or billing manager remains accountable for the decision. The packet should show who prepared it and who approved it. A recommendation is not an approval.

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

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