Sampling handoff errors in recruiting files

Published November 2, 2026

A protocol for finding the points where athlete records, coach notes, and visit details become incomplete or inconsistent when a recruiting file changes hands. The protocol below keeps the observation window, the unit, and the evidence standard in one place. It is written for a recruiting team that may hand the record to another reviewer. Use it to review one routine case and one exception before changing the workflow.

Question and scope

This study asks where a recruiting file loses accuracy when it moves from one owner to another. The file may include a contact log, academic documents, visit notes, film links, and the next-action list. The study examines the handoff record and the receiving state. It does not evaluate the people involved or the athlete's recruiting potential. A handoff is a system event, and the errors it produces are usually visible before anyone feels them. Set the scope to one handoff type, such as a weekly inbox transfer, a change from one support staff member to another, or the transition from a family-managed file to a staff-managed file. Record the date, the outgoing and incoming owners, the tools in scope, and the definition of a complete file. If the team changes tools or templates during the window, separate the periods.

Population and unit

The unit is one file or one defined subset of a file that was handed off and then reviewed by the receiving owner. A full recruiting file can be too broad, so the study may sample a section such as the contact log, the academic document index, or the visit packet. Record the section, the file identifier, and the version date. A handoff that moves three sections should produce three units if each section can fail independently.

Decide how to treat a handoff that happened informally, such as a conversation with no written transfer note. Those cases belong in the population if they were intended to transfer ownership. Mark them as informal and record what evidence exists. Excluding them would overstate the quality of the formal process and miss the most common failure path.

Exclude a file that was never handed off, even if it contains errors. The study is about the transition, not all data quality. If the same file is handed off twice, count each transfer separately only when the receiving state can be reconstructed. Otherwise, use the final observable state and note the limitation.

Error taxonomy

Use a small error taxonomy that the receiving owner can apply without guessing. Suggested categories are missing source, wrong owner, stale value, conflicting version, broken link or permission, missing next action, and misrouted personal data. Add a category for a file that is technically complete but includes an instruction the receiver cannot execute, such as a request that depends on an account they do not have. Separate an omission from a wrong value. If a transcript is absent, that is a missing source. If the transcript is present but an old GPA is copied into the summary, that is a stale or conflicting value. The distinction matters because the fixes differ: one needs a collection step, the other needs a version check. The coding should preserve both the field and the error type.

Record severity in terms of the next decision, not personal blame. A missing coach email may block an outreach batch. A broken film link may delay a review. A personal document in an unapproved folder may require an access review before anything else. Severity helps the team sequence repairs, but it should not become a public score for the outgoing owner.

Data collection and linkage

Collect the handoff note, the outgoing file version, the incoming file version, and the receiver's review notes. Use a stable file identifier and a version date. If the handoff was verbal, record the date, the participants, and the first written artifact that followed. Do not reconstruct the outgoing state from the incoming file alone; that would make the handoff look cleaner than it was.

Record the fields checked, not only the fields that failed. A sample that lists only errors cannot show the denominator or the overall completeness. For each unit, note the required sections, the sections present, the sections usable, and the receiver's first action. If the receiver had to ask a question before starting, record the question and the response time. Mask athlete names, contact details, and academic records in the analysis table. Keep the evidence in the approved system and record access. A handoff study can be performed with section-level counts and coded errors; it does not need to expose the family's private documents in a shared report.

Sampling and review

Export the handoff log for a fixed window and freeze it. Sample handoffs rather than individual fields, then review every required field within the selected handoff. This keeps the denominator meaningful and prevents a file with many minor omissions from dominating the result. Stratify by handoff type or owner pair when the process differs.

Use a random or systematic start and record the rule. If the population is small, review all handoffs. Have a second reviewer code a subset and compare the error categories. If the reviewers disagree about whether a link is broken or merely slow, clarify the test before continuing. The study should produce a repeatable assessment, not a one-time opinion.

Measure the receiver's time to first productive action. A file can be technically complete and still slow the next owner down because the context is missing. Record the start time, the first action, and any clarification request. This measure is often more informative than a simple error count.

Analysis and reporting

Report the number of handoffs, the required field count, the number with at least one error, and the error counts by type and severity. Show the share of files that required a clarification before the first action. Separate missing evidence from conflicting evidence and from access problems. A combined error rate hides the different remedies.

Inspect the handoffs with the most errors and describe the sequence. Maybe the outgoing owner transferred a file before a counselor correction arrived, or the receiving owner lacked access to the folder that held the source. The case detail should lead to a process change, such as a handoff checklist item or a permission precheck. Compare handoff types only when the file scope and the required fields are similar. A weekly inbox transfer and a full family-file migration should not be judged against the same denominator. If the team wants a trend, keep the definitions and the file scope stable across periods.

Limitations

The receiving owner's review can find only the errors they recognize. A missing context that neither owner knows about may remain invisible. The study measures observable handoff quality, not the full correctness of the recruiting record. A clean handoff review is not proof that every fact in the file is true.

Informal handoffs often lack a written outgoing version, so the comparison may rely on a later reconstruction. That reconstruction can be biased toward the receiving owner's experience. Record the limitation and, where possible, use a contemporaneous note, message, or file history. Do not present a reconstructed baseline as if it were captured at the time. The study uses local files and a local process. Public records rules and privacy frameworks inform the handling of student information, but they do not provide a benchmark for this team's handoff error rate. The result should guide a repair, not a public comparison of staff or suppliers.

Review and next action

Choose one repair tied to the dominant error: a required handoff checklist, a version check before transfer, a single folder for source documents, a permission precheck, or a clarification field in the handoff note. Assign an owner and a start date. Decide which error type should fall and which guardrail should remain, such as the time to first action or the number of access requests. Repeat the review on the next set of handoffs with the same definitions. Compare the error mix and the clarification count. If the checklist reduced missing sources but increased handoff time, report the tradeoff and decide whether the change is worth keeping. Close the review when the owner accepts the result and the next check is on the calendar.