PTO Request Form: Fields, Wording, and Approval Flow

A PTO request form is the document (paper or digital) that turns "hey, can I take next Friday off?" into a record: who's out, which dates, how many hours, who approved it, and what balance remains. Six fields do most of the work, and the approval flow around the form matters more than the form itself.

This guide gives you the exact fields, wording you can copy today, the flow that keeps approvals fair, and the policy rules (notice, blackouts, tiebreakers) that the form should quietly enforce. It's written for the owner or manager who's tired of time off living in text messages. A PTO request form for small business teams has one extra job that big-company templates ignore: with six people on the schedule, one approved week is a coverage decision, not a paperwork step.

What should a PTO request form include?

Every field on the form should either help the approval decision or settle a future dispute. That standard gets you to nine fields and nothing else:

Keep medical details off the form deliberately. For sick time, the type and dates are enough. Diagnoses and doctor information don't belong on a document that managers and payroll will pass around, and several states regulate what you can ask about sick leave. If a request might be something bigger than a sick day (a surgery, a new baby, a family crisis), that's a leave-of-absence conversation with its own process; our leave of absence guide covers when a simple pto form is the wrong tool.

PTO form wording you can copy

Here's a paid time off request form you can paste into a document and use tomorrow. Copy the two blocks below and you have a free PTO request form without buying anything:

Employee section: "Employee name: ____. Type of leave: Vacation / Sick / Personal / Unpaid. First day requested: ____. Last day requested: ____. Total hours requested: ____. Returning to work on: ____. Coverage arranged with: ____. Employee signature and date: ____."

Manager section: "Request: Approved / Denied. If denied, reason: ____. Remaining PTO balance after this request: ____ hours. Approved by: ____. Date: ____."

If your team runs on email instead, give everyone this template so every pto request arrives complete: "Subject: PTO request, [name], [dates]. I'd like to request [X] hours of [vacation/sick/personal] time from [first day] through [last day], returning [date]. I've arranged coverage with [name]." Same nine fields, different container. The uniformity is the point: an approver who gets complete requests can answer in minutes, and an incomplete request is the number one cause of the slow, mushy "let me get back to you" that frustrates everyone.

One wording tip for the balance line: state hours to one decimal. Accruals produce balances like 43.5, and rounding on the form while payroll keeps decimals is a tiny mismatch that grows into distrust. How does PTO accrual work behind that number? Employees accrue PTO either by the hour worked or by the pay period, and the form only reports where they've landed. To sanity-check the figure against your accrual rate, our free PTO calculator will calculate PTO balances for you, and our guide to accrued PTO explains where the numbers come from.

The approval flow that keeps it fair

The form is evidence. The flow is policy. A clean one has four steps and a stated clock:

1. Employee submits the form or digital request, complete, with the submission date captured automatically or written in.
2. Manager checks two things: the employee's current balance and the schedule for conflicts. Nothing else should be required to decide a routine vacation request.
3. Decision in writing within a stated window. Three business days is a fair commitment. A fast no beats a slow maybe: employees can rebook a trip, but they can't rebook two weeks of silence.
4. Approved hours flow to scheduling and payroll so the shift is covered and the time is coded on the right pay period. This step is where paper systems leak.

Here's the flow working under mild stress. It's March, and two of your four front-of-house staff request the first week of June. Under a loose system this is a mess in June. Under the flow above it's settled in March: the submission dates show Dana asked on March 3 and Marcus on March 9, first-come wins per the written policy, Dana gets the yes within three business days, Marcus gets a fast no plus first claim on the surrounding weeks, and the June schedule is built around one absence instead of a surprise. Nobody's thrilled, but nobody's blindsided, and neither of them thinks the decision was personal. That's the whole job of the flow: converting scarce weeks from favors into rules.

Decide your tiebreaker before summer does it for you. When two people want the same week and you can only spare one, the defensible options are first-come-first-served (simplest, and the reason the submission date field exists) or seniority. Pick one, write it in the policy, and apply it every single time. The moment you make one quiet exception, every future denial becomes a negotiation.

And kill the silent approval. A manager says "sure" in the hallway, nothing gets written down, and three weeks later the shift is uncovered and payroll coded nothing. One rule fixes it permanently: no form or system entry, no approved PTO. Enforce it on yourself first.

How to request PTO: instructions to hand your team

A PTO request form for employees only works when they know the steps. Paste something like this into your handbook and the requests that reach you will already be decision-ready:

1. Check your balance first. Your available hours are on your pay stub or in the time-off app. Don't request more than you'll have accrued by the dates you're asking for.
2. Submit through the one channel. The form or the app, not a text, not a hallway ask. Requests made anywhere else don't exist.
3. Give the required notice. Two weeks for planned vacation, same-day call-in for sickness, per the policy. Earlier is better for popular weeks; ties go to the first submission.
4. Wait for written approval before you book. The company isn't responsible for nonrefundable flights bought before the yes.
5. Arrange coverage where the policy asks for it, and name the person on the request.

Then coach around the two mistakes that generate most friction. The first is the assumption that submitting equals approved; make the confirmation explicit every time so nobody builds plans on silence. The second is the end-of-year pileup: employees who sat on their hours all year discover the carryover limit in November. A quarterly nudge ("you have 52 hours, the carryover cap is 40, book something") protects your December schedule and their vacations at the same time.

Paper PTO forms vs digital requests

Paper works at very small scale, and it fails in predictable ways as you grow. The form gets lost between the breakroom and the office. The approving manager can't see the current balance or who else is already off that week. At payroll time somebody reconciles slips of paper against a calendar. None of these are character flaws; they're properties of paper.

PTO request form software fixes the visibility problem at the moment of decision. In Kloqk's PTO tracking, an employee submits a request from their phone, the manager sees the live balance and the office calendar side by side, and the approval writes itself back to the calendar and the timesheet. Balances update automatically when the time is taken, so the number on the request is always the real number. It sits on the Pro plan at $29 per location while the time clock itself stays free, so the upgrade costs less than the paper it replaces.

If you're staying on paper for now, adopt two rituals that capture most of the benefit: the approver photographs or files every signed form in one folder the day it's signed, and approved time goes onto the master schedule the same day. A paper system with same-day filing beats a digital system nobody opens.

Policy rules the form should enforce

The form works best when it's the visible edge of written policy. Your PTO request form rules live in the handbook, and the form is just where employees meet them. Four to nail down:

• Notice periods that match the disruption. A common pattern: requests at least 2 weeks ahead for planned vacation of 3+ days, 3 days ahead for single days, and same-day notice by a stated method (call or message before shift start) for sickness. Put the numbers in the policy so the form and the policy agree.
• Blackout dates, published early. Retail in late December, accountants at filing season, restaurants on Mother's Day. Blackouts are legitimate if they're announced when you publish holiday schedules and applied to everyone. One quiet exception undoes the policy.
• Negative balances. Decide whether employees can borrow against future accrual, and how far (16 hours is a common ceiling). If you allow it, say how overdrafts are recovered at separation, and check your state's rules on final-check deductions first.
• How far ahead requests can land. Twelve months is a sensible cap. It lets people plan weddings without letting anyone claim every holiday for the next decade in January.

Where the legal lines are

Vacation requests are yours to approve or deny for business reasons. Sick time is not the same animal. States with paid sick leave mandates set their own accrual and usage rules; California, for example, requires at least 1 hour of paid sick leave per 30 hours worked, with a floor of 40 hours or five days a year, and limits how employers can condition its use. Your form can capture sick requests, but your approval rules for them have to follow the statute, not your vacation policy. Check the states where your people work; our paid sick leave laws by state pages map the mandates.

To see how prescriptive these mandates get, here are California's accrual checkpoints, the numbers an employer's records have to be able to prove:

Watch, too, for requests that trigger bigger protections. A request tied to a serious health condition, a new child, or a family member's care may fall under FMLA at covered employers, which provides eligible employees up to 12 workweeks of job-protected leave in a 12-month period. FMLA has its own notice and documentation process; the pto time off request form is where such a request might first surface, so train approvers to recognize when a form needs to become a conversation.

Finally, consistency is the quiet legal shield. Approvals and denials applied unevenly across similar employees are how discrimination complaints start. The tiebreaker rule, the notice rule, and the written record on every request are what let you show, not just claim, that the process treats everyone alike.

Questions that come up once the form is live

What is PTO supposed to cover on the form?

Vacation, personal days, and in most small companies sick time as well, which is why the type field exists. Keep the categories on the form even if they all draw from one bank, because sick time carries protections vacation doesn't and a state audit asks for it separately. If your team is fuzzy on the vocabulary, the PTO meaning guide is a two-minute read to hand around.

How much PTO is normal for small business?

Two weeks a year is where most owners start, with a step up around year three or five. The number matters less than the approval rate. Fifteen days that get approved beat twenty days that get denied every June, and employees compare notes about the second one.

How do I track employee time off after it's approved?

Approved hours have to land in three places: the schedule, the balance, and the pay period. Paper systems break at the third. Whatever you use, the test is whether you can pull one employee's year of requests, approvals, and hours used without opening a filing cabinet.

What does the form look like under unlimited PTO?

Same form, minus the balance line. Under unlimited PTO nobody is accruing PTO toward a ceiling, so the request captures dates, type, coverage, and approval, and the reporting shifts from hours remaining to days taken per person. That second number is the one that tells you whether the policy is working.

Does the request log matter when someone quits?

More than any other record you keep. Do companies have to pay out PTO when you quit? In earned-wages states, yes, and the payout is unused hours times the final rate, which means your request log and your accrual entries are the evidence for the number on that last check. The state-by-state split is in our guide to whether companies have to pay out PTO.

Set it up once, then stop thinking about it

One last operational note: connect the request record to the timesheet. An approved vacation day should appear on the schedule, block the shift from being assigned, and land on the correct pay period as PTO hours rather than worked hours. When those three systems disagree, payroll pays wrong, and every wrong paycheck costs you more trust than a denied request ever will. This is the strongest argument for keeping requests, schedules, and time tracking in one place instead of three.

A good pto request form takes an hour to set up: copy the wording above, add your notice numbers and tiebreaker, publish the blackout windows, and put the balance line on the form. A digital system takes about as long and removes the filing, the balance lookups, and the payroll retyping in the same move. Either way, the payoff is identical: the next time someone asks about that week in July, you'll answer from a record instead of a memory.