Day 14 — trainers can teach, clients can book

The platform is now actually multi-role. Three completely different people log in to three completely different experiences.

On the trainer side: lesson slots with status, level, and capacity; a slot creation form that handles datetime, ring, lesson type, and rates; a per-slot detail page showing booked clients with horse assignments, no-show marking, and slot cancellation. The piece I knew I'd need but underestimated the complexity of was recurring schedule templates — a trainer who teaches "Thursdays 4–7pm intermediate" wants to set that up once, pause for vacation, and extend four weeks at a time. That took two days alone.

The trainer also got a weekly calendar grid (desktop) plus a day list (mobile), color-coded by level. Trainers in the wild check schedules at 6:30 a.m. on a phone in the truck — that view has to load instantly. It does.

On the client side: open lesson slots filtered to the client's level, with a Book button. Their own bookings list with cancel. A makeup credits view with expiry dates. A horses view that shows their horse's name, stall, vaccines, and meds (read-only). A notification bell. The full quiet client experience that should reduce 80% of the texts a barn manager gets in a week.

The thing I kept reminding myself this week: don't make the client portal feel like a CRUD admin app. The whole point of building this is that clients shouldn't need to text the barn to find out when their lesson is. If the portal feels like work to use, they'll just text instead.

I think it's good enough. We'll see when actual clients touch it.

Two roles, two weeks, the whole "operations" side of the barn now has a real surface. Next week: the parts that actually make a barn money.