On this page
A college coach directory looks simple until recruiting mail starts bouncing. A name appears with a role, an email pattern, or a phone number that was accurate in May and is wrong by August. The error rarely announces itself. A family sends a thoughtfully drafted note to an address that no longer belongs to that program, the note never reaches the intended reader, and the follow up stalls for reasons that have nothing to do with athletic evaluation.
A verification routine prevents that drift by treating directory information as a dated fact that expires quickly. The routine below turns a casual look at a staff page into a dated record that a VA can maintain and an athlete can trust before each send.
Define what counts as verified
One staff page does not equal one verified contact. A verified entry needs four fields confirmed on the same date, from the same official source.
| Field | Source of truth | Why it matters |
|---|---|---|
| Full name and spelling | College athletics staff directory for that sport | Prevents misaddressed mail and wrong-name greetings |
| Current role and team assignment | Same directory, role line for that person | Ensures the question reaches the person who owns it |
| Email or contact method | Directory listing or linked profile page for that staff member | Avoids routing through a general inbox when a direct address is published |
| Date checked and URL | Access timestamp plus exact page URL | Shows when the record was current and where it was taken from |
If any of the four is missing, the entry is not verified. It is a lead that needs another check. This distinction matters because families often treat a name found on a recruiting site or a forwarded thread as equivalent to a directory listing. Those secondary sources may be correct, but they are not the controlling reference for that school on that date.
A VA supporting this work can create a one row template with those five columns and lock the set until all four are filled. The role line should be copied verbatim rather than paraphrased, because a recruiting coordinator and an assistant coach may handle different questions even when they appear on the same page.
Set the checking cadence by stage, not by habit
Checking every directory weekly wastes time. Checking only when mail bounces wastes opportunity. The cadence that balances both is tied to recruiting stage.
During initial research, the family checks a directory once when a program enters the target list and again when outreach begins. That two point check catches preseason staff moves that happen between list building and the first note.
During active outreach, the directory gets rechecked every time a new thread starts with that program and again if a reply comes from a different name than the one first contacted. Staff rotations inside a program are common during travel season, and a reply from a new name is information, not confusion, when the directory confirms the shift.
During visit planning or committee review periods, the directory gets rechecked within seven days of any travel or meeting, because the person who encouraged the visit may not be the person who hosts it.
A VA maintaining the tracker can add a light rule to flag stale entries. Any contact record older than thirty days during active outreach gets a recheck before the next send, regardless of stage. Any record older than ninety days during pure research gets a recheck before it becomes an outreach target. Those intervals keep the workload realistic while preventing stale data from driving a send.
Compare the directory against the message you plan to send
Verification does not end at the directory line. The message itself has to match what the directory shows. Three mismatches show up often.
The first is a name and role mismatch. A family addresses a note to a head coach when the directory lists that person as an associate head coach or director of operations. The correction is small but meaningful. Use the exact title shown and ask the question that fits that role. If the role remains unclear, note the uncertainty in the draft and let the athlete decide whether to ask the general program contact for routing.
The second is an email pattern mismatch. Many schools use a predictable pattern such as first.last at the campus domain, but some vary by sport or by staff category. Copy the address exactly as listed. If no direct address is listed, use the program contact provided on the staff page rather than guessing a pattern and testing it with a real recruiting note.
The third is a sport assignment mismatch. At larger schools, a coach may be listed under more than one sport or under a shared staff section. Confirm that the person is assigned to the athlete's sport in the current directory, not merely present on the site.
A VA preparing a draft can run these three checks in under a minute when the directory source is already open beside the draft. The preparation note should read like Checked August 23, 2026 at https://example.edu/staff, listing Head Coach Jane Lee for women's soccer, not like contact confirmed without detail.
Record the staff change when the directory moves
Directories change in two ways that look similar but mean different things. In a role change, the same person appears with a new title or sport assignment. In a departure, a new name appears where an old one was. Both require a record update, but the recruiting response differs.
For a role change, update the contact row to reflect the new role, keep the prior role and date in a history note, and keep the email if unchanged. The appropriate next step may be a brief continuity note that references the prior thread and asks who now handles the specific recruiting question.
For a departure, add the new person as a separate entry, mark the prior person as formerly listed with the last verified date, and pause any new outreach until the appropriate contact for the athlete's class and position is clear. Do not auto forward the old thread to the new name without reading the program's guidance on recruiting contacts. Some schools centralize initial contact through a recruiting coordinator even when individual assistants handle evaluation.
A VA can maintain a small change log per program with three columns: date noticed, what changed, source link. That log answers the inevitable family question about when a contact went stale, and it proves the current record is not a guess.
Keep the log useful to the athlete, not just accurate
An accurate log that no one reads helps no one. Make the record usable where the athlete actually works.
The simplest presentation is a one page table sorted by program, with columns for program name, coach name, current role, contact method, date checked, source link, and next recheck date. That table lives alongside the target list, not buried inside a folder structure. When the athlete opens the tracker to send a note, the current contact sits beside the draft, dated.
A second useful view is a per program history strip. It shows the last three directory states with dates, so the athlete can see that the contact has been stable or has changed recently. That context helps interpret a slow reply.
Finally, retire obsolete entries rather than deleting them immediately. Move a formerly listed coach to an archive section dated with the last verification, instead of erasing the row. The archive protects against resending to an old address pulled from an old draft, and it preserves the family record of who was contacted when.
When a VA owns the maintenance side, the athlete should still perform the final visual check before each send. The VA notes Checked August 23, 2026 at the staff URL. The athlete glances at the directory link and confirms the name and role one more time. That paired check takes thirty seconds and catches the one error that automation and memory both miss.
Frequently Asked Questions
How often should the family check the same directory if nothing seems to have changed?
Use the stage based cadence. Active outreach gets a recheck within thirty days of the last verification before each new thread. Pure research can stretch to ninety days, but any reactivation of outreach restarts the thirty day clock.
What if the staff page lists only a general program email, not individual coaches?
Use the general program contact as the directory intends, and note it exactly as listing only general inbox as of the checked date. Do not guess individual addresses. Ask the general contact for routing if needed, and log the routing response.
Should the athlete mention the directory in a coach email?
No. The verification is internal administrative evidence. The email should simply address the correct person with the correct role. The family keeps the source link and date in its tracker for its own accuracy.
How does this routine fit with broader recruiting support?
A VA can own the repetitive checking, change detection, and table formatting. The athlete owns the actual outreach and the final review before sending. The routine makes that division explicit, so helpful support does not become speaking for the athlete.
Related Articles
College Research
A Staff Directory Audit for College Recruiting Research
A practical, source-checked workflow to verify names, roles, and official contact routes before athlete outreach, with tracking fields, review steps, and questions for athletes and families.
College Research
How to Track College Coaching Staff Changes During Recruiting
A practical, source-checked workflow to keep outreach records accurate when a program changes staff, with tracking fields, review steps, and questions for athletes and families.
College Research
A Contact Page Log for College Athletics Research
A practical, source-checked workflow to keep official staff contact pages tied to a date and specific research question, with tracking fields, review steps, and questions for athletes and families.