Build and publish training programmes

A programme is the work players do in their own time: a return-to-training block, an in-season top-up, a pre-season prep. You build it once, with a demo video behind every movement and a prescription for every set, and publish it to one or more squads. Publishing is the moment this module reaches into a whole squad's phones at once, so it's worth knowing the full arc before you start: the library, the block, the send, and the board that tells you whether the work happened.

What the work costs each week is the other half of the job, covered in Monitor player load.

• Programmes live under Programmes in your sidebar. The page has two tabs: the programmes themselves and the Exercise library.
• A programme isn't tied to a squad. Name it after the block ("Return to training"), and assign it to as many squads as need it.
• Nothing reaches a player until you publish, so draft freely.

Every movement you prescribe comes from the library, so a well-kept library makes every future programme quicker to build. Each exercise has a name, a category, a YouTube demo (any YouTube link works) and the coaching cues players read under the video.

• Diagrams. For a drill a picture explains better than a video, Upload diagram takes a PNG, JPG or WEBP up to 5MB. Save the exercise first. Once a diagram is attached the button becomes Replace diagram, with Remove beside it.
• Retiring a movement. Archive under Archive this exercise stops it appearing when you pick movements. Programmes already using it keep working, and Restore brings it straight back, so there's no risk in tidying up.

dashboard.clubhouseapp.com.au

— enlargeExpand

1. Create it. New programme (or Build a programme on an empty list) asks for a Programme name, and Create and build opens the builder. To build on last block's work instead, use Duplicate on any programme's row menu. It copies the sessions, prescriptions and targets into a new draft called "U16 in-season strength block (copy)", with no squad assigned.
2. Set the length and the notes. In Programme settings, choose how many weeks it runs (1 to 52) and write the Notes for players: the suggested week, the intent, the one thing you want them to get right. Players aren't locked to days, so treat it as guidance.
3. Add sessions. Each session is Strength (exercises with sets, reps, RIR and rest, supersets and optional alternatives; drag an exercise to change its order, and the A1/B2 labels follow) or Conditioning (sets, distance and rest for each week, with pace, heart-rate targets and an optional route diagram). Progressions live inside the session, so you don't need a copy for every week.
4. Check the targets. A target is added automatically with the first session of each type, and it counts every session unless you loosen it to At least a number. Targets are what the Compliance tab measures against, and a minimum met counts as met: four of six against a target of four is on track.
5. Decide on the bodyweight check. Weekly bodyweight check in Programme settings gives adults a Monday morning prompt. Only they, you and medical staff see the number, so it's a trend line for the player, never a squad table.

The full builder reference is in the programmes answer.

Assign this programme opens Who is doing this. Under Who, choose Whole squad or Specific players and pick the squad. Then set Starts (week 1 begins on this date) and Targets by (the last day the programme counts), and press Assign. The assignment now shows as Not published, and players still see nothing.

For a whole squad, membership stays live. A player who joins the squad in week 2 picks the programme up, and a player who leaves stops being reminded. If the squad has Wearables switched on, players can attach a run from their watch; if not, the panel tells you their runs will be self-reported.

Choose Specific players for work only some of the squad should do: the goalkeepers' block, or a player carrying a niggle. The squad's players are listed by position with Goalkeepers first, then the outfield lines, then No position for anyone without one. A group heading ticks or clears the whole group, so "everyone except the keepers" is Select all, then untick Goalkeepers. The button counts who you picked: Assign to 2 players.

• Doing both. A player on a squad programme and a specific-players one is expected to do both. The list shows On: and the other programme's name beside anyone already on one, and the confirm window says so again.
• Not on the app. A player without their own login yet is marked Not on the app. You can include them, but they won't see it or get the notification until they sign in.
• The list is fixed. It doesn't follow the squad, so a player who joins later isn't added by itself. The row says how many of the squad's players it leaves out, with Add players beside it.

Change players on the row edits the list at any time. On a live programme, adding someone new opens a confirm window naming only the players who'll be notified, with a button like Add and notify 1 player. Taking a player off sends nothing: the programme leaves their phone and their logs are kept. A player who has left the squad stays on the list, marked Left and the squad's name, until you untick them.

Strength & conditioning is switched on or off per programme, under Settings → Modules & Programs. A squad whose programme has it off isn't offered in the picker. A draft already assigned to one keeps its dates and can still be finished, but Publish and notify stays greyed out, with a note saying why, until it's switched back on.

dashboard.clubhouseapp.com.au

— enlargeExpand

With a squad assigned, the status line at the top of the builder reads Ready to publish. Review and publish opens Who is doing this again, and Publish and notify on the squad's row brings up the confirm window before anything is sent:

dashboard.clubhouseapp.com.au

— enlargeExpand

The window is built to make a wrong send obvious before it happens. Publish to BYL U16? names the squad, with the programme, its dates and the head count underneath. For specific players it lists each player by name instead. It lists what will happen, starting with "The Workouts tab appears on their phones, with every session, the demos, and somewhere to record what they lift." It shows the notification word for word. And the button names the head count: Publish and notify 15 players. Not yet backs out without sending anything.

Three things worth knowing about the window:

• A programme with no targets says so. The window adds "This programme has no targets, so players get no progress bars and the Compliance tab cannot measure the squad." You can still publish, but you'd be running a block you can't measure.
• Late at night it warns you. Between 9pm and 6am Sydney time the window adds a line such as "It is 11:19pm in Sydney. Most phones silence notifications overnight, so players may not see this until morning." The notification is still sent the moment you publish. If you want players to notice it, publish in the morning instead. The same line appears when you add players to a live programme overnight.
• Editing after publishing is fine. Players who have already opened a session keep the version they started.

A squad with nobody in it yet publishes without a head count, and nobody is notified. If the send fails, the error stays inside the window with the chance to try again.

Every player in the squad who has their own Clubhouse login and hasn't muted programme notifications gets this, from the example above:

U16 pre-season prep is ready 3 sessions over 4 weeks, with demos and somewhere to record what you lift.

Parents aren't sent it. Your club also needs programme notifications switched on for S&C; if they're off, the programme still goes live but nobody is notified.

The notification is only the announcement. What matters is the Workouts tab, which appears at the front of Health on the player's own login. Here it is on Milan's phone, four weeks into a U13 block:

— enlargeExpand

Players see your notes, the week's sessions with what each involves, a demo behind every movement, and a place to log every set. When they finish, the last step has a Something feels off box. Ticking it sends their note to you and the physio, and nobody else.

A player with notifications off still finds the tab the next time they open the app. The message after you publish tells you which happened. It counts the players notified, or, when nobody has notifications on, says Nobody has notifications on yet, so they will see it next time they open the app.

When some players couldn't be reached, the same message names them, so you know who to tell in person:

• "Josh Ellis has no notifications set up, and will see it next time they open the app." They haven't allowed notifications on any phone yet.
• "Sam Lee has Workout Reminders turned off, so was not notified." They have muted programme notifications themselves.

Up to three players are named. Past that, the message gives a count instead, such as "4 players have no notifications set up, and will see it next time they open the app."

Read the player's side once before you publish your first block: Do your workouts walks through it. The squad's own coach follows the same block from their angle in Keep workouts on track.

The programme's Compliance tab shows every player against every session, week by week, with their progress towards each target and when they last trained. The headline gives you the count on track, behind and with a niggle, and the Show filter goes straight to the exceptions: Behind target, Niggle flagged, Nothing logged in 7 days and No longer in the squad.

dashboard.clubhouseapp.com.au

— enlargeExpand

Three things matter more than the grid itself:

• Niggles. When a player ticks Something feels off, you and the physio each get a notification with their note, and the board marks the session. The squad's coach sees the session as Stopped — niggle but never the note.
• Watch-verified runs. A run recorded on a player's watch carries a watch icon. Everything else is self-reported, which is the honest description of training done alone.
• Silence. Seven days without a log is worth a conversation, whatever the reason. Kai Nguyen and Kai Petrakis are flagged in red above for exactly that.

Tap a player's name for their own panel: sessions done, last activity, open niggles with their notes, the week-by-week log, and their weigh-ins if they're an adult. The footer states the privacy deal for the whole tab: "Staff only. Players see their own progress and never each other's."

A block finishes on its target date. From the next day it shows Finished with that date, in Who is doing this and on the programmes list, where a programme whose every block has ended moves under Finished, however many sessions are still unlogged. It stays on players' phones for 14 more days as a single compact row, so a session done before the end can still be logged to its day, then drops off by itself. The Compliance tab keeps every finished board, so you can read who did the work after the block has gone.

• Take off their phones on a finished row in Who is doing this removes it before those 14 days are up. Everything they logged is kept.
• Finish for this squad (or Finish for these players) does the same for a block that is still running. It goes from their phones straight away, and nobody is told why.
• A programme that has never been assigned can be deleted outright with Delete programme. There are no player logs to lose, but it can't be undone.
• A programme that has run gets Archive programme instead, including one whose blocks have finished but are still on phones. Archiving takes those off phones in the same step, and the confirm says whose. The squads that ran it keep their logs, and you can bring it back from the Archived filter with Restore, which returns it as a draft. Restoring doesn't put a block back on anyone's phone.
• A programme still running, or lined up to start, offers neither. Finish it for that squad first, or wait for its target date.

• The block shows Live for every squad that should have it, not Not published. Once its target date has passed it shows Finished instead.
• You've read the notification and seen the Workouts tab from the player's side.
• Every niggle got a reply the same day. That's what keeps players reporting them.
• The Nothing logged in 7 days filter is empty, or you know why it isn't.