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 billing setup errors originate in the new matter intake process. The unit is a setup error, defined as a missing or incorrect billing field discovered after the matter is opened. The purpose is to find the step where the error could have been prevented, not to assign blame to the person who happened to open the matter. The result should point to a specific intake control.
Scope the study to matters opened in a defined period and to the billing fields the firm requires at intake. Include rates, client guidelines, billing contacts, e-billing enrollment, matter identifiers, budgets, and trust arrangements. Exclude errors caused by a later client change unless the change was known at intake. State the matter types and the intake channels included.
Defining a setup error
A setup error exists when a required billing field is missing, inconsistent with the source document, or attached to the wrong matter. The error must be discoverable from a source record, not just from a disagreement between people. Record the field, the expected value, the actual value, and the source that proves the expectation. A field that was never required is not an error.
Distinguish a setup error from a data entry typo that has no billing effect. A wrong phone number in a contact field may be minor, while a wrong billing entity can delay an entire invoice. Classify errors by their operational consequence as well as their origin. The consequence helps the firm decide which fixes matter most.
Intake stages
Map the intake process into stages: client request, conflicts and engagement, matter opening, billing setup, e-billing enrollment, and first prebill. Assign each required field to the stage where it should be captured. A field with no assigned stage is a design gap, not a training problem. The map becomes the frame for coding the origin.
Include the handoffs between stages, because many errors occur when a field is known in one conversation but not transferred to the system. Record who owns each handoff and what evidence confirms the transfer. The intake map should be simple enough to compare across matters. If the process varies by practice group, map the variation explicitly.
Evidence sources
Use the engagement letter, the client guideline document, the rate card, the e-billing enrollment record, and the matter opening form as primary evidence. Compare the source with the field in the billing system. Record the date the source was received and the date the field was entered. The gap between the two is part of the error history.
If the source was a conversation, record the date, the participants, and the note that captured the instruction. A missing source is itself a finding, because it means the field cannot be verified. Do not treat a field as correct just because no one has complained. The evidence standard should be the same for every matter in the sample.
Sampling
Sample matters across practice groups, intake channels, and matter sizes. Include matters opened by different staff members so the sample is not concentrated in one person's work. Draw the sample before reviewing the errors to avoid selecting only the matters known to be problematic. Record the sampling frame and the number of matters in each stratum.
For a small firm, review every matter opened in the period. Extend the period rather than reducing the evidence standard. Track matters that were still being set up at the end of the window and report them separately. A matter that has not reached first prebill may not yet reveal its errors.
Coding the origin
Code the stage where the field should have been captured, the stage where it was actually captured, and the stage where the error was discovered. Use a short list of stages and a separate code for no assigned stage. The three-part code shows whether the problem is a missing step, a skipped step, or a late detection. That distinction is more useful than a single label.
Add a cause code for the mechanism, such as source not received, source not read, field not available, handoff missed, or system limitation. Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the evidence. If the codes are too broad, split the one that causes the most disagreement.
Analysis
Report the error rate by field, origin stage, and matter type. Identify the fields with the highest error rate and the stages where the most errors should have been caught. A field that is consistently missing at the same stage points to a process design issue. A field that is entered correctly but later overwritten points to a system or handoff issue.
Calculate the share of errors discovered at first prebill, because late discovery is the most expensive. Compare the error rate for matters opened with a checklist against those opened without one. Report the count behind each rate. The analysis should show where a control would have the greatest effect.
Reporting
Report the overall setup error rate, the field-level results, and the origin-stage results. Include the share of errors that reached the first prebill and the share that caused a client-facing delay. Show the number of matters in the sample. The report should separate frequency from consequence.
Present the findings to the intake owner, the billing manager, and the practice group lead. Ask which stage is easiest to change and which error causes the most rework. Set one control change and a follow-up date. A report that does not lead to a change is just another audit.
Limits and sources of error
The source documents may be incomplete, especially when a client provides information in a call or a meeting. A missing source does not prove that the field was never known. Report the completeness of the evidence before drawing conclusions. Name the owner of each source and the system where it should be stored.
Matters differ in complexity and client requirements, so a raw error rate can reflect the mix rather than the process. Report the context beside the rate and avoid comparing practice groups without adjusting for scope. The study is about intake design, not individual performance. Keep the limitations visible.
Privacy and retention
Store the sample and the source evidence in a controlled folder. Remove client names 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. Follow the firm's records policy for the retention period.
Limit access to the study team and the intake owner. Do not circulate a list of errors by staff member outside the management context. Aggregate the results before sharing them more broadly. The same privacy rule applies to any screenshots of the matter system.
Applying the result
If most errors originate at matter opening, add the missing fields to the opening form and require a source link for each. If they originate at the handoff to billing, add a confirmation step with a named owner. If they are discovered only at prebill, add a setup check before the first time entry. The fix should match the origin stage.
Test the change on the next group of matters and compare the error rate and the late-discovery share with the baseline. A lower late-discovery share is the most valuable result because it prevents client-facing delays. Record the result and set a review date. The intake process should improve with each cycle.
Review cadence
Repeat the study before each intake form change and at least annually. Keep the stage map and the error definition stable so the origin comparison remains valid. If a practice group changes its intake process, map that variation before combining the results. A current stage map is essential for interpreting where the errors originate.
Review the findings with the intake owner, the billing manager, and the practice group lead. Ask which stage is easiest to change and which error causes the most client-facing delay. Set one control change and a follow-up date. The next review should check whether late discovery fell, not just whether the total error count moved.
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


