Time Off Request Form: A Template You Can Copy

> TL;DR: A time off request form is the timestamped record of who asked for which dates, how many scheduled days that covers, and what was left in their balance when they asked. This article gives you a blank form to copy, a filled example, the notice rules that actually bind you under federal and city law, and the point at which paper stops paying for itself.

A server asks for the first week of July. She asks in the kitchen at 22:40, mid service, while you are carrying two plates, and you say yes because yes is the answer that takes the least time. Three weeks later two other people have booked the same week and nobody can prove who asked first.

That is the whole case for a time off request form. Not compliance theatre. A timestamp, a number of days, and a signature, so the July argument never happens.

What goes on a time off request form

Most templates you find online collect a name, two dates and a signature. That is not enough to schedule against, and it is the reason managers end up rebuilding the roster twice.

Here is the blank form. Copy it into a document, a spreadsheet, or a form builder; the fields matter more than the format.

Two of those fields carry most of the weight, and both get cut from the templates that circulate.

The first is first day back at work. Half the disputes we see are not about the leave; they are about the return. Somebody writes 21 to 27 June and means they are back on the 28th. Somebody else writes the same thing and means the 27th was travel and they are back on the 29th. Ask for the return date explicitly and the ambiguity disappears.

The second is scheduled days covered. A week off for a Monday to Friday office employee costs five days of balance. The same week off for a line cook rostered Tuesday to Saturday also costs five, but they are different five days, and if you deduct calendar days you are quietly overcharging weekend staff. Count rostered days, not squares on a calendar.

Filled in, for a line cook at a 48-cover restaurant in Austin, it looks like this.

Note the manager note. It records a gap that is still open on an approved request, which is exactly the kind of thing that evaporates when approval happens by text message.

How much notice can you require for time off?

This is where managers guess, and the guesses are usually too aggressive. There is no single national notice rule; there is a federal floor for protected leave and a set of city and state ceilings for sick and safe time, and they pull in opposite directions.

Read the last two rows twice. New York City also constrains how the notice is given. The procedure has to be reasonable, so you cannot route requests through a system people cannot access. And you cannot demand somebody turn up at the worksite to hand in a form while they are sick. If your only channel for a request is a paper tray in the back office, you have built exactly the barrier the rule describes. Our blog on New York sick leave law goes deeper on the accrual side.

The practical translation is a two-lane form. One lane for planned absence, with a stated notice window you can actually enforce. One lane for sick and safe time, with no advance notice requirement at all and a clear instruction on how to tell you. Managers who run a single lane end up applying a 14-day vacation rule to somebody with the flu, which is both unkind and, in several cities, unlawful.

What happens once the form lands on your desk?

Collecting requests is the easy half. The half that goes wrong is the answer.

Decide three things before your busy season starts, not during it:

• A response deadline you publish. Five working days is a reasonable default for a planned request. Whatever you pick, put it on the form. Silence is not a refusal, and staff will read it as a yes. The rules on employer response times for leave differ by jurisdiction, so check yours before you commit to a number.
• A tie-break rule, written down. First submitted wins on timestamp, or rotation by year, or seniority, or splitting the block. Any of them works. What does not work is deciding in June, because whichever rule you invent then will look like it was invented to suit the person you wanted to keep happy.
• A refusal that names an operational reason. Not a policy number. Coverage on a specific date, a certification that has not come back, a clash with another approved block. Your right to refuse leave is real, and it survives a challenge far better when the form says why.

At Shyfter, the pattern we run into most often is not managers refusing too much. It is managers approving everything in February and discovering in May that they have given away four of the six weeks of summer to the same station. A running balance and a per week cap on approved absences fixes that in one line of policy, and the form is where the cap becomes visible.

The cover field is worth defending too. Asking the requester to name somebody who could take the shift does not transfer your responsibility, and it must never turn into the employee having to find their own cover before you will consider the request. But it converts a lot of quiet no into a quick yes, because the person asking usually knows better than you who wants extra hours in June.

Paid, unpaid, and why the balance field is a liability

Here is the part that surprises people. There is no federal entitlement to paid vacation in the United States. The Department of Labor is explicit: the Fair Labor Standards Act does not require payment for time not worked, such as vacations, sick leave or federal or other holidays. Those benefits come from your policy or a negotiated agreement, full stop.

FMLA leave is a separate animal: up to 12 workweeks in a 12-month period, job protected, and unpaid, though an employee may run employer-provided paid leave concurrently with it. So a single request form may be drawing down a paid balance and a protected entitlement at the same time, and your form should capture which.

Then there is California, where the balance stops being an administrative number. The state labour commissioner treats vacation pay as another form of wages which vests as it is earned. A policy that forfeits unused vacation after a cut-off date, the classic use it or lose it, is illegal there, and Labor Code section 227.3 requires earned unused vacation to be paid out at the final rate of pay when employment ends.

Sit with what that means for a paper form. In California, the balance line on every request is a running statement of money you owe. A Belgian hotel group we work with in Bruges hit the same wall from the other direction when they opened a US site: their European habit of wiping the balance at year end simply did not travel. If your balances live in a spreadsheet that one person maintains, you are carrying a wage liability that nobody reconciles until somebody resigns.

When paper stops paying for itself

Take that nine-person front desk in Bruges. Nine people, each submitting roughly eight separate requests a year once you count single days and half days, is 72 forms. Four minutes each to log the request, recalculate the balance, check it against the published roster and reply, and you have burned close to five hours of a duty manager’s year on arithmetic. That is before a single conflict.

The threshold is somewhere around fifteen people, and it arrives earlier if your team includes students or casuals whose requests cluster around exams and holidays.

Past it, the request should stop being a document. It becomes a field: the employee submits from their phone, the balance recalculates on submission, and the request appears on the schedule as a block before you start building, not after. That is how leave and absence management works in Shyfter, and the piece that changes the most is not the approval, it is the visibility. Requests arrive through the employee app with a timestamp nobody can argue with, which settles the tie-break question before you have to apply the rule.

Declared availability and requested time off are two different signals and deserve two different forms. If you have not set the first one up, our employee availability form covers the standing limits that sit upstream of every request you receive.

Want to see requests, balances and the roster on one screen instead of three? Book a free demo and bring your worst month, the one where half the team wants the same fortnight. That is the one worth testing.

Frequently asked questions

How far in advance should a time off request form be submitted?

For planned absence, most employers set somewhere between two and four weeks, and the right number depends on how far ahead you publish rosters. Under the FMLA, an employee must give 30 days advance notice when the need is foreseeable and such notice is practicable; when it becomes foreseeable inside 30 days, notice is due as soon as practicable, generally the same or next business day. Sick and safe time is the opposite case: in New York City your written policy cannot demand more than seven days notice even when the need is foreseeable.

Can an employer refuse a time off request?

Yes, for ordinary paid vacation, provided the refusal is not discriminatory and does not hit leave that is separately protected by law. What matters is the record. Name the operational reason on the form itself, coverage on a specific date or a clash with an already approved block, rather than pointing at a policy number. A refusal with a reason attached to a timestamped request is defensible; a refusal by text message three weeks later is not.

Does a time off request form need a reason field?

Keep it, keep it optional, and say so on the form. A reason helps you rank two requests for the same dates and it is often the difference between a flat no and a split block. But demanding a reason for every day of paid vacation invites detail you do not want on file, and for sick or safe time in several jurisdictions you are restricted in what you may ask. One optional line is the right amount.

Should the form be paper or digital?

Paper is fine up to around fifteen people. Past that, the balance arithmetic is where it breaks: someone has to recalculate by hand, and the number on the form drifts from the number in payroll. A digital request carries its own timestamp, updates the balance on submission and lands on the schedule before you build it, which removes the two failure points paper cannot fix.