See the whole floor on one screen.
Weekly reports describe a business that has already moved on.
Est. deploy 4–6 weeksSee the walkthrough
Operations & Reporting · Fitness & Wellness
Plan classes around measured demand.
Class changes rely on anecdotes.
For: Studio managers and the team responsible for operations & reporting in fitness & wellness.
01 · The outcome
What good looks like.
The team has a manager-reviewed schedule proposal, with source evidence and an explicit approval before any external action. Track attendance relative to available places against a baseline; do not assume automation improves it.
A connected workflow that uses class capacity, attendance, waitlist counts, and coach availability to compare fill rates and waitlists while flagging small samples. It produces a manager-reviewed schedule proposal.
Where AI helps, and where a person decides.
AI can compare fill rates and waitlists while flagging small samples. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The studio manager verifies the source facts and approves the final action.
Studio manager is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Studio manager: Capture the source and scope
- Studio manager: Review the proposed outcome
- Studio manager: Release only the approved version
- Studio manager: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A weekly attendance report is available. Connect only class capacity, attendance, waitlist counts, and coach availability. The studio manager confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to compare fill rates and waitlists while flagging small samples. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a manager-reviewed schedule proposal against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Studio manager has recorded approval or a reason to hold the item.
After explicit approval, save a manager-reviewed schedule proposal in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review attendance relative to available places each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=fitness-schedule-demand
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- FITNESS-SCHEDULE-DEMAND-DEMO-001
- Trigger
- A weekly attendance report is available.
- Owner
- Studio manager
- Prepared output
- a manager-reviewed schedule proposal
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Attendance relative to available places
Start with your tools.
Connect Mindbody, Stripe, Google Calendar through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
Try this week / no DAVID required
A useful first step.
This week, have your studio manager time five examples of this work. Use redacted copies of class capacity, attendance, waitlist counts, and coach availability to make a manager-reviewed schedule proposal manually, then list which fields required judgment.
What to measure.
- Attendance relative to available places
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Spot chair-time gaps before the week starts.
Short gaps in the schedule go unused.
Est. deploy 4–6 weeksSee the walkthrough
Track every lab case to the right visit.
Lab work and appointment dates slip out of sync.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.