1. Salon + Booking + CRM + Inventory
  2. Process
  3. Cancellation and scope correction
Process · Cancellation and scope correction

Cancellation and scope correction

Review timing and authorized scope while keeping completed service and earlier decisions available.

Step by step

  1. Identify the current scope Front Desk

    Front Desk opens the booking and checks its current state, revision and any completed service use. Explain the requested change so Salon Manager can distinguish remaining work from an already executed result.

    • Establish current state and executed work
    • Updates Bookings, Service consumption, Review decisions
  2. Record cancellation or attendance outcome Front Desk

    Front Desk uses the supported cancellation or no-show action for an eligible booking. The action validates timing and records an operation receipt while preserving completed service evidence.

    • Record the eligible timing-dependent outcome
    • Updates Bookings, Operation receipts
  3. Authorize a scope correction Salon Manager

    Salon Manager reviews the reason for changing authorized work and uses the correction action. It cancels unexecuted scope where applicable and retains original executed records with successor evidence.

    • Preserve executed records and record successor evidence
    • Updates Bookings, Review decisions, Operation receipts
    ApprovalA person approves before the work moves on.
  4. Review the related consequences Service Professional

    Payment Reviewer examines provider events when the change has a payment question. Service Professional supplies the original actual-use context if completed work is part of the discussion. Follow each consequence through its configured process.

    • Follow payment and service context
    • Updates Payment evidence, Service consumption, Bookings
  5. Follow the resulting evidence Salon Manager

    Auditor reviews the source decision, earlier executed records and the successor evidence. Salon Manager identifies the current authorized arrangement before the team carries out further work.

    • Explain original work and the later authorized change
    • Updates Review decisions, Operation receipts, Service consumption

Where it usually breaks

And how to keep it from happening.

  • A cancellation is attempted without checking whether service has already been completed. Review the existing actual-use records first.
  • A change reason is too vague to explain the successor action. State which remaining work is changing and why.
  • A cancelled booking is taken as evidence of a provider refund. Inspect the actual provider event when assessing payment consequences.
Front Desk
, Salon Manager, Service Professional, Payment Reviewer, Auditor, Admin

Set up Salon + Booking + CRM + Inventory your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started