Build a recruiting phone tree for weeks when the usual parent is away

Recruiting does not pause because one parent is on a work trip or caring for a relative. A coach may call about a visit change on the one afternoon the usual contact is unavailable. Without a backup plan, the message sits in a voicemail box while a deadline moves closer. A phone tree is a small agreement about who answers, who decides, and who tells the athlete, and it works best alongside clear family communication boundaries.

Map the roles before the trip

Start with the jobs rather than the names. Someone has to answer the call, someone has to decide whether the athlete needs to respond personally, and someone has to update the shared record. In many families one person does all three, which is exactly why coverage fails when that person is away. Write the roles down and assign a primary and a backup to each.

Include the athlete in the map, even if the athlete is a minor. Coaches expect prospects to communicate directly once rules allow it, and a parent who always speaks for the athlete can weaken the relationship. The athlete's role might be limited to returning a call within a set window. That small responsibility keeps the process honest and gives the coach a direct path.

Write a call order that matches authority

The call order should follow decision authority, not family hierarchy. If a parent handles financial questions, that parent should be first for a call about aid, even if another relative is easier to reach. If the athlete handles scheduling, the athlete should be first for a visit change. Separate the call orders by topic so the tree does not send every message to the same person.

Keep the order short enough to use under pressure. Three names with numbers and a note about the topic are enough for most families. Add the time zone for anyone who travels, because a call at the wrong hour can waste the one window a coach has available. Review the order before each high-traffic recruiting week.

Keep a shared script short

A phone tree needs a short script for the person who answers a call that is not theirs. The script should confirm who is speaking, note the coach's name and program, ask whether a decision is needed today, and promise a specific callback time. It should not attempt to answer questions outside that person's role. A clean handoff is better than a confident guess.

Write the script in the family's own words and keep it under a minute. Put it in the shared notes app or beside the phone list so it is available without a search. Update it when a coach changes roles or a new program enters the list. A stale script with an old name is worse than no script because it signals that the family is not paying attention.

Test the tree during a quiet week

A phone tree that has never been used is a theory. Test it on a quiet week by having one person place a mock call and watching how the message travels. Time how long it takes to reach the right person and whether the shared record gets updated. Fix the first broken step before a real call exposes it.

The test should include a message that requires a decision and one that does not. The first tests authority, and the second tests whether the tree can close a loop without escalating. Most trees handle emergencies better than routine messages, which is why routine messages pile up. The test reveals that imbalance while there is still time to correct it.

Handle the parent who is unavailable

The person who is away should not disappear from the process entirely. Set a daily check-in window, even if it is only ten minutes, and agree on what counts as urgent enough to interrupt. Everything else waits for the window and goes into a single summary. That boundary protects the trip and keeps the recruiting file from becoming a second job.

If the away parent is the only person with access to a portal or an inbox, fix that before the trip. Add a backup recovery method or move the relevant messages to a shared mailbox. Do not share passwords through a group chat. A short access review before travel prevents the most common coverage failure, which is not a missed call but a locked account.

Close the loop when the week ends

At the end of the coverage period, review every message that arrived and confirm that each one has an owner and a next step. Update the contact record with what changed and close the items that are finished. Tell the coaches who the normal contact is again so they do not keep routing messages to the backup. The transition back is part of the tree, not an afterthought.

Keep the phone tree in the recruiting file after the week ends. The next trip or illness will arrive without much notice, and a current tree saves the family from rebuilding the plan. Update names and numbers at the same time as the contact preference record. A living document is more useful than a perfect one written once.

Sources

• NCAA Recruiting Rules
• NCAA Division I and II Recruiting Calendars
• BLS Occupational Outlook: Coaches and Scouts