All guides

Director guide

For directors of sport and heads of programme

about 10 min to read

You decide what 'development' means at your club: which physical tests matter, what skills you're building, what a report contains, and what you ask athletes every day. Set that up once and every coach works to the same standard.

1.Set up your sport

Do these in order — later steps depend on earlier ones. An hour here saves a season of inconsistency.

  1. 1

    Positions

    The positional roles in your sport. They drive position-specific reporting and squad views.

    Open /settings/positions →
  2. 2

    Fundamentals

    Your skill curriculum — the technical and tactical qualities you develop, grouped into categories.

    Open /settings/fundamentals →
  3. 3

    Physical tests

    The metrics you actually measure, with units and whether lower is better. Add benchmark standards so scores mean something.

    Open /settings/metrics →
  4. 4

    Reporting periods

    Terms, seasons or your own periods — this is what reports and testing are grouped by.

    Open /settings →
  5. 5

    Report templates

    What a report contains and who fills each part. Build it once; every coach uses it.

    Open /settings/templates →

2.Decide what you ask athletes daily

Monitoring is only as good as the questions. Keep the daily check-in short — five questions answered honestly beats fifteen answered on autopilot.

  1. 1

    Build the daily template

    Sleep, soreness, mood, energy — or your own. Add the body map if you want players marking exactly where they're sore.

    Open /monitoring/setup →
  2. 2

    Switch each team to Live

    In Monitoring → Setup → Team assignments, set every team that's using check-ins to Live. Until you do, its players get no reminders and its coach gets no morning digest — so a team nobody has set up never sends email.

    Open /monitoring/setup →
  3. 3

    Explain why you ask

    Every question has a 'why we ask' note that players see. Filling these in noticeably improves the quality of answers.

  4. 4

    Vary it by day

    Assign a different template on match days or rest days — day types follow the planner automatically.

  5. 5

    Priming and reflection

    Separate short templates for before and after a session, if you want that level of detail.

3.Teams and people

  1. 1

    Create teams

    Squads within your sport, each with a coach.

    Open /settings/teams →
  2. 2

    Add players

    One at a time, or import a spreadsheet of a whole squad. Players can belong to more than one sport.

    Open /players →
  3. 3

    Invite coaches

    Coaches see only the teams they coach. Directors see everything in the sport.

  4. 4

    Parental consent

    For younger athletes, consent requests go to parents and are tracked for you.

4.End of the year

Squads change every year. Do it in this order and no history is lost — team history, attendance and training load all stay with each athlete.

  1. 1

    Archive last season's teams

    Players → Teams → Archive. Archived teams keep everything but leave the pickers and stop check-in emails. (Teams with training history can't be deleted — archiving is the way to retire them.)

    Open /players/teams →
  2. 2

    Start a new school year

    At the bottom of Players → Teams. Moves every current player up a year group across the organisation, and can mark your top year as leavers in the same step. It runs once a year.

    Open /players/teams →
  3. 3

    Mark other leavers

    On the roster, tick anyone else who has left and choose Mark as left. They come off their team, stop getting emails and can't sign in; their records are kept, and you can reinstate them.

    Open /players →
  4. 4

    Build the new squads

    Create the new teams, then in Squad Assignment filter to an old team, tick everyone carrying on and move them in one go.

    Open /players/teams →

5.Turn features on and off

Modules stay hidden until you switch them on, so coaches aren't wading through things your programme doesn't use.

  1. 1

    Per-sport features

    GPS imports, match-day coding, training reviews, golden goals, benchmark groups — enable only what you'll use.

    Open /settings/features →
  2. 2

    Start small

    Daily check-ins, sessions and reports first. Add the rest once coaches are in the habit.

6.Seeing the whole programme

  1. 1

    Analytics

    Squad-wide test results, comparisons and progress across your sport.

    Open /analytics →
  2. 2

    Testing days

    Enter results for a whole squad in one grid — they save as you type. Running a test more than once? Set Trials per test: every trial is kept and the best one counts.

    Open /testing →
  3. 3

    Benchmarks

    Compare against your own cohorts, or — where your club belongs to a wider group — against comparable clubs, always as aggregates.

7.Your responsibilities

You're holding data about young people. The tools are here; the judgement is yours.

  1. 1

    Audit log

    Every time a staff member views or exports a player's data it's recorded, and you can see it.

    Open /settings/audit →
  2. 2

    Data requests

    Export everything held on one player — for a parent request — or your whole organisation.

  3. 3

    Retention

    Optionally erase players who have left after a period you choose. Off by default; it only ever touches players marked as left.

  4. 4

    Who sees what

    Coaches see their teams. Parents see published reports only. Players see their own data.