DUDES BASEBALL · RSVP · BUILD 04.23.26

One workflow
for attendance,
rosters, and intervention.

A bulk-RSVP platform for a volunteer-run travel-ball program with 10 teams, 117 players, and a pattern of last-minute shortfalls. Designed as a working tool, not a dashboard — every screen should end in a decision.

Teams in program
10
Players · 13U demo team
11
Events scheduled
8
T-7 status · Westside
SHORT 3
What's broken
  • Coaches text 11 parents individually for every event
  • RSVPs scatter across text, email, group-chat, and memory
  • Shortfalls only surface at T-2 when call-ups are harder
  • EVPs have no view into which teams are about to miss events
  • Season attendance trends invisible until it's too late
What we're building
  • Bulk RSVP request with T-14 → T-1 automated cadence
  • One-tap response page — no login, no app install
  • T-5 audit that flags shortfalls and deploys call-ups
  • Per-team dashboard with lineup, pitching plan, projections
  • EVP program view with trigger-based intervention
Design principles
  • Every screen ends in a decision, not a dashboard
  • Terminal density — volunteers don't have time to scroll
  • Cadence-aware — screens know where they are in the T-clock
  • Progressive disclosure — coaches see their team, EVPs see all
  • No login for parents — the email IS the auth
Parent
1 tap
Receives email. Opens link. Taps Yes / No / Maybe. Done. The entire parent UX is the email + one page. No app. No account.
Open parent view →
Coach
12 screens
Volunteer parent running 1 team. Imports events, sends bulk RSVPs, watches the cadence, deploys call-ups when the audit flags a shortfall, sets lineup and pitching plan.
Open coach dashboard →
EVP
1 view · 10 teams
Executive VP of Player Development. Sees all 10 teams at once, intervenes only where flagged. Trigger-based, not monitoring.
Open program view →
DUDES BASEBALL · RSVP
BUILD 04.23.26
10 TEAMS · 117 PLAYERS · 8 SCREENS