Setting Up Your Company Holiday Calendar

A solid company holiday calendar answers three questions before anyone has to ask: which days are paid, whether the office is open, and what happens when a holiday lands on a weekend. Get those three right and you eliminate the December scramble of "wait, are we off on the 26th?" emails. This guide walks through building one from scratch, including the federal holidays worth observing, how floating holidays plug the gaps, and a communication plan that actually sticks.

Start with the federal holidays

The federal government recognizes 11 holidays. Private employers are not required to observe any of them, but they make a sensible backbone because employees, banks, schools, and government offices already plan around them.

Here are the 11, with the typical observance pattern:

Most small teams land on a core six: New Year's Day, Memorial Day, Independence Day, Labor Day, Thanksgiving, and Christmas. From there, the popular add-ons are the day after Thanksgiving (a near-universal favorite) and Christmas Eve or New Year's Eve as a half or full day.

A realistic, generous package for a 10-person company might look like this:

1. New Year's Day
2. Memorial Day
3. Juneteenth
4. Independence Day
5. Labor Day
6. Thanksgiving Day
7. Day after Thanksgiving
8. Christmas Eve
9. Christmas Day

That is nine fixed paid holidays, which sits right in the middle of the typical 7-to-11 range. If you are deciding how many to offer, remember each one is a paid day where you collect no output, so it has a real cost. You can put a dollar figure on it with the PTO cost calculator before you commit to a long list.

Decide what "observed" actually means

A holiday on the calendar is not the same as the office being closed. Be explicit about three things for every holiday.

Closed vs. paid-but-open. A retail shop or support team may stay open on Independence Day but pay a premium or give the day back later. A B2B software company usually just closes. Write down which holidays close the business entirely.

Weekend observance. When July 4 falls on a Saturday, do you give the Friday before? When it falls on a Sunday, do you give the Monday after? The federal rule does exactly this, and copying it avoids reinventing the wheel:

• Holiday on Saturday → observed Friday
• Holiday on Sunday → observed Monday

Partial days. Christmas Eve and New Year's Eve are often half days. State the cutoff time so it is not left to a manager's mood. "Offices close at 1:00 PM" is clear; "early dismissal" is not.

If you operate across time zones or run shifts, count the actual working days affected rather than assuming every holiday removes one uniform day. The working days calculator is handy for figuring out how a holiday week shakes out for a Tuesday-to-Saturday schedule, for example.

Add floating holidays to cover what fixed dates miss

A fixed calendar has a built-in fairness problem: it picks specific cultural and religious days and ignores the rest. An employee who observes Diwali, Eid, Yom Kippur, Lunar New Year, or Orthodox Christmas gets nothing from a calendar built around Christmas and Thanksgiving. Floating holidays solve this.

A floating holiday is a paid day off that the employee schedules themselves, subject to advance notice and coverage. The defining traits:

• Limited count. Usually one or two per year, not an open bank.
• Employee's choice of date. That is the entire point.
• Often use-it-or-lose-it. Many companies expire floaters at year-end so they do not accrue into a liability.
• Separate from PTO. A floater is not vacation; it is a flexible substitute for a fixed holiday.

Here is how the three buckets compare:

A clean setup for that same 10-person company: nine fixed holidays plus two floating holidays. The fixed days handle the shared rhythm of the year, and the floaters let people honor the days that matter to them without you having to add every observance to the master calendar.

One practical rule worth writing down: floating holidays require the same advance notice as PTO, and they cannot be used to extend a fixed holiday into a four-day weekend unless coverage allows it. Without that line, every floater quietly migrates to the day before Thanksgiving.

A note on religious accommodation

Floating holidays are a benefit, not a substitute for legal obligations. Under federal law, employers generally must make reasonable accommodations for employees' sincerely held religious practices unless doing so causes more than a minimal burden. A generous floating-holiday policy makes those requests easy to grant, but it does not replace the duty to consider accommodations case by case.

Build the calendar as a real document

Once you have decided the days, turn the decisions into an artifact people can actually use. A good holiday calendar has:

1. A dated list for the specific year. Not "Thanksgiving" but "Thursday, November 27, 2025 and Friday, November 28, 2025 — office closed."
2. The observance rule for weekend holidays, stated once at the top.
3. Floating-holiday rules: how many, how to request, and the expiration date.
4. Coverage expectations for any team that stays open (support, retail, operations).
5. The owner. Who maintains it and who approves changes.

Worked example for a single entry:

• Independence Day — Friday, July 4, 2025. Office closed. Support coverage on call per the on-call rotation. Falls on a Friday this year, so no weekend adjustment needed.

That level of specificity is the difference between a calendar people trust and one they double-check every time.

Communicate it so it actually lands

A holiday calendar nobody can find is the same as no calendar. Use a layered rollout.

Publish early. Release the next year's calendar by early November. People book December and summer travel months ahead, and your own coverage planning is easier with lead time. Aim for 60 to 90 days before year-end at minimum.

Put it in three places. A single source of truth fails the moment someone forgets where it lives. Practical trio:

• The employee handbook or policy section (the authoritative version).
• A shared team calendar with each holiday entered as an all-day event, so closures appear automatically in everyone's scheduling.
• A pinned message in whatever chat tool the team lives in.

Send a reminder before each holiday. A short note the week before — "Reminder: office closed Friday for Independence Day; support coverage is on the on-call rotation" — prevents the "are we open?" questions and signals that the calendar is maintained.

Flag the edge cases explicitly. Half days, weekend observances, and any holiday where part of the team stays open deserve their own callout, not a buried line. These are exactly the cases people get wrong.

If you are writing the policy from scratch and want the holiday section to match the rest of your time-off rules, the PTO policy generator produces a starting draft you can adapt, including how holidays interact with accrual.

Common mistakes to avoid

• Leaving observance undefined. "We observe Christmas" tells no one what happens when December 25 is a Sunday. Spell out the weekend rule.
• Counting holidays as PTO. Holidays are employer-designated closures. Do not deduct them from someone's vacation bank, and make sure your tracking keeps the two separate.
• Forgetting accrual interactions. If your PTO accrues per pay period or per hour worked, decide whether paid holidays count toward accrual. Model it with the PTO accrual calculator so the numbers are consistent.
• No expiration on floaters. Unbounded floating holidays accumulate into a liability and an HR headache. Set a year-end expiration.
• Publishing late. A calendar released in mid-December is useless for anyone who already booked travel.

A starter template you can copy

For a small US team that wants to be competitive without overcommitting:

• Fixed holidays (9): New Year's Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Thanksgiving, the day after Thanksgiving, Christmas Eve, Christmas Day.
• Floating holidays (2): Employee's choice, same notice rules as PTO, expire December 31, cannot stack onto a fixed holiday without approved coverage.
• Observance rule: Saturday holidays observed Friday; Sunday holidays observed Monday. Christmas Eve and New Year's Eve are half days closing at 1:00 PM.
• Coverage: Support follows the on-call rotation on all closure days.

That gives 11 days of holiday flexibility, separates holidays cleanly from PTO, and respects the cultural diversity of your team without you having to play calendar referee.

Wrapping up

A company holiday calendar is one of the cheapest morale wins you have, but only if it is specific, published early, and easy to find. Decide your fixed days, add a floating holiday or two for flexibility, write down the observance rule, and put the calendar where people already look. SimplyPTO keeps fixed holidays, floating holidays, and PTO in separate, automatically tracked buckets, so the day after Thanksgiving never quietly eats someone's vacation balance. Start a free SimplyPTO account and set up your calendar in a few minutes.