Processing time and buffer time: accounting for the dead time in a service

Colour, perms, and straightening all carry a stretch of dead time. The stylist applies colour and then waits 30 to 60 minutes for it to develop, mostly hands-free. After the appointment ends, the chair still needs a few minutes of cleanup before the next client sits down. How a booking system accounts for both kinds of dead time decides how many more clients the same available facilities and staff can actually take in a day.

Two different kinds of dead time: buffer time and processing time

The names sound similar, but they're not the same thing.

Buffer time (cleanup time): the time needed after a service ends. During it, neither the assigned staff member nor the chair can take another booking.
Processing time: the wait inside a service. The client stays in the salon and the chair stays occupied, but the assigned staff member is genuinely free.

This isn't a distinction Biseo invented — it's already the industry standard. Mangomint documents the two as entirely separate concepts, stating plainly that "clients will not be able to book appointments via online booking during the buffer times of existing appointments" (Mangomint, "Processing, Finishing, and Buffer Times"). Processing time, by contrast, is treated by several platforms as a window where a second client can be booked in.

How other platforms calculate this

Boulevard, Vagaro, and Phorest mostly use an additive model — you enter an initial duration, a processing duration, and a final duration separately, and the platform adds them up into the total service length. Boulevard calls these "Initial/Processing/Final Duration," and lets clients self-book into the processing window online, but only "if their desired service fits within the allotted Processing Time" (Boulevard, "Service Timing Options"). Vagaro describes booking into a processing gap as being done "the same way as booking any other service" (Vagaro, "Manage Gap Processing Time"). Phorest offers the same concept under the name "Development Time" (Phorest, "Automatic gap for development time").

💡Note

The quotes above come from each platform's own current support documentation, but support pages change over time. Confirm the current behaviour directly with the platform before relying on it for a real decision.

Biseo's approach: keep the total duration, carve out a window inside it

The additive model is clean, but it comes with a cost — a service you've already listed as "45 minutes" has to be re-split into "15 min apply + 20 min processing + 10 min finish." For a salon that already has bookings on file and has been telling clients "45 minutes" all along, that's a migration that changes what the service duration itself means.

Biseo instead uses a carve-out model. A service's total duration (say, 45 minutes) stays exactly as it is; you only add an offset inside that 45 minutes marking when the staff-free window starts and how long it lasts. The duration shown to clients, the booking history you already have, and your revenue calculations don't need to change at all. Leave processing time off and everything behaves exactly as before — it's opt-in per service, off by default.

Should you turn it on?

The default-off setting is deliberate. Turning processing time on means "I'll take another client during this window" — which only makes sense if there's actually someone free to take that client. A solo stylist with no other staff has no one to hand a second client to while the colour develops, so there's nothing to gain from turning this on — buffer time alone covers the need. If you have multiple staff and genuine spare capacity during that wait, the same chair can now serve more appointments in a day.

One tricky case: the gap-filling booking's own cleanup time

This came up during real testing. A colour appointment (client A) runs 10:00–11:10, and 10:30–11:10 (40 minutes) of that is a processing window where the staff member is free. We tried booking a 40-minute haircut for a second client (B) into that exact window — but the haircut service itself carries its own 10-minute cleanup buffer, meaning it actually needed 50 minutes (40 + 10). The gap is exactly 40 minutes, so on paper that looks like it doesn't fit.

The real question is whether client B's 10-minute cleanup genuinely has to finish inside that gap. The stylist does need to be back with client A the moment the processing window ends at 11:10 — but cleaning client B's chair afterward doesn't require the stylist's hands, so it doesn't have to happen before then. We went back through the same platforms' documentation and found none that spell out this exact interaction (a gap-filling booking's own cleanup time). Boulevard's own wording is the closest guidance available — it talks about whether the requested service fits the processing time, not the service plus its own cleanup.

So Biseo exempts a gap-filling booking's own cleanup time from needing to fit inside the gap. In the example above, client B's 40-minute haircut fits the 40-minute gap exactly and gets booked; the following 10-minute cleanup happens after, outside the gap. Without this exemption, almost no real service — most carry at least some cleanup buffer — could ever actually use a processing gap, which would make the whole feature pointless in practice.

Where to turn it on

Setting	What it controls	Default
Service edit screen	Per-service "has processing time" toggle + start offset/length	Off
Booking policy settings	Per-service and shop-wide cleanup buffer	0 min
Booking policy settings	Whether the online booking form can offer processing gaps too	Off

Processing time is admin-only by default — it's meant for the owner to manually fill that window from the calendar, and it's never shown to clients. Whether the online booking form (the screen clients book through directly) can offer that window is a separate setting, also off by default. Even when it's on, a time only ever appears as an option if the client's chosen service fits the gap exactly — near-fits are never offered.

Want to see how processing time and buffer time actually behave on screen? Start free and take a look for yourself.