Home / Blog / Billing guidelines

Write a client billing guideline summary an assistant can use

How to turn a long client billing guideline into a short, checkable summary that a billing assistant can apply without guessing at the client's intent.

Legal Billing Assistant Editorial Team · Published · 8 min read

Editorial illustration representing Write a client billing guideline summary an assistant can use
Table of contents

Why the original guideline is not an operating instruction

A client billing guideline is written to govern a relationship, not to tell an assistant which field to check on a Tuesday. It may describe prohibited charges in one section and approval expectations in another, leaving the reader to connect them. The assistant needs a summary that puts the check, the evidence, and the escalation in one place. Copying the guideline into a shared folder is not a summary and does not reduce ambiguity.

Start by identifying the decisions the assistant is allowed to prepare and the decisions that remain with the firm. A guideline that says a charge is not permitted still needs a rule for what happens when the charge appears on a draft invoice. The summary should translate that rule into a status the assistant can assign and a note the reviewer can verify. If the guideline does not answer the question, the summary should say so explicitly.

Capture the client, matter, and effective date

Every summary needs a client name, the matters it applies to, and the date the guideline took effect. Add the version or source location so a reviewer can confirm the summary matches the current document. A summary without an effective date becomes dangerous during a rate change or a new outside counsel policy. The date also tells the assistant which older matters may still follow a prior rule.

Where a client uses different guidelines for different matter types, create separate summaries rather than one blended page. Blend the rules and the assistant will apply a litigation restriction to a corporate matter. Name the matter type in the summary header and link it to the matter record field that drives the choice. The reviewer should be able to tell in seconds which version applies.

Translate rules into checkable fields

Turn each guideline requirement into a field, a value, and an evidence source. A rule about block billing becomes a check on narrative structure with examples of acceptable and unacceptable entries. A rule about travel time becomes a check on the timekeeper, the rate, and the client approval reference. The assistant should not have to interpret a paragraph to know which field to inspect.

Keep the field names aligned with the systems the assistant actually uses. If the billing system calls the field matter identifier, the summary should use the same term rather than introducing a new label. Consistency reduces translation errors and makes training easier. When a field cannot be checked directly, write down the manual evidence that must be attached.

Separate prohibited charges from approval requirements

A prohibited charge should never appear on a prebill without a documented exception. An approval requirement is different because the charge may be valid once the right person agrees. Mixing the two categories causes assistants either to strip legitimate charges or to release invalid ones. Give each category its own status and its own escalation route.

For prohibited charges, write the exact action the assistant takes when one is found. The action might be to remove the line, flag it for the billing manager, or hold the prebill until the client responds. For approval requirements, name the approver and the evidence that must be attached. The distinction should be visible in the summary even to someone reading it for the first time.

Record the source page and version

Each rule in the summary should point back to the page or section of the client guideline that supports it. A reviewer who questions a status can then check the original wording without searching the entire document. Page references also help when a client issues a revised guideline with only a few changed paragraphs. The summary becomes auditable when every rule has a traceable origin.

Store the source document in a location the assistant can reach without asking for permission each time. Keep the version label in the file name and in the summary header. When a new version arrives, mark the old summary as superseded rather than deleting it. Reviewers may still need the prior rule for matters billed under an earlier agreement.

Show worked examples for ambiguous rules

Some guidelines are clear in principle but difficult at the margin, so include two or three worked examples for each ambiguous rule. Show a clean entry, a borderline entry, and an entry that must be escalated. Explain the decision in one sentence per example so the assistant can compare the reasoning. Examples reduce the chance that two reviewers apply the same rule in opposite ways.

Choose examples from the firm's own redacted records when possible, because generic examples often miss the local billing system's quirks. Remove client identifiers and keep the narrative structure intact. Update the examples when a frequent exception reveals a gap in the rule. A summary with no examples tends to be read once and then abandoned under queue pressure.

Set an escalation route for conflicts

Write down what the assistant does when the client guideline conflicts with a partner instruction or a matter record field. Name the person who resolves the conflict and the maximum time the record may wait before escalation. The route should include a place to record the question and the answer. Without a route, assistants either guess or stop working, and both outcomes cost the firm.

Distinguish a true conflict from missing information. A conflict requires a decision from an authorized owner, while missing information may only require a call to the matter team. The summary should show the assistant how to tell the difference and what to write in each case. Clear escalation language protects the assistant from being pulled into a judgment the role does not own.

Review the summary when guidelines change

Set a review trigger for every new client guideline, annual refresh, or material rate change. Compare the new source with the existing summary and record each addition, deletion, or clarification. Do not rewrite the whole summary when only one section changed, because unnecessary edits create new opportunities for error. A dated change log beside the summary makes the revision visible to reviewers.

Ask the assistants who use the summary to report rules that still cause hesitation. Their questions are evidence that the translation is incomplete or the example is missing. Fix the summary before the next billing cycle and note the change in the log. A guideline summary earns trust when it improves through use rather than sitting unchanged for a year.

Common questions answered

Can the summary replace the client guideline? No, the summary is an operating aid and the client guideline remains the controlling document. Keep the source linked and versioned so a reviewer can verify any rule. Use the summary to make routine checks faster, not to narrow the client's rights. When the two conflict, stop and escalate to the owner.

How long should the summary be? Keep it short enough that an assistant can scan it during a live review. Most summaries work best as a few pages organized by check rather than by the client's document order. Move detailed examples into an appendix if the main summary becomes unwieldy. Length is less important than whether each rule is checkable.

Who should approve the summary before use? The billing manager or supervising attorney who owns the client relationship should approve it. Ask that person to confirm the prohibited charges, approval thresholds, and escalation owners. Record the approval date with the version. An unapproved summary should not be used to release a prebill.

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. Legal Electronic Data Exchange Standard

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