Template A5
90-day integration plan
Eight fields that turn what you learned into a plan for your own team. Module 5 ends with this plan.
0 / 8 fields filled
Save or print your plan and put the review dates in your calendar today: a plan without booked dates is an intention.
Incomplete. Fill at least six fields for the plan to be usable.
Be specific about what already exists: most plans fail by ignoring the current workload.
Examples
- Grassroots football
- Grassroots youth football academy; 20 players aged 12-16; budget €1,200; paper sRPE logs + shared GPS pod.
- Para sport
- Wheelchair-basketball team; 12 senior athletes; national league; IMU stroke counts + weekly shoulder-pain scales.
If it cannot be answered yes or no by day 90, it is a theme, not a question.
Examples
- Grassroots football
- Can weekly sRPE-based load flags reduce avoidable overuse complaints this season?
- Para sport
- Can stroke-count + shoulder-pain monitoring catch overuse two weeks earlier?
Use the mean and SD you computed in Module 3.
Examples
- Grassroots football
- Weekly sRPE, monotony, ACWR (from sRPE), wellness. Flag: ACWR>1.5 or 2 wks wellness decline.
- Para sport
- Weekly stroke count vs 8-wk chronic, shoulder-pain (0-10), wellness, sRPE. Flag: pain >=4 or +1 SD strokes.
Start from the gaps your self-audit flagged.
Examples
- Grassroots football
- Guardian consent (minors), coach-only access, retain 24 months post-season (Template A1).
- Para sport
- Explicit athlete consent, medical+coach access, retention per club policy (Template A1).
Brief before the system runs, not after the first flag fires.
Examples
- Grassroots football
- Brief players + parents at season start; frame flags as 'modify, not punish'.
- Para sport
- Brief athletes; pain scales collected privately; framing as shared decision.
Day 30 is usually about compliance, day 60 about data quality, day 90 about decisions changed.
Examples
- Grassroots football
- D30: logs complete >90%. D60: flags reviewed weekly. D90: fewer overuse complaints vs baseline.
- Para sport
- D30: monitoring routine embedded. D60: 2 early flags acted on. D90: lower shoulder time-loss.
Book them now. A review that is not in the calendar does not happen.
The field most coaches leave blank, and the one that protects your credibility.
Examples
- Grassroots football
- Stop if logging burden causes drop-off or players show number anxiety.
- Para sport
- Stop if monitoring adds no decision value or increases athlete anxiety.
What you worked out in the modules
What you work out in the module tools appears here, and goes into the printed plan and the file: your baseline, your early-warning system, your governance audit and your reflections.
Delete what you entered here?
Review your plan
Read your plan field by field and rate each one. Be honest: the rating is for you, or for a colleague who reviews your plan in a course.
| In place | Partly | Watch for | |
|---|---|---|---|
| 1 Context analysis | States the sport, the level, the number of athletes, what is monitored today, the resources available and who is on the staff. | Names the setting, but says nothing about current practice or current workload. | Most plans fail by ignoring the current workload. |
| 2 PDCA question | One specific question that wearables will answer this season, and that can be answered yes or no by day 90. | A theme, or several questions at once. | If it cannot be answered yes or no by day 90, it is a theme, not a question. |
| 3 Metrics (3-5) + personalised thresholds for one named athlete | Three to five metrics, with personalised thresholds for one named athlete. | Metrics are listed, but there are more than five, or the thresholds are missing or not personalised. | Use the mean and SD you computed in Module 3. |
| 4 Governance statement (consent, access, retention) | Says how consent is obtained (from guardians too, for athletes under 16), who has access, how long the data is kept, and who owns each. | Covers consent, but leaves access or retention open. | Start from the gaps your governance self-audit flagged. |
| 5 Communication plan (athletes / parents) | Says how athletes (and parents, where applicable) will be briefed, and when. | A briefing is planned, but only after the system has started, or without saying how. | Brief before the system runs, not after the first flag fires. |
| 6 Success criteria at Day 30 / 60 / 90 | Says what will be true at day 30, at day 60 and at day 90 if the plan is working. | Describes success in general terms, or for day 90 only. | Day 30 is usually about compliance, day 60 about data quality, day 90 about decisions changed. |
| 7 Review checkpoints (calendar dates) | Calendar dates for review, booked, with the people who will sit in the room. | Intervals without dates. | A review that is not in the calendar does not happen. |
| 8 Stop conditions | Names what would cause you to stop or substantially change the plan. | A general intention to review if needed. | The field most coaches leave blank, and the one that protects your credibility. |
- The plan is usable when at least six of the eight fields are filled in, whether you rate them "Partly" or "In place".
- In a course, plans are reviewed by a peer in the cohort. On your own, review your plan within two weeks of writing it.
