Crew selection for New Zealand rowing coaches: seat racing, Maadi 1st VIII and the politics of the cut

Weighting the criteria before the seat race

Before a single pair goes out at Karapiro for the first round of selection trials, write down what each criterion is worth. A typical Maadi 1st VIII rubric across a serious NZ school programme weights the 2k erg around 25 percent (bodyweight-handicapped for lightweights), side-by-side pairs work around 30 percent, the seat-racing block in fours around 30 percent, and coach-rated technical scoring across the camp around 15 percent. The exact split is the coach\'s call. The discipline is locking it in before the testing starts, sharing it with the athletes at the start of the block, and refusing to retrofit the weights to the lineup you wanted. Selection that is defensible against an angry parent has the rubric on paper before the first test.

What makes selection hard in a Kiwi programme

The selection process itself is straightforward. Everything around it is where coaches lose hours, sleep, and occasionally the trust of the squad. Three recurring patterns show up in every programme I work with.

Every hour spent reconstructing the picture from messages and notes is an hour not spent watching the actual rowing. The companion guide on running training sessions efficiently covers the scheduling side of the same problem.

How Row HQ holds the selection workflow

Row HQ\'s crew assignment tool brings the confirmed availability for the next selection session, the erg history for every athlete in the squad, the previous round\'s seat-race times, and the saved lineups from last week into a single drag-and-drop view. Instead of stitching the picture together from four sources at ten on a Sunday night, the coach builds the next round\'s pairings from a shortlist that already has the relevant numbers attached, sees which seat-race matchups have not been run yet, and publishes the call to the squad in one tap. The rower gets a notification the moment the lineup lands.

Drag-and-drop pairings for a seat-racing round

Seat a rower by dragging the name into a position. Availability status sits on each name in colour (green confirmed, amber tentative, greyed out unavailable) so the cross-referencing stops and the "are you on the water Saturday?" messages stop with it. See the interface in the screenshot gallery.

Saved seat-race matchups and trial lineups

When a seat-racing round produces clear results, save the matchup so the same pairings can be loaded again later in the block under different conditions. Row HQ stores crew configurations and loads them back in a single click, so a Friday-morning matched-pairs session at Karapiro reproduces the previous week's pairings without anyone reconstructing them on the jetty. Useful for any pre-Maadi or NZURA regatta block, equally useful for a club development quad you are slowly building toward a Trans-Tasman trial.

Side, seat and capability tracking

Seats are not interchangeable. Row HQ lets you assign each athlete to a specific position with member preferences and capabilities visible as you build: who is rated to cox, who rows stroke side only, who has been working on bow-side technique for the last six weeks. The bit that matters in selection is being able to filter the squad by capability before the seat-racing round starts, so a stroke-side-only athlete is not accidentally seeded into a matchup that needs bow-side cover.

Selection principles that survive Maadi week

Software clears the admin. Coaching judgement still fills the seats. A handful of principles that consistently hold up across NZ school, club and university programmes:

• Lock the rubric before the first test: Write down what the 2k erg is worth, what side-by-side pairs is worth, what the seat-racing series is worth, and what coach-rated technique is worth. Share the rubric with the squad. Refuse to change it after a result lands. The rubric is what makes the selection defensible.
• Run the seat race like a controlled experiment: Matched conditions, matched rates, side-by-side over a fixed stretch, at least three swap rounds. One race is a data point. Three rounds with the same two athletes swapping across different combinations is a verdict. Capture every time. Attendance and session tracking over the full block makes the data hard to argue with.
• Treat erg scores as one input, never the whole story: A bodyweight-adjusted 2k is a useful filter for the initial shortlist. It is a poor proxy for boat-moving. Hamish Bond was not the fastest erg in the Rowing NZ squad through the mid-2010s and he won eight world titles in the pair. The erg metrics guide walks through how to weigh the test against on-water evidence.
• Honour the side and rig: A stroke-side-only athlete cannot be a swing seat. A heavyweight in the front pair throws the run. Height matched through the middle, the calmest rhythm in the squad at stroke, the steadiest hands at bow. The structural principles are not negotiable, even when they cost you a strong erg score.
• Announce in writing, never live: Row HQ pushes lineup notifications to every member in the crew the moment you publish. Send the call the evening after the block closes, brief any athlete affected by a change in person the next morning, and field the parent calls in a one-on-one rather than on the jetty.

What changes when the admin is automated

The time saving is the first thing every coach notices. The second is that the selection itself gets better, because the call is being made from data rather than from memory of the last good piece:

• Time reclaimed: Selection planning moves from a Sunday-night slog through four data sources to a focused review in front of one screen. The time recovered goes back to the coaching that actually moves boats.
• Better communication: Lineups go out as automatic notifications the moment they are published. No misread message, no rower who missed the group chat, no Year 13 finding out about their drop to the 2nd VIII at the same time as the squad.
• A defensible audit trail: Every seat-race time, every erg score, every lineup tried across the block is recorded. When a parent challenges the call, the rubric and the data are in one place. The call defends itself.
• Faster adaptations: A late withdrawal reshuffles in seconds. The coach adjusts the boat in the app, notifications go out immediately, and the seat-racing round still runs on time.

What Kiwi coaches report back is that Sunday-evening selection planning, which used to take an hour or more of cross-referencing the Google Sheet against the WhatsApp thread against the seat-race notebook, now wraps in around fifteen minutes. A late dropout shows who is available to fill the seat without sending a single message. See what coaches at Oundle Town Rowing Club found after making the switch, and use our free Concept2 erg tool when working through bodyweight-adjusted 2k splits in the selection rubric.

The Bond and Murray reference

Hamish Bond and Eric Murray are still the cleanest case study a Kiwi coach can point at when explaining what a real seat-racing process produces. Rowing NZ ran them against every plausible combination in the men's pair through the early 2010s, in matched-pair trials at Karapiro under controlled conditions, with the times recorded and the swaps documented. The pairing held under every test the system threw at it. Eight unbeaten seasons followed. The lesson for a school or club coach picking a Maadi 1st VIII or an NZURA Bond Cup boat is that the selection only earns the squad's trust when the process is visible, the conditions are controlled, and the rubric is locked before the testing starts. Do that work and the call you announce on the Friday evening before Maadi defends itself. Skip it and you are negotiating with parents on the jetty for the rest of the season.

The principles hold across every level of New Zealand rowing, from a small Otago club picking a senior four through to a competitive Saint Kentigern or Hamilton Boys 1st VIII heading into Ruataniwha for Maadi week: weight the criteria before the test, run the seat race like a controlled experiment, record the data, announce the call privately and in writing, and field the response in a one-on-one. See our pricing page for a plan that suits a Kiwi club or school, or check the FAQ for anything else.

Key Takeaways

• Lock the rubric before the first test of the selection block; refuse to retrofit the weights to the lineup you wanted
• Run the seat race like a controlled experiment: matched conditions, matched rates, side-by-side rigged pairs, at least three swap rounds
• Hamish Bond and Eric Murray are the reference point - a controlled pairs process produced eight unbeaten seasons
• Announce the call in writing after the block closes, never in the boatshed with the squad watching
• When a Year 13 is dropped from the 1st VIII, front-foot the conversation and find a real role in the 2nd VIII
• Ready to organise the selection block in one place? Get started with Row HQ today