Create a source-preserving entry check for athlete intake

Published October 27, 2026

A grounded sports recruiting support note for recruiting agency owners: athlete intake with explicit evidence, decision rights, and a verified close.

Most athlete intake problems in sports recruiting support start before the work is done: the request is accepted without a source, a deadline, or a clear boundary around what the operator may change. If the destination record is wrong, the team may send a correct-looking update while recruiting agency owner still sees the old value in the recruiting CRM. Treat the athlete intake as a closed loop rather than a message: every action needs a source, a boundary, a destination, and a time. The risk is highest when the recruiting CRM looks current but the athlete intake behind it was never opened.

The risk around athlete intake is not that staff forget a task; it is that the record can look complete even when the coach outreach list was never checked against the athlete database. If the destination record is wrong, the team may send a correct-looking update while athlete still sees the old value in the athlete database. Make the queue owner visible for every athlete intake item, and give that owner the authority to pause the work when the evidence is not enough. The operator should be able to point to the exact field in the athlete database that will change, not only to the message that requested the change.

If coach supplies the instruction, keep the instruction and the underlying coach outreach list together rather than replacing one with a summary of the other. If the coach outreach list contains sensitive data, store it in the approved location and record only the minimum reference needed for the athlete intake review. If the coach outreach list is incomplete, the safest next step may be to pause athlete intake rather than fill the gap with a plausible assumption. If the coach outreach list contains personal or confidential data, use the approved access path and record only the reference in the queue.

For athlete intake, the governing source is the coach contact list; a note in the queue is only a pointer to that source. Keep the original roster update and the corrected version side by side, with the reason for the change and the person who approved it. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the coach contact list. A source that cannot be opened by the reviewer is not a usable source, even if the operator can see it on their screen.

For athlete intake, the governing source is the camp registration system; a note in the queue is only a pointer to that source. The reviewer should be able to open the camp invitation from the case without searching a personal drive or asking for a screenshot. When the conflict affects incomplete compliance packet, escalate before changing the destination record so the decision is visible outside the queue. Keep the camp invitation in the approved repository and link it to the athlete intake case instead of attaching it to a personal message.

Write the athlete intake boundary in plain language: which systems the operator may touch, which fields may change, and which questions must go back to recruiting agency owner. The boundary should be visible to the requester as well, so a request for athlete intake does not become a promise the operator cannot keep. The approval record should point to the roster update that was reviewed, not only to the request that started the work. When the operator is unsure whether a change is preparation or judgment, the safe default is to pause and ask.

Name the role that can approve athlete intake before the work begins; a shared inbox can receive the request, but it cannot own the decision. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. Record the approval in the athlete intake case with the approver, the time, the scope, and the evidence reviewed. For high-risk athlete intake work, require a second reviewer who is not the person who prepared the packet.

Use the same athlete intake queue for new work, corrections, and reopened cases so the daily count reflects the real load. At mid-day, check the athlete intake items that have no next action; those are the ones most likely to age silently. Close the day by checking that each completed athlete intake has a destination update in the camp registration system and a confirmation for the requester. Use the same athlete intake status values across owners so the daily count means the same thing to everyone.

The daily athlete intake routine should begin with a queue count by owner and age, not with the easiest request in the inbox. When the next step belongs to compliance adviser, write the request and the due time instead of leaving the case in a waiting state. Before the shift ends, reconcile the athlete intake queue and write a carryover note for every item that is still open. If the queue is too large to review, split it by risk or channel rather than sampling only the newest items.

If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new athlete intake work. Keep the athlete intake case note short enough to read during the day and specific enough to survive a weekly review. Leave the next shift a queue that can be worked without reconstructing the day from chat history. At the end of the day, compare the open queue with the morning list and explain every unexplained difference.

Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. An escalation that ends in silence should remain open; silence is not approval. When the source is unavailable, do not substitute a familiar value from an earlier athlete intake; stop and record the gap. When a case is blocked by access, record the system, the role requested, and the person who can grant it.

When duplicate outreach is involved, use the highest escalation path even if the athlete intake request looks routine. An escalation packet should include the athlete intake link, verified facts, the unresolved decision, the deadline, actions already taken, and the safest next step. If access is wrong or unexplained, stop the athlete intake work before opening the highlight repository with borrowed credentials. The escalation packet should be short enough to read on a phone and complete enough to decide without a meeting.

When ineligible contact is involved, use the highest escalation path even if the athlete intake request looks routine. The packet should state what the operator did not do and why, so the owner can see the boundary that was preserved. When the request conflicts with policy or the approved scope, the operator should route it rather than negotiate a workaround in the queue. A stop-work decision should be visible to the requester so they know why the athlete intake work is paused.

The close condition should name the field, the expected value, the approver, and the time of the final check. If the destination value differs from the approved value, keep the case open and route the variance. If the update fails or the requester disputes the result, reopen the athlete intake case and link the new evidence to the original record. If the final value differs from the approved value, record the variance and the person who accepted it.

The close condition should name the field, the expected value, the approver, and the time of the final check. The reviewer should be able to trace the athlete intake from the original request to the final field without opening a personal inbox. If the correction affects ineligible contact, notify compliance adviser before the next dependent action. If the final value differs from the approved value, record the variance and the person who accepted it.

Pick the sample from the recruiting CRM, not from the cases the team remembers, so the review is not biased toward easy work. Report open cases by age and dependency, not only the total, because a stable total can hide an aging tail. If the gap is caused by an unavailable recruiting agency owner, add a backup decision path rather than letting the athlete intake queue wait indefinitely. Track the number of sampled cases, the number with missing evidence, and the number reopened after review.

Keep the sample small enough to finish and large enough to expose a repeated gap. Use the correction log to estimate rework, and separate corrections caused by source errors from those caused by judgment. If the gap is caused by an unavailable athlete, add a backup decision path rather than letting the athlete intake queue wait indefinitely. Track the number of sampled cases, the number with missing evidence, and the number reopened after review.