A Time Off Request Form That Keeps Your Routes Covered

A time off request at a 200-person company is a notification. At a nine-person operation with four routes going out at six in the morning, it’s a logistics problem. And if the request arrives as a text at 9pm on Friday for the following Tuesday, it’s a logistics problem you’re solving at 5am.

That’s the real reason this form matters for a business that delivers its own orders. It isn’t HR paperwork. It’s the thing that turns “can I have Tuesday off?” into a question with a written answer, so you’re not negotiating from memory every time and quietly letting two drivers book the same week.

This post covers the form itself: which fields earn their place, the notice and blackout rules behind it, and how to run approvals so the answer is predictable. For why leave policy is a retention issue at all, the common causes of employee turnover at small businesses makes the case: unpredictable scheduling is the cheapest cause to fix and one of the most common.

The Bottom Line

• Add one field most templates leave out: a coverage plan. Who runs this route, who covers the counter, who’s been asked. It converts an approval into a plan.

• Two weeks’ notice is the workable standard for planned leave, with more flexibility for appointments and none required for genuine emergencies (Homebase).

• Write your blackout dates down before anyone asks. Retail and restaurant policies commonly block periods like 20 November to 2 January or Mother’s Day weekend (Homebase).

• Decide first-come-first-served versus seniority once, in writing. Deciding it per request is how you end up with a favouritism problem.

• Answer in 48 hours, in writing, every time, including the no’s.

• People under-use the leave they have: only 57% of employees use all their earned time off (Clockify). A form that’s easy to submit is part of the fix, and rested drivers make fewer mistakes.

What to include on a time off request form

Keep it to one page. Every field has to either affect the decision or affect payroll.

Employee name and role. Role matters more than department in a small operation; “driver” tells you immediately whether a route is at risk.

Date submitted. This is what makes your notice rule enforceable, and it’s what settles two requests for the same week.

Type of leave. Paid vacation, unpaid, sick, bereavement, jury duty, parental, other. Not nosiness: it drives payroll and, in a growing number of states, legal obligation. Thirteen states had paid sick leave mandates as of 2026, with some cities going further (Homebase), and you can’t apply a rule you didn’t record.

First day off and first day back. Ask for the return date explicitly, not the duration. “Five days from Monday” gets mis-counted around weekends and holidays; “back on Monday the 14th” doesn’t.

Total hours or shifts requested. Hours for hourly staff, because that’s what the accrual balance is in.

Shifts affected. Which specific shifts or routes fall inside those dates. The employee knows their own schedule, so let them do this arithmetic. It’s the field that makes the decision fast.

Coverage plan. The field that separates a form that works from a template. Three lines: who can cover each affected shift or route, whether they’ve been asked, and anything the cover person needs to know, like the account with the loading-bay code, the customer who needs a call before arrival.

Employee signature and date.

Manager decision block. Approved or declined, who decided, the date, and a reason line if declined. Keep the reason factual: “two drivers already approved that week,” not “bad timing.”

Optional but useful: a balance-before and balance-after box, so the conversation about how many days are left happens on the form rather than in a doorway.

Why the coverage plan field changes the conversation

Most time off request templates ask what the employee wants. Almost none ask how the work gets done. In a business where a missing driver means a customer doesn’t get their order, that’s the only part that’s hard.

Asking the employee to propose the cover does three things:

• It surfaces the conflict early: If the two people who can run the Thursday wholesale route both want that week, you find out at request time instead of the night before.
• It moves the problem to where the knowledge is: Your team knows who’s free, who owes a swap and who wants the extra hours. You’d be guessing.
• It makes “no” rare and legible: Most declines happen because nobody could cover. When the employee has already tried and failed to find cover, the decline is a shared fact rather than a judgement call.

For this to work, somebody other than the requester has to be able to do the job. Any route or task with exactly one trained person is the reason leave requests feel impossible, and it’s fixed upstream by deliberate cross-training, which affordable small business employee training covers as a standing practice rather than a crisis response.

Notice rules, blackout dates and the approval order

The form is half of it. The policy behind it is what makes the answers consistent, and it’s four decisions you make once.

How much notice to require

Two weeks is the standard most small-business policies land on for planned time off, with appointments treated more flexibly (Homebase). The longer window for a full week matters, because that’s the request that needs a route re-planned rather than a shift swapped.

Which dates are closed

Write your blackout periods down in the policy and post them in January, before anyone books flights. Published examples cluster around the obvious peaks: 20 November to 2 January for retail, Valentine’s and Mother’s Day weekends for anything floral or restaurant-adjacent (Homebase).

For a business that delivers, your blackouts are your own demand curve, not a generic calendar. Pull last year’s order volume by week and block the top three or four. And be specific: “the two weeks before Christmas” is an argument waiting to happen, while “8–24 December” isn’t.

One concession makes blackouts much easier to enforce: say what you will approve inside them. One person off at a time, approved strictly in submission order, is a rule people accept because it’s visibly fair.

Who wins when two people want the same week

Pick one rule and write it down:

• First come, first served: Simple, transparent, and rewards planning. Also rewards whoever is best at admin, which can quietly disadvantage your most senior driver.
• Seniority: Predictable, common in route-based work, and the price is that newer staff rarely get prime weeks.
• Rotation on the contested dates: More work to administer, and the fairest option for the three or four weeks everyone wants.

Any of them beats deciding case by case. The decision itself matters less than the fact that it’s written down before the clash happens. Competing requests are where small operations develop a favouritism reputation, and that is a resignation risk, not just an irritation.

How fast you answer

Within 48 hours, in writing, always. A pending request is a person who can’t book anything, and the silence is read as a no with extra steps. Declines especially need to be written and reasoned, because an unexplained verbal no is the version that gets retold to the rest of the team.

Paper, spreadsheet or digital form?

All three work. The question is how many people you’re scheduling.

Paper. Print the one-pager, keep a folder, write approvals on the sheet. Fine up to about ten people. Fails the moment you need to know whether anyone else is off that week without walking to the filing cabinet.

Shared spreadsheet plus a form. The sweet spot for most small operations. Requests land in a sheet, you approve in a column, and a second tab is a leave calendar everyone can see. Visibility is the whole gain here: most double-bookings happen because nobody could see the existing approvals.

Scheduling or payroll software. Worth it once leave balances and accruals are the hard part rather than the coverage. The practical test: if you’re spending more time calculating how many days someone has left than deciding whether they can go, the software will pay for itself.

Whichever you pick, make submission take under two minutes from a phone. A driver finishing a shift at 4pm will not open a laptop, and a form nobody can file is how you end up back at 9pm texts. One low-friction trick for a mixed paper-and-phone team: build the form once in a QR code form builder like Tiger Form and stick the printed code inside the van door and by the time clock, so filing a request is a scan rather than a search for a link. It’s a signup-based tool with a free tier, so check what the free plan covers before you standardise on it.

How leave planning fits the rest of your scheduling

A leave calendar is only useful next to the other things you plan around. Three habits make it work:

Publish the rota further ahead than you think you need to. Two weeks out is the realistic target for an hourly team, and it’s the single cheapest retention lever a small employer has. It also makes the notice rule fair: you can’t ask for two weeks’ notice on a schedule you only publish three days out.

Keep leave and reviews off each other’s calendars. When you’re booking twice-yearly reviews, check who’s away; the people you most want in the room are often the ones with a week booked. The employee evaluation form covers the review side of that.

Treat chronic coverage gaps as a headcount signal, not a leave problem. If you’re declining reasonable requests most months, you’re not over-generous, you’re under-staffed, and the fix is in the small business hiring process rather than in a stricter policy.

And resist the instinct to discourage leave. Only 57% of employees use all the time off they’ve earned (Clockify), and in a job that involves driving for a living, a team that never takes a break isn’t a win on any measure you care about.

Frequently asked questions

What should a time off request form include? Employee name and role, date submitted, type of leave, first day off and first day back, total hours or shifts requested, which specific shifts or routes are affected, a coverage plan, the employee’s signature, and a manager decision block with date and reason. A leave balance box before and after is a useful extra.

How much notice should employees give for time off? Two weeks is the common standard for planned leave, scaling to about 30 days for a full week or more, 48 hours for appointments, and none for sick leave or emergencies (Homebase). Whatever you choose, you can only enforce it fairly if you publish the schedule at least that far ahead.

Can a small business deny a time off request? Generally yes for discretionary paid leave, provided you apply the policy consistently and don’t discriminate. Statutory leave is different: thirteen states had paid sick leave mandates as of 2026, with some cities adding their own (Homebase), so check your state and city rules before declining anything sick-leave related, and record a factual reason on the form either way.

Do I need a separate sick leave form? No. Use one form with a leave-type field. Sick leave is usually reported rather than requested, so let it be filed retroactively and note that the notice rule doesn’t apply to it.

How do I handle two requests for the same week? Decide the rule before it happens (first come first served, seniority, or rotation on contested dates), write it in the policy, and use the date-submitted field to apply it. During blackout periods, state in advance how many people can be off at once and approve strictly in submission order.