Squads

A squad is a named group of athletes. Squads are how you assign gym plans to a group at once and how you track whether that group is actually doing the work.

Who can use it: everyone can view squads. Creating, editing and managing membership is for admins and coaches.

The squads list

The Squads page shows your active squads — name, description, member count and when each was created — with archived squads tucked into a collapsible section below. Click a squad to open it, or use New squad to create one.

Inside a squad

The squad detail page has two jobs:

• Manage membership. The members list shows who's in the squad and when they joined. Add players from the searchable list of available athletes, or remove them. Changes apply immediately.
• See upcoming work. The next seven days of assignments for the squad are listed, each linking to its assignment detail.

From here, coaches can edit the squad's name and description, or archive it when it's no longer in use (archiving keeps the history; it doesn't delete anything).

Engagement

Click View engagement to open the squad's engagement heatmap — is each player interacting with the programme? It covers up to four dimensions, switched with the All / Field / Gym / Jumps / Wellness filter (only the features your org has enabled appear; the percentages always follow the active filter):

• Field (always on) — attendance at scheduled training, matches and fitness tests, inferred from GPS data. Round chips: ✓ attended (GPS data inside the scheduled window), ✕ expected but no GPS data, — excused (player marked unavailable), ○ upcoming / awaiting ingest. Several events in a week collapse to an attended/expected count.
• Gym — assignment adherence. Square chips: ✓ completed, ⚠ started but not finished, ○ flexible window still open, · assigned but not started.
• Jumps — participation on jump-test days. A test day the org actually held (a Chronojump import exists for that date) counts as an expectation for every member: ✓ tested, ✕ no result recorded, — excused, ○ awaiting results. Several jump types on one date are a single test day.
• Wellness — daily check-in rate, shown as ✓ / · per day (or a checked/possible count per week). Check-ins are voluntary, so missed days are never red, today only counts once a player has checked in, and the rate stays out of the headline % — a month of daily check-ins would otherwise swamp the handful of sessions in the denominator.

The headline engagement % is field + gym + jump tests (the event-like expectations). In the All view, jumps and check-ins appear as summary columns beside the percentage rather than extra chips in every cell.

Sort by engagement to push the athletes who need a nudge to the top, set the date range, and click any cell to jump into the underlying GPS session, gym session, or assignment.

A few honesty notes on the field half:

• "No GPS data" is not proof of a no-show — it can also mean no pod was worn, the pod failed, or the data hasn't been ingested yet.
• Athletes with no StatSports mapping show a no GPS link badge and aren't counted against field attendance at all.
• By default every schedule event counts for every squad. If your club runs several squads, set the Squad field on a schedule event to scope it to one squad only.

Players marked unavailable (injured, ill, away…) are excused from field sessions and jump tests from their unavailability start date — unless they took part anyway, in which case it counts.

Engagement is a coach/admin view — it spans the whole squad, which players aren't permitted to see.

Related

• Gym plans — how assignments get created and overridden.
• Session templates — the workouts you assign.
• Athletes — the per-player view.