Weddings, funerals and the rota

Most of shift-work coordination is about recurring things. This is about the ones that happen once and cannot be moved — and they split into two completely different problems.

The ones booked months ahead

Weddings, christenings, milestone birthdays, graduations. Announced far in advance, on a fixed date, usually a Saturday.

The failure here is almost never that leave was refused. It is that nobody connected the date to the rota while there was still time.

The save-the-date arrives in March for September. It goes on the fridge. The September rota is built in July, by which point the leave window has closed and the popular dates have gone.

What to do, in order:

1. The day you hear the date, put it in the calendar — the shared one, so it is not only in your head.
2. Work out when the rota covering it is built, and when leave requests open for it. This is the piece people miss.
3. Request it as early as the system allows. For contested dates, request order genuinely decides outcomes.
4. If leave is refused, start on a swap immediately. Months out, somebody will trade. A fortnight out, nobody will.

That sequence gets people to weddings. The alternative — remembering in August — mostly does not.

The ones with two days’ notice

Funerals, someone taken ill, an emergency. No planning possible.

Know what you are entitled to before you need it. Most jurisdictions and most employers have some provision for bereavement or emergency dependant leave. It is frequently unpaid, frequently limited, and frequently more available than people assume. Reading the policy at the point of crisis is the worst time.

Ask directly and early. Managers are generally more accommodating on these than on anything else, and asking within the hour is better than agonising for a day.

Say what you need rather than asking what is possible. “I need Thursday and Friday” gets a clearer answer than “is there any chance”.

Let colleagues help. In most teams, somebody will cover a funeral. The barrier is usually that people do not want to ask, not that nobody would say yes.

The ones you will miss

Some you cannot get to. Mandatory coverage, a refused swap, a date in the middle of a block with no cover available.

Two things reduce the damage.

Say early, not late. Telling the family in June that you probably cannot make the September wedding gives everyone time to adjust and — occasionally — to move something. Telling them the week before does not, and it reads as not having tried.

Send someone, or do something else. A partner attending, a video call, a visit the following week. Not the same, and considerably better than absence with nothing attached.

Make the dates visible in both directions

The practical thing that prevents most of this: the family events and the rota need to be in the same place.

If your partner books a wedding into a shared calendar and your shifts are in the same view, the clash surfaces in March rather than August. If they are in two different places — a group chat and a rota on a fridge — nobody sees it until it is unfixable.

That is the whole mechanism. Most missed family events are not refused leave; they are a collision that nobody was in a position to see in time.