SITEMAP.XML operating spine

Next actions

• Unify member timeline events
• Add lifecycle transition actions
• Expose high-risk member alerts

Acceptance

• Every member has a status trail
• Staff can see billing, attendance, notes, and family context together

Next actions

• Queue lead conversion drafts
• Connect trial outcomes to member creation
• Add intake completeness checks

Acceptance

• A lead can move from enquiry to trial to member
• Intake data follows the member into onboarding

Next actions

• Add family switch context
• Strengthen payer reassignment review
• Show household risk and billing impact

Acceptance

• Families can be merged, split, and assigned payers
• Pickup and billing permissions are visible

Next actions

• Create parent dashboard actions
• Add child context switcher
• Expose parent-safe progress and billing

Acceptance

• A parent can switch children safely
• Parent views avoid exposing staff-only notes

Next actions

• Queue document review actions
• Add medical alert escalation
• Connect guardian approvals to family permissions

Acceptance

• Missing or expiring documents are visible
• Medical and guardian data is permission-aware

Next actions

• Promote churn insights into tasks
• Link re-engagement messages to member timelines
• Add intervention outcomes

Acceptance

• At-risk members have suggested actions
• Resolved retention work is auditable

Next actions

• Add promotion queue
• Connect achievements to member profile
• Show readiness evidence by coach

Acceptance

• Progress is visible per member
• Promotion decisions have evidence and history

Next actions

• Persist schedule optimization decisions
• Add generated-session review
• Connect session changes to audit

Acceptance

• Staff can manage templates and sessions
• Session changes are reviewable before persistence

Next actions

• Apply no-show policy to cancellations
• Connect pack-credit consumption
• Add family booking guardrails

Acceptance

• Bookings respect capacity and member status
• Cancellations can trigger waitlist and policy work

Next actions

• Add QR check-in path
• Show medical flags with permissions
• Connect no-show outcomes to policy drafts

Acceptance

• Roster can record attendance outcomes
• Exceptions are captured in audit-safe drafts

Next actions

• Add coach availability drafts
• Connect cover requests to staff records
• Expose workload pressure

Acceptance

• Coach cover is visible
• Staff credentials and workload affect session planning

Next actions

• Add spot-expiry timers
• Queue promotion notifications
• Report demand pressure into scheduling

Acceptance

• A waitlisted member can be promoted or resolved
• Promotion history is visible

Next actions

• Turn insights into session edits
• Track experiment outcomes
• Connect waitlist pressure

Acceptance

• Recommendations can be queued
• Schedule experiments have owners and outcomes

Next actions

• Persist open mat session drafts
• Track visitor participation
• Capture safety and comp notes

Acceptance

• Open mat is not just a generic class
• Visitors and focus rounds are tracked

Next actions

• Assign cover to real staff users
• Notify affected sessions
• Report uncovered shifts

Acceptance

• Coverage gaps are visible
• Cover requests are tied to sessions or shifts

Next actions

• Create promotion review queue
• Add rank-history timeline
• Support multiple ranking systems

Acceptance

• Rank changes are auditable
• Promotion readiness is evidence-based

Next actions

• Connect class focus to curriculum blocks
• Add assessment drafts
• Expose curriculum progress

Acceptance

• Classes can reference curriculum focus
• Member progress can point to curriculum evidence

Next actions

• Create event readiness workflow
• Track results and follow-up
• Connect comp prep to coach notes

Acceptance

• Competitors have readiness status
• Competition outcomes feed progress history

Next actions

• Queue reviewed coach-note drafts
• Summarize class briefings
• Connect notes to progress

Acceptance

• Coach notes can be reviewed
• Member-sensitive notes are permission-aware

Next actions

• Connect training load to attendance
• Add wellness check-in drafts
• Show coach-safe support notes

Acceptance

• Wellness data has clear permission boundaries
• Training load can inform comp readiness

Next actions

• Queue credential renewal tasks
• Connect credentials to coach eligibility
• Add expiry alerts

Acceptance

• Expiring credentials are visible
• Credential status can affect staffing decisions

Next actions

• Add stock adjustment drafts
• Connect member sales to profile
• Create reorder workflows

Acceptance

• Sales can be tied to members
• Stock health and reorder risk are visible

Next actions

• Persist ledger entries
• Connect provider events
• Add refund and credit workflows

Acceptance

• Billing actions are auditable
• Member ledgers show payments, invoices, and recovery

Next actions

• Connect recovery to payment retry links
• Track resolution outcomes
• Report recovered revenue

Acceptance

• Failed payments can be queued and resolved
• Recovery communication is visible

Next actions

• Add cashflow forecast sources
• Connect GST exports
• Create owner summary narrative

Acceptance

• Finance signals are explainable
• Exports match ledger and invoice data

Next actions

• Persist GST review records
• Generate export artifact history
• Add Xero-ready mappings

Acceptance

• GST totals can be exported
• Tax invoice language is Australian-ready

Next actions

• Persist issued packs
• Consume credits from attendance
• Expose remaining credits to members

Acceptance

• Pack purchases are GST-aware
• Credit usage is tied to sessions

Next actions

• Persist private invoices
• Connect coach availability
• Attach lesson notes to progress

Acceptance

• Private lesson invoices are GST-aware
• Session notes do not mix with group attendance

Next actions

• Apply discounts to future invoices
• Show payer impact preview
• Audit exceptions

Acceptance

• Family pricing has a reason trail
• Discounts are visible to billing staff

Next actions

• Store provider event payloads
• Add webhook health dashboard
• Connect retry and refund writes

Acceptance

• Provider events are visible
• Payment actions map to ledger and invoices

Next actions

• Add conversation review queue
• Connect trial booking intents
• Define escalation boundaries

Acceptance

• AI conversations are reviewable
• Lead capture can hand off to intake

Next actions

• Explain risk signals
• Queue retention drafts
• Track intervention outcomes

Acceptance

• Risk insights have why explanations
• Outreach requires human review

Next actions

• Draft class briefing summaries
• Extract progress signals
• Require coach approval

Acceptance

• AI notes are reviewable
• Sensitive coaching content is permission-bound

Next actions

• Draft lead follow-up sequences
• Connect review snippets
• Track conversion outcomes

Acceptance

• AI messages are human-approved
• Lead stage changes are auditable

Next actions

• Connect forecast inputs
• Explain confidence
• Tie actions to finance workbench

Acceptance

• Forecasts show assumptions
• Owner actions can be queued

Next actions

• Log AI decision metadata
• Add review outcomes
• Connect sensitive actions to audit

Acceptance

• AI actions are traceable
• Sensitive automation has review gates

Next actions

• Create lifecycle triggers
• Queue campaign sends
• Track automation outcomes

Acceptance

• Automations have clear triggers
• Campaigns can be reviewed before sending

Next actions

• Queue reward approvals
• Connect referrals to leads
• Track conversion by advocate

Acceptance

• Referral status is visible
• Rewards require approval

Next actions

• Queue review responses
• Reuse positive reviews in campaigns
• Escalate urgent feedback

Acceptance

• Reviews have response status
• Urgent sentiment creates follow-up

Next actions

• Create page publishing drafts
• Connect program content
• Add booking CTA tracking

Acceptance

• Pages can be drafted and reviewed
• Public pages point to correct booking flows

Next actions

• Add page variants
• Track lead sources
• Connect campaign lifecycle

Acceptance

• Landing pages can map to campaigns
• Leads retain source context

Next actions

• Queue send approvals
• Add audience filters
• Connect performance reporting

Acceptance

• Campaigns have audience and status
• Messages can be queued and reviewed

Next actions

• Add template actions
• Track channel delivery
• Connect comms to member timelines

Acceptance

• Queued communications are visible
• Communication history is linked to context

Next actions

• Add exportable report slices
• Connect dashboard filters
• Add owner narrative summaries

Acceptance

• Reports are filterable
• Key operational trends are explained

Next actions

• Scope schedules by location
• Add location permissions
• Track location-level health

Acceptance

• Locations can be compared
• Staff and sessions are location-aware

Next actions

• Add staff profile actions
• Connect credentials and cover
• Expose workload warnings

Acceptance

• Staff have roles and owner context
• Workload affects operations

Next actions

• Queue task templates
• Connect automation triggers
• Track workflow outcomes

Acceptance

• Tasks have owners and due state
• Automations are reviewable

Next actions

• Centralize draft replay audit
• Add sensitive filters
• Expose AI action evidence

Acceptance

• Sensitive actions are traceable
• Audit entries link to source records

Next actions

• Add permission review drafts
• Connect roles to UI gates
• Flag risky access

Acceptance

• Permissions are explainable
• Sensitive scopes are reviewable

Next actions

• Add provider health feeds
• Track failed jobs
• Expose deployment readiness

Acceptance

• Admin health has visible status
• Provider failures become actionable

Next actions

• Link incidents to facility tasks
• Track asset health
• Add safety follow-up workflows

Acceptance

• Incidents have severity and owner
• Facility and asset issues produce follow-up

Next actions

• Add migration run records
• Show import verification
• Track cutover checklist

Acceptance

• Migration has preflight and signoff
• Dry runs show issues before cutover

Next actions

• Persist mapping templates
• Add validation results
• Support transform previews

Acceptance

• Mappings are reusable
• Invalid rows are explained

Next actions

• Create dry-run summary route
• Queue owner signoff
• Add rollback checklist

Acceptance

• Cutover cannot proceed without review
• Rollback and verification are visible

Next actions

• Document endpoint inventory
• Add API key workflow
• Expose rate-limit and audit model

Acceptance

• API consumers and scopes are visible
• Endpoints have ownership and status

Next actions

• Persist delivery attempts
• Add retry queue
• Expose signature and event docs

Acceptance

• Webhook failures are visible
• Events can be replayed safely

Next actions

• Add connection status
• Queue integration setup tasks
• Track provider errors

Acceptance

• Integrations have health state
• Provider setup is auditable

Next actions

• Add health check results
• Connect provider alerts to tasks
• Report degraded systems

Acceptance

• Provider failures show up quickly
• Failures have clear owner and next action