Features
What the pilot does
A focused set of tools for one college club: fewer screens, every one of them backed by real data and permissions.
Recruitment
- Campaigns with per-person limits (for example one taster, two tank sessions)
- Capacity enforced atomically: two people cannot take the last place
- FIFO waiting list with expiring offers that hold the place
- Late-cancellation rules you choose, shown plainly to members
Crews and sessions
- Squads, crews and boats you define — novice, senior, anything
- Numbered seats with Bow and Stroke, coxes and reserves
- Coach, cox and bank-rider acceptance per session
- Favourites such as “M2 – Sandford” prefill everything except people's commitments
Head-coach confirmation
- Readiness lists every unresolved issue
- Confirmation applies to one exact plan revision
- Material changes withdraw it and say what changed
- Safety blockers and qualification gaps cannot be overridden
Substitutes
- Can't attend keeps the original selection on record
- Propose a substitute or let eligible members volunteer
- A coach approves; the place is never awarded twice
- Attendance credits the person who actually rowed
Races
- Multi-day events with per-day availability
- Fill all days, then edit exceptions
- Entry status kept separately from internal selection
- Links to the organiser's current instructions
Attendance and reports
- Mark the expected lineup present, adjust exceptions, finalise
- Rates with the denominator explained
- Benchmarks compared only within the same protocol
- CSV exports that match the underlying records
Deliberately not included
Payments, social feeds, automatic crew selection, live results, bumps calculations, GPS or wearable data, and a full maintenance system are outside the pilot.