UCRFC Club Hub
A season hub for an amateur rugby club — match week, availability, and paperwork in one dashboard.
Context
An amateur rugby club runs on group chats, spreadsheets, and a coach chasing people for waivers. The Club Hub gives Union County Mudturtles RFC one screen for the thing that actually matters each week: who is playing on Saturday.
Problem
Availability, paperwork, schedule, and results each lived somewhere different. Selection depended on a coach reconciling all of it by hand, and players had no single place to see where they stood.
Role & Approach
A Finrez engagement, and the Club Hub is one piece of it. The same scope covered the club’s brand guidelines, its public website, dues collection through Stripe, an SMS channel for match-week notices, and the integration with TeamSnap the club was already living in. Designing the hub after those decisions rather than before them is why it behaves like a front door instead of another destination: the fixture, the availability question and the paperwork are the only things it asks a player to deal with, and everything that already had a home — rosters, payments, messaging — stayed where it was and got surfaced.
Process
The dashboard is organized around match week. The fixture leads — opponent, kickoff, ground, and arrival time — and the availability question sits directly under it as three buttons: In, Maybe, Out. Social proof (“twenty-two others have answered”) and a stated selection deadline do the chasing that a coach used to do manually. Around it sit the player’s own season — tries, training percentage, caps — the last result, the next three fixtures with inline availability, and a paperwork checklist that shows what is on file against what is due.
User Journey
A player signs in, sees the fixture, taps In, and clears whatever paperwork is outstanding — registration, medical waiver, concussion protocol, dues — without leaving the page. Role tabs for player, coach, and admin change what the same hub exposes.
Constraints
The club is run by volunteers, which sets the ceiling on everything. Nothing here can require an administrator who is paid to maintain it, so the hub had to replace a coach’s spreadsheet without becoming a second system he has to keep current. It also could not ask the club to abandon TeamSnap, which the squad already uses and which holds the roster of record — so the hub reads alongside it rather than competing with it. Dues run through Stripe for the same reason: money handled by a service the treasurer can audit without the club owning any of it. And a player’s side of it has to work on a phone, one-handed, in the two minutes between a notification and putting the phone back in a pocket — which is the real constraint the availability question is designed against.
Summary
The Club Hub collapses a season’s worth of admin into one dashboard, and makes the weekly availability question something a player answers in a single tap.
Next Steps
TODO — what shipped, whether the club is using it, and what is still open.