A business closing for a week's holiday, or a single team member taking a few days off, are two completely different situations that are easy to accidentally handle the same way -- usually by just not booking anything for that period and hoping clients don't try. Both actually have a proper setting, and using the right one matters more than it looks.
Whole-business closures vs. one person's time off
The distinction that matters: is the business closed, or is one team member unavailable while everyone else keeps running normally? Treating a single staff member's holiday as if the whole business were closed means turning away bookings for colleagues who are perfectly available -- and treating a genuine business-wide closure as "just don't book that day" leaves the door open for a booking to slip through anyway if anything about your setup isn't airtight.
In ScheduloApp, this is exactly the split Settings > Time Off is built around: a time-off entry can block the whole business for a date range, or be scoped to one specific team member, leaving everyone else's calendar untouched. A solo business only ever needs the first kind; a team needs both, used for the right situation each time.
Why this needs to be approved time off, not just an empty calendar
The reason this lives as its own feature, rather than just leaving a gap in the schedule, is that an approved time-off entry is actively excluded from what clients can book -- it isn't passive. A day you simply don't fill with availability can still, depending on your setup, end up looking bookable by accident; a real time-off entry removes those slots from consideration entirely, the same way a day genuinely marked closed would.
This also matters for partial-day absences, not just whole days off. A team member leaving early on a Thursday, or a business closing for a staff meeting for two hours in the afternoon, doesn't need the whole day blocked -- time off can cover just the affected window, leaving the rest of the day's slots untouched and still bookable.
Setting it up ahead of time, not reactively
The real value of this feature shows up when it's used proactively -- holidays booked weeks in advance, a planned closure for stocktaking, a team member's known day off every week. Set it up as soon as you know about it, and every booking made between now and then already correctly excludes it, instead of you having to manually catch and reject bookings that land on a day you forgot to block.
A quick checklist before you go
- Taking personal time off, business stays open? Scope the time-off entry to yourself (or whichever team member it applies to) -- not the whole business.
- Business genuinely closing? Use the whole-business option so every team member's calendar reflects it, not just yours.
- Only part of the day affected? Use a specific time range rather than blocking the entire day unnecessarily.
- Know about it in advance? Set it now. A time-off entry only protects bookings made after it exists -- it can't retroactively cancel something already booked into that slot.
Getting this right once means you don't have to think about it again until the next time off comes around -- it's one of the few settings in the app that's genuinely "set it and forget it."