Run a testing phase

A testing phase is a window (pre-season, mid-season, end of season) where you run the same physical tests across every squad. One phase gives you numbers. A season of consistent phases gives you trends, and trends are what let you show a coach that a player has genuinely moved. This page runs one phase from set-up to reading the results.

Starting testing for a new season? Testing reads No testing phases for 2027 yet until you create one, and Reports reads No data available until a phase has results. Both are the start, not a fault. Work through it in this order.

1. Set your battery and targets under Test Settings. See Get started with S&C.
2. Create the season's phases, under Create the phase. With templates set up, one button creates the lot.
3. Record the first phase on the day, under Record results on the day.
4. Chase the gaps and close it, under Chase the gaps and close the phase.
5. Read the results, under Read the results. One phase gives you numbers; the trend charts need a second.

dashboard.clubhouseapp.com.au

— enlargeExpand

• Your default battery and age-group targets should already be set under Test Settings. See Get started with S&C.
• Name phases on a pattern ("Pre-Season 2027", "Mid-Season 2027") so trend charts read cleanly across years.
• Test at least at pre-season and the end of the season. A mid-season phase is what turns two points into a direction.

Everything starts from Testing, titled S&C Testing. The Season picker switches years. Pick next year and a note confirms you're planning: phases you create "stay out of the way until that season starts."

There are two ways to create phases:

• From your templates. While a season has no phases yet, and you have templates set up, the page offers Generate phases from templates. It lists the phases it will create from your Season Phase Templates. Each starts with your default battery, with dates left open until you set them.
• One at a time. New Phase opens a two-step form. Details first: the name, the phase type (Pre-Season, In-Season, Mid-Season, End of Season or Ad-Hoc), an optional Test Date and an optional Expected Month, which families see as the rough timing when there's no date yet. Then Tests, with your default battery already selected, which you can adjust for this phase before Create Phase.

The phases answer covers editing and deleting a phase.

Open the phase. Until it has results, it offers three ways to get them in: Live Testing, Manual Entry and Import from Spreadsheet.

Live Testing is built for the testing session itself. Choose a squad and a test, press Start Testing, and work down the line:

• Each result saves as you go, and Save & Next moves to the next player.
• Mark as Absent records who wasn't there, so an absence is on record rather than a blank. The button changes to Marked Absent — tap to undo, so a late arrival costs one tap.
• The header counts how many players in the squad are done, for example 12/15 complete. You can leave at any point and pick up where you left off with Resume Testing.

Manual Entry is a grid of every player against every test, with a squad filter. Nothing is kept until you press Save Results, which suits a clipboard session typed up that evening.

Import from Spreadsheet takes a CSV or Excel file in four steps: upload, match your columns to the tests, preview, and import. Download template CSV gives you a file in the right shape. In the preview each row's player match reads Exact, Fuzzy or No match. Check the fuzzy ones carefully before you import, because they're brought in as matched, while rows with no match are skipped.

The data entry answer has the detail on each method.

dashboard.clubhouseapp.com.au

— enlargeExpand

Once results are in, the phase shows them grouped by age group, with a Squad filter, a player search, Export CSV for the raw numbers and Edit Results for corrections. An age group missing from the list hasn't been tested yet, so the list is also your chase list. A phase where two squads never got tested weakens every comparison in Reports, so testing every squad matters more than anything else here.

On the Testing list, a phase with some results reads Partially Complete. When the last squad is in, open the phase and press Mark Complete: it reads Completed, and the Resume Testing prompt goes away. That's the signal the phase is ready to read. Completing a phase doesn't lock it. Edit Results still works, and if a squad turns up a week late, Reopen Testing puts the phase back to work.

The numbers live on the phase; the reading happens in Reports, one programme at a time, across four tabs:

• Squad Summary. Each age group's average for every test, coloured against your targets: green when it's more than 5% better, amber within 5% either side, red when it's more than 5% worse. If a whole age group sits well to one side, check the target before you decide the group is unusual.
• Players. The per-player table, with a link to each player's S&C profile.
• Trend Analysis. One test across phases, with a card for each squad marked Better, Worse or Stable from the first phase to the last, and the average and number tested in every phase. It needs at least two phases, and it tells you when the players tested in the first phase and the last differ ("Uneven testing between first and last phase"), so a roster change can't pass for a fitness gain.
• Insights. Observations written from the data, grouped under Needs attention and Worth knowing.

The reports answer and the trend analysis answer go deeper.

As soon as results are entered, families find their player's numbers in the app under Health, on the S&C tab. Nobody is notified, so let the squad know when a phase is done, and add the context the numbers can't: what they mean for the player's training.

• Every squad in the phase is tested, or you know which ones are outstanding and why.
• Results went in during the testing window, not reconstructed weeks later.
• The phase is marked Completed before anyone reads it in Reports.
• Your technical director has seen the trends, and at least one training decision changed because of them.