Setup vs Operations: Who Defines Cohorts vs Who Runs the Roster Board

Two Screens, One Pipeline

Setup (org admin): create program, define cohort, set age window and price, publish sessions, duplicate cohort for next quarter.

Operations (any staff): roster board with seat fill, filter by instructor, drill into cohort drawer, edit session time, cancel registration with refund.

Trainers and desk should not need admin keys to move Thursday class indoors when it rains.

Why the Split Matters

Facilities that lock everything behind owner login create shadows: trainers text schedule changes, desk retypes refunds, finance reconciles Stripe manually.

API-enforced permissions mean part-time staff cannot accidentally publish a $0 cohort — but can refund a dropout before class starts.

Deep Links

?cohort= on the operations URL lets managers share one cohort from email without navigation tutorials.

Mobile Reality

Session time edits and cancel-and-refund happen from tablets at the front desk. Mobile kennel software expectations apply to training ops — not only boarding check-in.

Scenario

Lead trainer on vacation. Assistant moves session five indoors via roster drawer. Admin login untouched. Owners see updated time on portal schedule. No group text required.

Platform

Dog training class software documents both surfaces. Dog training facility software places class ops beside boarding and B&T dashboards staff already use.