On this page

A recruiting office can lose more than a coach when a staff member leaves. It can lose the record of who spoke to whom, when, and through which channel. A compliance contact log is the memory of those conversations. When it is complete, a new assistant can pick up a thread without guessing and a compliance officer can answer a question without reconstructing the week from text messages. The log is a simple tool, but it protects the office from a costly gap.
This log is not a recruiting CRM and should not be treated as one. The CRM tracks interest, notes, and next steps. The compliance log records contacts that the rules require the office to document. Keeping the two separate makes each one easier to use. The log should be short enough to complete after every call and specific enough to survive an audit.
Decide what counts as a contact
Write a short definition of a contact that fits the office and the sport. Include phone calls, emails, text messages, social messages, and in-person conversations where the rules treat them differently. A definition that says only "communication" leaves the staff to interpret every case. The office should agree on the list before the busy season starts. A written example is easier to apply than a principle.
Add borderline cases to the definition as they appear. A direct message to a parent may be a contact in one situation and a routine answer in another. The compliance office should decide, not the assistant who is trying to close a visit. Record the decision beside the definition so the next person can follow it. The list should grow slowly and stay readable.
Record time, channel, and participants
Every entry needs a date, a time, a channel, and the people involved. Use the athlete's full name and the staff member's full name rather than initials. Note whether a parent or guardian joined the call. These details answer the first questions a reviewer will ask, and a missing time can make two contacts look like one. A full name is easier to match against a staff directory.
Add a short subject line and the outcome of the contact. "Discussed camp schedule; athlete will confirm by Friday" is more useful than "called prospect." The outcome should describe what changed, not how the call felt. A log full of impressions is hard to audit and easy to misread. The subject line should be specific enough to search six months later.
Separate recruiting talk from compliance questions
Use one field for the recruiting substance and another for any compliance question raised. A conversation about a visit can include a question about a scholarship, an agent, or a disclosure. The compliance question should be routed to the right office and noted as pending. Mixing the two into one paragraph hides the item that needs follow-up. A separate field makes the open question visible at a glance.
Record who answered the compliance question and when. If the answer came later by email, link the message to the entry. A pending question should not disappear when the staff member changes. The log should show the question, the owner, the resolution, and a short note about the answer. A closed question with a written answer is a useful training example for the next hire.
Store the log where the office can find it
Choose a single storage location and restrict editing to the people who own the log. A shared spreadsheet can work if it has version history and a clear owner. A folder of individual documents usually fails because no one knows which file is current. The location should be backed up and accessible to the compliance office. The path to the log should be written in the office handbook.
Set permissions before the first entry, not after a problem. Recruiting staff may need to add entries, while only the compliance office can delete or correct one. Keep a change history that shows who edited each row. A log that anyone can quietly rewrite is not a reliable record. Access should be removed on the last day of employment, not at the end of the month.
Hand off the log with a written index
When a staff member leaves, ask for a handoff note that lists open conversations. The note should name the athlete, the last contact, the pending item, and the next date. Attach it to the log rather than sending it as a separate message. A new assistant should be able to read the note and know what to do first. The note should be short enough to finish during the transition.
Review the index with the compliance office during the transition. Identify entries with missing fields or unclear outcomes and fix them before access changes. A short transition meeting is cheaper than a later audit failure. The handoff is part of the log's life, not an afterthought. The outgoing staff member should also name the person who will answer follow-up questions.
Correct errors without erasing history
Use a correction entry instead of overwriting an old row. Note the original value, the corrected value, the reason, and the person who approved the change. This keeps the record honest and shows that the office reviews its own work. A clean history is more credible than a spotless table with no trail. The correction should be visible without opening a separate document.
Set a rule for how quickly a correction must be made. A same-day fix is ideal for a wrong date or a misspelled name. A substantive correction should go through the compliance office. The rule should be written beside the log so a new staff member can follow it. A correction that is made quietly is worse than an error that is explained.
Audit a sample every month
Pull ten entries each month and check them against the field list. Look for missing times, vague subjects, and open questions without an owner. Share the results with the staff in a short meeting. The goal is to fix the process, not to embarrass an individual, so the findings should be framed as questions about the form. The sample should include entries from every staff member who logs contacts.
At the end of the season, review the full log for patterns. A repeated missing field may mean the form is too long, and a repeated late entry may mean the workflow is wrong. Adjust the form and the training, then keep the older log unchanged. A log that improves each season is more useful than one that is replaced every year. The review should end with one or two concrete changes.
Sources
Related Articles
Coach Outreach
Build a coach response log that separates silence from a soft no
A coach response log for recruiting outreach that records channel, timing, and next action so a family can tell a slow reply from a polite decline.
Recruiting Support
Set a recruiting social media review checklist before a coach follows
A social media review checklist for recruits and families, covering account inventory, old posts, photo consent, comments, and a simple posting boundary.
Recruiting Support
Build a prospect data hygiene checklist for a recruiting database
A prospect data hygiene checklist for recruiting databases, covering record ownership, duplicate cleanup, field standards, contact verification, source notes, and archive rules.