Legal Services Offshore research · Handoff Reliability
Where client document dumps stall before review
A stage-by-stage method for locating the delay between a client production and the first substantive review, using a frozen collection and a written intake standard.

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 decision use
This study asks where time accumulates between the delivery of a client document collection and the start of substantive attorney review. The decision it informs is whether to change the intake form, the transfer method, the inventory step, or the review staffing. The study measures elapsed time and stage completion, not the quality of the legal analysis that follows. A fast intake does not guarantee a good review, and a slow intake does not prove that the review was weak.
The question should be framed around a specific bottleneck. If the team suspects that clients deliver incomplete collections, the study should measure the time from delivery to a complete inventory and count the follow-up requests. If the team suspects that internal routing is slow, the study should measure the time from a complete inventory to the first reviewer assignment. Each stage needs its own start and stop event, recorded from a system timestamp rather than from memory.
Population and unit
The population should be a frozen list of client collections received during a defined window, with the delivery method, the client, and the matter recorded. Include collections that were delivered in several parts, and record each part as a linked event. Exclude test transfers and collections that were withdrawn before intake began. The unit is one collection followed from delivery to the first substantive review event.
If a collection is supplemented later, keep the original unit and add the supplement as a linked event. Do not restart the clock unless the team's procedure defines a new intake for a materially different scope. Record the collection size, the file count, and the number of formats so the reader can see whether a long intake reflects complexity or a process delay. A large collection may legitimately take longer, and the analysis should account for that rather than comparing raw days.
Evidence dictionary
Define each stage and its evidence. Delivery may be the timestamp of a secure transfer, an email with a link, or a physical media receipt. Inventory complete may be the timestamp when the file count and custodian list are recorded. Privilege screen complete may be the timestamp when flagged items are routed. Review started may be the first substantive note in the review log. Each definition should name the system and the field used.
Distinguish an event that happened from an event that was recorded. A reviewer may have started reading before the assignment was logged, and a client may have delivered before the transfer was acknowledged. Use the best available timestamp and record its source. If the team relies on manual status changes, note that limitation. A study built on inconsistent timestamps can still be useful for finding large gaps, but it should not claim precision the data cannot support.
Sampling and reviewer calibration
Draw the sample from the frozen collection list. Stratify by client, delivery method, collection size, and matter type so the study does not overrepresent one kind of intake. Include collections that triggered follow-up requests and collections that moved smoothly. Record the selection method and any replacement. If the sample is small, report every collection rather than a rate.
Calibration matters most for the boundary between inventory complete and review started. Two reviewers may disagree about whether a preliminary read counts as substantive review. Define the threshold in advance and test it on a calibration set. Compare the reviewers' stage assignments and discuss the disagreements. Preserve the initial ratings and the adjudication. If the team cannot agree on the boundary, the stage measure is not ready for a formal comparison.
Measures and reporting
Report the median and the range for each stage, not only the total elapsed time. A total of twenty days may hide a two-day transfer and an eighteen-day wait for review. Report the count of collections that required a follow-up request and the reason for each request. Report the count that were incomplete at first inventory and the time to complete them. These counts show whether the delay is a client-side or an internal issue.
Include the age of open collections at the observation date. A collection that is still waiting for a missing custodian is different from one that is waiting for a reviewer. Use counts and durations together, and show the denominator for every result. A chart that shows only the average can hide a small number of very slow collections that consume most of the team's attention. Report the outliers and inspect their narratives.
Analysis and interpretation
Compare stages rather than clients when the sample is small. A pattern of long inventory times across clients may point to a transfer or naming problem, while a pattern of long review waits may point to staffing or prioritization. Inspect the case notes before assigning blame. A client who delivered a corrupted drive is not the same as a client who ignored a request for a custodian list, even if both produced a long intake.
Do not use the study to rank individual preparers. The same person may handle the easiest and the hardest collections, and the stage data may reflect assignment rather than skill. If the team wants to compare performance, it needs a design that accounts for collection complexity and review scope. For most legal operations teams, the more useful question is where the process loses time and what change would remove the loss. That question can be answered without a performance rating.
Limitations and sources of error
The study observes collections that reached the intake frame and may miss material that was delivered through an informal channel and never logged. It cannot measure the quality of the review or the effect of the delay on the client outcome. The timestamps may be incomplete, and the stage definitions may not fit every matter. The result describes the sampled collections, not every collection the firm receives.
System changes can affect the result. A new transfer tool, a revised intake form, or a change in review staffing may alter the timings. Note the relevant dates and avoid comparing periods as if the process stayed constant. A small sample can reveal a large gap without supporting a precise estimate. The report should state that limitation plainly and avoid presenting a local observation as an industry benchmark.
Privacy and role boundaries
Use the minimum client and matter information needed for the study. Replace client names with study keys, restrict access to the crosswalk, and follow the firm's retention rules. Do not copy document contents into the analysis file when a reference to the collection is enough. The offshore team may prepare the sample, record stage timestamps, and maintain the study log.
The supervising attorney decides whether a collection is complete enough for review and what the review should cover. The study should not be used to make a client-facing statement about the firm's responsiveness or the strength of a matter. If a collection contains material from another client, stop and report it through the firm's incident path. The privacy rule applies to the intake study just as it applies to the underlying documents.
Worked example
A client delivers a compressed archive on a Friday afternoon. The intake coordinator records the delivery at 3:10 p.m. and finds that the archive contains three custodians instead of the four named in the request. The inventory is marked incomplete at 4:40 p.m., and a follow-up request goes to the client the same day. The missing custodian arrives on Tuesday, and the inventory is completed that afternoon. Review begins on Thursday because the assigned reviewer is in trial.
The stage data shows a two-day client-side delay and a two-day internal wait. The team might be tempted to describe the whole intake as slow, but the two stages have different remedies. The client-side delay calls for a clearer custodian checklist at the request stage, while the internal wait calls for a backup reviewer or an earlier assignment. Without the stage split, the team might train the coordinator on a problem that actually sits with staffing. The example is ordinary, which is why it is useful: most intake delay is a sequence of small waits, not one dramatic failure.
From finding to controlled change
Choose one change based on the stage with the largest avoidable delay. It might be a required custodian list at delivery, a standard folder structure, a named intake owner, or a review assignment rule. Name the owner, the due date, and the measure that will show whether the change helped. Recheck the same stage measure after two cycles rather than declaring success after one fast collection.
Keep a decision log with the finding, the change, the owner, and the result. The log helps the team see whether a change addressed the cause or only shifted the delay to another stage. If the measure does not move, inspect the narratives again. The goal is a collection that reaches the right reviewer with a complete inventory and a clear set of open questions, not a collection that merely arrives quickly.
Sources and method
Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.