Availability
Offer times your business can actually deliver
An empty space on a calendar is not necessarily an available appointment.
A business may be open.
A staff member may appear free.
There may be no appointment visibly occupying that time.
And yet the Service the customer wants may still be impossible to perform.
That is because real availability depends on more than time.
It depends on whether the business can provide everything the Service needs throughout its workflow.
SkedSERVICE uses the Service’s Tasks, their timing, their Resource requirements, and the actual availability of suitable Resources to determine which start times can really work.
Availability is specific to the Service
Different Services can have different requirements.
A simple consultation may need:
- one suitable person;
- for 30 minutes.
A color Service may need:
- a Stylist and Styling Chair;
- then a Waiting Chair;
- then a Stylist and Wash Station;
- then a Stylist and Styling Chair again.
A massage may need:
- a Massage Therapist;
- and a Treatment Room;
- for the duration of the session.
Because the requirements are different, the same moment can be available for one Service and unavailable for another.
For example:
| Start time | Consultation | Hair color | Massage |
|---|---|---|---|
| 10:00 | Available | Unavailable | Available |
| 10:30 | Available | Available | Unavailable |
| 11:00 | Available | Available | Available |
There is no single answer to:
“Is 10:00 available?”
The useful question is:
“Can this particular Service be delivered if it starts at 10:00?”
Business hours are only the first boundary
The business must first be open when the work needs to happen.
If a business operates from 9:00 to 17:00, that establishes the general window in which work can be scheduled.
But opening hours alone do not create bookable capacity.
A business may be open while:
- the required staff are unavailable;
- the necessary room is occupied;
- equipment is already being used;
- a Resource has been blocked;
- or a later Task in the Service cannot be accommodated.
Business hours tell SkedSERVICE when scheduling is generally possible.
The Service’s requirements determine whether a particular appointment can actually fit inside that window.
The entire Service has to fit
A Service is made of ordered Tasks.
If the Service starts at a particular time, each Task begins at its corresponding point in the workflow.
Consider this 100-minute salon Service:
| Time from start | Task | Duration |
|---|---|---|
| 0 min | Preparation | 10 min |
| 10 min | Apply Color | 30 min |
| 40 min | Processing | 30 min |
| 70 min | Rinse | 10 min |
| 80 min | Finish | 20 min |
If the Service starts at 10:00, those Tasks occur at:
| Clock time | Task |
|---|---|
| 10:00 | Preparation |
| 10:10 | Apply Color |
| 10:40 | Processing |
| 11:10 | Rinse |
| 11:20 | Finish |
SkedSERVICE does not need only the beginning of the appointment to work.
The Resource requirements must remain satisfiable as the Service moves through all of those stages.
Each Task brings its own Resource requirements
Every Task can define the kinds of Resources it needs through Roles.
For example:
| Task | Required Roles |
|---|---|
| Preparation | Stylist, Styling Chair |
| Apply Color | Stylist, Styling Chair |
| Processing | Waiting Chair |
| Rinse | Stylist, Wash Station |
| Finish | Stylist, Styling Chair |
When evaluating a possible start time, SkedSERVICE needs to determine whether suitable Resources can satisfy those requirements at the moments when each Task occurs.
The question is therefore not simply:
“Is a Stylist free at 10:00?”
It is closer to:
“Can suitable Resources be found for every requirement of every Task at the time that Task needs them?”
A Resource only needs to be available when its Task needs it
One of the important consequences of Task-level scheduling is that a Resource does not necessarily need to be free for the entire Service.
Consider the same salon workflow:
| Time | Task | Required Resources |
|---|---|---|
| 10:00 | Preparation | Stylist, Styling Chair |
| 10:10 | Apply Color | Stylist, Styling Chair |
| 10:40 | Processing | Waiting Chair |
| 11:10 | Rinse | Stylist, Wash Station |
| 11:20 | Finish | Stylist, Styling Chair |
The Wash Station is irrelevant at 10:00.
It matters at 11:10.
The Waiting Chair is irrelevant during preparation.
It matters during processing.
The Stylist is not required during the Processing Task in this example.
Availability follows those changing requirements instead of assuming that every Resource involved in the Service must be free continuously from beginning to end.
A later conflict can make an earlier start time unavailable
Suppose everything needed at 10:00 is free.
That still does not automatically mean the Service can begin at 10:00.
Imagine this availability check:
| Time | Task | Requirement | Result |
|---|---|---|---|
| 10:00 | Preparation | Stylist | Available |
| 10:00 | Preparation | Styling Chair | Available |
| 10:10 | Apply Color | Stylist | Available |
| 10:10 | Apply Color | Styling Chair | Available |
| 10:40 | Processing | Waiting Chair | Available |
| 11:10 | Rinse | Stylist | Available |
| 11:10 | Rinse | Wash Station | Unavailable |
| 11:20 | Finish | Stylist | Available |
| 11:20 | Finish | Styling Chair | Available |
The Service cannot satisfy all of its requirements.
So even though 10:00 initially looked open, it is not a valid start time for this Service.
This is why availability has to look beyond the beginning of the appointment.
Roles allow availability to use the whole Resource pool
A Task may need a Stylist.
It does not necessarily need Maria.
Suppose the Resource pool contains:
| Resource | Role | Available at 10:00? |
|---|---|---|
| Maria | Stylist | No |
| Alex | Stylist | Yes |
| Sofia | Stylist | No |
The Stylist requirement can still be satisfied because Alex is available.
If the Task had been permanently tied to Maria, the same time would appear unavailable.
Roles allow SkedSERVICE to evaluate the suitable capacity that actually exists rather than treating one particular Resource as the only possible option.
The same principle applies to rooms, equipment, workstations, chairs, and other Resources.
Resource availability can differ from business availability
A business can be open even when a particular Resource is not available.
For example:
- the salon is open from 9:00 to 18:00;
- Maria works only until 15:00;
- Alex starts at 12:00;
- Treatment Room A is unavailable for part of the afternoon;
- a piece of equipment may be unavailable during a particular period.
SkedSERVICE can account for the availability of the Resources the work actually depends on.
This allows the business to remain generally available without pretending that every Resource is available every moment the business is open.
Blocked periods remove capacity temporarily
Sometimes a Resource would normally be available but should not be scheduled during a particular period.
That may happen because of:
- a break;
- a meeting;
- maintenance;
- training;
- personal time;
- preparation work;
- or any other reason the Resource should not be used for appointments.
A blocked period temporarily removes that Resource from the available pool.
For example:
| Resource | Normal availability | Blocked period |
|---|---|---|
| Alex | 9:00-17:00 | 12:00-13:00 |
| Wash Station 1 | 9:00-17:00 | 14:00-15:00 |
| Room A | 9:00-17:00 | None |
During the blocked period, SkedSERVICE cannot rely on that Resource to satisfy a Task requirement.
If another suitable Resource exists, the requirement may still be satisfiable.
If no suitable Resource remains available, affected start times become unavailable.
Existing appointments consume capacity
Resources already committed to scheduled work cannot simultaneously satisfy conflicting work.
If Alex is already required by another Task from 10:00 to 10:30, Alex is not available to satisfy another overlapping requirement during that period.
The same applies to physical Resources.
If Wash Station 1 is already in use, another Task cannot depend on that same station at the same time.
But if Wash Station 2 is suitable and available, the Wash Station Role may still be satisfiable.
For example:
| Resource | Role | Status |
|---|---|---|
| Wash Station 1 | Wash Station | In use |
| Wash Station 2 | Wash Station | Available |
The requirement can still be met.
Availability depends on whether sufficient suitable capacity remains, not whether every Resource is free.
Shared Resources can become the limiting factor
Staff availability is only one part of capacity.
Imagine a wellness clinic with:
- three Massage Therapists;
- two Treatment Rooms.
At 14:00:
- Therapist A is performing a massage in Room 1;
- Therapist B is performing a massage in Room 2;
- Therapist C is available.
The clinic has an available therapist, but both Treatment Rooms are already in use.
So the business cannot accept another massage appointment at that time.
The limiting Resource is not staff.
It is the Treatment Room.
The same situation can occur with:
- bathing stations in a grooming business;
- wash stations in a salon;
- treatment rooms in a clinic;
- equipment in a technical service;
- service bays in a workshop;
- or any other shared Resource.
Resource-aware availability allows those real constraints to influence which times are offered.
A Resource can return to the available pool before the Service ends
Because Resource requirements are attached to Tasks, capacity can change while an appointment is still underway.
Consider this Service again:
| Time | Task | Stylist needed? |
|---|---|---|
| 10:00 | Preparation | Yes |
| 10:10 | Apply Color | Yes |
| 10:40 | Processing | No |
| 11:10 | Rinse | Yes |
| 11:20 | Finish | Yes |
At 10:40, the customer’s appointment continues.
But the Stylist is no longer needed by the Processing Task.
That Resource can potentially satisfy other work during that period.
At 11:10, the Service needs a Stylist again.
This allows Resource occupancy to follow the actual workflow rather than automatically following the full duration of the customer’s appointment.
The same business can have several kinds of availability
There are several different questions hidden inside the word “available”:
Is the business open?
Is a suitable Resource normally available?
Has that Resource been blocked?
Is it already committed to other work?
Can the Resource requirements of this particular Service be satisfied throughout its Tasks?
SkedSERVICE brings those questions together when determining whether a start time can work.
That is what turns general availability into bookable availability.
Availability can change without changing the Service
The Service definition may remain exactly the same while its bookable times change throughout the day.
For example, the Service may always require:
- a Stylist;
- a Styling Chair;
- a Waiting Chair;
- and a Wash Station.
But the available Resources capable of filling those Roles change as:
- staff begin and end their workdays;
- appointments consume capacity;
- Resources enter or leave blocked periods;
- rooms and equipment become occupied or free again.
The Service describes the work.
The Resource pool describes the capacity currently available to perform it.
Bookable availability emerges from the intersection of the two.
Why calculate availability this way?
Offer times the business can actually fulfill
A start time is useful only if the Service’s requirements can be satisfied throughout the appointment.
Account for more than staff calendars
Rooms, workstations, equipment, and other limited Resources can affect availability too.
Avoid hidden downstream conflicts
A Service is not considered workable merely because its first Task can begin.
Later Tasks and their requirements matter as well.
Use interchangeable capacity
If one Resource is busy but another suitable Resource can fill the same Role, capacity may still exist.
Avoid unnecessarily blocking Resources
Resources only need to be occupied during the Tasks that actually require them.
Let different Services have different availability
A simple Service and a Resource-intensive Service do not have to share the same set of bookable times.
A simple way to think about availability
SkedSERVICE starts with the work the customer wants to book and asks whether the business has the capacity to deliver it.
The relationship looks like this:
| Layer | Question |
|---|---|
| Business availability | Is the business operating during this period? |
| Service | What is the customer trying to book? |
| Tasks | What work happens, and when? |
| Roles | What kinds of Resources does each Task need? |
| Resources | Which actual suitable people, rooms, stations, or equipment exist? |
| Resource availability | Are those Resources available when the Tasks need them? |
| Existing commitments and blocks | Has that capacity already been removed or reserved? |
| Bookable availability | Can the entire Service actually be delivered from this start time? |
The result is not simply an empty slot.
It is a time at which the business has the real capacity required to perform the Service.