Why schoolsRisk & duty of careImplementationPerformanceA season, reviewedYour staffWho sees whatThe coaching boardIntegrationsGet started

Implementation

Nobody has time
for another system.

So this one asks almost nothing. Thirty seconds a day from the athlete, nothing new to maintain for the coach, and a queue instead of a corridor conversation for your trainer.

What it costs your people, honestly

The daily ask, by role.

30sAthlete · daily check-in on her own phone
2 minCoach · glance at the squad board before a session
0New data entry for coaches — the board builds itself
1Trainer queue, replacing the informal corridor triage

Phased rollout

One sport. One season. Then decide.

We do not recommend a whole-school launch. Prove it on one squad where the AD already has a concern, and let the result make the argument.

ScopingSport, staff, your existing policyWeek 0
Baseline screenWhole squad assessedWeek 1
OnboardAthletes & families self-serveWeek 1–2
Staff walkthroughCoaches, trainer, nurseWeek 2
RunningDaily check-ins, re-screensWeek 3+
Season reviewThe expansion decisionEnd of season
1
Scoping call

Which sport, which staff, what your consent and student-records policy already says. We map to your policy rather than asking you to adopt ours.

Week 0 · 45 minutes
2
Baseline screening

The squad is screened — phone video for most, in-person where risk is elevated. This is the single session that requires real time from anyone.

Week 1 · one training slot
3
Athletes and families onboard

Athletes install and start checking in. Parents get their own view. No school admin time — invitations go out from the roster you already have.

Week 1–2 · self-serve
4
Staff walkthrough

One session each for coaches and for your trainer and nurse. Coaches learn to read the board; clinical staff learn the escalation queue and where the clinical line sits.

Week 2 · 60 minutes each
5
Running normally

Daily check-ins, warm-up protocols on the board, re-screens every four weeks. Your AD starts seeing programme-level patterns rather than incidents.

Week 3 onward
6
Season review

Availability, injury count, protocol compliance and the documented-decision record, against the season before. That review is the expansion decision.

End of season

What we hear first

The objections, answered plainly.

“My coaches will not use it.”

They are not asked to maintain anything. The board is built from the athletes’ check-ins and the screening data. A coach who ignores it entirely still benefits, because the trainer is seeing the flags.

“We do not have an athletic trainer.”

Then the escalation routes to your school nurse, and the referral path goes to your named external provider. Schools without a full-time trainer usually gain the most, because there is currently nobody watching between incidents.

“Parents will use it to argue with coaches.”

The opposite happens. Parents currently argue because they cannot see anything. Given the same picture as the coach, the conversation stops being about whether something is real.

“Our students will not log honestly.”

Some will not, at first. The pattern shifts once they see that an honest low score changes the plan rather than getting them benched. Silence is handled too — no check-in means the day sits at Hold, never Push.

“We already have an injury-report system.”

Then you have a record of injuries that already happened. This is the layer before that — the weeks of signal that precede the report.

“This sounds like a technology project.”

There is no integration required to start. No SIS work, no IT project, no hardware. If you can email a roster, you can run the pilot.

Start small on purpose

One squad is enough
to know if this is real.

Pick the sport where you already have a concern. A season is a short enough experiment and a long enough proof.