Measuring cycle time for client intake from request to verified close

Research findings

## Question and scope Write the primary question and one supporting question, then stop; a long list of questions usually hides an undefined unit. Exclude a reopened case only when the reopening did not create a new requirement; keep the exclusion count and reason. Distinguish an administrative pause from a failure: a pause waits for a named decision, while a failure leaves the next action unowned. Name the population, the observation window, and the systems included in the extraction. Keep the measurement note short enough to read with the case and specific enough to support the reported task cycle time. The scope is one defined population of client intake cases observed from first request through verified close in the task queue. Record the opening count, additions, withdrawals, resolutions, and unresolved items at the end of the window. A case is complete only when the task queue shows the approved destination value and the team roster supports it. Separate the operational question from the compliance question; this method does not certify either outcome. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

## Population and unit When several team roster updates belong to one request, state whether the request or each update is the unit and apply that rule consistently. Record the queue at the start and end of each observation day so additions and withdrawals are visible. Define how a case that waits for team lead is counted: paused, open, or excluded, but not silently dropped. Report a case that moved between owners as one case with two owner periods unless the process creates a new requirement. Link the observation to the exact field in the task queue and to the team roster that supports it. Record how duplicate requests were matched, merged, or kept separate, because that choice changes the denominator. A denominator that changes during the window should be reported separately for each period. 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. Do not let a summary written later replace the evidence that was available at the first decision.

## Definitions and measures A pause should have a reason, an owner, and a review date; otherwise it is an unowned case with a different label. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. Define whether a case that waits for a third party is open, paused, or excluded, and apply that rule to every owner. State how duplicate, cancelled, and reopened cases enter the numerator and denominator. If the case moved between owners, include both owner periods in the review note and name the handoff time. Define the controlled event as the moment a client intake request becomes work, not the moment someone starts typing a note. Keep the original text and the coded value together so a reviewer can check the classification. Before collection, test the definitions on a missing quality review, a reopened case, and a handoff. Record the pause rule and the person authorized to release a paused case. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

## Data dictionary and evidence Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. If a field is derived, record the formula and the source fields used to calculate it. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. Each case needs the source, the observation time, the field supported, the owner, and the reviewer. Version the dictionary and report which version was used for each observation period. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Use a separate field for reviewer notes so the coded values stay comparable. At Outsourced Company, the client intake review should end with a dated note and a named owner for the next check. If the source is a document, record the page or field; if the source is a system, record the record identifier and extraction time. If a field is derived, record the formula and the source fields used to calculate it. A missing value should have a reason code, not a blank cell or a zero. Keep the original request, the approval, and the destination value linked to the same key. If the evidence is sensitive, record the approved reference and access path rather than copying the content.

Discussion

## Sampling and collection Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. 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. Record the sampling frame as an export with a date, filter, and row count. The note should distinguish what was observed, what was inferred, and what still needs an owner decision. Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Record the time of each observation so a later reviewer can distinguish a late entry from a changed decision. A sample of recent closures can miss the oldest unresolved work, which is often the most informative. Do not let the reviewer choose the sample after seeing the results. Record this decision in the study log with the case key, the review date, and the person who approved the classification. Include adverse cases: a missing client intake, a conflicting source, an unavailable team lead, and a tight deadline. Collect the case from the client service portal, the client intake, and the approval record, and stop at the verified close. Record the eligible count and every exclusion before the sample is drawn. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.

Implications and limits

## 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 client intake, report the age distribution and the share of cases waiting on a named owner. If the result is unstable, say which cases create the variation and what a larger sample would test. End with the decision the evidence supports and the decision it does not support. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. Compare rework rate across owners only after checking the case mix, the channel, and the evidence standard. Compare periods only after checking the case mix, the definitions, and the queue rules. Keep the case-level table available for review and summarize only the measures that answer the question. Report the numerator, denominator, observation window, and exclusion count for each measure. At Outsourced Company, the reviewer should be able to explain this step to offshore worker from the case record alone.

## Limitations Small samples are sensitive to one case; report the instability instead of presenting a percentage as a stable rate. The record may be incomplete or delayed, so the method cannot infer work that never entered the queue. Record the response or access problems that prevented a case from being reviewed. Report the limits of the client service portal data, including fields that were unavailable or changed. Use the same note in the case file and the study extract; do not create a second version in a personal document. The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. The study cannot determine whether a professional judgment was correct, only whether the record supports it. Name the follow-up evidence that would reduce the largest uncertainty. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

## Review and next action Keep the review note with the client intake evidence so the next reviewer can see why the process changed. Choose one change and one measure to test it; a long action list is hard to evaluate. Choose a measure that can move within one cycle and a second measure that checks for unintended effects. Use a short action log that names the change, the owner, the due date, and the measure that will show whether it worked. Keep the measurement note short enough to read with the case and specific enough to support the reported timekeeping exception rate. Record the decision and the next check so the study does not end as an archive. Report what moved, what stayed the same, and what the study still cannot explain. Report the action result even if the change did not work; a failed test is still evidence. Record the owner, due date, and exact change that will be tested at the next review. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.