Measuring reply time in coach outreach

Published November 2, 2026

A study protocol for measuring the interval between a recruiting outreach message and the first meaningful coach response, with clear definitions and honest limits. 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 protocol asks how long it takes, in one defined recruiting program, for a coach or staff member to return the first meaningful response after an outreach message. It measures the interval between recorded events, not the quality of the coach's answer, the athlete's fit, or the likelihood of an offer. A fast reply can be a polite decline; a slow reply can be a genuine evaluation. The result describes timing, not interest.

Set the observation window and the program population before collecting messages. Include only outreach sent through the channels the study can observe, such as the recruiting platform, a tracked email address, or a documented phone log. Exclude messages sent from a personal inbox that the team cannot export. Record the exclusion count and the reason so a later reader does not mistake an unobserved channel for silence.

Population and unit

The unit is one outreach thread tied to one athlete and one program. A thread can contain several messages; the first response is the first reply from the program side that addresses the athlete or the request, not an automated receipt. If a coach forwards the message to an assistant and the assistant replies, the response belongs to the same thread. If the family sends a new message after a long silence, keep the original thread and record the restart separately.

Decide whether a program can appear more than once. If the athlete contacts the same school at two different times with a material change, treat the later outreach as a new unit only when the message starts a new evaluation cycle. Otherwise, count the program once and use the first response. Record the rule and apply it consistently across the sample.

Exclude generic camp advertisements and automated questionnaire confirmations from the response definition unless the study explicitly asks about them. A newsletter is not a reply. A questionnaire receipt may show that a form arrived, but it does not show that a person reviewed the athlete. Keep those events in the dataset as context, not as the primary measure.

Definitions and clocks

Record the send time in the time zone in which the system logs it, then convert to a single reference zone for analysis. The sending time should be the moment the message left the athlete's or family's account, not the time a draft was created. The response time should be the timestamp of the first meaningful reply. If a reply arrives while the family is asleep, the clock still runs; the study is measuring elapsed time, not working hours.

Define a working-time view only if the team needs it for staffing decisions. A calendar-day measure is easier to explain and harder to manipulate; a working-time measure can be more useful for service planning but requires a published holiday and weekend rule. Report both if both are used, and never switch definitions midway through the sample. Classify the response: request for information, invitation to a camp or visit, request for film, referral to another staff member, decline, or unclear. The classification should come from the message text, not from the family's interpretation of tone. A response that asks for a transcript is a real response even if it does not mention the athlete's athletic ability.

Data sources and fields

Collect the school, sport, division, coach role, channel, send timestamp, response timestamp, response type, and whether the response was automated. Add the athlete's graduation year and position because the same program may respond differently to different cohorts. Record the message version or outreach batch identifier so a later reviewer can connect the row to the original content. Preserve the raw event timestamps and the source system. A spreadsheet summary that says four days is not enough if the team later needs to check daylight saving, a delayed sync, or a message that was sent from a different account. Keep the link or message identifier in the approved system and record access restrictions for any personal data. Mask names and contact details in the analysis table. The study does not need a coach's personal mobile number or an athlete's home address to compute a time interval. Record the school and role, not the individual's private contact information, unless the team has a documented need and approval.

Sampling and collection

Export the outreach records at a fixed time and freeze the frame before selecting rows. A sample drawn from the most recent replies will overrepresent fast responses because slow threads have not had time to finish. Include threads that are still waiting at the cutoff and mark them as censored. That is the only honest way to describe response time in a live queue.

Stratify by division, sport, and outreach batch if those factors could change the response pattern. Use a random or systematic start within each stratum and record the rule. If the frame is small, report every eligible thread rather than pretending a sample is representative. A complete small census can be more useful than a large biased sample.

Do not let the person who sent the messages choose the sample after seeing the replies. A second person should apply the frame and the inclusion rule. If that separation is impossible, record the conflict of interest and have another reviewer check a subsample. The measurement is more credible when the selection rule is visible.

Analysis and reporting

Report the number of threads, the number with a response, the number still open at the cutoff, and the number excluded. Show the median and the distribution of response time, not only the mean. Response times often have a long tail, and a mean can make a program look slower or faster than the typical experience. If the sample is small, show the individual times or a simple range.

Compare groups only when each group has enough cases to support the comparison. A difference between two sports may reflect the season, the coaching calendar, the athlete's graduation year, or the sample size. Report those possibilities rather than attributing the difference to coach responsiveness. The result should help the team decide where to follow up, not label a program as unfriendly.

Include the share of threads with no response at the cutoff. A short median among replies can hide a large group that never answered. The no-response group is part of the result, not a missing-data problem to be dropped. If the team later follows up and receives a reply, add a dated note rather than erasing the original silence.

Limitations

The study can observe only the channels in the frame. A coach may have replied by phone, through a club coach, or at a camp without leaving a record in the tracked inbox. Those responses are invisible, so the measured interval may overstate the program's silence. State the unobserved channels and the likely direction of the error.

The meaning of a response varies. A request for film may start an evaluation, while a camp invitation may be a mass recruiting step. The timing measure should not be interpreted as interest or as a prediction of an offer. Pair it with a response-type count and a qualitative review of a small number of threads if the team needs to understand what the replies actually meant. Public recruiting rules and calendars describe when contact can occur; they do not provide a local benchmark for reply time. The result is a description of this program's observed behavior during this window. It should inform follow-up practice and staffing, not become a public ranking of coaches or schools.

Review and next action

Give the result to the person who owns the outreach cadence and the person who manages the inbox. Choose one change to test: a shorter follow-up interval for quiet threads, a clearer message subject, a different send day, or a weekly review of the oldest unanswered outreach. Record the decision, the owner, and the date the change starts. Repeat the protocol after the change with the same definitions and a comparable window. Compare the response count, the censored count, and the distribution, not just the median. If the change did not move the result, report that and inspect whether the message content, the channel, or the season changed at the same time. End with a decision about the next test, not a permanent dashboard.