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 much invoice review time goes to resolving disbursement questions. The unit is a reviewer handling event, and the purpose is to measure the active minutes per disbursement question without turning the result into a performance judgment. The study is limited to every invoice review session in the period and uses the definitions the firm already maintains. A disbursement question can take two minutes to answer and twenty minutes to find, so the study should separate search from decision.
Scope the study to the invoices reviewed by the billing team during the period. Include the cases that were approved, rejected, and still open so the denominator reflects the full workload. Exclude records that do not meet the event definition, and keep the exclusion list with the study file. State the period, the systems, and the owner so the result is not generalized beyond the sample.
Defining the event
Define a disbursement question before collecting any data. The definition should say what counts, what does not, and which source proves the event occurred. Write two examples and one boundary case so two reviewers apply the same rule. A handling event starts when the reviewer opens the cost line and ends when the line is approved, corrected, or escalated.
Distinguish a disbursement question from a related but different case. A follow-up, a correction, and a duplicate can look similar in the queue but point to different fixes. Code the related cases separately rather than forcing them into the main category. The separation keeps the report honest about what was measured.
Population and denominator
The population is every invoice review session in the period. Report the number of records in the population, the number excluded, and the number in the final sample. Track the records that arrive late so the study does not silently drop them. The population is the review session, because one invoice may contain several cost questions that are handled at different times.
Use one consistent unit for the denominator. Count a reviewer handling event rather than messages, lines, or people unless the study is explicitly about that unit. If a record contains several events, split it or state that it is treated as one. Consistency matters more than precision when the source data is imperfect.
Evidence sources
Use the invoice cost line, the vendor receipt, and the client authorization as the primary evidence. Compare the source with the field in the billing and accounting systems and record the date each was observed. If the review time log is missing, mark the record incomplete instead of inferring the value. The invoice line, the receipt, the authorization, and the time log should share one case reference.
Keep a short evidence hierarchy so reviewers know what to trust first for disbursement review time. A signed client document is stronger than a summary written by the person who handled the case. A contemporaneous note is stronger than a later recollection, and the report should say which was used. Record the evidence type so the analysis can separate a documentation problem from a process problem.
Sampling
Sample across the groups that could change the result. Include different clients, matter types, staff members, and volume bands where the data allows. Draw the sample before reading the outcomes so the selection is not biased toward the obvious cases. Sample across cost types and reviewers so a single unusual vendor does not distort the average.
If the population is small, review every record and extend the period rather than lowering the evidence standard for disbursement review time. Track the records that are still open at the end of the window and report them separately. Do not drop an inconvenient case without a documented exclusion reason. A reproducible sample is more useful than a large one with unclear boundaries.
Coding the record
Use a short code list that points to a specific repair. Code the primary cause, the stage where it was discovered, and any secondary factor that changed the outcome. Add an unknown category for cases the evidence cannot resolve. Code the question type as missing receipt, unclear authorization, wrong matter, tax issue, duplicate, or other.
Have a second reviewer code a sample of a disbursement question and compare the results. Resolve disagreements by returning to the source rather than by majority vote. Report the agreement rate and revise any code that is used inconsistently. If the reviewers cannot agree on the definition, stop and fix the definition before continuing.
Measuring time
Measure the active time or the elapsed time that matches the question. Use a short log completed at the moment of the work, and separate search, decision, and communication time for a disbursement question. Report the median and the range rather than a single average. Measure active minutes in categories and report the median and range rather than a single total.
Do not convert time to a dollar figure without an approved labor rate for disbursement review time. The study measures effort and delay, not price, unless the firm has explicitly asked for a cost estimate. Keep the raw time entries with the analysis file so a reviewer can check the calculation. A precise number built on rounded guesses is less useful than a range with a clear source.
Analysis and reporting
Report the overall rate, the group results, and the number behind each figure. Show the share that reached a client-facing stage, because late discovery usually costs more than early detection. Compare only groups with similar scope and duration. Report the share of review time spent on disbursement questions beside the number of invoices and cost lines reviewed.
Give the reader one table or chart that answers the main question about disbursement review time and put the detail in an appendix. Write the finding in plain language before presenting the technical definition. Include the cases that contradict the main 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
Source records are often incomplete, and a missing record is not proof that the event did not happen. Report the completeness of the evidence before drawing a conclusion, and name the owner of each source. Small samples, changing guidelines, and reviewer disagreement can all limit interpretation. Self-reported time can be rounded, so pair the log with a small observation sample and report the estimate.
Avoid comparing groups that differ in complexity or client requirements for disbursement review time. A long matter has more opportunity for an event, and a fixed-fee matter may have none by design. Describe the context beside the rate and avoid ranking individuals. The purpose is to improve the process, not to judge professional worth.
Privacy and retention
Store the sample and the evidence 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 vendor and client details out of the analysis file and redact amounts when an example is shared.
Do not circulate a person-level or client-level list about disbursement review time 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 cause in the data. If the gap is a missing field, add it to the template; if it is a late approval, add a named owner and a deadline. Test the change on a defined group and compare the same measures with the baseline for disbursement review time. If search time dominates, fix the filing convention; if decision time dominates, clarify who can approve the cost.
A lower rate is not the only useful result for disbursement review time. Faster detection, clearer evidence, and fewer repeated questions can all improve the process even when the count stays similar. Report both the direct result and the service result, and keep the definitions stable. Stop the change if it shifts the work into a private channel where it cannot be reviewed.
Review cadence
Repeat the study on each invoice cycle and after any major change to the template, system, or client requirement. Keep the definitions and the unit stable so the comparison is meaningful. Report the records that were excluded or still open beside the main rate. Review the time study after each invoice cycle and keep the categories stable for comparison.
Review the result with billing manager and the people who maintain the record for disbursement review time. 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 study 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


