Home / Research / Matter records

How much do billing contacts change during a matter lifecycle?

A contact-churn protocol that counts billing role changes from matter opening to close and reports their effect on escalation and approval paths.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How much do billing contacts change during a matter lifecycle?
Table of contents

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 often the billing contacts on a matter change between opening and closing. The unit is a role change event, not a person, because a matter can have several billing roles with different stability. The purpose is to understand how often the escalation path depends on an outdated record. The result describes the record, not the performance of any individual contact.

Scope the study to matters opened and closed within a defined period, or to open matters observed for the same length of time. Include client billing contacts, firm billing owners, and approvers named in the matter record. Exclude contacts who were never assigned a billing role. State the observation window and the matter types included.

Defining a contact change

A contact change occurs when the person or role named for a billing function changes, or when a named contact leaves and no replacement is recorded. Distinguish a substitution from a reassignment: a substitution keeps the same role and authority, while a reassignment changes the scope. Both affect the record, but they have different implications for approval. Report the two event types separately so the churn rate does not combine a name change with a scope change.

Count a change only when the matter record or the controlled contact sheet is updated or should have been updated. A new name in an email signature is not a record change. The evidence standard should require a dated source. A change that is known only through conversation should be coded as undocumented. Record the authority level with each role so a contact change can be separated from an authority change.

Roles to track

Track the roles that actually appear in the billing workflow: client billing coordinator, client accounts payable contact, firm billing owner, responsible attorney, rate approver, and guideline interpreter. Some matters will not have every role. Record whether the role was absent, unfilled, or filled by a named person. Absence is different from churn and should not be counted as a change.

Define the authority attached to each role at the start of the study. If the authority changes without a person change, record that as a separate authority event. A new coordinator with the same approval limit is a contact change, while the same coordinator with a new limit is an authority change. Keeping them separate makes the analysis more useful.

Evidence and collection

Use the matter record, the contact sheet, and the client's written notices as the primary sources. Record the effective date of each change and the date the firm updated its record. The gap between the two is a useful measure of record lag. If the change was never recorded, mark it as a missing update rather than dropping it.

Collect the data at matter opening and at defined milestones, such as a major staffing change, a rate review, or closing. A single end-of-matter review may miss changes that were corrected before closing. The milestone approach captures the state the reviewer actually saw. Keep the collection dates so the timeline is clear. Note the source of the update, such as a client notice or a system change, beside the effective date.

Measuring churn

Calculate the number of role changes per matter and the share of matters with at least one change. Report the median time between changes and the share of changes with a gap before the record was updated. A simple count without the timing does not show the operational effect. Report the number of matters with no contact change as well as the number with several.

Compare churn by matter duration, client, and matter type. Longer matters have more opportunity for change, so report changes per year as a secondary measure. A high-churn client may need a standing contact review, while a low-churn client may need only a closing check. The comparison should be descriptive, not a rating of the client relationship.

Analysis and reporting

Report the roles with the highest change rate and the roles with the longest update lag. A frequently changing coordinator role may need a shared mailbox rather than a named person. A slow-updating approver role may need a system prompt at the point of prebill release. The role-level view points to a specific control. Include the share of matters where the record was updated after a billing question had already occurred.

Show the share of matters where the recorded contact was wrong at the time of a billing question. This is the operational consequence measure, and it may be more persuasive than the raw churn rate. If the study cannot observe actual questions, report the share of records that were stale at a milestone instead. Label the measure accurately.

Limits and sources of error

The matter record may be incomplete, especially for client-side contacts who are not regular correspondents. A missing contact is not proof that no contact existed. Report the completeness of the source before drawing conclusions. A study based only on the firm's record may undercount client changes. Name the owner of each contact update and the system where the change is recorded.

Matter duration and client size can confound the comparison. A large client with a procurement function may change contacts more often than a small client with a single relationship partner. Report the context beside the rate and avoid ranking clients on churn alone. The purpose is to improve the record, not to evaluate the client.

Retention and privacy

Store the contact history in the controlled matter record and keep the study file separate from the live sheet. Remove personal contact details from the analysis file. If a report includes a role change, use the role rather than the person's name. Follow the firm's privacy policy for client and employee data. Record the matter duration and the number of billing cycles observed for each matter.

Do not circulate a list of departed contacts outside the team that needs it for continuity. Keep the historical record available for billing questions but restrict access. A contact history is useful evidence and also sensitive personal information. Handle it with the same care as the matter record. Record the access rule that governs the historical list in the same note.

Applying the result

If client-side roles change often, add a shared billing mailbox and a named firm owner who maintains the relationship. If firm-side roles change, add the contact review to the matter transition checklist. If the update lag is the main problem, trigger a review at the milestones where changes are known to occur. The response should match the role and the timing. State the completeness rate of the matter record beside the churn result.

Test the change by measuring the share of stale records at the next milestone. A drop in stale records is the direct result; a drop in escalations sent to the wrong person is the operational result. Report both if the data allows. The study should improve the escalation path, not just describe it. Use role labels in the group report and keep names in the controlled study file, then remove the names from any shared extract.

Review cadence

Repeat the study annually and after a major client or firm reorganization. Keep the role definitions stable so the comparison is valid. If a new role is added, report it separately for the first period. A churn measure that changes its categories every cycle cannot show a trend. Record the role definitions with the result so a later study uses the same categories.

Review the findings with the billing manager and the matter administration lead. Ask which role causes the most rework and which update trigger is easiest to add. Set one change and a follow-up date. The cadence should be tied to the operating decisions the measure supports. Write the next review date in the matter team's calendar before the meeting ends.

Reporting the result to the matter team

Present the role-level result to the matter team with the update lag and the stale-record share beside the churn count. The team needs to see which role causes the most rework, not just how many contacts changed. Use role labels in the group view and keep names in the controlled file. A short table is easier to act on than a long narrative.

Ask the team which milestone would have caught the most changes and add that trigger to the matter checklist. Test the trigger on the next group of matters and compare the stale-record share. Record the change and the owner in the study file. The result should improve the escalation path in a way the team can verify.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. NIST Privacy Framework
  2. NIST Cybersecurity Framework
  3. U.S. Government Accountability Office Green Book
  4. American Bar Association Model Rules of Professional Conduct
  5. Federal Trade Commission data security guidance
  6. United States Department of Labor work hours guidance

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