Scheduling a team: when every staff member has their own hours and services

A one-person business copes with a calendar. A three-person business does not, and not because of volume — because "is 14:00 free?" stops being one question. Free with whom, and for what exactly.

What has to be per-person

• Working hours. Someone who works Tuesday to Thursday should not show as available on Sunday.
• Their service list. Not everyone who cuts also colours. Assigning services to a person is what prevents a booking nobody can perform.
• Time off. One person being away does not close the business; it only thins their availability.

What stays shared

Prices, service durations and whole-business closures — a holiday, a refit, a team day — belong to the business. Manage them per-person and you get three versions of the same truth, none of them current.

Why the order of choices matters

What breaks a booking is not the order itself but a second list that is not filtered by the first choice. A customer who picks a service and is then shown the whole team can choose someone who does not perform it — a dead end right after they decided.

In Sagarnu the customer picks the service first, and the list of people shown next is narrowed to those who actually perform it. Availability is then computed from that person’s own hours. What it looks like.

Common questions