Codes 'n' Coffee Tech
Sweat Fit Wellness · Fitness and wellness

Coordinating classes, trainers, memberships, and leads across three locations.

A configurable scheduling and CRM platform that coordinates Pilates and bootcamp capacity, trainers, branches, packages, bookings, attendance, and continued member engagement.

Updated 24 July 2026

Scheduling engine used: Zlot Manager

Illustrative workflow
Classes, trainers, locations, and packages in one schedule
Sweat Fit Wellness
Resource
09:00
10:00
11:00
Member
Trainer
Location
Package
All required constraints agree Bookable class
Illustrative workflow based on the described operating scope. No live client data is shown.
Sweat Fit Wellness logo
At a glance

From operating constraint to working system.

Problem statement

Spreadsheet-led planning could not scale cleanly across three Mumbai locations. Pilates and bootcamp schedules depended on trainer availability, branch capacity, service rules, and member packages, while leads, trials, bookings, attendance, and renewals created a second operating journey around the timetable.

Delivered system

Codes 'n' Coffee Tech configured Zlot Manager as the booking infrastructure for the fitness operation. Pilates, bootcamp, trial, and class contexts are represented through categorized slot types; master data describes branches, trainers, rooms, capacity, packages, and memberships. Conditional layers evaluate those records before a generated class slot or one-off exception becomes bookable. CRM, booking-status, attendance, and renewal workflows then carry the member relationship beyond the eligibility decision.

How the system connects

Scheduling connected to the complete member journey

Zlot Manager sits between CRM demand and branch operations. Slot types select the relevant fitness rules, master data supplies the current branch, trainer, capacity, package, membership, and status context, and the engine exposes only eligible options.

SystemProcessOutcome

Zlot Manager sits between CRM demand and branch operations. Slot types select the relevant fitness rules, master data supplies the current branch, trainer, capacity, package, membership, and status context, and the engine exposes only eligible options.

  1. System: Lead and member CRM. Leads, trials, members, and follow-up retain one relationship context.
  2. Process: Service and entitlement rules. Pilates, bootcamp, packages, and memberships define booking eligibility.
  3. Process: Branch and resource rules. Trainer, location, room or capacity, and schedule conditions are explicit.
  4. System: Zlot Manager. The engine evaluates the published conditions for the selected slot type.
  5. Outcome: Valid class options. Only complete bookable combinations continue to customer and team views.
  6. Process: Member, trainer, and branch experiences. Booking, schedules, attendance, and delivery share the same slot context.
  7. Outcome: Usage and renewal context. Attendance and package usage return to continued member engagement.
  • Lead and member CRM to Service and entitlement rules: Journey context.
  • Service and entitlement rules to Zlot Manager: Eligibility.
  • Branch and resource rules to Zlot Manager: Constraints.
  • Zlot Manager to Valid class options: Validate.
  • Valid class options to Member, trainer, and branch experiences: Bookable.
  • Member, trainer, and branch experiences to Usage and renewal context: Attendance + usage.
CRM owns the relationship; Zlot Manager owns slot configuration and booking eligibility; branch, trainer, attendance, and membership experiences own the operational actions that follow a confirmed booking.
Operating modules

Designed around the work people need to complete.

Each module has a clear responsibility and passes the right context into the next owned action instead of becoming another isolated tool.

01Lead and trial journey

Enquiries, follow-up, and trials sit in the same operating context as the services and branches a prospective member is considering.

02Zlot Manager booking layer

Categorized slot types load branch, service, trainer, room or capacity, package, membership, and status context before the engine permits a booking.

03Booking and attendance

Customer bookings connect to class capacity, trainer assignments, attendance, and the operating view used by each branch.

04Package and renewal lifecycle

Package eligibility and usage remain connected to booking activity, continued engagement, and renewal follow-up.

How the operation runs

From lead or member to a valid class and continued engagement

The relationship journey supplies the slot type, service, branch, resource, status, and entitlement context. Zlot Manager validates the complete class combination before booking activity continues into attendance and renewal follow-up.

EntryProcessDecisionExceptionOutcome

The relationship journey supplies the slot type, service, branch, resource, status, and entitlement context. Zlot Manager validates the complete class combination before booking activity continues into attendance and renewal follow-up.

  1. Entry: Lead or existing member. CRM retains the relationship and service interest.
  2. Process: Trial, package, or membership context. The journey identifies the entitlement that applies to booking.
  3. Process: Choose service and branch. Select Pilates or bootcamp and the relevant Mumbai location.
  4. Decision: Valid class combination?.
  5. Exception: No bookable option. Offer the next combination that satisfies trainer, capacity, branch, and package rules.
  6. Outcome: Class booking confirmed. The valid option carries its trainer, branch, capacity, and package context.
  7. Process: Attendance and branch delivery. Trainer and branch teams act from the shared schedule.
  8. Outcome: Usage, engagement, and renewal. Attendance and package context continue into member follow-up.
  • Lead or existing member to Trial, package, or membership context: Qualify.
  • Trial, package, or membership context to Choose service and branch: Eligible journey.
  • Choose service and branch to Valid class combination?: Check constraints.
  • Valid class combination? to No bookable option: Invalid.
  • Valid class combination? to Class booking confirmed: Valid.
  • Class booking confirmed to Attendance and branch delivery: Deliver.
  • Attendance and branch delivery to Usage, engagement, and renewal: Continue.
Generated class schedules and one-off slot exceptions use the same eligibility path. Service, branch, trainer, room or capacity, package, membership, and status conditions must pass before a class option becomes bookable.
Implementation process

From operating reality to a system teams can run.

The implementation separates discovery, domain rules, architecture, module delivery, validation, and live operational improvement.

  1. Phase 01

    Three-branch workflow discovery

  2. Phase 02

    Fitness domain modelling

  3. Phase 03

    Zlot Manager configuration model

  4. Phase 04

    CRM and role experiences

  5. Phase 05

    Constraint and lifecycle validation

  6. Phase 06

    Location rollout and refinement

Implementation phase detailRead how discovery, modelling, architecture, delivery, validation, and continuous improvement were handled.
  1. Phase 01

    Three-branch workflow discovery

    Map how leads, trials, services, trainers, schedules, capacity, packages, and attendance were managed across each location.

  2. Phase 02

    Fitness domain modelling

    Define Pilates and bootcamp services, branch-specific availability, trainer assignments, group capacity, and package eligibility as explicit scheduling rules.

  3. Phase 03

    Zlot Manager configuration model

    Configure categorized slot types, fitness master data, booking statuses, and conditional layers before returning a bookable class option.

  4. Phase 04

    CRM and role experiences

    Connect lead, trial, member, booking, branch, trainer, and attendance journeys to the shared scheduling context.

  5. Phase 05

    Constraint and lifecycle validation

    Exercise capacity limits, trainer conflicts, package eligibility, cross-branch schedules, cancellations, and member-state transitions.

  6. Phase 06

    Location rollout and refinement

    Adopt the operating model across three locations and refine services, schedules, packages, and engagement flows as the business evolves.

Implementation detail

Decisions, validation, and clear system boundaries.

The complete technical explanation remains available here without interrupting the primary operating story.

Technical decisionsHow each operating constraint shaped an implementation choice and ownership boundary.
Constraint

A free time on the calendar is not necessarily a valid class booking.

Implementation

Use categorized slot types and conditional layers to evaluate service, branch, trainer, capacity, package, membership, and status rules through Zlot Manager.

Why it matters

Availability reflects the complete operating combination rather than an empty time interval.

Constraint

Fitness classes combine group capacity with individual package eligibility.

Implementation

Keep capacity and member entitlement checks inside the booking decision.

Why it matters

A class can remain operationally accurate while each booking respects the member's package context.

Constraint

Lead conversion and member retention happen around the schedule.

Implementation

Connect CRM, trials, bookings, attendance, usage, and renewal follow-up.

Why it matters

Commercial and service teams can continue the relationship without losing its operational context.

Validation and rolloutScenarios used to test the combinations most likely to disrupt live operations.

Capacity boundaries

Confirm that simultaneous bookings cannot move a class beyond its configured capacity.

Trainer and branch conflicts

Test overlapping assignments and changes that affect more than one class or location.

Package eligibility

Exercise expired, exhausted, incompatible, and newly activated package states during booking.

Lifecycle continuity

Verify that trial, conversion, booking, attendance, and renewal activity retains the correct member context.

Technical boundariesWhat the architecture owns, and where adjacent systems or human decisions remain responsible.
  • Zlot Manager owns slot configuration and booking eligibility while CRM, attendance, and membership workflows own their operational state.
  • Scheduling rules and CRM state remain separate so a booking change does not erase relationship context.
  • Capacity, package eligibility, attendance, and renewal remain distinct operational states.
Ongoing engineering partnership

Technology that keeps moving with operations.

Codes 'n' Coffee Tech provides ongoing product engineering and application support as services, locations, membership rules, and customer journeys change.

Related capabilities and industries
Intelligent Resource Scheduling Sports, fitness and wellness
Scheduling engine used
Zlot ManagerConfigurable booking infrastructure for slot types, rules, and workflows
Let's talk

Make every bookable slot operationally valid.

We can map the people, locations, services, packages, and CRM journeys behind your scheduling operation.

Book a discovery call
Codes 'n' Coffee Tech
Share the constraint
Map the operating flow
Choose a practical next step