Working With Your Team

As soon as a second person takes bookings, the calendar stops being personal. Questions appear that simply did not exist before: whose client is this, who moved the visit, why is one stylist empty while another has a two-week queue. This guide is about setting up shared work so those questions have answers — and so the answers are not buried in chat threads.

The order is the same as everywhere else: first the things without which the rest does not work. Shared work starts not with access rights or schedules, but with making sure every action in the system has an author.

What changes when there is more than one of you

Alone, the system is a convenience: it remembers so you do not have to. In a team it becomes shared memory — the one place where it is visible who did what, and when. That sounds like a detail right up until the first disagreement about a moved visit.

Three things you have to settle immediately:

• Who works under which login — the entire history of actions depends on it;
• Who has which schedule — the page must offer a specific person’s time, not an abstract one;
• Who sees what — not everyone needs the money and the full client base.

Settle those three at the start and the rest is a technical detail. Leave them open and each one eventually turns into a conflict, to be sorted out exactly when there is least time for it.

Step 1. Everyone gets their own login

The invitation

Send the invitation to the person’s own work email, not to a shared salon mailbox. They set their own password — you do not know it and should not. From then on every booking, reschedule and cancellation carries the name of whoever did it, and the history becomes worth reading.

It also means the person can change their password, turn on two-step verification and sign out of someone else’s device without asking anyone. A personal login is not a formality; it is where responsibility begins.

Why not a shared password

A shared login looks simpler right up until the first unclear situation. When “somebody” moved a visit, the history has the action but not the author: working out what happened is impossible, however much you want to. The same goes for the client base — you can see a card was changed, but not by whom.

The second problem shows up later: when one person leaves the team, everybody has to change passwords everywhere. And until that is done, they still have access — not out of malice, but simply because nobody remembered.

A shared password is not saved time but a postponed problem. It comes back exactly when getting to the bottom of something matters most.

Step 2. Each person’s schedule

Working hours

Every member has their own working hours, and the page offers a client only the times that particular person is genuinely free. You never merge schedules by hand — but a mistake in someone else’s schedule costs more than one in your own: it is the stylist standing in front of the client who has to decline.

Set hours per weekday. In a team an uneven week is the rule rather than the exception: one person works three days, another only evenings, a third covers every Saturday.

Days off and holidays

Days off are set per person, not for the whole business. Block a holiday as soon as the dates are known: in a team this matters more, because clients often book “with a particular stylist”, and a refusal damages that relationship rather than the general schedule.

If someone is ill, block their time the same day. An empty slot nobody takes costs less than a booking that has to be cancelled an hour before it starts.

Covering for each other

If stylists cover for one another, decide the rule in advance: either the client picks the person, or the system offers whoever is free. Both work. Only the third option is bad — where the rule is never stated and every case is decided by hand, because then every cover becomes a negotiation.

Step 3. Services and who performs them

Not everyone does everything. If your colourist does not cut and your administrator performs no services at all, the system needs to know — otherwise a client gets booked with someone who cannot take them, and it gets sorted out on the doorstep.

The same service can also take different people different amounts of time. An experienced stylist does in an hour what a newcomer needs ninety minutes for, and honest numbers matter more than formal equality: otherwise the newcomer’s day slides every single day, and it is the person who looks at fault rather than the setting.

The same applies to prices if they differ by seniority. Better for the difference to be visible on the booking page than to become a surprise at the till.

Step 4. Access

Roles answer one question: what can this person see and change. Setting them once is easier than explaining later how the whole client base ended up somewhere else.

The minimum for a new person

A sensible starting set:

• their own calendar and their own bookings;
• the cards of the clients they work with;
• no access to revenue, prices or reports;
• no right to change services, other people’s schedules or account settings.

Access can be widened any time, in a minute. Taking it back is always awkward, because it reads as distrust even when the reason is purely technical. So start smaller: it is easier to explain at the start than to walk back a month later.

Money and the full base

Revenue, prices and the list of every client are exactly what is worth keeping narrow. A stylist rarely needs the whole base to do their own visits well, and almost nobody but the owner and whoever keeps the books needs the finances.

This is not about distrusting a particular person. It is that the client base is the most valuable asset the business has, and the number of people who can export it should be small by default.

Who changes settings

Services, prices, the booking page and the subscription stay with the owner. One person changing a price by accident is a bad day; several people changing it at once is a bad month and an argument with clients who saw different numbers.

Step 5. Whose client, and who is responsible

In a team every visit has an owner — the person who performs it. They get the notifications about new bookings, reschedules and cancellations, and it is their name the client sees in the confirmation. That removes the most common confusion: when notifications go to everyone, nobody acts on them.

The client base, meanwhile, belongs to the business rather than to an individual. That is not about trust but about continuity: people come and go, and the visit history has to stay where the client returns.

If a client always books with one particular person, the history shows it — and it is the history, not the administrator’s memory, that lets you offer a sensible alternative when that person is away.

When someone leaves

Close their access the same day, not “at the end of the month”. The bookings they took and the client history stay with the business — it is the access that ends, not the work. This is ordinary procedure, and it is better for it to be the same for everyone: then it does not read as personal distrust.

Move their upcoming visits to whoever will perform them, and tell those clients in advance. Someone who discovers the change of stylist on the doorstep almost certainly will not book again — and that is the loss not of one visit but of all the history that would have followed.

The owner’s weekly routine

Five minutes on Monday:

• check that everyone’s hours are open two weeks ahead;
• block known absences, holidays and training days;
• look at the load: who is empty, who has a queue;
• review the access list if the team has changed.

The last point feels unnecessary until you find that someone who left six months ago still has access. The first three surface problems before they become complaints: an empty schedule for one stylist while another has a queue is either a question of distribution or a question of the booking page, and either way it is better seen on Monday.