Estimating rework in document index from correction and reopen records

Question and scope

The scope is one defined population of document index cases observed from first request through verified close in the conflict database. A count without a denominator is not a measurement, especially when the queue changes size during the day. Distinguish an administrative pause from a failure: a pause waits for a named decision, while a failure leaves the next action unowned. Separate the operational question from the compliance question; this method does not certify either outcome. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The protocol does not estimate an industry benchmark; it produces a local description that law firm administrators can review. The unit definition should be stable enough that two reviewers can classify the same case the same way. Define age from the first recorded request, not from the first time someone remembered to open the case. Name the population, the observation window, and the systems included in the extraction. At Legal Services Offshore, the reviewer should be able to explain this step to vendor from the case record alone.

Population and unit

The unit is one document index case, from the opening request to the verified close, and linked events stay with that case. The population should include unresolved cases, not only closures, or the study will overstate completion. The stop event should be the verified destination update, not the last message in the thread. If a request was reopened after the window, keep it in the original population and report the later event separately. Use the same note in the case file and the study extract; do not create a second version in a personal document. Include cases opened before the window but closed inside it only when the protocol says they belong to the population. The population should include unresolved cases, not only closures, or the study will overstate completion. If the definition of matter reopen rate changes, keep the old and new values side by side for the transition period. Report a case that moved between owners as one case with two owner periods unless the process creates a new requirement. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

Definitions and measures

Define how a correction after close is linked to the original case and whether it creates a new case. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. Record the person who approved the definition and the date it became effective. If two reviewers disagree, preserve both classifications until the definition is clarified. Keep the measurement note short enough to read with the case and specific enough to support the reported deadline completion. Define how a correction after close is linked to the original case and whether it creates a new case. Record the source system, the record identifier, the extraction time, and the reviewer for every extracted value. If a case is outside the scope rule, record the rule and the date of exclusion rather than removing it silently. Keep a change log for every definition adjustment and the date it took effect. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

Data dictionary and evidence

Record the version or date of the conflict packet and the billing portal value so a later reviewer can see what was known at the first action. Version the dictionary and report which version was used for each observation period. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. Use a separate field for reviewer notes so the coded values stay comparable. Link the observation to the exact field in the billing portal and to the conflict packet that supports it. Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. Version the dictionary and report which version was used for each observation period. Keep the source reference and the coded value in the same row, and do not overwrite the original with a later correction. Define who may change a coded value and how the change is logged. Do not let a summary written later replace the evidence that was available at the first decision. Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Version the dictionary and report which version was used for each observation period. Use one row per case and one column per required field; do not bury evidence in a long free-text note. Keep the original request, the approval, and the destination value linked to the same key. If the case moved between owners, include both owner periods in the review note and name the handoff time.

Sampling and collection

Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Use the same collection form for every case and keep the original record linked to the extracted fields. Record the eligible count and every exclusion before the sample is drawn. A case that is difficult to access is still part of the frame; report the access failure rather than replacing it silently. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory. Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. Do not clean the data by filling missing values; preserve the missing state and report it as a result. A sample of recent closures can miss the oldest unresolved work, which is often the most informative. Include at least one case from each owner in scope when the frame allows it. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. Include adverse cases: a missing deadline entry, a conflicting source, an unavailable supervising attorney, and a tight deadline. Do not clean the data by filling missing values; preserve the missing state and report it as a result. Include reopened, unresolved, and exception cases in the sample frame. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. At Legal Services Offshore, the document index review should end with a dated note and a named owner for the next check.

Analysis and reporting

If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. For document index, report the age distribution and the share of cases waiting on a named owner. Use a simple before-and-after comparison only when the definitions and observation window are the same. Report the numerator, denominator, observation window, and exclusion count for each measure. If the evidence is sensitive, record the approved reference and access path rather than copying the content. Compare conflict check cycle across owners only after checking the case mix, the channel, and the evidence standard. Use case-level review to explain an outlier before treating it as a process signal. Report the number of cases that changed status after the first extraction and how the change was handled. End with the decision the evidence supports and the decision it does not support. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.

Limitations

The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. The cited sources describe recordkeeping, privacy, security, or control practice; they do not supply a local benchmark. Record the response or access problems that prevented a case from being reviewed. Report the limits of the conflict database data, including fields that were unavailable or changed. Record this decision in the study log with the case key, the review date, and the person who approved the classification. Report what remains unknown and what evidence would be needed to answer the next question. A clean summary can hide missing evidence, especially when the operator who did the work is also the reviewer. Record the response or access problems that prevented a case from being reviewed. Record the access problems that prevented a case from being reviewed. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.

Review and next action

Report what moved, what did not, and which result is still unexplained. Keep the review note with the document index evidence so the next owner can see why the process changed. Link the action to the specific document index cases that motivated it. Close the review when the owner accepts the finding and the next test is on the calendar. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. Repeat the protocol after the change with the same definitions, window, and exclusions. If the action changes privilege mislabel, record the approval from paralegal before implementation. Link the action to the specific document index cases that motivated it. If the action needs approval, record the approver and the date before the change is applied. At Legal Services Offshore, the reviewer should be able to explain this step to paralegal from the case record alone.

Related research

• Testing whether deadline calendar monitoring catches silent failures
• Testing evidence completeness in conflict packet without a convenience sample
• Measuring cycle time for matter intake from request to verified close