PTO Request Form: What to Include, Example Wording, and Approval Flow

What a PTO request form should capture

Six fields do the real work: employee name, type of leave (vacation, sick, personal, unpaid), first day off, last day off, total hours requested, and the date the request was submitted. The hours field matters more than people expect — "Friday off" could be 8 hours for a full-timer or 4 for someone on half days, and your PTO balance math depends on the number, not the dates.

Add three more fields and you've covered the operational side: return-to-work date (removes the ambiguity of whether "through the 15th" includes the 15th), coverage notes (who's handling the requester's shifts or duties), and a comments box. Then a decision section for the manager: approved or denied, by whom, on what date, and a reason if denied.

Keep medical details off the form. For sick leave, the type and dates are enough — diagnoses and doctor details don't belong on a document that managers and payroll will handle, and several states regulate what you can ask about sick leave. Confirm specifics with your state labor department.

Example wording you can copy

A simple paid time off request form can read: "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: ____."

And the manager's section: "Request ☐ Approved ☐ Denied. If denied, reason: ____. Remaining PTO balance after this request: ____ hours. Approved by: ____. Date: ____." Including the post-request balance on the form is a small touch that prevents the most common dispute — an employee believing they had more time left than they did.

If employees ask how to request paid time off by email instead, give them a template: "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 fields, different container — the point is that every request arrives with the same information.

The approval flow that keeps it fair

A clean flow has four steps: the employee submits the form, the direct manager checks two things (the employee's PTO balance and the schedule for conflicts), the manager approves or denies in writing within a stated window — 3 business days is a reasonable commitment — and the approved request goes to whoever runs payroll so the hours are coded correctly on the right pay period.

Decide your tiebreaker rule before you need it. When two people request the same week and you can only spare one, the common options are first-come-first-served (simplest and easiest to defend — another reason the submission date field matters) or seniority. Pick one, write it into the policy, and apply it every time.

The deadliest failure mode is the silent approval: a manager says "sure" in passing, nothing is written down, and three weeks later the shift is uncovered and payroll never coded the time. The rule that fixes it: no form (or no entry in the system), no approved PTO.

Paper PTO forms vs digital requests

Paper pto forms work at very small scale, but they fail in predictable ways: forms get lost between the breakroom and the office, the manager approving can't see the employee's current balance or who else is already off that week, and at payroll time someone is matching slips of paper against a calendar.

Digital requests — whether a shared spreadsheet plus email or proper PTO tracking software — fix the visibility problem. The manager sees the balance and the team calendar at the moment of decision, the employee gets a timestamped answer, and payroll pulls approved hours instead of retyping them. Software also keeps the running balance honest by deducting hours automatically when the time is taken.

If you're staying on paper for now, at least add one ritual: the approver photographs or files every signed form in one folder, and PTO is entered on the master schedule the same day it's approved.

Policy tips: notice periods, blackout dates, and balances

Set a notice expectation that matches the disruption: a common pattern is requiring requests at least 2 weeks ahead for planned vacation, while sick time is same-day notice by a stated method (call or message before shift start). Put the numbers in your policy so the form and the policy agree.

Blackout dates are legitimate — retailers commonly restrict vacation in late December, accountants around filing deadlines — but they only work if announced well in advance and applied to everyone. Publish next year's blackout windows when you publish holiday schedules, and never approve quiet exceptions; one favor undoes the whole policy.

Two more rules worth writing down: whether employees can go negative on PTO (borrowing against future accrual), and how far ahead requests can be made (12 months out is a sensible cap). Note that some states treat accrued PTO as earned wages with rules about payout and forfeiture — confirm with your state labor department before finalizing a use-it-or-lose-it policy.

Frequently asked questions

Keep reading