Resources
Represent the people, rooms, equipment, stations, and other limited capacity your work depends on
Every business has things that cannot be in two places at once.
A person can only perform so much work at the same time.
A treatment room can only hold one appointment at a time.
A wash station, grooming table, service bay, piece of equipment, or workstation may also be shared between many Services throughout the day.
SkedSERVICE represents those real, limited things as Resources.
Resources are the actual capacity the scheduling engine works with when deciding whether a Service can happen at a particular time.
A Resource is something the work actually depends on
A Resource can represent a person:
- a stylist;
- a massage therapist;
- a groomer;
- a technician;
- an instructor.
But Resources are not limited to staff.
They can also represent:
- treatment rooms;
- styling chairs;
- wash stations;
- grooming tables;
- workstations;
- equipment;
- service bays;
- or other limited things your Services need.
The important question is not whether something is a person or an object.
The important question is:
Does its availability affect whether the work can happen?
If the answer is yes, it can be useful to represent it as a Resource.
Roles describe what a Resource can be used for
A Resource is the actual person, room, station, or piece of equipment.
A Role describes the kind of requirement that Resource can satisfy.
For example:
| Resource | Role |
|---|---|
| Maria | Stylist |
| Alex | Stylist |
| Chair 1 | Styling Chair |
| Chair 2 | Styling Chair |
| Wash Station 1 | Wash Station |
| Room A | Treatment Room |
A Task does not need to know every individual Resource that might be suitable.
Instead, it can define the Role it needs.
SkedSERVICE can then look at the Resources capable of satisfying that Role.
This separates:
what the work requires
from:
which actual Resource is available to provide it.
Resources turn abstract requirements into real capacity
Consider a Task called Color application.
It requires:
- a Stylist;
- a Styling Chair.
Those are Role requirements.
The business might have:
| Resource | Role | Available at 10:00? |
|---|---|---|
| Maria | Stylist | No |
| Alex | Stylist | Yes |
| Chair 1 | Styling Chair | Yes |
| Chair 2 | Styling Chair | No |
The requirement does not fail simply because Maria or Chair 2 is unavailable.
Suitable capacity still exists:
| Requirement | Resource that can satisfy it |
|---|---|
| Stylist | Alex |
| Styling Chair | Chair 1 |
That is the difference between defining a Service around specific objects and defining it around the capacity the work actually needs.
People and physical Resources participate in the same scheduling model
From the scheduling engine’s perspective, a staff member and a treatment room have something important in common:
both have limited availability.
A massage appointment may need:
- a Massage Therapist;
- and a Treatment Room.
Neither requirement alone is enough.
A therapist without a room cannot perform the appointment.
An empty room without a suitable therapist cannot perform it either.
For the Task to happen, SkedSERVICE needs to be able to satisfy the Resource requirements that Task defines.
For example:
| Requirement | Available Resource |
|---|---|
| Massage Therapist | Elena |
| Treatment Room | Room B |
When both requirements can be satisfied at the required time, that part of the Service has the capacity it needs.
Resource availability matters when the Task needs the Resource
A Resource does not necessarily need to be available for an entire Service.
It needs to be available during the Task or Tasks that require it.
Consider a salon Service:
| 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 does not need to be available at 10:00.
It is not required until 11:10.
Likewise, the Stylist is not required during the Processing Task in this example.
SkedSERVICE can evaluate Resources according to when the workflow actually needs them, rather than assuming that every Resource involved in a Service must remain occupied from the appointment’s beginning to its end.
Resources can become available again while an appointment continues
Suppose a stylist finishes applying color at 10:40.
The customer’s Service is not finished.
The customer still has processing, rinsing, and finishing ahead.
But during the Processing Task, that Service may no longer require the stylist.
That distinction matters.
The appointment continues.
The customer remains in the workflow.
But the Resource that performed the previous Task may potentially be available for other work.
The same principle applies to physical Resources.
A Styling Chair used during one Task does not need to remain blocked during later Tasks if those Tasks no longer require it.
A Wash Station needed later does not need to be reserved before its Task begins.
This allows Resource occupancy to follow the work itself.
Shared Resources can limit otherwise open schedules
A calendar can appear to have plenty of free time while the business still lacks the Resources necessary to perform a Service.
Imagine two massage therapists are available at 2:00 PM, but the business has only one treatment room.
Two therapists do not create capacity for two simultaneous appointments if both appointments also require the same limited room.
Likewise:
- several groomers may share one bathing station;
- several stylists may share a limited number of wash stations;
- several technicians may depend on one piece of equipment;
- several Services may depend on the same specialized room.
SkedSERVICE can include those shared Resources in the scheduling model.
That allows availability to reflect the constraints that actually exist in the business.
Resources help prevent conflicting use
When a Resource is needed by scheduled work, that capacity is no longer available for conflicting work during the same period.
This applies whether the Resource is:
- a person;
- a room;
- a chair;
- a station;
- equipment;
- or something else represented in the Resource pool.
For example, if Treatment Room A is already required by a Task between 10:00 and 11:00, another Task that also needs that same Resource cannot use it during the conflicting period.
The same rule applies to a staff member who is already required elsewhere.
This helps the schedule answer a more useful question than:
“Is there empty space on the calendar?”
It can instead ask:
“Can the business actually provide everything this Service needs at this time?”
Resources can represent interchangeable capacity
Businesses often have more than one Resource capable of satisfying the same requirement.
For example:
| Resource | Role |
|---|---|
| Maria | Stylist |
| Alex | Stylist |
| Sofia | Stylist |
A Task requiring a Stylist does not necessarily depend on one of those people specifically.
The Role tells SkedSERVICE what kind of Resource is needed.
The Resource pool tells SkedSERVICE which actual options exist.
If one suitable Resource is unavailable but another is available, the requirement may still be satisfiable.
The same principle applies to physical capacity:
| Resource | Role |
|---|---|
| Room A | Treatment Room |
| Room B | Treatment Room |
| Room C | Treatment Room |
The Service depends on having a suitable Treatment Room available.
It does not necessarily depend on one particular room.
Different Tasks can require different Resources
A Service does not need to use the same Resources throughout its entire duration.
That is one of the reasons Resources are connected to Tasks rather than treating the appointment as one indivisible block.
For example:
| Task | Required Resources |
|---|---|
| Consultation | Stylist, Styling Chair |
| Color application | Stylist, Styling Chair |
| Processing | Waiting Chair |
| Rinse | Stylist, Wash Station |
| Finish | Stylist, Styling Chair |
Each Task describes the capacity needed for that stage.
The complete Service is therefore a sequence of changing Resource requirements.
This gives SkedSERVICE enough information to understand not just how long the appointment lasts, but also what the business needs throughout that time.
Resource schedules are part of real availability
Business opening hours alone do not determine whether a Service can be booked.
A business might be open from 9:00 AM to 5:00 PM, but that does not mean every Service can begin at every point inside those hours.
For a potential start time to work, the necessary Resources must also be available when each Task needs them.
For example:
| Time | Requirement | Result |
|---|---|---|
| 10:00 | Stylist | Available |
| 10:00 | Styling Chair | Available |
| 10:40 | Waiting Chair | Available |
| 11:10 | Stylist | Available |
| 11:10 | Wash Station | Unavailable |
Even though most of the workflow fits, this particular start time cannot satisfy all of the Service’s Resource requirements.
The apparently open time is therefore not truly available for that Service.
This is how Resource-aware scheduling turns general business availability into Service-specific bookable availability.
Why represent Resources explicitly?
Prevent double booking of limited capacity
People, rooms, stations, and equipment can be treated as real scheduling constraints rather than assumptions the business has to remember manually.
Make shared capacity visible to the scheduling engine
If several staff members depend on the same room or equipment, the scheduler can account for that shared limitation.
Avoid blocking Resources longer than necessary
Resources can be required during the Tasks that actually need them rather than automatically for the full duration of the appointment.
Use interchangeable capacity
Several Resources can satisfy the same Role, allowing the scheduler to work with suitable capacity that is actually available.
Model more than staff calendars
The schedule can represent the physical and operational constraints around the people doing the work.
Make bookable times more truthful
A time is useful only if the business has the actual capacity required to deliver the Service.
A simple way to think about Resources
The relationship between the main scheduling concepts is:
| Concept | Question it answers |
|---|---|
| Service | What is the customer booking? |
| Task | What work needs to happen, and when? |
| Role | What kind of Resource does that work need? |
| Resource | What actual person, room, station, or equipment can satisfy that requirement? |
| Availability | Can those requirements be satisfied throughout the Service? |
A Resource is where the scheduling model meets the real world.
It is the actual capacity that turns a Service from something the business offers into something the business can genuinely deliver at a particular time.