PTO blackout dates your team can understand

Start with the smallest group that actually needs to be available. A finance close doesn't automatically require the design team to cancel its plans, and a launch doesn't justify leaving an entire quarter unavailable.

Define the vacation blackout period before requests arrive¶

Name the work that needs coverage, choose its start and end dates, and identify the people needed to do it. Publish that information before employees begin booking. A useful blackout is a specific planning decision with an owner, rather than a manager's last-minute explanation for turning down an otherwise ordinary request.

Write down what ends the restriction too. A fixed end date is easier to understand than “until things calm down.” If a launch moves, update the published window and tell the affected employees what changed.

Keep protected leave on its own decision path. FMLA rights cannot be displaced by an ordinary scheduling preference when the law applies. The blackout clause below is for discretionary scheduled vacation, not a rule that illness or another protected absence must wait.

Copy this blackout dates policy clause¶

Publish a clause that tells employees the scope, dates, reason, and person who owns an exception decision. State how existing approvals will be treated, and use the same wording in your announcement and policy document. Replace every bracketed field before sharing the clause so employees receive an actual decision rather than a template.

Scheduled-vacation blackout: From [start date] through [end date], inclusive, employees in [department or location] should not book discretionary vacation because [specific coverage need]. Existing approved vacation remains approved unless we separately discuss and agree a change with the employee. Send requests for an exception to [named contact and channel], who will give a recorded answer before you make plans. This restriction does not replace procedures or rights for protected sick, medical, family, or other legally protected leave. Report those needs through [separate contact/process]. We will announce changes to this window in [communication channel] and update the calendar.

Use the separate contact process to handle sensitive situations, not a public channel thread asking an employee to explain their health. The template states your intended process; it doesn't create an exemption inside a software rule.

This is general US information, not legal advice.

Pick a window that matches the work¶

Use industry examples to start a staffing discussion, then narrow the dates to your actual workload. The table gives suggested patterns, not standard restrictions every employer should adopt. Decide who needs to be present and what backup would remove the need for a blackout before reserving the whole team's calendar.

If only the number away matters, use a coverage rule rather than banning a whole date range. Cabana's Maximum teammates away is a different control from Blocked Dates: it counts approved coworkers in the same department on overlapping dates and blocks the request at submission when the limit is reached.

Set blocked dates in Cabana¶

Use a scoped block when the affected group must not submit requests for that range. A Cabana admin creates the rule in Settings → Blocked dates. When a new request overlaps an applicable block, submission is rejected before the request reaches the manager's approval queue, including requests started in Slack or Teams.

1. Open Settings → Blocked dates and find Add Blocked Dates.
2. Enter a clear Name, such as Retail peak.
3. Set Start date and End date.
4. Choose Applies to: Org-wide, Department, or Location.
5. Select the matching Target, then choose Add Blocked Dates.

For the November example, an overlapping request receives: Leave requests are blocked during "Retail peak" (2026-11-27 – 2026-11-30). It doesn't become a pending request that a manager can approve from the notification.

Keep the exception process separate from the block¶

Agree on exception handling before turning on the restriction. A manager needs a way to hear about protected or exceptional circumstances and record the outcome. Explain that path alongside the rule, rather than asking employees to repeatedly submit a form that is designed to reject their dates.

Cabana's current block applies to every leave type within its scope, including sick leave. The form doesn't offer a leave-type exclusion or a request-specific override. Keep blocks narrow so they never stand between an employee and legally protected leave such as sick time, and have a named admin handle any protected absence that falls inside one.

Creating the block doesn't automatically cancel leave already approved. Review the existing calendar first and honor the clause's commitment to discuss any change separately. In California, employers can control vacation timing, but that doesn't turn every type of absence into discretionary vacation.

Announce the dates where employees request time off¶

Tell the affected group what changed, why, and whom to contact before they encounter the submission error. Use an announcement that names the exact window and scope, then link the written clause. That makes the rule understandable to someone who missed the meeting where the coverage problem was discussed.

For example: “Customer support: scheduled-vacation requests are blocked November 27–30 for Retail peak. Existing approvals remain in place. Contact Maya privately for exceptions or protected-leave needs. Other departments aren't included.”

Keep the announcement and the actual block aligned. Cabana shows blocked ranges on its team calendar; the daily Out today post isn't a substitute for explaining a future blackout.

Use Cabana for a defined booking restriction¶

Choose Cabana when you want the written window reflected in the request process, with a department, location, or organization scope. The blocked-dates guide explains the rule; the Team vacation calendar helps you review existing approved absences first.

Both PTO tracking in Slack and PTO tracking in Microsoft Teams connect to PTO tracking software for small teams. Use Vacation policy best practices and the Free PTO policy generator for the written process.

One plan costs $4 per user per month, with a $20/month minimum. Start a 30-day free trial with no credit card.