Juvant Workforce Management

Time-off rules and blackout dates that hold up

How to handle requests fairly, when blackout dates make sense, and the difference between a firm day off and a preferred one.

4 min read · Updated November 2, 2026

Nothing tells a store team what you think of them faster than what happens to a day off. A forgotten request ruins someone's weekend and costs you far more goodwill than the shift was worth. Yet in most stores, time off runs through text messages, sticky notes and a manager's memory. Here is how to set up something that holds.

Separate three different things

Most trouble starts because different kinds of requests get treated as one. Name them separately.

Time off is specific dates or hours when a person will not work. Once approved, it is firm. You do not schedule over it.

Availability is a repeating pattern, such as "never Thursday evenings because of class". It applies week after week until it changes.

A preferred day off is a wish. "I'd like Sundays off if you can." You try to keep it, and you tell the person when you cannot.

Each of these deserves different handling. If everything is firm, you can't build a schedule. If everything is a preference, nobody can plan their life.

Write the policy on one page

A short policy that people have read beats a long one nobody opens. Cover:

  • How to ask. One channel only. If a request came through any other way, it does not count.
  • How far ahead. For example, two weeks before the schedule goes out.
  • Who decides, and how fast. A named person, and a time limit such as three working days. A slow answer often feels like a no.
  • How competing requests get decided. See below.
  • How the answer is recorded. One place where anyone involved can see it.
  • Blackout dates. When they apply, and how they are announced.

Some leave is protected by law, including certain sick, family and medical leave, and the rules vary by state and city. Your policy cannot override those rights. Blackout dates and approval rules usually should not apply to protected leave. Have counsel review your policy before you publish it.

Deciding between competing requests

When three people want the same Saturday in December, you need a rule that you could explain to all three. Common options, and their trade-offs:

MethodHow it worksTrade-off
First come, first servedEarliest request winsSimple, but rewards whoever plans earliest
SeniorityLongest-serving winsClear, but newer people may never get a holiday
RotationLast year's winner goes to the backFeels fair, but needs records
LotteryDraw namesUnbiased, but ignores real differences in need

Many stores combine them: first come first served in normal weeks, and rotation for the most-wanted holidays. Choose one, write it down and stick to it. Always leave room for a manager to make an exception for real hardship, and record it when they do.

When blackout dates make sense

A blackout date is a date when you generally do not grant time off. They exist because a few days carry so much of the year that a store can't run them short.

They work well when:

  • They are short. Pick the fewest days you can defend. If everything is a blackout, the policy means nothing.
  • They are early. Announce them months ahead, before anyone books flights.
  • They are consistent. The same rule applies to managers and new hires.
  • They are honest. A blackout that managers quietly ignore for favorites is worse than none.

Give something back. If you block the week before Christmas, you might guarantee a choice of days off in January, or give first choice next year to those who worked. People accept a hard week far more easily when they can see what comes after it.

Handling requests already approved

What happens when you announce a blackout and someone already has an approved day inside it? Keep the approval. Ask nicely if they could move it, and thank them if they do. Going back on an approved day off teaches everyone that an approval means little.

Preferred days off: keep them, and say when you cannot

Preferences are a low-cost way to give people some control over their lives. A sensible order of priority for building a schedule:

  1. Never schedule over approved time off.
  2. Cover your staffing needs.
  3. Keep preferred days off wherever you can.
  4. If a preference has to give, tell the person. Do it before the schedule goes out, if you can.

Telling people is the important part. Most people accept losing a Sunday occasionally. What they do not accept is finding out from a posted schedule, with no word from anybody. Keep a rough count too, so that the same person does not lose out each time.

Use one calendar for everything

If time off lives in one place, holidays in another and special sale days in a third, somebody will miss something. Put these in one calendar:

  • Approved time off
  • Preferred days off
  • Holidays and store closures
  • Blackout dates
  • Special days with different hours or staffing

Everyone who writes a schedule should look at the same calendar. When you add a date, it should be visible to whoever is planning that week.

Check it after each season

Look back after your busy periods. Who asked and was refused? Who has not had a weekend off in a while? Did the rule produce an answer you would be embarrassed to explain? Change the policy where it failed, and tell people what changed.

A time-off policy works when people stop thinking about it. They ask, they get a straight answer, and it holds.