Measuring cycle time for athlete intake from request to verified close

Published October 27, 2026

A grounded sports recruiting support note for recruiting agency owners: athlete intake with explicit evidence, decision rights, and a verified close.

The study measures the record and the handoff, not the professional judgment of recruiting agency owner or the legal outcome of the work. State how duplicate requests are identified and whether they are merged, linked, or counted separately. Define the start event, the stop event, the pause rule, and the treatment of a missing athlete intake before collecting data. Record the exclusions in advance so a difficult case cannot be removed after the result is known. Link the observation to the exact field in the recruiting CRM and to the athlete intake that supports it.

Write the primary question and one supporting question, then stop; a long list of questions usually hides an undefined unit. A count without a denominator is not a measurement, especially when the queue changes size during the day. If a definition changes during the review, keep the earlier classification and apply the new rule only to later cases. The protocol should be short enough for an operator to follow and specific enough for a reviewer to repeat. Do not let a summary written later replace the evidence that was available at the first decision.

Test the unit definition on a case that crosses owners, a case that is still open, and a case that was reopened. A case that moves between owners stays one case unless the process defines a new requirement at the handoff. A correction should be classified by the original case and by the correction event, with both dates retained. Record the extraction date and the queue filter so another reviewer can reproduce the population count. If the case moved between owners, include both owner periods in the review note and name the handoff time.

Record the opening count by owner and channel, because a single total can hide a queue concentrated in one person. Record the queue at the start and end of each observation day so additions and withdrawals are visible. The start event should be the first recorded request, not the first time the team opened the case. Separate cases opened before the window from cases opened and closed inside it, and report both counts. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

Test each definition on a routine case, a missing-evidence case, and a case that crossed owners. A blank field, a not-applicable field, and a confirmed negative field should have different codes. Use the same status vocabulary in the queue, the evidence extract, and the report so a case does not change category. 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.

Define how a correction after close is linked to the original case and whether it creates a new case. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Give one concrete example and one boundary case to each reviewer before collection begins. At Sports Recruiter Support, the athlete intake review should end with a dated note and a named owner for the next check.

Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. Give every case a study key that is not the client name, member number, or candidate email. Use one row per case and one column per required field; do not bury evidence in a long free-text note. Use a separate field for reviewer notes so the coded values stay comparable. If the evidence is sensitive, record the approved reference and access path rather than copying the content.

Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Use a controlled list for exception reasons; do not let free text become the analysis category. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Pilot the dictionary with two reviewers and compare their classifications before the main sample. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.

Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Record the extraction time separately from the event time so a late entry is visible. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. Keep the original request, the approval, and the destination value linked to the same key. Record this decision in the study log with the case key, the review date, and the person who approved the classification.

Use consecutive athlete intake cases where possible, then stratify by owner, channel, and risk class. Do not clean the data by filling missing values; preserve the missing state and report it as a result. 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.

A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Record the time of each observation so a later reviewer can distinguish a late entry from a changed decision. Record the eligible count and every exclusion before the sample is drawn. Record the sampling frame as an export with a date, filter, and row count. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.

Use consecutive athlete intake cases where possible, then stratify by owner, channel, and risk class. If a source cannot be accessed, mark it unavailable and record the access problem rather than asking the operator to reconstruct it from memory. Record the eligible count and every exclusion before the sample is drawn. Record the date of the sample and the version of the queue export. At Sports Recruiter Support, the reviewer should be able to explain this step to coach from the case record alone.

Keep case-level detail available for review, because a summary chart without records cannot support a decision. For athlete intake, report the age distribution and the share of cases waiting on a named owner. Show the unresolved cases by owner, age, and dependency instead of reporting a single completion percentage. Keep descriptive findings separate from causal claims and label exploratory results. Use the same note in the case file and the study extract; do not create a second version in a personal document.

A difference between two periods is a signal to inspect, not proof that a process change caused the change. Keep descriptive findings separate from causal claims. Report the number of cases that changed status after the first extraction and how the change was handled. End with the decision the evidence supports and the decision it does not support. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

Changes in definitions, staffing, or the recruiting CRM during the window can create a trend that is not a process effect. Selection bias remains when the team chooses cases that are easy to open or owners who are likely to cooperate. Report the limits of the recruiting CRM data, including fields that were unavailable or changed during the window. Report the limits of the recruiting CRM data, including fields that were unavailable or changed. Keep the measurement note short enough to read with the case and specific enough to support the reported athlete intake completeness.

The method also cannot observe work that never entered the queue, which may be the most important missing population. Selection bias remains when the team chooses cases that are easy to open or owners who are likely to cooperate. Keep the limitations with the result so a later reader does not turn a local observation into a general claim. State that the result describes the observed sample, not the whole industry or every team in the service. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

Keep the review note with the athlete intake evidence so the next reviewer can see why the process changed. 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. Report a failed action with the same detail as a successful one so the team can learn from it. Link the observation to the exact field in the athlete database and to the coach outreach list that supports it.

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. 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. Do not let a summary written later replace the evidence that was available at the first decision.