← All posts

Salon booking window: minimum notice and how far ahead clients can book

Set a salon booking window from preparation time and approved staff schedules. Use the service worksheet, boundary checks and three client messages.

An emerald salon chair on a paper calendar between a clock and clipped future pages

A salon booking window sets the earliest and latest appointment a client can reserve today. Choose limits that give your team time to prepare and keep offered dates within the approved staff schedule. Decide both ends before opening another month of the calendar.

The worksheet and times below are planning examples, not industry benchmarks. Use your own preparation tasks, staffing decisions and client requests to choose the limits for each service.

Separate minimum notice from the furthest bookable date

Minimum notice is the gap required between making a booking and starting the service. A four-hour rule means a client browsing at 10:00 cannot reserve an appointment starting before 14:00. A booking horizon limits how far into the future appointments are offered. A 42-day horizon controls the other end of the calendar.

Microsoft's scheduling policy documentation describes these as separate controls and notes that its minimum notice uses elapsed hours rather than business hours. Check the calculation in the tool you use; labels and boundary behaviour can differ.

Service duration determines how much time a visit occupies. Preparation between visits needs its own space. Changing the advance-booking limits does not make a long service fit into a short gap. Use the service duration guide when the uncertainty concerns what happens during the visit.

Choose minimum notice from work that must happen first

For each service, list what needs to be complete before the client arrives. Include reviewing the requested work, checking materials, assigning a suitable professional and receiving any information needed to agree the scope. Give each task an owner and a realistic completion time.

Ask when someone can do those tasks. If reception closes at 18:00 and reopens at 09:00, a booking made at 22:00 for 10:00 leaves one staffed hour for review. Twelve elapsed hours have passed, but most of them provided no opportunity for the team to prepare.

Walk through the slowest required task before choosing the cutoff. Some tasks run together; others wait for a colleague's answer or for a delivery. Do not add every estimate mechanically. Write down the sequence and identify the point when the service can safely be promised.

For an illustrative standard service, the team might need 20 minutes to review the request and prepare the station, with someone available throughout the advertised booking hours. For a specialist session, that review may only happen at fixed times. The two services can reasonably have different notice rules even when their treatment lengths are similar.

Where the scope needs a conversation, offer a consultation or a request for review using a route the team monitors. Tell the client when to expect an answer. A request needs an explicit status until the team can confirm the service and its time.

Open dates only as far as the rota is reliable

Write down the latest dates for which staff availability, opening hours and essential shared resources are approved. Use the earliest relevant limit for the service being offered.

Suppose the studio wants to offer appointments 56 days ahead. Staff availability is approved for 42 days, and a required room is confirmed for 49 days. For that service, 42 days is the supported starting horizon. Offering all 56 days would include dates with staffing still undecided.

The whole studio does not need to share one horizon. An owner working an established schedule may be able to commit further ahead than a visiting professional whose dates arrive monthly. Document these differences by service or professional so reception can explain the dates clients see.

Before expanding the horizon, resolve known leave and closure dates. Use the weekly capacity worksheet to check staffed time and service skills. Keep unapproved weeks out of the offered schedule until someone takes responsibility for opening them.

Give each service a short booking-window record

Use one row per service group. Combine groups when their preparation and staffing constraints are the same. Avoid creating an exception for every small variation in the menu.

Field Decision to record
Service group The services covered by this rule
Required preparation Tasks that must finish before arrival
Review coverage Who reviews requests, and when
Minimum notice The proposed interval and how it is counted
Furthest date offered The limit supported by the approved schedule
Release routine Who opens more dates, on which day
Requests outside the window Contact route and realistic reply time
Existing bookings Which commitments stay in place
Version and review Effective date, owner and next check

For a studio testing three service groups:

Service group Minimum notice to test Horizon to test Condition before release
Standard repeat service 4 elapsed hours 42 days Qualified cover approved for all offered shifts
Specialist session 24 elapsed hours 28 days Reviewer available and materials checked
Group visit Reviewed request Dates agreed individually All required staff and resources confirmed

These numbers describe one example operation. A group request cannot be represented by an automatic confirmation if staff still need to check several schedules. Give the person coordinating the group a clear reply deadline and record who owns the review.

Check that regular clients can book their next visit

Compare the proposed horizon with the return dates clients ask for. If a client wants to return in six weeks but the calendar only opens four weeks ahead, staff need a consistent response. An invitation to book again is frustrating when the relevant dates are unavailable for administrative reasons.

Choose a process your team can maintain: approve more of the rota, agree individual future bookings after checking availability, or offer to contact the client when dates open. A request for contact should state what happens next and whether any time has been reserved.

For contact lists, record the requested period, service, suitable professional, agreed contact route and follow-up owner. Check that contacting the client about newly released dates will not duplicate an existing booking. Keep these requests separate from a list of clients waiting for cancellations on dates already open.

The rebooking measurement worksheet can help distinguish a confirmed future visit from an intention to return. Keep a request for unopened dates recorded as a request until a booking is agreed.

Make the release routine manageable

A rolling horizon moves forward with time. A fixed release opens a block of approved dates together. Choose the approach the team can keep accurate, then explain it in specific terms.

For a rolling approach, check that the next day entering the window has staff and resource cover. A nominal 42-day setting can expose a new day before anyone has checked it. For a block release, write down the release date and the period being opened. Avoid promising a release time while leave requests remain unresolved.

Use a small release checklist: approve the rota, apply closures and protected time, verify service availability, check the client view, then update the message about dates. Assign an owner and a backup so opening the next period does not depend on one person's memory.

Skedful's page for hair salons describes service scheduling and the client booking page. Check what clients can reserve against your approved schedule. Confirm the advance-booking controls available in your account before mapping this worksheet to settings, and name the person who manages date releases and exceptions.

Test the boundaries in the client view

Check the actual booking route on a phone before publishing the policy. Use a test service or another controlled method that avoids making live availability inaccurate. Record the current time, business time zone, requested service and expected result for each case.

  1. Try a start just before the minimum-notice boundary, then one at or after it. Choose valid start intervals for both tests.
  2. Check the latest date intended to be open and the following date. Confirm whether the horizon counts dates or exact elapsed time.
  3. Repeat outside reception hours. A bookable morning appointment must still leave enough staffed preparation time.
  4. Check an approved closure, a professional's day off and a service requiring a shared room. A date within the window still needs real availability.
  5. Open the public page without a staff login. Confirm that the client sees the intended services and dates.
  6. Test across a clock change if your region observes one. Compare explicit local dates and times rather than assuming every calendar day contains the same number of elapsed hours.

If a boundary result differs from the written rule, resolve the setting or wording before relying on it. Save the observed result with the policy record so another team member can repeat the test after a configuration change.

Give clients a useful answer outside the window

For a requested appointment that starts too soon:

We need [notice] to prepare [service]. The earliest available option we can confirm is [date and time, time zone]. For a request sooner than that, contact [route]. We will check whether we can prepare in time before agreeing a booking.

For a date that has not opened yet:

Our calendar is currently open through [date]. We expect to open [next period] on [release date, if approved]. If you would like us to contact you then, send [necessary details] through [route]. This request does not reserve a time.

For a requested specialist whose future dates are pending:

[Professional]'s dates after [date] are awaiting confirmation. We can offer [verified alternative] or contact you once those dates are approved, if you prefer. We will confirm the appointment separately when a suitable time is available.

Replace every bracket and remove a release promise that the manager has not approved. Give reception one current version to use on the phone and in writing. An exception needs the same preparation and availability check as any other booking.

Review requests the rule could not accommodate

For the first four weeks, log requests that fell before the earliest permitted start or beyond the furthest open date. Record the service, requested date, reason it could not be offered and whether the client accepted an alternative. Include requests made by phone so the review covers more than successful online bookings.

Look at repeated causes before changing a limit. Several suitable requests beyond the horizon may justify approving the rota earlier. Several short-notice requests that need no extra preparation may justify a controlled trial for that service. A specialist shortage needs a staffing decision even if the studio has other open hours.

Change one rule for a defined service group and retain already confirmed bookings unless an individual change is agreed. Write the next release date and its owner into the worksheet, then run the boundary tests before those dates become available to clients.

About this article

Skedful is responsible for this blog.

Worked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.

Found an error? Send us the article link and the passage that needs a correction.

Report an error to Skedful

Reminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy