Handling Requests for Time Off

In scheduled operations, time-off requests interact with rota building in a way that salaried environments do not experience.

The timing problem

A request received after the rota is built costs a change; before it, it costs nothing.

Which means the request deadline should sit before the build date, with a stated gap.

Publish both dates: requests by this day, rota out by that day.

Most operations state the second and not the first, which produces requests arriving during the build.

The minimum process

Requests in one place, in writing.

A stated response time — three working days is common — and meeting it.

Approval recorded before the rota is built, so the builder sees it.

A limit on how many can be off at once, stated in advance rather than decided per request.

Blocked periods announced at the start of the year, not as refusals when requests arrive.

The three rules

Check the calendar before the entitlement. Someone can have plenty of days left and still be the fourth person off that week.

Answer promptly, including no. Silence is the complaint that comes up in exit conversations, more than refusals.

Never withdraw an approval after someone has booked something around it, which is the situation that ends in a grievance.

Requests that are not holiday

Appointments, study, a family event, a religious observance.

Frequently short and specific, and frequently easier to accommodate than a full day if the person is asked what they actually need.

Recorded separately from annual leave, because conflating them distorts both the balance and the absence figures.

Fairness in refusals

Record refusals as well as approvals.

A pattern of one person's requests being refused is something to notice yourself rather than have raised.

And check who is asking: people who have been refused twice stop asking, which looks like flexibility and is resignation.

The measure

Requests received, approved, refused, by site.

Response time.

And requests arriving after the deadline, which if high means the deadline is not communicated rather than ignored.

Publish both dates

The request deadline and the publication date.

Most operations state the second and not the first.

Which means requests arrive during the build, where each one costs a change rather than costing nothing.

Put the deadline before the build date, with a stated gap, and repeat both every period.

Turn the principle into a test

For a concrete product reference, this workflow reference can help turn the principle above into a test. Verify the current behaviour in a trial and judge the record it creates, not the wording on the page.