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 complete the audit trail is for time that was written off before or after billing. The unit is a written-off time entry or a write-off decision line, and the measure is whether the record contains the reason, the approver, the client basis, the amount, and the final outcome. The study looks at the documentation, not at whether the write-off was commercially wise. It does not attempt to reconstruct a decision that was never recorded.
Scope the study to matters with a write-off posted during the period. Include write-offs made at prebill, at invoice review, and after a client dispute. Exclude corrections that were purely clerical, such as a duplicate entry reversal, and record the number excluded. State the billing system, the approval policy, and the owner of the analysis.
Defining the event
Define a complete write-off record as one that links the amount, the affected time entries, the reason, the approver, and the client or matter basis. A note that says only courtesy or client request is not complete for this study. A complete record should let a reviewer understand what was reduced and why without interviewing the person who approved it. Write two examples and one boundary case before coding.
Distinguish a write-off from a write-down, a credit, and a fee adjustment. A write-off removes time that will not be billed, while a write-down reduces the rate or the amount on a billed line. Code the type separately because the approval path and the client communication differ. A blended category would hide which control failed.
Population and denominator
The population is every write-off decision posted in the period, counted at the decision-line level. Report the number of matters, the number of lines, the number excluded, and the number in the final sample. If one decision covers several time entries, state whether it is counted once or per entry. Use the same unit across periods so the completeness rate is comparable.
Report the share of write-off value covered by a complete record as well as the share of lines. A small number of large write-offs can carry most of the value, so a line count alone may overstate the quality of the trail. Keep both measures in the report. The value measure should use the posted amount, not a notional rate.
Evidence sources
Use the write-off approval, the billing system note, the client correspondence, and the invoice or credit memo as the primary evidence. Compare the posted amount with the time entries it covers and record the date each source was observed. If the approval is only in an email, record the email and the date rather than inferring the decision. The evidence log should let a second reviewer repeat the match.
Rank the sources so reviewers know what to trust first. A signed approval with a stated reason is stronger than a system note added later. A client email that explains the dispute is stronger than an internal summary of it. Record the evidence type for each line so the analysis can separate a documentation gap from a missing decision.
Sampling
Sample across matter types, approvers, and write-off sizes so one large matter does not define the result. Include write-offs with a client dispute, a prebill adjustment, and an internal quality decision. Draw the sample before reading the outcome so the selection is not biased toward the well-documented cases. If the population is small, review every line and extend the period.
Stratify the sample by whether the write-off was above or below the firm's approval threshold. A small adjustment may follow a lighter process by design, while a large one should carry a fuller record. Report the completeness rate for each stratum rather than pooling them. The reader should be able to see whether the policy is being followed at each level.
Coding the record
Use a short code list that points to a specific repair. Code each required field as present, partial, or missing, and record the write-off type. Add an unknown category for records the evidence cannot resolve. Code the reason category, such as client dispute, quality correction, relationship decision, scope confusion, or billing error, because the reason shapes the fix.
Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the approval and the client correspondence, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on what counts as a complete record, stop and fix the definition before continuing.
Measuring the variable
Measure the completeness rate by line, by value, and by required field. Report the median and the range for the amount behind each line so a few large write-offs are visible. Measure the time between the write-off decision and the invoice or credit memo, because a late record is harder to explain. Keep the raw counts with the analysis file so a reviewer can check the calculation.
Do not convert the written-off amount to a realization percentage without the approved fee and collection data. The study measures documentation, 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 data is less useful than a clear field-level gap count.
Analysis and reporting
Report the overall completeness rate, the field-level gaps, and the number of lines behind each figure. Show the share of value covered by a complete record and the most common reason category. Compare only groups with similar approval rules and matter types. Include the records that are complete 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 note is not proof that no reason existed, and a later summary is not proof that the reason was considered at the time. Report the completeness of the evidence before drawing a conclusion. Small samples, changing approval rules, and reviewer disagreement can all limit interpretation. A write-off approved in a meeting may have no system record even when the decision was sound.
Avoid comparing groups that differ in client sensitivity or approval authority. A relationship write-off may be deliberately documented in a narrower channel than a quality correction. Describe the context beside the rate and avoid ranking individual approvers. The purpose is to improve the trail, not to judge professional worth.
Privacy and retention
Store the approvals, client correspondence, and billing records in a controlled folder with access limited to the study team. Remove client names, amounts, and matter details from the analysis file when they are not needed. If an example is shared, use a role label and redact the client and the specific amount. Keep privileged material in a separate restricted location.
Do not circulate a client-level or approver-level list about write-offs 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 billing system and to quoted client 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 gap. If the reason field is weak, add a short required prompt with a small code list. If the approval is missing, route the write-off through the system rather than email. If the client basis is absent, add a link to the correspondence. Test the change on one approval level before applying it broadly.
A higher completeness rate is not the only useful outcome. Faster approvals, clearer client conversations, and fewer repeated write-offs can all improve the process even when the rate stays similar. Report the direct result and the service result separately. Stop the change if it turns the reason field into a longer free-text box that no one reads.
Review cadence
Repeat the audit each billing cycle and after any change to the approval policy, the billing system, or the client's fee arrangement. Keep the definitions and the unit stable so periods can be compared. Report the lines 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 preparer. Ask which fix is easiest to sustain and which gap causes the most rework. Set one change and a follow-up date, then check whether the change held. The next audit should test the repair, not just repeat the same count.
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


