The Days Nobody Answers the Phone: A 2027 Calendar Check Before Sign-Off

Every planning season has the same small ritual. Someone opens a spreadsheet, types the project weeks across the top, and drops in the public holidays as pale grey cells. Then the plan gets signed, the milestones look tidy, and everyone moves on. Six weeks later a decision sits unanswered, a delivery slips, and somebody says the words no project needs: “We didn’t account for Easter.”

That is not a failure of effort. It is a failure of attention. Bank holidays, school breaks and the strange quiet of late August are not decoration on the calendar. They are real working constraints, and they deserve a place in the plan before anyone signs it off.

For 2027, the calendar is already knowable. The surprise is optional.

Start with the shape of the year, not the task list

A useful first step is to stop treating “bank holidays” as a single UK-wide block. England, Wales, Scotland and Northern Ireland do not share exactly the same pattern. If your team, client or supplier sits across more than one jurisdiction, the plan needs to reflect that. A delivery date that works in Manchester may not work in Glasgow if the local holiday pattern differs.

Then look at the shape of the breaks, not just the dates. In 2027, Easter falls in late March, with Good Friday on 26 March and Easter Monday on 29 March. That is a cluster, not a single day off. May brings two Mondays that can quietly remove long weekends from the working rhythm. Late August delivers the summer bank holiday just as many people are already running on reduced capacity. Christmas lands on a weekend, with substitute days following, which can stretch the shutdown in ways a simple date list does not show.

Add the things that never make it onto the official list: school half-terms, local festival weeks, supplier maintenance windows, client shutdowns, and the informal days when nobody books a meeting because half the team is travelling. These are not excuses. They are operating conditions.

Build a collision map, not a holiday list

A holiday list tells you when people are away. A collision map tells you what that means. Take the project’s key decision points and test each one against the calendar.

Which approvals need a named human in a specific chair? Which sign-offs depend on a finance team that closes early before a long weekend? Which delivery acceptance needs a client representative who will be on a beach in Cornwall? Which supplier milestone relies on a warehouse that runs a skeleton crew around Easter?

If a decision is due within three working days of a known break, assume it will slip. Not because people are careless, but because the normal machinery of review, challenge and sign-off needs working days to turn. You have two sensible options: bring the decision forward, or accept the later date openly and adjust the plan around it. What you should not do is leave the original date in place and hope.

Make buffers explain themselves

“Contingency” is a word that invites argument. “Five working days because the client’s finance team closes the quarter and the approver is on leave” is a sentence that ends the argument.

Good buffers sit before the collision, not after it. If a decision must be made by mid-March to keep an April milestone alive, work backwards through the review cycle and set a decision-by date that leaves room for one round of comments. Put the buffer where the pressure actually lands. A week of float after a missed deadline is not a buffer; it is a recovery position.

It also helps to avoid the Friday afternoon before a bank holiday weekend. That is not a moral judgement about Friday afternoons. It is a practical observation: people leave early, inboxes go quiet, and a request that arrives at 4pm on the Thursday before a long weekend is unlikely to get the attention it needs.

Run the check in 45 minutes

This does not need to become a new governance layer. A single working session can do the job:

• List the public holidays that apply to each team, client and supplier in the project.
• Overlay the project milestones and mark anything within five working days of a break.
• Name the owner and an alternate for each affected decision.
• Agree bring-forward dates where the decision can move earlier.
• Write a short calendar note into the plan so the assumptions are visible.
• Share the note with the client and key suppliers, not just the internal team.

That last point matters. A calendar note is not a private warning. It is a shared expectation. It says: these are the days when normal progress is unlikely, and here is how we have planned around them.

If the schedule is already signed

Most people reading this will not be planning from a blank page. The schedule may already be agreed, the budget locked, and the milestones published. That does not mean nothing can be done.

You do not need to re-baseline the whole plan. Add calendar notes to the existing schedule. Re-sequence the work that sits immediately before and after known breaks. Update the decision log with realistic decision-by dates. And use plain language when you talk about it: “known non-working period” is easier to hear than “risk”, and it points everyone towards the same practical response.

A small habit with a long life

The calendar check is one of those quiet habits that pays back out of proportion to the effort. It costs less than an hour. It prevents the sort of slippage that takes a fortnight to explain.

As 2026 closes out, the 2027 calendar is sitting there in plain sight. The days nobody works are already marked. The only question is whether the plan acknowledges them before sign-off, or discovers them one missed approval at a time.