Search "basketball return to play protocol" and you'll find the same staged progression on every sports-medicine site: rest, then light activity, then non-contact practice, then full-contact practice, then competition. It's good clinical guidance, and it ends exactly where a coach's real problem begins. The handout doesn't say how many minutes a player should get in their first game back, how that number should climb over the next three games, or who's responsible for making sure a well-meaning coach doesn't forget the plan in the fourth quarter of a close game. That part is left to memory, and memory is exactly what breaks down when a game is tight and a player who's been cleared says they feel fine.
Clearance is a green light, not a number
"Cleared to return" from a doctor or athletic trainer means the medical progression is done — it doesn't mean a player should go from zero minutes to a normal 24-minute workload in one game. Most clearance notes say nothing about pacing because that's a coaching decision, not a medical one. Without a written plan, that decision defaults to feel: the player looks good in warmups, the game is close, and the cap that existed in someone's head three days ago quietly disappears by the second half.
What an actual minutes progression looks like
A usable plan is specific and short — not a philosophy, a schedule. Something like: game one back, a hard cap of 10 minutes split across two stints with a mandatory check-in at halftime; game two, 15 minutes if there's no reaction; game three, 20 minutes and a return to a normal rotation spot if the player reports no soreness the next day. The exact numbers depend on the injury and the clearance, but the structure matters more than the specifics: a cap per game, a condition for raising it, and a built-in checkpoint before the next game is scheduled.
Track the plan against the actual minutes, not just whether they played
A box score tells you a player logged 14 minutes. It doesn't tell you whether 14 was the plan or a number that crept up because the bench was thin and the fourth quarter got close. The only way to catch the gap between the two is to write the planned cap down before the game and compare it to what actually happened afterward — not as a gotcha, but because the pattern of "plan said 12, actual was 19" repeated twice is the thing that gets a player hurt again, and it's invisible if the only record is a final-score box score with no plan next to it.
The handoff between trainer, coach, and parent is where plans die
A return-to-play plan usually gets handed off verbally — the athletic trainer tells the head coach, the head coach mentions it to the assistant running the bench that night, and the parent hears a version of it secondhand. Three games later, nobody has the same number in their head anymore, and the player who's asked "how are you feeling" after every practice says "fine" because that's what players say. A plan that only exists as something someone remembers telling someone else isn't a plan by the second week back — it's a rumor with good intentions.
A record also protects the decision, not just the player
If a player re-aggravates an injury and a parent asks whether the team rushed them back, "we were careful" is not an answer anyone will accept without proof. A dated log showing the planned minute caps for each game, what was actually played, and that the progression stepped up gradually rather than all at once is the difference between a coaching decision you can defend and one you can only describe from memory after the fact.
That's the same minutes and game-stats tracking HoopVault already gives you for rotation decisions, applied to a return-to-play plan — log the planned cap next to the same per-game minutes you're already recording, so a quiet overage shows up before it becomes a setback instead of after. Track return-to-play minutes in HoopVault — free to browse, no card required.