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 completely a write-down approval can be reconstructed from the records the firm retains. The test is whether an independent reviewer can identify the adjustment, the reason, the approver, the date, and the evidence without asking the original preparer. A complete trail does not prove that the decision was wise, but an incomplete trail makes the decision impossible to review. The question is about evidence, not about the merits of any particular write-down.
Define the write-down population, the billing period, and the approval levels included in the review. Include adjustments that were proposed but not approved, because a missing denial record can hide an unresolved request. State whether the review covers individual invoice lines, whole invoices, or both. The scope should also name the systems searched for evidence.
Unit of analysis
Use one write-down decision as the unit, from the request to the final disposition. If one request covers several invoices, record each invoice as a linked item under the same decision. If the approver changes the requested amount, record the proposal and the final amount separately. This structure preserves the decision history instead of reducing it to a single number.
Record the matter, the client, the amount, the reason code, the preparer, and the approver. Link the decision to the prebill or invoice record that contains the adjustment. A decision that cannot be linked to a billing record cannot be tested against the actual charge. The unit should be specific enough to support both the review and a later audit.
Defining completeness
A complete evidence trail has five elements: the proposed adjustment, the reason, the supporting source, the approver, and the date. It should also show the final amount if it differs from the proposal, and any condition attached to the approval. Missing any of the first five makes the decision incomplete for review. Additional elements can be useful, but they should not substitute for the core five.
Distinguish a complete trail from a persuasive narrative. A well-written explanation without the client guideline or the time entry is still incomplete. A short note with the right evidence can be complete. The protocol should score the elements rather than judge the prose. This keeps the result consistent across reviewers with different writing styles. A confident explanation is not a substitute for a dated source.
Evidence standard
The supporting source should be the document that establishes the basis for the adjustment, such as the client guideline, the engagement letter, a written client approval, or the time entry that contains the error. Record the source location and the date observed. If the source is a conversation, record who said what and when, and mark it as a conversation rather than a document. The reviewer should be able to find the same source again.
Keep the evidence in an approved system with access controls that match the sensitivity of the matter. Do not store client-confidential material in a personal inbox or an unmanaged desktop folder. If the evidence includes privileged content, limit the review to the people who need it. A complete trail that is not secure is not a control.
Sampling and collection
Collect decisions from several billing cycles and include both approved and denied requests. A sample of only approved write-downs will miss the requests that stalled or were resolved informally. If the population is large, stratify by amount, reason code, and approver. Include at least one decision that changed amount after review, because those are often the most revealing.
Record the collection window, the systems searched, and the number of decisions for which no record was found. A missing record is a finding, not an exclusion. If a decision was handled entirely in conversation, note the evidence gap and the person who can confirm it. The report should distinguish a missing file from a decision that was never made.
Scoring the trail
Score each decision on the five core elements and report the number of complete, partial, and missing trails. A partial trail has at least one core element but lacks another, while a missing trail has no identifiable approval record. Show the element-level counts so the owner can see whether the problem is the reason, the source, or the approver. A single completeness percentage hides which element needs repair.
Have a second reviewer score a small overlap sample and compare the results. Disagreement may mean the element definitions are unclear or the evidence is ambiguous. Resolve the definition before scoring the rest of the population. Record the codebook version so a later comparison uses the same standard. If the overlap sample is small, report the raw disagreements instead of a precise agreement rate.
Analysis and reporting
Report the decision count, the complete count, the partial count, the missing count, and the element-level gaps. Break the result down by reason code and approver role where the numbers allow. Avoid naming individual preparers in a report that is shared beyond the control owner. The purpose is to improve the trail, not to create a performance ranking.
State the action implied by the leading gap. A missing source may call for a required attachment in the request form. A missing approver may call for a named approval step in the workflow. A missing date may call for an automatic timestamp. Give the owner a specific change and a date to test it in the next cycle.
Limits and sources of error
The review can only see the records that were retained, and a missing record may reflect a retention practice rather than a missing decision. The five core elements are a minimum standard, not a full account of the client relationship. Reviewers may disagree about whether a conversation counts as sufficient evidence. Small samples produce unstable completeness rates, especially when one approver dominates the population.
The cited public sources frame recordkeeping, privacy, and internal control practice; they do not provide a completeness result for the firm. The protocol measures the evidence trail, not the fairness or propriety of the adjustment. Use the result to strengthen documentation and routing, not to second-guess a decision without its context. A complete trail is a condition for review, not a substitute for judgment.
Sampling the decision context
Read a small number of complete decisions in full before scoring the larger sample. The context shows whether the recorded reason matches the actual issue and whether the approver had the information needed. A trail can be complete on paper while the evidence supports a different decision. Use the reading to refine the element definitions, not to replace the scoring.
Separate a documentation gap from a disagreement about the decision. A missing source is a documentation gap, while a source that supports a different conclusion is a judgment question for the approver. Keep the two findings separate so the report does not imply misconduct where the record is merely incomplete. The owner can then choose the right remedy.
Testing a documentation fix
Add one required element to the request form, such as the source location or the approver role, and pilot it on the next cycle. Compare the completeness score and the review time before and after the change. A form that adds fields without improving the trail may simply move the gap. Ask the approver whether the new field made the decision easier to review.
Keep the old form and the new form available during the pilot so the comparison is fair. Document the change date and the person who approved it. If the fix works, update the scoring guide and the training material. If it does not, remove the field rather than preserving a control that produces no evidence.
Review cadence
Repeat the review after a change to the request form, the approval workflow, or the retention system. Compare the same elements and reason codes so the movement is meaningful. Set a review date and name the billing manager or finance owner who will act. A one-time completeness check can identify a gap, but a repeat shows whether the fix lasted.
Choose one improvement and test it in the next sample. The improvement might be a required source field, a named approver, or a same-day timestamp. Keep the scoring guide, the sample list, and the open questions together for the next reviewer. The goal is a trail that lets an independent person reconstruct the decision without relying on memory.
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


