1. Salon + Booking + CRM + Inventory
  2. Features
  3. Revision Decisions and Corrections
Feature · Revision Decisions and Corrections

Revision Decisions and Corrections

Keep the reason and source revision visible when a booking decision or authorized scope changes.

OverviewDecision Register
Salon + Booking + CRM + Inventory · Revision Decisions and Corrections

Decision Register

Review decisions

New
ParentSource revisionDecisionReviewerDecided atReason
BKN-85796470Approve04 OctApprove rd-514
BKN-30961800Return10 OctReject rd-143
BKN-7501230Approve10 OctReturn rd-666
BKN-51235470Return09 OctApprove rd-763
BKN-65813310Approve17 OctReject rd-995
6 of 6 records
Approve rd-514Review decisions · RD-69958
Approve
ParentBKN-85796
Source revision470
Decided at04 Oct
Operation keyOK-397
Example screen with sample data

What you can do

Keep the decision attached to the version reviewed

Salon Manager records an independent decision with the source revision, reviewer and reason against the parent booking. Approve, Reject and Return describe the decision made at that point. Front Desk uses the reason to understand what may proceed and what requires more work before the next operating action.

A later change to the appointment needs its own review of authorized scope. The correction action records the reason, cancels unexecuted scope where appropriate and retains original executed records with successor evidence. This lets Auditor explain how the current arrangement relates to earlier work without losing the accepted history.

How the work is organized

  • Independent decision. Salon Manager examines the source revision being presented and records the reason for the outcome. The team must be able to identify the version covered by that decision before acting on it.
  • Follow-up work. Front Desk or Service Professional addresses a rejected submission or a Return decision according to the reason. Refresh the current source before presenting the next version for consideration.
  • Authorized correction. Salon Manager uses the supported correction or cancellation action with an explicit reason. Executed records remain available while successor evidence explains the subsequent change.

What to agree during setup

Agree which booking changes require independent review and how the decision refers to the relevant source version. Confirm the relationship between booking decisions and service close-out approval during configuration. The person preparing the work and the person deciding it should understand which version is authorized for the next action.

Decide how the team handles a change after part of a booking’s work has already occurred. Identify the unexecuted scope and preserve the evidence of completed service. When a payment-related consequence needs attention, Payment Reviewer follows the provider evidence through the configured connection. The scope discussion should identify that follow-up without assuming a cancellation itself proves a refund.

Check the handoff on an actual case

Take a confirmed booking whose remaining work changes after a service segment has been completed. Front Desk identifies the requested change and Salon Manager reviews the current revision with the earlier decision and completion evidence. Record the reason for the authorized correction and use the supported action to address the unexecuted portion.

Ask Auditor to follow the original booking evidence and the successor information. The completed service should still be explainable from its original records. Then review a Return decision and have the preparer describe the next correction it requires. The handoff is ready when the current scope and its reason are clear, while each earlier executed result remains tied to the version under which it occurred.

What your team sees

  • Decision Register — Follow independent decisions with their source revision, reviewer and reason.
  • Review Follow-Up — Find rejected and returned decisions that require an explained next step.
  • Cancelled and No-Show Bookings — Review bookings whose operating outcome needs cancellation or attendance follow-up.

Follow the work through

Use Cancellation and scope correction, then inspect the resulting outcomes in Completion and Exceptions.

What it keeps track of

Data model
Review decisions
Independent review decisions recorded against a source revision.
Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Service consumption
Service close-out extensions recording actual product and service use.
Operation receipts
Idempotent operation receipts for guarded workflow commands.
Payment evidence
Verified provider payment events reconciled against bookings.

Who uses it

Permissions
Salon Manager
, Front Desk, Service Professional, Payment Reviewer, Auditor, Admin.
Salon Manager
Authorizes scope changes; the preparer addresses the reason; Auditor reads the retained history.

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