Home / Research / Write-offs

How consistently are write-down approval limits applied across billing managers?

A control study that compares the written authority, the applied approval level, and the recorded reason for adjustments of the same size.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How consistently are write-down approval limits applied across billing managers?
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 how consistently write-down approval limits are applied across billing managers. The unit is an approved adjustment, and the measure is whether the approver's authority, the recorded reason, and the supporting evidence match the written policy for that amount. The study covers adjustments on invoices issued during the period. It does not evaluate whether the adjustment was commercially wise.

Scope the study to billing managers who approved at least one adjustment during the period and to adjustments above the firm's documentation threshold. Include adjustments that were later reversed or corrected so the denominator reflects real decisions. Exclude adjustments below the threshold and record the number excluded. State the policy version, the approval system, and the owner of the analysis.

Defining the event

Define an adjustment as any reduction to a billed amount, including a write-down, a write-off, a courtesy credit, and an error correction. The approval limit is the maximum amount a named role may approve without escalation. The applied approver is the person whose name appears on the approval record. A verbal approval that was never recorded counts as undocumented for this study.

Distinguish a split adjustment from a single adjustment. Splitting a large reduction into smaller entries to stay inside a limit is a control failure, not a series of routine decisions. Code the split separately and record the total amount. A legitimate partial credit on separate invoices should not be coded as a split when the client requested it that way.

Population and denominator

The population is every adjustment above the documentation threshold on an included invoice. Report the number of managers, the number of adjustments, the number excluded, and the number in the final sample. If one invoice received several adjustments, count each one separately or state the rule used. Keep the unit stable across periods so the consistency rate is comparable.

Report the share of adjustments approved inside the limit, above the limit with an escalation, above the limit without an escalation, and with no recorded approver. Also report the median amount by manager group. A high share inside the limit can still hide a split, so report the count of split cases beside the rate. Report the share of adjustments with a completed evidence package as a separate measure.

Evidence sources

Use the approval record, the delegation schedule, the invoice history, and the client correspondence as the primary evidence. Compare the approver and the amount with the limit in force on the approval date. Record the date each source was observed and the policy version. If the approval record is missing, mark the adjustment as undocumented rather than inferring authority from the title.

Rank the sources so reviewers know what to trust first. A signed approval record is stronger than an email, and a dated delegation schedule is stronger than a current org chart. A client request is stronger than an internal assumption about why the adjustment was made. Record the evidence type for each adjustment.

Sampling

Sample across managers, offices, and adjustment sizes so one large credit does not define the result. Include adjustments near the limit, because that is where interpretation differs most. Draw the sample before reading the outcome so the selection is not biased toward the suspicious cases. If the population is small, review every adjustment and extend the period.

Stratify the sample by whether the adjustment was a courtesy credit or an error correction. A courtesy credit may follow a different approval path from a correction. Report the consistency rate for each stratum rather than pooling them. The reader should be able to see whether the policy or the practice explains the difference.

Coding the record

Use a short code list that points to a specific repair. Code each adjustment as inside limit, escalated, not escalated, split, or undocumented, and record the reason category. Add the approver role, the amount, and the policy version. Keep the code list short enough that two reviewers can apply it consistently.

Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the delegation schedule and the approval record, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on which policy version applied, stop and fix the timeline before continuing.

Measuring the variable

Measure the consistency rate by adjustment and by manager group. Report the median and the range for the adjustment amount so a few large cases are visible. Measure the share of adjustments with a complete reason and evidence package. Keep the raw counts with the analysis file so a reviewer can check the calculation.

Do not convert the adjustments to a realization figure without the approved fee and collection data. The study measures approval consistency, not profitability. If the firm wants a realization view, run it as a separate analysis with the finance owner. A precise percentage built on incomplete records is less useful than a clear exception count.

Analysis and reporting

Report the overall consistency rate, the exception count by type, and the number of adjustments behind each figure. Show the results by manager group and by adjustment size. Compare only groups with the same policy version and approval system. Include the adjustments that followed the policy so the report shows the full distribution.

Give the reader one table that answers the main question and put the coding detail in an appendix. Write the finding in plain language before presenting the technical definition. Include the cases that contradict the pattern rather than hiding them in an average. A report that cannot be acted on is just another record of the past.

Limits and sources of error

A missing approval record is not proof that no approval occurred, and a recorded approval is not proof that the authority was valid. Report the completeness of the evidence before drawing a conclusion. Small samples, mid-period policy changes, and reviewer disagreement can all limit interpretation. A manager who inherited a decision may appear inconsistent through no fault of their own.

Avoid comparing managers who handle different client relationships or matter types. A manager with many long-standing clients may see more courtesy adjustments than one with new clients. Describe the context beside the rate and avoid ranking individual managers. The purpose is to clarify the policy, not to judge professional worth.

Privacy and retention

Store the approval records, delegation schedules, and invoice histories in a controlled folder with access limited to the study team. Remove manager names, client names, and specific amounts from the analysis file when they are not needed. If an example is shared, use a role label and redact the client and the amount. Keep the unredacted evidence separate from the working analysis.

Do not circulate a manager-level list about approval consistency outside the management context. Aggregate the results before sharing them more broadly, and check that a small group cannot be re-identified. The same rule applies to screenshots of the approval system and to quoted messages. Privacy is part of the method, not an afterthought added at the end.

Applying the result

Choose one change that matches the most common exception. If the limit is unclear, rewrite it with examples at the boundary. If splits dominate, add a check for multiple adjustments on the same invoice. If the approval record is missing, make the field required before the invoice can be released. Test the change on one manager group.

A higher consistency rate is not the only useful outcome. Faster approvals and clearer client conversations can improve the process even when the rate stays similar. Report the direct result and the service result separately. Stop the change if it adds a step that the team works around instead of using.

Review cadence

Repeat the study each quarter and after any change to the delegation schedule or the approval system. Keep the definitions and the unit stable so periods can be compared. Report the adjustments that were excluded or still open beside the main rate. Review the coding guide after the first repetition and keep the changes visible.

Review the result with the billing manager and the finance owner, not only with the approvers. Ask which fix is easiest to sustain and which exception creates the most rework. Set one change and a follow-up date, then check whether the change held. The next study should test the repair, not just repeat the same count.

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. U.S. Bureau of Labor Statistics
  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