Legal Services Offshore research · legal-support-governance

How often do client status updates omit the source of a date change?

A bounded method for checking whether client status updates name the record behind a changed date and separating a missing source from a changed plan.

Published · 4 sources

How often do client status updates omit the source of a date change? research illustration

Research context

This research brief is designed for legal operations planning. Use the findings to ask better workflow questions. Test any proposed process against the firm’s jurisdiction, professional duties, systems, and client commitments. Treat every local result as a starting point for review rather than a universal benchmark.

Question and scope

This study asks how often a client status update reports a changed date without naming the record that supports the change. It treats the update as the unit and the source record as the evidence standard. The scope is one firm, one set of active matters, and a fixed review window. The result describes that setting and should not be read as a client-satisfaction measure.

The unit is one date change reported in one client update. A change is eligible when the update gives a new date or a new date range. Updates that repeat an unchanged date are excluded. Record the inclusion rule before reviewing so the denominator is not built from the most dramatic changes.

Record whether the update was sent before or after the source record was filed. A message sent before the filing may rely on a draft date that later changes. Report the timing with the source category. That distinction prevents a correct update from looking unsourced.

Definitions and evidence standard

Define a sourced date change as one where the update or its internal support identifies the court notice, filed document, calendar entry, or written instruction behind the new date. A change is unsourced when the update gives a date but no record can be tied to it. A change is partially sourced when the record exists but the update does not identify it. Record the source and the date with the entry.

Use the sent message, the matter calendar, and the source document as the evidence. If the date came from a phone call, record who confirmed it and when. A date that cannot be reconstructed from the file is unsourced even if the writer remembers the conversation. The study measures the record, not the writer's confidence.

Record whether the update was written from the calendar or from the matter file. A calendar-only update may miss the source document, while a file-based update may be slower but easier to verify. Report the source workflow with the result. That variable helps separate a template problem from a research habit.

Sampling and measurement

Select client updates from the window and freeze the list before review. Include updates from more than one matter type and more than one writer. If the firm sends both routine and event-driven updates, report them separately. Record the number of updates and the number of date changes.

Measure the number of changes with a complete source, a partial source, and no source. Add the number of updates that explained the reason for the change. Report the counts by matter type and by writer role. A rate without these counts can make a small sample look more precise than it is.

If a date change was reported in a phone call and confirmed in writing later, record both events. The written confirmation may be the source, but the timing of the call matters. Report the confirmation date with the source category. A later confirmation should not be treated as if it existed when the update was sent.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of unsourced changes in one matter type may mean the calendar is not linked to the update template. A cluster under one writer may mean the source is kept in a personal note. A cluster around hearing dates may mean the court notice is not being saved with the update.

Read the updates behind the largest gaps and compare them with the source record. Record whether the source was missing, hard to find, or simply not cited. A writer may know the source but omit it because the template has no field. Distinguish a knowledge problem from a template problem before recommending a fix.

Compare the unsourced rate with the number of date changes in each update. An update with several changes has more chances for a missing source. Report the count beside the rate. A simple update and a complex one should not be judged as if they carried the same burden.

Compare the unsourced rate with the number of reviewers who touched the update. A second reviewer may add a date without adding the source. Report the reviewer count beside the rate. The review step is part of the evidence path.

Limitations

The study measures the written update, not the client's understanding. A sourced update can still be confusing, and an unsourced update can still be accurate. It also cannot decide whether the firm met a professional communication duty. Those questions need a substantive review by the responsible lawyer.

The window may include a court closure or a matter change that affects the dates. If the update template changed during the period, the fields may not be comparable. Record these limits with the result and keep the sent messages with the method. Record the source and the date with the entry.

If a client asked for a date change, record the request and the firm's response. A change made at the client's request may have a different source path from a court-driven change. Report the requester with the source category. Keep the evidence beside the decision in the file.

Practical next step

Choose one control that matches the most common gap, such as a required source field, a calendar link, or a second-reader check. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same source categories. Test it on the next set of updates.

Keep the before and after updates separate so the comparison is honest. Record the updates that were excluded and why. Review the result with the lawyers and the client team. If the change does not help, record that result too. The purpose is a dated, checkable update, not a longer message.

Test the source field on one update type before applying it to every client message. A routine update may need only a date source, while an event-driven update may need the order and the trigger. Record the test group and the result. A type-specific field is easier to use than a universal form.

Comparing update types

Routine updates and event-driven updates may carry different source expectations. A routine update may repeat a known date, while an event-driven update reports a change that needs a court notice. Report the count and the rate for each type, and label small groups as descriptive only. Record the source and the date with the entry.

If one type shows a consistent gap, check whether its template has a source field and a reviewer. A type that looks worse may simply carry more changes. Compare the process, not the writer. The next study can test a type-specific template before applying it to every update.

Keep the sent messages and the source extracts in a restricted workspace. Publish only the aggregate categories and the matter-type counts. If a client asks for the result, describe the method and the control rather than sharing the correspondence. Keep the evidence beside the decision in the file.

Keep the sent messages and the source extracts in a restricted workspace. Publish only the aggregate categories and the matter-type counts. If a client asks for the result, describe the method and the control rather than sharing the correspondence. Ask the named owner to confirm the record.

What the evidence does not show

The study does not establish that a client relied on the unsourced date or that the firm missed a deadline. It also does not measure whether the date itself was correct. Those questions need a separate review. A missing source is a communication-record observation, not a legal conclusion.

Do not use the result to promise a client that every update will be sourced or that no date will ever change. Do not publish client names or matter details. Keep the sample size, the source definitions, and the review decisions with the result. If the firm needs a legal conclusion, it should ask counsel.

Review the result with the lawyer who sent the updates, not only with the support team. The lawyer may have a different view of which source is authoritative. Record the disagreement and the agreed rule. The study should improve the record, not create a parallel standard.

Using the result in a client conversation

A client may ask how the firm keeps status updates accurate, and the study supports a careful answer. Describe the window, the number of updates, the source categories, and the control that was added. Do not say that every update is complete or that no date will ever move. Explain that the measure covers the written record and that the lawyer reviews the substance.

If the client asks for a commitment, offer a process commitment such as a source field, a calendar link, and a second-reader check. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. The study is an internal communication tool, not a service guarantee.

Keep the source extracts and sent messages in a restricted workspace. Publish only the aggregate categories and matter-type counts. If a client asks for the result, describe the method and the control rather than sharing correspondence. Record the source and the date with the entry.

Sources and method

Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.

  1. U.S. Courts, Federal Rules of Civil Procedure
  2. American Bar Association, Model Rules of Professional Conduct
  3. GAO, Standards for Internal Control in the Federal Government
  4. NIST Cybersecurity Framework 2.0

Related research

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.