Measuring cycle time for task scope from request to verified close

Question and scope

This protocol asks how task scope can be described from the operational record in overseas VA support without turning a completion count into a quality claim. Record the opening count, additions, withdrawals, resolutions, and unresolved items at the end of the window. Distinguish an administrative pause from a failure: a pause waits for a named decision, while a failure leaves the next action unowned. Record the exclusions in advance so a difficult case cannot be removed after the result is known. If the case moved between owners, include both owner periods in the review note and name the handoff time. The protocol does not estimate an industry benchmark; it produces a local description that business owners hiring overseas can review. The unit definition should be stable enough that two reviewers can classify the same case the same way. Define the start event, the stop event, the pause rule, and the treatment of a missing inbox triage note before collecting data. State whether the study covers one team, one client, or all cases in the defined service. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

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. Define whether a request that generates several inbox triage note updates is one case or several before counting begins. Use plain language in the definition and add one example and one non-example for the reviewer. If the queue was archived during the window, report the loss and exclude the affected period rather than assuming the cases were resolved. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. If a reopened case creates a new requirement, count it as a new case and retain a link to the earlier record. The population should include unresolved cases, not only closures, or the study will overstate completion. A correction should be classified by the original case and by the correction event, with both dates retained. If the queue was archived during the window, report the loss and exclude the affected period rather than assuming the cases were resolved. At Overseas Virtual Assistant, the task scope review should end with a dated note and a named owner for the next check.

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. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. Before collection, test the definitions on a missing calendar brief, a reopened case, and a handoff. State how duplicate, cancelled, and reopened cases enter the numerator and denominator. If the evidence is sensitive, record the approved reference and access path rather than copying the content. If the definition of completion changes, keep the old and new rules side by side for the transition period. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. Use the same status vocabulary in the queue, the evidence extract, and the report so a case does not change category. Give one concrete example and one boundary case to each reviewer before collection begins. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.

Data dictionary and evidence

Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. Version the dictionary and report which version was used for each observation period. Record the data extraction date and the version of the CRM used for the population count. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. Record this decision in the study log with the case key, the review date, and the person who approved the classification. Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. 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. A case key should remain stable if the case moves between owners or changes status. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue. Each case needs the source, the observation time, the field supported, the owner, and the reviewer. Use a controlled list for exception reasons; do not let free text become the analysis category. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. A case key should remain stable if the case moves between owners or changes status. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.

Sampling and collection

Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. Record the time of each observation so a later reviewer can distinguish a late entry from a changed decision. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. Record the date of the sample and the version of the queue export. At Overseas Virtual Assistant, the reviewer should be able to explain this step to business owner from the case record alone. Include adverse cases: a missing trial scorecard, a conflicting source, an unavailable VA, and a tight deadline. Collect the case from the time tracker, the trial scorecard, and the approval record, and stop at the verified close. 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. Use the same note in the case file and the study extract; do not create a second version in a personal document. Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Keep the collection window and the number of collectors in the report; both affect how the result should be interpreted. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. Include at least one case from each owner in scope when the frame allows it. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

Analysis and reporting

For task scope, report the age distribution and the share of cases waiting on a named decision rather than a single average. Keep descriptive findings separate from causal claims. If the result is unstable, say which cases create the variation and what a larger sample would test. Use a case-level table to explain an outlier before treating it as a process signal. Keep the measurement note short enough to read with the case and specific enough to support the reported access closure. For task scope, report the age distribution and the share of cases waiting on a named decision rather than a single average. 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 number of cases that drive a small-sample result and the direction of the effect. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

Limitations

The method also cannot observe work that never entered the queue, which may be the most important missing population. Small samples are unstable; report the range and the cases that create the variation. State that the result describes the observed sample and not the entire industry or every team in the service. Report the limits of the task board data, including fields that were unavailable or changed. Link the observation to the exact field in the task board and to the task scope that supports it. The method also cannot observe work that never entered the queue, which may be the most important missing population. The cited sources describe recordkeeping, privacy, security, or control practice; they do not supply a local benchmark. Do not treat a missing record as proof that the work did not happen; it is evidence about the record. If the queue changed during the window, explain how the change affects the denominator. Do not let a summary written later replace the evidence that was available at the first decision.

Review and next action

Record the decision and the next check so the study does not end as an archive. If the result is inconclusive, say so and choose a narrower question rather than claiming a trend. Close the review only when the owner has accepted the result and the next check is scheduled. Keep the prior procedure available so the next reviewer can compare the old and new states. If the case moved between owners, include both owner periods in the review note and name the handoff time. Repeat the protocol after the change with the same definitions, window, and exclusions. Name the owner, the review date, and the decision the study is expected to inform. Choose a measure that can move within one cycle and a second measure that checks for unintended effects. Schedule the next review before the action begins, not after the result arrives. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

What is measured?

Whether the operating record supports a reproducible review.

Who decides?

The named client owner.

Main limit?

A small sample cannot establish causation.