Coverage gaps in family recruiting contact plans

Natural workspace photo for Coverage gaps in family recruiting contact plans
On this page
  1. Question and scope
  2. Population and unit
  3. Definitions and measures
  4. Evidence standard
  5. Collection
  6. Coverage test
  7. Replay and disagreement
  8. Limits and next step
  9. Sources

Key Stats

1 declared windowReview windowsSource: Frozen review protocol
4 linked referencesOfficial sourcesSource: NCAA and BLS
0Performance claimsSource: Bounded review

Key Takeaways

  • Define coverage by the decision that needs an answer, not by who usually answers the phone.
  • Give every open question a primary and a backup responder before the busy week starts.
  • Record the time a covered message arrived and the time a backup acted.
  • Report unresolved coverage gaps as a finding instead of blaming the absent parent.

Question and scope

This review asks a narrow operational question: when the family member who usually handles recruiting contact is unavailable, which open questions lose a usable responder? The unit is one open question tied to one athlete and one program. The review does not attempt to measure family commitment, parent involvement, or an athlete's recruiting chances. It looks only at whether a written coverage plan produces an action when the primary responder is away, and it extends the coach outreach reply sampling study without repeating its reply-time measure.

The scope is fixed before any case is read so the result cannot be steered by a dramatic example. Eligible questions must have a named primary responder, at least one open action, and a period when the primary was unavailable. A question with no open action is excluded because coverage has no consequence. A question with no recorded unavailability is excluded because the plan was never tested.

The family record is the object of study because the family controls the coverage plan even when it does not control the program. A coach may call once and move on, and the family's plan determines whether that call produces a next step. The review therefore treats the family's dated log as the primary evidence and the coach's later message as a check. That order prevents a successful outcome from hiding a coverage failure.

Population and unit

The population is the set of open recruiting questions a family or support assistant tracked during one recruiting cycle. Each question must name a program, a decision, a primary responder, and at least one backup. Questions that name only a program are excluded because they cannot test coverage. The same athlete may contribute several questions if the questions belong to different programs or different topics.

The unit stays the question, not the family member, because coverage fails one decision at a time. A question that is reassigned after a missed call remains in the set under its original key. That rule prevents a repaired plan from disappearing and making the record look more robust than it was. Every removal from the set carries a written reason and the date of the decision.

Definitions and measures

Coverage exists when an open question has a named primary responder, a named backup, and a documented path for the backup to act. The path can be a shared inbox, a phone tree, or a written delegation, but it must be available without the primary person. A name on a list without an action path is not coverage. The definition focuses on the action because that is what the family can observe.

The primary measure is the number of hours between the arrival of a covered message and the first action by a backup. A second measure records whether the backup had access to the records needed to answer. Both measures are reported with the eligible count and the number of questions that could not be resolved. A percentage without those counts would hide the shape of the sample.

Evidence standard

Each question is tagged covered, partial, or uncovered using the record that was open at the time of review. A covered question has a primary, a backup, and an action path. A partial question has a backup but no access to the needed records. An uncovered question has no usable backup at all. The tag describes the plan, not the family's intentions.

When two sources disagree, both stay in the file until a later message or a written clarification settles the question. A verbal promise to cover a week is recorded separately and cannot retroactively change the tag. The reviewer records the question, the retrieval date, and the specific line that supports the tag. An empty backup field is never treated as an acceptable default.

A coverage claim must be testable from the record. The reviewer notes whether the backup had the login, the phone number, and the context needed to act. This is the same discipline used in the contact preference record, applied to a narrower unit. A coverage claim without those details is treated as a gap rather than a completed action.

Collection

The sample is drawn from questions that entered an active recruiting queue during the declared window. Collection uses a fixed interval and a written stopping point so the reviewer cannot keep adding cases until a pattern appears. Questions are included whether or not the family liked the backup, because a comfortable relationship can hide a missing access path. The note states how many questions were eligible, how many were read, and where reading stopped.

Late additions are refused after the results become visible. A question added at that point would be selected with knowledge of the outcome and would weaken the comparison. If a question is discovered after the stop, it is logged as out of scope and kept for the next window. The reviewer also records any program that required a portal login the backup did not have, because that absence is itself an operational finding.

Every program with no usable coverage path is listed in the collection note even when no message arrived. That list shows whether the sample is limited by the family's plan or by the program's contact method. A reviewer who cannot find a path should not silently drop the program from the frame. Listing the gap keeps the denominator visible and gives the next cycle a concrete place to start.

Coverage test

The coverage test asks three questions of each record. First, does the backup know that the question exists? Second, can the backup reach the program without the primary person? Third, can the backup update the record after acting? A record that fails the first test is invisible, and a record that fails the third is incomplete even when the call happened.

The test is applied before the busy week, not after a missed message. Applying it afterward invites the reviewer to credit a lucky save. The order matters because a near miss can make an uncovered plan look adequate. The reviewer records the answers and the date so a second reader can see the sequence.

A question that fails the test is moved to an uncovered list rather than assigned to the most available person. The family then knows that the next step is to fix access, not to hope for a quiet week. The uncovered list is reported with the main result instead of being hidden in an appendix. That visibility keeps the family from mistaking a quiet week for a covered one.

Replay and disagreement

A second reviewer reads the same protected questions against the same written definitions. The comparison checks the backup name, the access path, and the first action time for each question. Where the two reviewers disagree, the recruiting coordinator decides and records the reasoning. The exercise judges the written rule, not the person who happened to be away.

Replay is not a search for a perfect match. It is a test of whether the definitions are clear enough for two people to apply them the same way. A high disagreement rate is a finding about the protocol, not proof that one reviewer was careless. The dated note stays with the case until the review window closes.

Limits and next step

The conclusion is tied to the cycle, the mix of programs, and the access available during the window. A shorter absence or a set of questions concentrated in one sport may produce a different result. Re-running the review after the next travel week shows whether the pattern holds. Where the second run differs, the report shows both outcomes and names the operational decision that depends on the choice.

The output supports one process fix and a scheduled retest, not a judgment about any parent's availability. A reasonable next step is to name a primary and a backup for every open question before a busy week. A second step is to test the backup's access to the records and the program contact path. Neither step requires a new platform, and both can be checked without collecting more personal data.

A conclusion would change if the review window overlapped a major holiday or if most questions came from one program. A larger sample with more families would test whether the pattern is local or general. A second reviewer with less recruiting experience would test whether the definitions depend on insider knowledge. The report names those conditions instead of treating the current result as final.

Sources

Related Research

Recruiting Operations Evidence

Abbreviation drift in recruiting handoff notes

A bounded review of how private shorthand in recruiting files changes meaning across handoffs, with definitions, a frozen sample, and a replay check.

Recruiting Operations Evidence

Contact attribution when coach territories overlap

A bounded evidence review of how families decide which coach owns a recruiting conversation when two staff members appear to cover the same area.

Recruiting Operations Evidence

Coach departure timing and contact record decay

A bounded evidence review of how contact records lose reliability around coaching departures, with explicit measures, a frozen population, and dated official sources.