What should a weekly athlete check-in include?
A useful weekly athlete check-in asks about the athlete’s recent experience, progress toward one goal, obstacles, upcoming demands, and the support they want. Keep the routine brief and explain who will read the answers. Its purpose is to start a conversation and agree on a next step.
A coach can see attendance and training results while missing the context behind them. A regular conversation gives the athlete room to describe that context in their own words. Start with a small routine that your staff can consistently review.
The template below is a coaching example, not a validated screening tool or a test of medical readiness. It does not determine whether someone is safe to train or compete.
Which five questions can a coach ask?
Use the same core questions each week so athletes know what to expect. Let them keep personal details private and offer a separate conversation when needed. Ask for information you can use within your role, rather than collecting details because a form has space for them.
- What went well for you this week? Invite a specific win, useful habit, or moment of progress.
- How did the week compare with the goal we agreed on? Discuss the plan without turning the answer into a character judgment.
- What made that goal easier or harder? Look for practical barriers such as travel, scheduling, or unclear instructions.
- What is coming up next week that we should plan around? Make room for school, work, competition, or changing availability.
- What support would be useful, and would you prefer to discuss it privately? Give the athlete a way to ask for a conversation without describing a sensitive issue in a shared space.
For example, “I missed two sessions because my work shift changed” leads to a different conversation from “I did not understand the plan.” The useful output is an agreed action, not simply another completed form.
How do you turn answers into follow-through?
Assign a named reviewer, choose a review window, and agree on one manageable next step with the athlete. At the next check-in, revisit that step before adding more goals. Never invite responses into a system that nobody is responsible for reading.
| Moment | Coach’s action | Useful output |
|---|---|---|
| Before the week | Explain the purpose and response window | Everyone knows what happens next |
| After responses arrive | Read responses and arrange appropriate follow-up | A conversation or a practical plan change |
| During the week | Check whether the agreed support happened | Accountability from staff as well as athletes |
| Next check-in | Review the previous action | A continuing conversation rather than a reset |
One example: an athlete wants to establish a more consistent routine during travel. The athlete and coach might agree on a realistic planning step for the next trip, then review whether it helped. This is an illustrative workflow, not a promised performance result.
What boundaries should the team establish?
Tell athletes who has access, why information is requested, how long it is kept, and how to get help outside the check-in. Do not promise absolute confidentiality if safeguarding or other duties may require escalation. A weekly check-in must not become the route for urgent concerns.
For medical symptoms, injury concerns, or mental health needs, follow the organisation’s established procedures and involve appropriately qualified professionals. A coach’s check-in does not replace clinical assessment. For youth teams, confirm age-appropriate consent, parent or guardian involvement, and safeguarding procedures before launching.
The IOC’s guidance on athlete mental health describes support as a shared responsibility across sport and highlights confidentiality concerns and role-appropriate staff education. That elite-sport guidance supports careful boundaries; it does not validate this five-question template.
Where does Kivi fit into a team routine?
Kivi connects software for habits, check-ins, and capacity with the people who support growth. A team should first define its coaching routine, then evaluate whether the software fits that routine. The discovery conversation is the place to confirm current capabilities, access arrangements, and implementation needs.
Compare Kivi for sports teams with Kivi for coaches. If you also need people to help deliver the program, explain that requirement rather than assuming software access includes a staffed service.
Bring your roster size, staff roles, current check-in process, and biggest follow-up problem. The athlete experience matters as much as the staff workflow: athletes should understand why taking part is useful to them.
Frequently asked questions
How often should coaches run a check-in?
Choose a cadence your staff can reliably review. Weekly is a practical starting example; travel, competition, and the team’s support procedures may call for a different rhythm.
Should athletes give a readiness score?
A number can invite discussion, but it should not independently decide medical readiness or participation. Establish an appropriate interpretation and follow-up process with qualified staff.
Should answers be shared with the whole team?
Do not default to public sharing. Establish appropriate access and explain it before collecting responses.
Can this template be used outside Kivi?
Yes. It is a general coaching conversation template. Evaluate any software separately against the workflow and privacy requirements of your organisation.
Build a team routine your staff can follow through on.
Bring your current check-in process to a discovery call with Justin. Explore whether Kivi software or a supported program fits your athletes and staff.
Book a discovery call ↗
Connect