Estimating exception spillover in document index

Question and scope

This protocol asks how document index can be described from the operational record in legal support operations without turning a completion count into a quality claim. If the population is too small to sample, say so and report the complete set rather than implying a larger study. Define age from the first recorded request, not from the first time someone remembered to open the case. If the study is exploratory, label it exploratory and do not present the result as a stable baseline. Use the same note in the case file and the study extract; do not create a second version in a personal document. The document index review at Legal Services Offshore should state whether the deadline entry was current on October 28. The scope is one defined population of document index cases observed from first request through verified close in the deadline calendar. If the population is too small to sample, say so and report the complete set rather than implying a larger study. Write the primary measure and one supporting measure; a measure without a denominator or observation window is not ready. If the study is exploratory, label it exploratory and do not present the result as a stable baseline. Keep the measurement note short enough to read with the case and specific enough to support the reported privilege exceptions. The October 28 document index note should distinguish a missing outside counsel invoice from a confirmed negative.

Population and unit

A population that changes size during the day should be reported with the start, end, and net change, not only the closing total. Exclude cases opened outside the window only when the exclusion rule was written before collection. Define how a case that waits for supervising attorney is counted: paused, open, or excluded, but not silently dropped. If a request was reopened after the window, keep it in the original population and report the later event separately. Link the observation to the exact field in the deadline calendar and to the outside counsel invoice that supports it. The supervising attorney decision on document index should be dated October 28 and linked to the outside counsel invoice. A population that changes size during the day should be reported with the start, end, and net change, not only the closing total. Record the queue at the start and end of each observation day so additions and withdrawals are visible. The definition should make it possible to classify a case without asking the person who did the work. If a request was reopened after the window, keep it in the original population and report the later event separately. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 document index close should name the destination field, the approver, and the matter reopen rate check.

Definitions and measures

Name the owner who can declare a case complete, and record that role in the data dictionary. Record the source system, the record identifier, the extraction time, and the reviewer for every extracted value. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Write the start and stop events as observable actions, not as opinions about whether the work felt finished. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 document index exception log should show the reason code, owner, and release decision. Test each definition on a routine case, a missing-evidence case, and a case that crossed owners. Record the version of the conflict packet and the billing portal snapshot used for each case. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. A definition that depends on the reviewer’s memory is not reproducible enough for this study. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 document index recovery test should record the restore point and the conflict check cycle result.

Data dictionary and evidence

Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. Keep the identity crosswalk in the approved system and restrict it to the review owner. Record the data extraction date and the version of the billing portal used for the population count. Archive the dictionary with the study so a later reviewer can reproduce the categories. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Legal Services Offshore should name the document index source, the owner, and the next review time. Record the version or date of the document index and the matter management system value so a later reviewer can see what was known at the first action. Keep the identity crosswalk in the approved system and restrict it to the review owner. Keep the source reference and the coded value in the same row, and do not overwrite the original with a later correction. Do not use a zero or an empty string to represent missing evidence. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for document index should show the source version and the paralegal decision. Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. If a field is derived, record the formula and the source fields used to calculate it. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. Use the same note in the case file and the study extract; do not create a second version in a personal document. The document index review at Legal Services Offshore should state whether the privilege log was current on October 28.

Sampling and collection

If the population is small, report every case and the reason the sample is exhaustive rather than presenting a false precision. Use the same collection form for every case and keep the original record linked to the extracted fields. Do not expand the sample only because the early result looks weak or strong. Include at least one case from each owner in scope when the frame allows it. Keep the measurement note short enough to read with the case and specific enough to support the reported invoice review time. The October 28 document index note should distinguish a missing document index from a confirmed negative. A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Keep the collection window and the number of collectors in the report; both affect how the result should be interpreted. Do not expand the sample only because the early result looks weak or strong. Do not let the reviewer choose the sample after seeing the results. Link the observation to the exact field in the document management system and to the privilege log that supports it. The vendor decision on document index should be dated October 28 and linked to the privilege log. Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Collect the case from the conflict database, the deadline entry, and the approval record, and stop at the verified close. If a stratum has fewer cases than planned, report the smaller count instead of replacing it with a convenience case. Record the sampling frame as an export with a date, filter, and row count. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 document index close should name the destination field, the approver, and the deadline completion check.

Analysis and reporting

Report the eligible count, the sample, the missing-field rate, the exception rate, and the unresolved count at the close of the window. Report denominators with every rate and separate missing evidence from negative evidence. Show the unresolved cases by owner, age, and dependency instead of reporting a single completion percentage. Report the numerator, denominator, observation window, and exclusion count for each measure. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 document index exception log should show the reason code, owner, and release decision. If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. Use case-level review to explain an outlier before treating it as a process signal. 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. The October 28 document index recovery test should record the restore point and the conflict check cycle result.

Limitations

Small samples are sensitive to one case; report the instability instead of presenting a percentage as a stable rate. Selection bias remains when the team chooses cases that are easy to open or owners who are likely to cooperate. Do not treat a missing record as proof that the work did not happen; it is evidence about the record. 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. The October 28 control note for Legal Services Offshore should name the document index source, the owner, and the next review time. The study cannot determine whether the professional decision was correct, only whether the record and handoff are reconstructable. Small samples are unstable; report the range and the cases that create the variation. Record the response or access problems that prevented a case from being reviewed. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for document index should show the source version and the vendor decision.

Review and next action

Repeat the protocol after the change with the same definitions, window, and exclusions. A quality review should end with a testable next step, not a general instruction to improve. Record the owner, the due date, and the exact change that will be tested at the next review. Close the review when the owner accepts the finding and the next test is on the calendar. Use the same note in the case file and the study extract; do not create a second version in a personal document. The document index review at Legal Services Offshore should state whether the outside counsel invoice was current on October 28. A quality review should end with an owner, a date, and one testable change, not a list of intentions. Report what moved, what stayed the same, and what the study still cannot explain. If the action requires a policy or access change, route it to the owner and record the decision. If the action needs approval, record the approver and the date before the change is applied. Keep the measurement note short enough to read with the case and specific enough to support the reported matter reopen rate. The October 28 document index note should distinguish a missing matter intake from a confirmed negative.

Related research

• Auditing backup-owner coverage for privilege log
• Measuring decision latency in matter intake
• Testing evidence retention across conflict packet corrections