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 where matter record updates wait before a billing close and how long they remain in each waiting state. A stall can occur when a request is sent to a matter team, when a partner approval is pending, or when a system field cannot be edited by the person who found the gap. The question is about the handoff, not about the speed of any individual. The result should show which waiting states consume the most calendar time.
Define the matter population, the billing period, and the record fields included in the review. A close may involve client entity changes, rate updates, timekeeper assignments, billing contacts, and matter status changes. Include only fields that affect the close or the invoice, and state that boundary. A broad data-quality review would produce a different and less actionable result.
Unit of analysis
Use one update request as the unit, from the date the gap is identified to the date the field is corrected or formally deferred. If a request contains several fields, record each field separately when they have different owners or waiting states. A combined request can hide the one field that delayed the close. Link the fields to the same request identifier so the relationship is preserved.
Record the source of the request, the current value, the requested value, and the evidence for the change. A vague request such as fix the matter record cannot be aged or routed. The unit should show what was needed, who was asked, and what happened next. This structure supports both the measurement and the correction workflow.
Defining the waiting states
List the possible states in the handoff: identified, assigned, awaiting evidence, awaiting approval, ready to update, updated, and deferred. Define each state with an observable event and a timestamp. A request is awaiting evidence when the owner has asked for a document, not when the requester is still gathering it. Clear state definitions make the stall visible without relying on a narrative.
Separate a wait caused by missing information from a wait caused by missing authority. The first may be resolved by a document, while the second needs a person who can approve the change. A request that sits in the wrong state will be routed to the wrong remedy. The state list should be short enough to apply consistently and specific enough to guide action.
Evidence standard
Every state change should have a date, a person or system, and a short note that explains the transition. An email request with no response is evidence of a wait, but it is not evidence that the owner accepted the request. Record the channel and the recipient when the request is sent. If the owner responds in a meeting, add the note the same day.
Keep the source for the corrected value, such as the engagement letter, the client message, or the approved rate notice. A field changed without a source may be correct, but the next reviewer cannot tell. Mark a deferred request with the reason and the person who accepted the deferral. An unexplained deferral is a stall that has simply been renamed.
Sampling and collection
Collect update requests from several billing cycles so the sample includes ordinary and peak periods. A single close may be dominated by a holiday, a system outage, or one large client. If the volume is large, stratify by field, matter type, and requesting role. Include requests that were never resolved, because those are often the longest stalls.
Record the collection window and the source systems used to reconstruct each request. If a request moved through a channel that is not retained, note the evidence gap. Do not infer a state from the absence of a message unless the channel is known to be complete. A clear collection note helps a later reviewer judge the result.
Measuring stall time
Calculate the calendar time in each state and the total time from identification to correction or deferral. Report the median and the longest cases, with the number of requests in each state. Calendar time is the right measure for a close because the invoice waits on the calendar, not on the effort spent. A request that required ten minutes of work but waited five days is still a five-day stall.
Separate business days from weekends and holidays if the billing calendar treats them differently. State the rule and apply it consistently. A long wait that spans a holiday may look different from a long wait in an ordinary week. The report should show enough detail for the owner to judge whether the delay was structural or seasonal.
Analysis and reporting
Report the request count, the resolved count, the deferred count, and the median time in each waiting state. Identify the state that contributes most to the total delay and the field that appears most often. A chart of average time by state can help, but the raw counts should remain visible. The owner needs to know where to intervene, not only that the process is slow.
State the action implied by the leading stall. A wait for approval may call for a named backup, while a wait for evidence may call for a matter-opening checklist. A system permission problem may need an access change rather than a new policy. Give the owner one decision and one test for the next close. A report with many recommendations is less likely to produce a change.
Limits and sources of error
The record of a request may be incomplete, especially when people coordinate in meetings or hallway conversations. A request that was never logged cannot be measured, and a request logged late may appear faster than it was. Different fields may have different owners and different evidence standards. The report should state these limits and avoid treating the measured states as the whole process.
The cited public sources frame recordkeeping, privacy, and internal control practice; they do not provide a stall time for the firm. The protocol measures the observed requests, not the quality of the underlying matter record. Use the result to improve the handoff and the evidence standard, not to assign blame. A stalled request is usually a system problem before it is a person problem.
System permissions and access
Map who can edit each field and which role can approve a change. A request that waits because the requester lacks permission is a different problem from a request that waits for a decision. Record the permission gap and route it to the system owner rather than asking the matter team to work around it. Shared logins may solve the immediate task while destroying the audit trail.
When a permission change is needed, state the field, the role, and the reason in the request. Ask for an audit trail that records the user and the date of each change. A permission fix that cannot be audited may create a new control problem. Review access after the close to confirm the change did not widen beyond the intended role.
Testing a handoff fix
Pilot one handoff change on a single billing close, such as a named backup approver or a required field at matter opening. Compare the stall time and the evidence quality against the prior close. A faster handoff that produces an unsupported field is not an improvement. Ask the reviewer who receives the record whether the change made the correction easier to verify.
Keep the pilot limited until the result is clear. If the fix works, document the new step and update the matter-opening checklist. If it does not, record why before trying another change. The measurement should end with a decision about the handoff, not only a description of the delay. A second close gives a better signal than a single busy week.
Review cadence
Repeat the measurement after a close, an access change, or a new matter-opening process. Compare the same states and fields so the movement is interpretable. Set a review date and name the operations owner who will act. A one-time review can identify a stall, but only a repeat can show whether the fix held. Keep the prior state definitions so a change in the measure is not mistaken for a change in the process.
Choose one handoff improvement and test it in the next cycle. The improvement might be a named backup approver, a required field at matter opening, or a shared evidence folder. Keep the state definitions and the sample notes together so the next reviewer can repeat the method. The measure is useful when it shortens the wait without weakening the record.
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


