Your project works on Christmas Day (unless you tell it otherwise)

Two December timelines for the same 8-day task in Microsoft Project: without holidays it ends December 30, with the Christmas shutdown declared it ends January 8

This article is part of the guide The plan that holds: Microsoft Project best practices, symptom by symptom, nineteen things you can see in a plan and the move that reveals each one in thirty seconds.

There’s a question that always made the room go quiet when I taught Microsoft Project: “according to your plan, when is your company closed?” Someone ventures “over Christmas”, someone says “the summer shutdown”. In most of the plans I’ve reviewed over twenty years, the real answer is: never. Here’s the typical scene. In October the plan promises delivery by year end, and the steering committee approves it. In January the delivery isn’t there, and the blame goes looking for a culprit: the supplier, the testing, bad luck. The real culprit was written into the plan back in October — you just had to know where to look.

The Standard calendar doesn’t know your holidays

Every new Project plan is born with the Standard calendar: Monday to Friday, eight hours a day, all year round. Zero holidays. No Christmas Day, no New Year’s Day, no Thanksgiving, no bank holidays — and certainly not your company’s shutdown between Christmas and New Year, which in many businesses means a full week or more. That’s not an oversight by Microsoft: holidays change from country to country, and shutdowns from company to company. Project can’t guess them, so it preloads none. It waits for you to declare them. Until you do, December 25th is just another productive Friday. The consequence is sneaky because it produces no visible error: every task that crosses days when your company is closed looks shorter on paper. The finish date you read is optimistic, and across a chain of tasks the optimism adds up. Here’s the effect on a concrete case — an eight-working-day task planned across the Christmas shutdown:
Scenario 1 · December, according to Project (every day is a working day)
212223242528293031145678
Testing (8 d)
Planned finish: Wednesday, December 30. On paper.
Scenario 2 · The real December (shutdown Dec 24 – Jan 1 in Exceptions)
212223242528293031145678
Testing (8 d)
Same task, honest calendar: finish Friday, January 8 — well into the new year.
task (8 working days)company shutdown (Exceptions)working day
Working days, December 2026 – January 2027.
The plan says December 30th. Reality says January 8th. Better to know that in October than to discover it in January.

The fix: five minutes in Exceptions

Open your plan and go to the Project tab, Change Working Time button. At the top, “Standard (Project Calendar)” is selected; in the lower half of the dialog you’ll find the Exceptions tab. Each row is one exception to the calendar: type a name (“Christmas shutdown”, “New Year’s Day”, “Company holiday”), a start date and a finish date. Click OK and look at your Gantt chart: the closed days now show in grey like weekends, and every bar that crossed them has stretched by itself to leap over them. Your finish dates now tell the truth. [SET-SCREENSHOT: the Change Working Time dialog with the Exceptions tab filled in]

Which days to load

The list depends on where you are, but the method doesn’t:
  • your country’s public holidays — Christmas, New Year’s Day, and whatever your calendar adds, from Thanksgiving to Boxing Day to a national day
  • company shutdowns: the week between Christmas and New Year, a summer closure, an annual inventory freeze
  • holidays that move every year — Easter Monday where it applies — need updating annually
  • and if you work with suppliers or teams in other countries, remember their calendars don’t match yours: exceptions are declared, not hoped for

The trick that saves you doing this every time

Exceptions live in the plan where you enter them: your next project will start from scratch, with its pristine, optimistic Standard calendar. The remedy costs five minutes once: prepare an empty plan with the calendar already filled in — all the holidays for this year and the next, plus your company’s shutdowns — and use it as the starting point for every new project. Anyone else planning in your company should start from the same base: plans with different calendars produce dates you can’t compare.

Where the project calendar ends

One limit worth knowing: exceptions on the project calendar apply to everyone. They say when the company is closed, not when a person is on leave. Individual vacations — Smith’s two weeks in July, the part-timer’s Fridays, shift patterns — live on another level: the resource calendar. It’s a mechanism of its own, with its own precedence rules, and it deserves its own article. For now, the practical rule: the company goes in the project calendar, the people go in the resource calendars. And if you’re wondering why some tasks still finish on a Saturday — that’s a calendar story too, and it’s the next one I’ll tell.
ProjectEdgeTools builds small tools that fix real Microsoft Project headaches — from cleaning sensitive data out of your plans to getting them into Power BI in one click. Have a look at the suite.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top