Home / Research / Write-offs

What share of write-off requests lack a documented client basis?

An evidence-completeness study for write-off requests that separates a client-driven adjustment from an internal quality decision.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing What share of write-off requests lack a documented client basis?
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 what share of write-off requests lack a documented client basis. The unit is a write-off request, defined as a formal request to reduce or remove a charge before or after invoicing. The purpose is to distinguish an adjustment supported by a client rule or communication from one supported only by an internal opinion. The result is an evidence-quality measure, not a judgment about whether the write-off was appropriate.

Scope the study to requests submitted in a defined period and to the records the firm maintains for each request. Include requests approved, rejected, and still pending. Exclude routine courtesy discounts that follow a published policy with no client-specific basis. State the approvers, the request types, and the period included so the result is comparable.

Defining a documented client basis

A documented client basis is a written client rule, guideline, contract term, or communication that supports the adjustment. The evidence should identify the client, the requirement, and the date it applied. A general statement that the client would not pay is not a documented basis unless it is tied to a specific client communication. The standard should be strict enough that a second reviewer can verify it.

Distinguish a client basis from an internal quality basis. A firm may write off a charge because a timekeeper made an error, even when the client never objected. That is a legitimate internal decision, but it should be coded separately. The study measures whether the stated basis is documented, not whether every write-off must be client-driven.

Population and denominator

The population is every write-off request submitted in the period, including those below the approval threshold if they are recorded. The denominator should count requests, not line items, unless the study is specifically about line-level adjustments. Report the total amount requested and the total approved so the reader can see the financial scale. A request count without amounts can understate the issue.

Exclude requests that were withdrawn before review or that were duplicates of an earlier request. Record the exclusion rule and the number excluded. If a request contains several unrelated adjustments, split it into separate units or state that it is treated as one. Consistency in the unit is essential for comparing rates.

Evidence standard

For each request, look for the source document, the date, the specific rule or statement, and the person who confirmed it. A link to a client guideline is stronger than a summary written by the requester. If the basis is a phone call, the evidence should include the date, the participants, and a note made at the time. A later recollection is weaker evidence and should be labeled as such.

Score the evidence as complete, partial, or missing. Complete means a reviewer could verify the basis without asking the requester. Partial means the basis is referenced but the source or scope is unclear. Missing means there is no client evidence at all. Define the three levels with examples so two reviewers apply the same standard.

Sampling

If the number of requests is small, review every one. If it is large, sample by amount, client, approver, and request type. Include both approved and rejected requests so the study does not reflect only the ones that passed. Draw the sample before reviewing the evidence to avoid selecting the most obvious gaps.

Report the sampling frame and the number of requests in each stratum. Track pending requests separately because their evidence may still be assembled. Do not drop them, since a pending request with no basis is a live risk. The sample should let the firm estimate the share of all requests with a complete basis.

Coding completeness

Code the primary evidence type: client guideline, client email, contract term, client call note, internal quality review, or none. Add a secondary code when more than one type applies. The primary code should point to the fix, such as a guideline summary or a call-note template. The coding should not reward a long narrative that lacks a source.

Have a second reviewer score a sample and compare the results. Resolve disagreements by reading the source and the request together. Report the agreement rate. If the reviewers cannot agree on what counts as complete, the standard is too vague and should be revised before continuing.

Analysis

Report the share of requests with complete, partial, and missing evidence. Break the results down by request type, amount band, and approver group. A high missing share for small requests may point to a threshold that skips documentation, while a high share for large requests is a more serious control gap. Show the count behind each rate.

Compare the evidence quality with the approval outcome. A request can be approved despite weak evidence if the approver knows the client, but that pattern should be visible. Report the share of approved requests with missing evidence. That measure shows where the control depends on individual knowledge rather than a record.

Reporting

Report the completeness rate, the amount represented, and the share of approved requests with missing evidence. Include examples of each evidence level, with client details removed. The report should let a reader see both the frequency and the financial exposure. Avoid presenting a single percentage without the categories behind it.

Present the findings to the billing manager, the finance approver, and a relationship partner. Ask which evidence type is easiest to require at submission and which gap causes the most rework. Set one change to the request template and a follow-up date. The report should improve the quality of the next request, not just describe the last one.

Limits and sources of error

The request file may not contain every client communication, especially when the basis was discussed in a meeting. A missing document is not proof that no basis exists, but it is still a documentation gap. Report the share of requests where the reviewer had to ask for evidence. That share is a useful signal of how often the file is incomplete.

Approvers may apply judgment that is not captured in the request, so the study can understate the evidence available in practice. Interview a small sample of approvers to understand what they relied on. Label that information as supplemental rather than treating it as a written basis. The study measures the record, not the private knowledge of the approver.

Privacy and retention

Store the request sample and the evidence links in a controlled finance folder. Remove client names and matter details from the analysis file when they are not needed. If an example is shared, redact the client and the amount. Follow the firm's records policy for the retention period.

Limit access to the study team, the billing manager, and the finance approver. Do not circulate a requester-level list outside the management context. Aggregate the results before sharing them more broadly. The same rule applies to any client communication quoted in the report.

Applying the result

If missing evidence concentrates in one request type, add a required source field to that template. If it concentrates in small requests, decide whether a simplified documentation rule is appropriate and record the risk. If approved requests often lack evidence, add a pre-approval check that the source is attached. The fix should match the gap that the data shows.

Test the change on the next group of requests and compare the completeness rate and the approval rework with the baseline. A higher completeness rate with no increase in approval time is a clear gain. Record the result and set a review date. The goal is a request file that supports the decision without slowing it down.

Review cadence

Repeat the study quarterly while the request template is being revised, then move to a semiannual cycle. Keep the evidence levels and the request unit stable so the completeness comparison is valid. Report approved requests with missing evidence separately from rejected requests. A change in the approval threshold should be noted beside the rate.

Review the findings with the finance approver, the billing manager, and a relationship partner. Ask which evidence type is easiest to require at submission and which gap causes the most rework. Set one template change and a follow-up date. The next review should check whether completeness improved without slowing approvals.

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. U.S. Government Accountability Office Green Book
  2. American Bar Association Model Rules of Professional Conduct
  3. Internal Revenue Service recordkeeping guidance
  4. Legal Electronic Data Exchange Standard
  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