Legal Services Offshore research · legal-support-operations
Where does delay accumulate in a legal intake queue?
A stage-level method for locating wait time in legal intake without treating every long cycle as a performance problem.

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 where time is spent between the receipt of a legal intake request and the first substantive review. It separates active preparation, waiting for missing information, waiting for an approval, and waiting for a system or access step. The scope is one intake queue or one defined matter type during a fixed period. The result describes that queue and is not a benchmark for other firms.
The unit is one intake item followed from receipt to the defined review point. Record the timestamps from the system of record where possible, and mark estimated times separately. If an item was reopened, keep the original cycle and add the new segment. Exclude duplicates and test submissions, and record the exclusion reason. Report the number of items and the number of stages observed.
Method and evidence standard
Define each stage and its start and end events before extracting data. A stage begins when the item enters the queue and ends when the required action is recorded. Do not use the time a message was read as a proxy for the time work began unless the system records that event. If a timestamp is missing, record the gap rather than filling it with an average.
Sample items across request types, arrival days, and assigned teams. Include items that were escalated and items that moved without escalation. Two reviewers should compare a small set of timelines and resolve differences in stage boundaries. The study measures elapsed time, not effort or quality. A fast item is not necessarily complete, and a slow item is not necessarily poorly handled.
Measures, findings, and interpretation
Report the median and range for each stage, the share of items with a missing timestamp, and the most common reason for a wait. Show the result by request type and arrival period. A long wait for missing information is different from a long wait for an internal approval, and the report should keep those categories separate. Use counts with the rates so a small group is not overinterpreted.
Inspect the items behind the longest waits before assigning a cause. A cluster in one stage may reflect a staffing gap, a system step, or a rule that sends every item to the same reviewer. A cluster across stages may reflect an unclear intake form. The study cannot show whether the eventual decision was correct, and it should not be used to rank individual reviewers without additional evidence.
Limitations and practical next step
The timestamps reflect the system's record and may not capture work done in email, chat, or a personal queue. The study also cannot observe the urgency of each item or the quality of the underlying legal judgment. A queue with a stable median can still contain a small group of very old items that matter more than the average. Report the tail and the missing data alongside the central measure.
Choose one stage for a bounded improvement, such as a clearer missing-information request or a named approval backup. Record the owner, the start date, and the measure that will show whether the wait changed. Recheck the same stage after the change and keep the before-and-after sample. The most useful result is a specific next test, not a general claim that the queue is fast or slow.
Sources and method
Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.