A practical system for reducing no-shows

Scope and non-claims

This draft is a U.S.-baseline operational planning guide for salons, barbershops, nail salons, spas, med spas, PMU/brow/lash studios, independent professionals, and salon suites. It teaches a measurement and decision process. It does not supply a universal cancellation window, reminder schedule, deposit amount, fee, refund rule, dispute script, consent form, retention period, or exception list.

The exact policy depends on the selected state and locality, the service and client relationship, the payment rail, the merchant's processor/acquirer and card-network terms, gift-card or membership treatment, taxes, professional rules, accessibility obligations, communication technology, message content, consent record, and privacy requirements. Those inputs are publication blockers, not optional implementation details. [G07-S08, G07-S09, G07-S10, G07-S11, G07-S12]

This draft does not classify a deposit, cancellation fee, refund, retained amount, gift-card balance, membership payment, or disputed transaction for accounting or tax purposes. It does not establish a right to charge a client. It does not provide legal advice or processor instructions.

No number in the worked scenarios is a typical no-show rate, recommended deposit, appropriate fee, expected refill rate, industry average, or proof that a process works. The 30-day plan is an editorial implementation cadence requested for this draft. The ledger describes a four-week experiment only as an editorial starting period and warns that low volume, seasonality, and long service cycles may require a longer observation window. EDITORIAL_CADENCE — no official source validates 30 days or four weeks as sufficient.

Define every appointment outcome

Define statuses before measuring. Each scheduled event should end in exactly one primary status. If staff can choose two primary statuses for the same appointment, the dashboard cannot be interpreted.

Core status dictionary — EDITORIAL_METHOD

Exact working definitions

No-show. For this worksheet, a no-show is an eligible client appointment for which the client did not attend, did not complete an eligible cancellation or reschedule before the business's documented cutoff, and did not receive an approved exception. This is an EDITORIAL_METHOD, not an official definition or legal conclusion.

Late cancellation. A late cancellation is an eligible client cancellation recorded after the business's documented cutoff and before the no-show decision point. The cutoff is an owner-defined policy input subject to qualified review; this guide supplies no standard number of hours or days.

Refill. A refill occurs when capacity released by a cancellation or no-show is assigned to another client and the replacement appointment reaches the documented completed state. Track refill_offered, refill_booked, refill_completed, and refill_collected_amount separately. A waitlist message, booking attempt, or replacement booking that does not complete is not a completed refill.

Provider cancellation. A provider or business cancellation is not a client no-show. Keeping it separate prevents the business from improving its reported client rate merely by misclassifying business-side disruptions.

Exception. An exception is a documented override under an approved process. It is not a hidden deletion. The business should retain the minimum information necessary to explain the decision without collecting unnecessary health, family, disability, immigration, or financial details.

These definitions implement the ledger's editorial instruction to use mutually exclusive statuses and preserve service, duration, provider, booking source, lead time, reminder delivery/response, refill outcome, and booked/collected amounts without exposing client identity in the analysis. EDITORIAL_METHOD — G07 no-show experiment; no official source.

Build the eligible denominator

The denominator should be stated beside every rate.

EDITORIAL_METHOD:
eligible_scheduled_appointments
  = all scheduled client appointments in the observation period
  - business/provider cancellations
  - rescheduled-before-cutoff original slots
  - duplicate, test and administrative holds
  - other documented ineligible statuses

no_show_rate
  = client_no_shows / eligible_scheduled_appointments

late_cancellation_rate
  = client_late_cancellations / eligible_scheduled_appointments

client_disruption_rate
  = (client_no_shows + client_late_cancellations)
    / eligible_scheduled_appointments

completed_refill_rate
  = completed_refills / refill-eligible released slots

These are transparent editorial definitions, not official standards. A denominator can change when the status policy changes, so the report should preserve the definition version used for each period.

Every rate requires a strictly positive eligible denominator. If eligible_scheduled_appointments <= 0 or refill-eligible released slots <= 0, return not_calculated / N/A — no eligible observations; never coerce the denominator to one or report 0%. A negative numerator, or a numerator greater than its eligible denominator, is a data-integrity error that blocks the calculation rather than a value to clamp silently.

Required denominator notes

Record:

• observation start and end date;
• timezone and appointment timestamp policy;
• services, locations, providers, booking sources, and client groups included;
• how multi-service or multi-provider bookings are counted;
• how same-day add-ons, recurring bookings, classes, room reservations, and group appointments are counted;
• the cutoff definition and policy version;
• excluded statuses and counts;
• unresolved records and data-quality failures;
• whether the appointment system permits retroactive status changes; and
• the extraction date and query or report version.

Do not compare two periods if one counts an appointment per ticket and the other counts each service line. Do not compare providers when service mix, hours, schedule access, client type, booking lead time, or exception decisions differ. Low counts should be shown, not hidden behind percentages.

Measure without confusing value cash and profit

Booked value, blocked booked value, collected cash, fees, refunds, contribution, and business profit answer different questions.

Measurement dictionary — EDITORIAL_METHOD

Recommended dashboard fields

• raw scheduled appointments;
• eligible scheduled appointments;
• completed appointments;
• client no-shows;
• client late cancellations;
• provider/business cancellations;
• rescheduled-before-cutoff originals;
• approved exceptions;
• unresolved records;
• reminder attempted, delivered, failed, replied, confirmed, or opted out;
• released slots, refill offers, refill bookings, completed refills;
• booked service value and blocked booked value;
• deposits/prepayments collected, fees collected, refunds, credits, disputes, reversals, and recovered amounts under reviewed definitions;
• complaints and accessibility or communication failures; and
• policy version, consent version, payment-flow version, and data-extraction version.

The dashboard should use aggregated or pseudonymized analysis identifiers where possible. Client identity should not appear in a management chart merely because it exists in the booking system. EDITORIAL_METHOD — the ledger supports preserving analysis fields without exposing client identity; no source supplies a retention period or privacy implementation.

Diagnose the process before changing the policy

A no-show count does not identify the cause. Review the journey from booking to appointment completion.

Booking setup

• Was the service, provider, location, date, time, duration, price presentation, and preparation requirement clear?
• Did the system create duplicates, timezone shifts, wrong-location bookings, or appointments the provider could not perform?
• Was the client able to review the cancellation/deposit term before finalizing, and is there evidence of which version was shown and accepted? Proper disclosure and documentation can matter in selected Visa disputes; no dispute outcome is promised. [G07-S08]
• Were material statements truthful, non-deceptive, and supported? FTC guidance does not approve this draft's policy or a particular placement. [G07-S12]

Confirmation and reminder journey

• Which messages were operational, which contained advertising, and which mixed both purposes?
• Which channel, sender, technology, template version, and consent record applied?
• Was the message delivered, bounced, filtered, rejected, or sent to an outdated contact?
• Could the client confirm, cancel, reschedule, request help, or revoke consent through an accessible path?
• Did promotional content get added to a reminder without communications review? Message purpose, technology, consent, opt-out, and state law can change the analysis. [G07-S10, G07-S11]

Service and schedule design

• Are long or high-preparation services confirmed differently based on actual operator evidence rather than an assumed risk label?
• Are recurring appointments created so far in advance that clients forget or circumstances change?
• Is the schedule updated when a provider, room, device, or service becomes unavailable?
• Does a waitlist or standby process know which service, provider, duration, location, notice, and access requirements a replacement client can accept?

Policy and human handling

• Do staff describe the term consistently?
• Can staff see the applicable policy version and the client's recorded acceptance?
• Is the exception owner named?
• Are complaints, disputes, refunds, and credits connected back to the appointment record?
• Does the process distinguish first incidents, repeated patterns, system failures, emergencies, accessibility needs, and business-caused failures without making unsupported legal distinctions?

Do not change reminders, fee terms, cancellation cutoff, exception logic, and refill outreach all at once if the goal is to learn which process change mattered. The ledger recommends changing one element at a time where practical and warns that unequal or undisclosed tests involving fees or consent need legal, ethical, and operational review. EDITORIAL_METHOD — no official source proves causation.

Design a clear cancellation and exception policy

A policy should help a client understand what to do, when to do it, and what the business may do next. It should not be written as a trap.

Policy decision worksheet

Disclosure and acceptance record

For each covered booking, preserve:

• policy identifier and version;
• exact term displayed or a durable reference to it;
• where and when it was shown;
• language or accessible format provided;
• client action used to indicate acceptance, if the reviewed process requires it;
• appointment, service, amount, and payment-flow identifiers;
• later policy changes and which version remained applicable; and
• refund, credit, exception, complaint, or dispute outcome.

Visa's first-party merchant guidance supports the narrow statement that properly disclosed cancellation/return terms and documentation can be relevant in selected dispute contexts. It does not establish enforceability, a right to charge, guaranteed-reservation eligibility, another network's rule, or a guaranteed outcome. [G07-S08]

FTC guidance supports truthful, non-deceptive, fair presentation and evidence for objective claims. It does not approve a salon cancellation term or supply a universal disclosure placement. [G07-S12]

Keep reminders and promotions separate

Classify the primary purpose and content of each template before sending it.

FCC rules make relevant distinctions involving consent, technology, content, opt-out, and revocation, and qualifying texts are treated as calls in relevant provisions. The source does not grant blanket permission to text anyone who booked, provide a universal form, resolve a vendor's technology, or establish state compliance. [G07-S10]

FTC CAN-SPAM guidance distinguishes commercial email from narrowly defined transactional or relationship messages and describes requirements such as accurate headers/subjects and opt-out handling within its scope. It does not provide text/voice consent or make booking consent a universal marketing permission. [G07-S11]

Consent and delivery checklist

• Exact channel and technology are documented.
• Exact template, primary purpose, links, images, and promotional content are archived.
• The consent or relationship basis used by the reviewed workflow is recorded.
• Revocation, unsubscribe, stop, preference, and complaint paths reach the system that sends messages.
• Delivery failure does not become evidence that the client received a reminder.
• Contact data corrections are auditable.
• Staff do not move a client from operational preferences into marketing without a reviewed basis.
• Vendor behavior, quiet hours, frequency, suppression, and state requirements are checked before implementation.
• An accessible non-digital route exists for clients who cannot use the default channel.

Map deposits charges refunds and disputes

Do not use “deposit” as a generic label for every payment event.

Payment-flow map

For covered preauthorized electronic fund transfers from a consumer account, Regulation E includes authorization and copy requirements within its defined scope. That source does not decide every credit-card, debit-card, card-on-file, one-time deposit, or no-show charge. The account, payment rail, transaction pattern, processor flow, and legal applicability must be reviewed. [G07-S09]

Refund and dispute ledger

Keep a transaction-level record that can reconcile:

EDITORIAL_METHOD:
gross_amount_collected
- refunds
- reversals
- credits converted to cash refunds where applicable
- dispute debits
+ dispute recoveries
= net_cash_effect_within_the_defined_period

The equation is a reconciliation aid, not revenue recognition, tax treatment, or proof that the amount was owed.

For a dispute, preserve only relevant, permitted evidence under the current processor/acquirer/network process:

• appointment and transaction identifiers;
• policy version, display, and acceptance evidence;
• service/date/location and whether the business was ready to perform;
• confirmation, reminder, cancellation, exception, and refund communications;
• refund, credit, or resolution offered;
• processor deadline, submission, response, and final status; and
• correction made to the operating process.

Do not represent a chargeback packet as guaranteed. Do not cite Visa guidance as authorization to charge or as the rule for another network. [G07-S08]

Make cancellation and exceptions accessible

Reducing friction means making the intended action possible, not merely stating a penalty.

Accessible cancellation path — EDITORIAL_METHOD

• Put the date, time, location, service, provider/resource, and change path in a format the client can understand.
• Avoid relying only on color, images, tiny text, hover, or a single mobile interaction.
• Offer a staff-assisted or alternative channel when the default path is not usable.
• State channel hours and how messages received outside those hours are timestamped.
• Let clients correct contact details and report delivery/access problems.
• Do not require a client to disclose unnecessary medical or disability details to request assistance or an exception.
• Record whether the business's own website, phone, messaging, payment, weather, facility, provider, or scheduling failure affected the event.
• Make the exception owner, response time, remedy options, and correction route visible to staff.
• Review whether language access, disability access, emergency circumstances, caregiving, transportation disruption, severe weather, or technology failure require a different process in the selected jurisdiction and business.

This ledger contains no source that approves an exception list or accessibility workflow. These are editorial design prompts requiring qualified accessibility and legal review before publication or implementation.

Exception decision record

Use comparable decision criteria for comparable facts, but do not turn a worksheet into a claim that every case is legally equivalent.

Run a controlled 30-day plan

The following is an EDITORIAL_CADENCE, not an official standard, recommended legal notice period, or promise that the effect can be measured in 30 days. Extend the window when volume is low, service cycles are long, seasonality is material, or the status/data definitions changed.

Days 1–5 — lock definitions and audit data

• Approve the mutually exclusive status dictionary.
• Define the eligible denominator and exclusions.
• Map appointment, reminder, payment, refund, dispute, exception, and refill fields.
• Reclassify a sample using evidence; record unresolved cases instead of guessing.
• Remove client identity from the analysis dataset where it is not needed.
• Freeze the baseline query/report version.

Days 6–10 — map the real client journey

• Capture booking, confirmation, reminder, cancellation, reschedule, waitlist, payment, refund, and dispute steps.
• Inventory exact policy and message versions.
• Verify who owns each exception and correction.
• Identify system failures, inaccessible channels, duplicate records, staff workarounds, and undelivered messages.
• Do not change payment or communication terms without the required qualified review.

Days 11–15 — choose one change

Choose one operational change supported by the audit, such as clearer appointment details, a working cancellation path, corrected contact data, staff training on statuses, or better delivery-error handling. A fee, new deposit, new card flow, new consent, new marketing message, or unequal client test is not a routine experiment; it requires payments/legal, communications/privacy, accessibility, ethical, and operational review as applicable. [G07-S08, G07-S09, G07-S10, G07-S11, G07-S12]

Document:

• hypothesis;
• exact change and version;
• population and exclusions;
• start/stop rule;
• operational owner;
• client-risk and fairness review;
• primary and guardrail measures;
• rollback trigger; and
• known concurrent changes.

Days 16–23 — operate and monitor

• Use the same status and denominator definitions.
• Record delivery, response, cancellation, refill, payment, refund, dispute, complaint, and exception outcomes.
• Check that staff apply the process consistently.
• Stop or correct the change when it creates payment errors, inaccessible paths, consent failures, misleading copy, client harm, or data corruption.
• Do not wait for the end of the period to correct a known error.

Days 24–27 — reconcile

• Reconcile appointment counts to status counts.
• Reconcile payment events to refunds, credits, reversals, disputes, and recoveries.
• Review unresolved records and classification changes.
• Compare service mix, schedule availability, booking lead time, provider/resource mix, holidays, closures, and seasonality before comparing rates.
• Separate completed refill value from booked refill value.

Days 28–30 — decide

Choose one outcome:

• keep and monitor — the process is usable and no guardrail requires rollback;
• revise and retest — data or workflow shows a correctable issue;
• roll back — the change creates unacceptable friction, risk, inaccuracy, or operational cost;
• extend observation — the sample or service cycle is insufficient; or
• stop and escalate — legal, payment, consent, privacy, accessibility, or fairness review is unresolved.

Do not claim causation merely because the later rate is lower. Report the numerator, denominator, absolute counts, classification changes, concurrent changes, and limitations.

Worked editorial scenarios

All values below are EDITORIAL_SCENARIO. They are constructed only to demonstrate arithmetic and must not become defaults, benchmarks, targets, or recommendations.

Scenario A — denominator and mutually exclusive rates

EDITORIAL_SCENARIO: eligible appointments
EDITORIAL_SCENARIO: = 100 - 4 - 10 - 2 - 4
EDITORIAL_SCENARIO: = 80

EDITORIAL_SCENARIO: status reconciliation
EDITORIAL_SCENARIO: = 66 completed + 8 no-shows + 6 late cancellations
EDITORIAL_SCENARIO: = 80 eligible appointments

EDITORIAL_SCENARIO: no-show rate
EDITORIAL_SCENARIO: = 8 / 80
EDITORIAL_SCENARIO: = 10%

EDITORIAL_SCENARIO: late-cancellation rate
EDITORIAL_SCENARIO: = 6 / 80
EDITORIAL_SCENARIO: = 7.5%

EDITORIAL_SCENARIO: combined client-disruption rate
EDITORIAL_SCENARIO: = (8 + 6) / 80
EDITORIAL_SCENARIO: = 17.5%

The constructed rates are only as reliable as the status definitions and records. A different exclusion policy changes the denominator.

Scenario B — blocked booked value is not profit

EDITORIAL_SCENARIO: blocked booked value
EDITORIAL_SCENARIO: = 4 × $90
EDITORIAL_SCENARIO: = $360

EDITORIAL_SCENARIO: completed refill collection
EDITORIAL_SCENARIO: = 2 × $80
EDITORIAL_SCENARIO: = $160

Keep all four scenario magnitudes separate: $360 is listed booked value that had been reserved; $160 is collected cash from completed refill appointments; $45 is a separately timed amount collected under the hypothetical cancellation/no-show workflow and not yet refunded; $40 is a documented direct variable cash cost avoided. This draft does not subtract those fields or create an “unrecovered” or contribution proxy because they can have different timing, eligibility, refund, tax, package, membership, labor, capacity, and accounting bases. A derived comparison would require a complete, consistently defined basis approved by the operator and qualified financial reviewer. None of the four values is cash loss, profit loss, damages, tax loss, owner income, or evidence that a policy recovered value.

Scenario C — a lower no-show rate does not prove causation

EDITORIAL_SCENARIO: baseline no-show rate
EDITORIAL_SCENARIO: = 12 / 120
EDITORIAL_SCENARIO: = 10%

EDITORIAL_SCENARIO: test-period no-show rate
EDITORIAL_SCENARIO: = 7 / 110
EDITORIAL_SCENARIO: = 6.36% rounded for display

EDITORIAL_SCENARIO: displayed no-show-rate difference
EDITORIAL_SCENARIO: = 6.36% - 10%
EDITORIAL_SCENARIO: = -3.64 percentage points

EDITORIAL_SCENARIO: baseline client-disruption rate
EDITORIAL_SCENARIO: = (12 + 6) / 120
EDITORIAL_SCENARIO: = 15%

EDITORIAL_SCENARIO: test-period client-disruption rate
EDITORIAL_SCENARIO: = (7 + 9) / 110
EDITORIAL_SCENARIO: = 14.55% rounded for display

The no-show category fell more than the combined disruption category in this constructed example. Possible explanations include reclassification from no-show to late cancellation, a real process effect, different clients/services, schedule mix, seasonality, or data error. The arithmetic does not decide which explanation is true.

Scenario D — deposits, refunds, and retained amounts must reconcile

EDITORIAL_SCENARIO: gross deposit cash
EDITORIAL_SCENARIO: = 3 × $30
EDITORIAL_SCENARIO: = $90

EDITORIAL_SCENARIO: net deposit cash after refund
EDITORIAL_SCENARIO: = $90 - $30
EDITORIAL_SCENARIO: = $60

EDITORIAL_SCENARIO: reconciliation
EDITORIAL_SCENARIO: = $30 applied to completed service + $30 retained under constructed policy
EDITORIAL_SCENARIO: = $60 net deposit cash

This scenario does not establish that EDITORIAL_SCENARIO: $30 is an appropriate or lawful deposit, that the retained amount is revenue, that the refund rule is valid, or that the transaction falls under a particular payment law. The payment rail, authorization, disclosure, processor terms, state law, tax, gift-card, and accounting treatment remain unresolved. [G07-S08, G07-S09, G07-S12]

Vertical implementation paths

The definitions stay stable, but the capacity unit, client journey, exception process, and evidence differ. These are EDITORIAL_METHOD prompts, not vertical benchmarks.

Hair salons

• Separate consultation, color correction, multi-stage services, assistants, processing time, and chair/provider constraints.
• Do not multiply a long-service menu price by every blocked hour and call the result lost profit.
• Record whether a replacement client could actually use the provider, duration, service capability, preparation, and notice available.
• Review product preparation or patch-test dependencies as operational inputs without offering clinical or legal conclusions.

Barbershops

• Separate appointment capacity from walk-in capacity and queue abandonment.
• Do not treat an unfilled appointment as fully blocked when the shop actually served a walk-in in that slot.
• Define whether the capacity unit is barber time, chair time, or a hybrid.
• Keep chair-rental or worker-model questions outside this guide's no-show arithmetic.

Nail salons

• Preserve technician, station, service duration, removal/repair/add-on time, and ventilation/workflow constraints.
• A replacement must match the service, technician capability, station, and usable duration.
• Do not generalize a deposit or exception rule from one service to all nail services without the required review.

Spas

• Model room, therapist/provider, turnaround, laundry, intake, preparation, and membership/package terms separately.
• A room becoming free does not prove another qualified provider or prepared client can refill it.
• Keep non-medical operations distinct from any service requiring additional clinical or regulatory review.

Med spas

• Treat appointment communication, eligibility, records, deposits, privacy, clinical readiness, and licensed-provider availability as separate controls.
• This guide does not decide medical necessity, clinical eligibility, scope, supervision, cancellation of medical services, HIPAA applicability, or state consumer-health-data requirements.
• Require qualified clinical, privacy, payment, and jurisdiction review before using any path in this draft.

PMU, brows, and lashes

• Separate consultation, eligibility, patch-test or preparation workflow where actually applicable, initial service, fill/touch-up, and follow-up.
• Verify whether deposits, consent, age, body-art, professional-board, health-department, and refund rules apply to the exact service and location.
• Do not treat a touch-up window or fill cycle as a universal no-show policy.

Independent professionals

• Measure the provider's real saleable time and administrative time without calling every open hour lost revenue.
• Design a cancellation route that remains usable while the professional is performing services and cannot answer immediately.
• Name a backup decision process for emergencies, provider illness, facility failure, and payment corrections.

Salon suites

• Separate the suite operator's appointment policy from landlord, shared-building, or platform rules.
• Record access, parking, building closure, security, and shared-system failures that can affect attendance.
• Do not assume the suite agreement decides client-payment, consumer, communication, or accessibility obligations.

Copyable worksheets

Appointment event worksheet

G07 APPOINTMENT EVENT — EDITORIAL WORKSHEET

CONTROL
Analysis event ID:
Appointment system ID:
Location/timezone:
Policy ID/version:
Consent/message template versions:
Payment-flow version:
Data extraction date/query version:

APPOINTMENT
Service family and exact service:
Provider/resource:
Scheduled start/end:
Booked duration:
Booking source:
Booking lead time:
Booked service value definition and amount:

PRIMARY STATUS — SELECT EXACTLY ONE
[ ] completed
[ ] client_no_show
[ ] client_late_cancellation
[ ] rescheduled_before_cutoff
[ ] business_or_provider_cancellation
[ ] late_arrival_not_served
[ ] approved_exception
[ ] duplicate_test_or_admin_hold
[ ] unresolved

STATUS EVIDENCE
Cutoff and decision point:
Cancellation/reschedule timestamp and channel:
Business/provider failure involved:
Exception category and owner:
Unresolved evidence:

COMMUNICATION
Confirmation channel/template/time/result:
Reminder channel/template/time/result:
Client response/confirmation:
Revocation/opt-out/preference event:
Delivery/access problem:

REFILL
Slot released at:
Refill eligible under defined method:
Offers attempted:
Replacement booked:
Replacement completed:
Refill collected amount under defined method:

PAYMENT
Flow type/rail:
Amount collected:
Disclosure/acceptance evidence:
Refund/credit/reversal:
Dispute opened/resolved:
Net cash effect within period:

CORRECTION
Complaint or friction signal:
Data correction:
Policy/process correction:
Owner and due date:

Policy and payment approval worksheet

G07 POLICY/PAYMENT APPROVAL — NOT LEGAL OR PROCESSOR APPROVAL

Selected jurisdiction:
Exact services and booking types:
Processor/acquirer/network:
Payment rail and transaction pattern:
Deposit/prepayment/card-on-file/recurring-transfer distinction:
Policy text and version:
Display location and timing:
Acceptance record:
Cancellation cutoff and timezone:
Refund/credit logic:
Exception and accessibility process:
Gift-card/membership/package interaction:
Tax/accounting questions:
Dispute evidence workflow:
Current processor terms captured at:
State/local primary sources captured at:
Payments reviewer:
Legal reviewer:
Accounting/tax reviewer:
Decision and limitations:
Refresh triggers:

Reminder and consent matrix

G07 MESSAGE CONTROL

Template ID/version:
Primary purpose:
Exact copy/links/media:
Channel:
Sending technology/vendor:
Recipient selection rule:
Consent/relationship basis used by reviewed process:
Evidence and timestamp:
Revocation/opt-out handling:
Suppression synchronization:
Delivery status fields:
Quiet-hours/frequency decision:
State-law/privacy review:
Accessibility/alternate channel:
Promotional content present:
Communications/privacy reviewer:
Approval scope and expiry:

Dashboard worksheet

G07 DASHBOARD — EDITORIAL_METHOD

Observation period/timezone:
Status-definition version:
Included locations/services/providers/sources:
Raw scheduled appointments:
Excluded business/provider cancellations:
Excluded advance reschedules:
Excluded duplicate/test/admin holds:
Other exclusions:
Eligible scheduled appointments:
Completed:
Client no-shows:
Client late cancellations:
Late arrivals not served:
Approved exceptions:
Unresolved:

No-show rate formula/result:
Late-cancellation rate formula/result:
Combined disruption rate formula/result:

Reminder attempted/delivered/failed/replied/opted out:
Released slots:
Refill offers/bookings/completions:
Completed refill rate formula/result:

Blocked booked value definition/result:
Amounts collected:
Refunds/credits/reversals:
Disputes/debits/recoveries:
Refill collected amount:
Direct variable cash cost avoided definition/result:
Any contribution proxy formula/result and exclusions:

Complaints/access failures:
Concurrent changes:
Sample/seasonality/service-mix limitations:
Owner decision:

Bookendo commercial boundary

Salon.guide and Bookendo share ownership. That relationship must be disclosed next to any future Bookendo link or product mention.

The internal note docs/BOOKENDO_CLAIM_VERIFICATION_2026-07-12.md recorded that Bookendo's public page stated, when checked on 2026-07-12, that the product offered online booking/public profiles, appointment and schedule management, automatic SMS/email reminders and confirmations, and deposits/pre-payments during booking. That note also requires refresh before production and when the public feature set changes.

Those are narrow, vendor-published feature statements—not independent performance evidence. They do not establish:

• that Bookendo reduces no-shows or late cancellations;
• a delivery, consent, compliance, accessibility, dispute, refund, or payment outcome;
• suitability for a selected jurisdiction, processor, service, or business;
• a ranking or comparison against another platform; or
• that any feature is included, configured, available, or unchanged for a particular account.

This editorial draft therefore contains no Bookendo recommendation or product CTA. If a later immutable revision adds a contextual link, it must use an adjacent common-ownership disclosure, rel="sponsored noopener noreferrer", refreshed first-party evidence, and no guarantee, ranking, conversion claim, or claim that the software itself solves no-shows.

Related Salon.guide resources

• Client Experience hub — policies, communication, booking, and service-recovery resources.
• No-Show Cost Calculator — model blocked booked value separately from profit after its own methodology and evidence gate.
• Cancellation Policy Template — structure policy decisions only after local payments/legal review.
• Salon Client Retention and Rebooking Guide — distinguish attendance, rebooking, and cohort return behavior.
• Salon Marketing Plan — keep promotional communication and claims separate from operational reminders.
• How to Choose Salon Software — evaluate requirements, consent logs, payments, data, exports, and vendor evidence without turning this guide into a software ranking.

These resources may remain draft or subject to separate gates. An internal link does not assert that the destination is publication-ready.