Three booking loops converge on coordination
Path A connects a participant to a trainer for a private session. Path B enrolls into a venue or academy session. Path C starts when a trainer publishes a session others can join. Payment can continue in-app or at the venue, followed by confirmation and check-in patterns.
Full coordination graph
Selected path context
- Origin · Multiple booking origins
- Availability · Slot readiness across loops
- Convergence · Shared booking core
- Role sync · Participant · Trainer · Venue
- Pay / check-in · In-app or at-venue path
Multi-path booking orchestrator
Three booking loops — trainer 1:1, venue/academy session, and trainer-created venue-linked sessions — converge on a shared booking core, then confirmation, payment path, role sync, and check-in.
PATH A
Trainer 1:1
- Discover
- Profile
- Slot lock
- Private book
PATH B
Venue / Academy session
- Catalogue
- Eligibility
- Capacity
- Enroll
PATH C
Trainer-created venue-linked
- Publish
- Venue slot
- Roster
- Joiners
Booking core
Convergence · role sync
- REQUEST
- HELD
- CONFIRMED
- CHECK-IN READY
Participant · Trainer · Venue synchronize after confirmation. Pay in-app or at venue, then check-in.
Resource → slot → summary → pay path
Participant booking screens reconstruct the designed loop: choose a resource, pick availability, review the summary, then continue with an in-app or at-venue payment path.
- active status: active
Coach 02 · Racket
Path A · 1:1
Court block · Academy
Path B · Session
Explicit order beside the coordination board
Select
Provider / session
Availability
Slot resolve
Confirm
Summary
Pay path
In-app or venue
Check-in
Confirmation pattern
Official catalogue bookings stay distinct from community-created participation activities.
Design a booking coordination system?
Three designed booking loops with in-app and at-venue payment path concepts plus confirmation and check-in patterns.