1. Home
  2. Work
  3. Rowing Coaching Hub for a School Program

Case study

Rowing Coaching Hub for a School Program

A coaching hub that replaced the roster spreadsheet, the weekly WhatsApp plan and the PDF calendar for a school rowing program, used daily by coaches since October 2026 and designed so the school can run it themselves.

The problem

A school rowing program with twelve to sixteen volunteer and part-time coaches ran on a weekly roster spreadsheet, a WhatsApp message from the head of rowing with the week's plan, and a PDF calendar. Nobody could see which sessions had no plan, who was away, which boat was out for repair or what the lake conditions would be at 6 am. Coaches are not going to install and learn a complex app, so whatever replaced the spreadsheet had to be simpler than the spreadsheet.

What we built

  • RosterWeekly grid with coach status (confirmed, tentative, away), a drag-and-drop roster builder, copy-last-week, clash checks and the week exported as a picture or PDF.
  • Session plansA plan-builder wizard and drag-to-reorder editor, with an eight-step training "spine" for each squad.
  • Drill libraryAbout 302 drills, including 107 land and ergometer items and 54 games, each tagged with the fault it fixes.
  • MessagesEvery coach automatically receives tomorrow's session plan at 6 pm. The director gets a 4 pm warning about sessions with no plan.
  • Crew boardsBoards that match the shed whiteboards, imported from photos of the real ones: drag or tap rowers into seats, swap, save line-ups.
  • Boats and repairsA boat register and a repairs log with a history for every item.
  • Erg testingUpload a results sheet; per-rower history, split graphs and repeat pieces, visible only to the squad's own coaches.
  • ConditionsLive Bureau of Meteorology observations from the nearest airport plus an Open-Meteo forecast for the lake, a wind chart and a cancel-or-change-and-notify flow.

Coaches use it as an installable phone app (a progressive web app) with Web Push notifications, with WhatsApp share links as a fallback. They are invited by mobile number with one-time links, so there is no SMS provider and no password to forget. Daily snapshots keep each day's plans unedited as a history. Rowers appear as first name and initial only; there are no athlete or parent logins.

Design that coaches would actually use

The first version looked like software. The client's honest reaction was that coaches would not use it. We iterated: identity fonts, a real colour system, an app shell with a desktop sidebar and phone bottom tabs, proper cards and buttons, screenshots at every width in both light and dark themes. Several rounds later it looked like a product, and adoption followed. That lesson, iterate on design until it is good rather than delivering it once, now applies to everything we build.

Stack, cost and handover

Django 6 with PostgreSQL on Render (a Singapore web service and a fifteen-minute cron), Cloudflare DNS and plain CSS with no framework, chosen deliberately so the school can maintain it. Running cost is about US$13 a month. A 121-test suite covers the roster, plans, messaging and permissions. The school will own the system, and a handover checklist is part of the delivery. A companion coaching-program reference site covers the skills ladder, stroke breakdown, drills, season calendar and coach-mentor program.

Have something you need built?

Tell us the problem, the systems you already use and what a good outcome looks like. You will get a plain-language reply within one business day, usually with a first sketch of how we would build it.