Home / Blog / Time capture

Set up a privilege-safe billing narrative review for litigation matters

A review routine that improves billing narratives without exposing privileged substance to the wrong reviewer.

Legal Billing Assistant Editorial Team · Published · 9 min read

Editorial illustration representing Set up a privilege-safe billing narrative review for litigation matters
Table of contents

Separate the narrative from the privileged substance

Billing narratives describe the work well enough to support a fee without revealing the legal advice behind it. A reviewer needs the task, the matter phase, and the outcome that justifies the charge. That reviewer does not need the client's litigation strategy or the attorney's mental impressions. Start by defining which fields the billing reviewer may read and which fields stay inside the legal team.

A privilege review is not the same as a billing review, and one person should not silently do both. Give the billing reviewer a redacted export that keeps dates, timekeepers, and task categories while removing privileged content. Document the export rule in the matter file so a later reviewer can repeat it. The goal is a defensible fee record, not a broader distribution of sensitive material.

Define what a reviewer may read

Write a short access matrix that maps each role to the fields it can see. The billing coordinator can usually see time, task codes, and invoice amounts, while the responsible attorney sees the full narrative. A client-facing professional may see only the redacted description that will appear on the invoice. The matrix should name the systems where each view is enforced, not just the intent.

Test the matrix with a sample export before the first live review. Ask the reviewer to identify the task and the fee basis without opening a privileged document. If the redacted view is too thin to support the charge, add a neutral task description rather than restoring the privileged text. Record the decision so the next matter can reuse the same pattern.

Build a redaction and escalation ladder

Some narratives contain a single phrase that creates risk, such as a reference to advice on a settlement position. Teach reviewers to escalate that phrase to the responsible attorney instead of rewriting it themselves. The attorney can decide whether to replace the phrase, move the detail to a privileged file, or leave the entry out. The escalation should take minutes rather than days, or the prebill will wait.

Keep a log of escalations with the matter, the date, and the resolution. The log shows whether one timekeeper or one task type produces most of the sensitive wording. Use it to improve the entry guidance rather than to criticize the writer. A repeated escalation is a sign that the narrative standard needs a clearer example.

Standardize narrative patterns without inventing facts

Provide a small set of sentence patterns that describe common tasks, such as reviewed documents for a filing, conferred with the client on a schedule, or prepared a draft for partner review. These patterns help timekeepers write consistently, but they must never replace a fact the timekeeper cannot recall. A template that invents a meeting or a document is worse than a short honest entry. Each pattern should point to the evidence the reviewer can check, not to a conclusion the writer did not reach.

Review a sample of narratives each month against the source notes. Mark the entries that use a pattern without the supporting fact. Return those entries to the timekeeper for a correction before the prebill is released. The review should focus on accuracy, not on prose style.

Review the prebill in a controlled workspace

Move the prebill review into a workspace with version control and a clear owner. The reviewer should be able to leave a comment, request a change, and see who approved the final text. Do not circulate a spreadsheet by email, because versions will diverge and the privileged text will spread. A single workspace also gives the firm a record of who saw what.

Lock the narrative fields once the prebill is approved. Late edits should go through a short exception note that names the editor and the reason. This prevents a last-minute change from reintroducing sensitive wording after the privilege check. The lock is a control, not a sign of distrust.

Train new reviewers on boundary cases

Give every new reviewer the same five boundary examples before they touch a live prebill. Include a narrative that reveals a client's business plan, one that describes a settlement authority, and one that is simply too vague to support the fee. Ask the reviewer to explain what they would keep, redact, or escalate. Compare the answers with the approved rule.

Repeat the exercise after any change to the billing system or the client's outside counsel guidelines. A new export can expose fields that the old one hid. Update the training examples and the access matrix together so the guidance does not drift from the system. Keep a dated record of who completed the training.

Measure narrative quality without reading content

Count the entries returned for a missing fact, the entries escalated for privilege, and the entries cleared on the first pass. These measures show whether the review is working without requiring a manager to read every narrative. Report them by timekeeper and by task type, with enough context to avoid a simple ranking. Keep the measure stable so one month can be compared with the next without redefining the sample.

Track the time from prebill release to approval as a separate measure. A fast review that misses a sensitive phrase is not a success, and a slow review that catches everything may still be too expensive. Set a target range and inspect the exceptions. The measures should guide coaching, not punishment.

Keep the record after the invoice is sent

Retain the redacted export, the escalation log, and the approval record with the matter file. The firm may need them if a client questions the invoice or a regulator reviews the engagement. Store them under the same retention rule as the invoice, not in a personal folder. Name the records so a successor can find them without asking the original reviewer.

Review the retention rule once a year and after any change in the client's guidelines. Delete working copies that are no longer needed, but keep the approved record and the log. A clean retention practice protects the firm and makes the next review faster. It also shows the client that the billing process is controlled.

Common questions answered

Who owns the narrative review? The responsible attorney owns the legal content and the privilege decision, while the billing coordinator owns the queue and the evidence. Name both owners in the matter record so a late question reaches the right person. The coordinator should never make a privilege call alone.

What if the redacted entry is too vague to bill? Add a neutral task description that identifies the work without the strategy behind it. If the description still cannot support the fee, ask the timekeeper for a contemporaneous note. Do not restore privileged text just to make the invoice look complete.

How often should the access matrix be tested? Test it at least once a year, after any billing system change, and when a new client guideline arrives. A short sample export is enough to confirm that each role sees the intended fields. Record the test date beside the matrix.

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

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