Time Off Request Form

Why use a time off request form?

A time off request form gives the employee and reviewer a shared record of the proposed dates and the decision. It shows the employee what they submitted, gives the manager the details needed for review, and tells the schedule or leave-record owner which dates were approved. Submission is still only a proposal. For example, the U.S. Office of Personnel Management's leave form separates the employee's request from the reviewer's dated approval or disapproval. A workplace can preserve that distinction without using the same form.

Suppose an employee mentions taking Friday off and a manager says, “That should be fine.” The conversation may leave the exact hours, final decision, or person responsible for updating the schedule unclear. A recorded request followed by a dated response resolves those questions. If the manager approves Friday, the schedule and any applicable balance record can be updated from that response. If the manager suggests Monday instead, Friday remains a requested date until the employee and manager settle the change through their usual process. The record also gives both sides something specific to check later if they remember the conversation differently.

The form records how a request was handled. Applicable policy, agreements, and local law set notice, eligibility, pay, and the grounds for a decision. A “paid” box or available-balance entry gives the reviewer useful information, but it neither establishes an entitlement nor guarantees approval.

What information should the form collect?

The form needs enough detail to identify the requester, describe the time away, reach the right reviewer, and record the response. The useful fields depend on the employer's process and the kind of absence.

Employee identity and requested time

Start with the employee's name and, where it helps route the request, their team or department and the manager or HR contact who will review it. An employee ID can distinguish people with similar names or connect the request to an HR record, but it need not be a default field on a small team's form. Add a contact detail only if the reviewer cannot reach the employee through the normal work channel. The form or its instructions should say where to submit it and where the employee will receive the answer, such as a named manager's work email or a designated portal.

Record when the employee submitted the request. A separate received date can be useful if a paper form or forwarded email reaches the reviewer later. Then specify the first and last requested dates and the scheduled workdays or hours affected. If the employee wants only part of a shift, show the date and the hours to be missed; calling it a whole day would obscure the amount of time being requested. An expected return date can help a team plan a handoff, especially if the last day away and the next scheduled workday are not adjacent.

For example, an employee who normally works Monday through Friday requests time away from Friday through Monday. That span covers four calendar dates but only Friday and Monday are scheduled workdays for this employee. Recording those two workdays makes the request clearer before anyone checks the applicable leave balance. A colleague scheduled on Sunday would need a different work-time entry for the same calendar span.

Leave category, pay status, and balance

A leave-category field tells the reviewer which process to use. For a routine planned absence, the relevant choice might be vacation or annual leave, PTO, personal leave, or an unpaid request, depending on the employer's policy. Sickness, family or parental leave, bereavement, jury duty, and military leave can call for different contacts or documentation. Listing those categories on one form does not make them interchangeable or give them the same eligibility, pay, or approval rules. A PTO- or vacation-specific form can stay narrower; a general time off form needs a way to direct a request to the appropriate route. If the available choices do not fit, the employee should ask where to submit the request rather than select a misleading category.

Where useful, the form can show the requested paid or unpaid status and a current leave-balance figure. These are prompts for review. The manager or HR contact checks the applicable policy and authoritative balance record before confirming whether the requested time is available and how it will be treated for pay. For example, an employee may ask to use two days of PTO, but the displayed balance still needs checking before the response states what was approved. The form need not duplicate a full accrual ledger.

Keep the category useful for routing without asking for a detailed personal explanation on every request. Someone requesting routine vacation can identify the dates and category without a private narrative. If sickness or another specialist route requires supporting information, direct the employee to the appropriate contact and process. In the UK, the Information Commissioner's Office advises keeping detailed sickness or injury records separate from simple absence information where possible; that guidance supports collecting the route on an ordinary form while handling necessary medical details separately.

Decision, coverage, and record fields

Leave room for the reviewer to identify themselves, record when they received the request if that differs from the submission date, and give a dated response. The response should make the outcome and the exact dates or hours clear. A practical status field can distinguish pending, approved, declined, and an alternative proposed by the reviewer. An offered alternative still needs a response before it becomes an approved absence; a pending request should not be silently entered as approved time. A short comment can explain a proposed change or direct the employee to the next step after a refusal. An employee acknowledgement or signature may help where the process uses one, but neither a signature nor a written reason for refusal is a universal field requirement.

An optional coverage note belongs here when work needs a handoff. If a client deliverable falls during the requested absence, the employee could name the colleague taking it over, the deadline, and where the work stands. A role with no such handoff need not fill in a placeholder. The note should describe the work to cover, rather than share the employee's private reason for being away with colleagues who only need the schedule.

Once a decision is final, the leave-record owner can update the team schedule and, where applicable, the balance and pay input from the approved dates and hours. Keep the dated request and response available to the employee and the appropriate manager or HR contact. If the outcome is still pending or an alternative has merely been offered, retain that status instead of treating the proposed dates as final.

How does a request move from submission to a decision?

For routine planned leave, the employee submits proposed time away through the designated channel, a manager or HR contact reviews it, and a dated response establishes what happens next. The schedule should reflect the resulting decision rather than the proposal alone.

Before and when the employee submits

First check the relevant policy or agreement: which leave route applies, who receives the request, and what notice the employee should give. Check the current leave balance if the category uses one, but ask the appropriate HR contact if the figure is unavailable or unclear rather than treating a form entry as confirmation. Then enter the proposed dates and the scheduled workdays or hours affected, choose the applicable category, and send the request to the named reviewer or channel. A sick or specialist-leave situation may call for a different route than an advance vacation request.

For foreseeable leave, submitting early gives the reviewer time to consider staffing and gives the employee time to discuss any handoff for work due during the absence. “Early” depends on the applicable rules; a template's fixed two-week instruction is not a general rule. For example, GOV.UK's statutory-holiday booking guidance sets out a general notice framework for UK holiday and allows different contractual arrangements. That example does not set notice for sickness or for another country. The employee should follow the rule that governs their request rather than assume a template supplies it.

An email, completed document, shared spreadsheet, or portal can carry the request if it reaches the designated reviewer and the response can be found later. For email, keep the relevant dates and reply in the same thread. A document needs a clear handoff; a spreadsheet needs an identifiable request and status; a portal needs to show the submission and decision to the right people. A conversation about possible dates can help with planning, but when the process expects a recorded decision, the employee should still submit through that process and wait for its response.

Manager/HR review and response

The reviewer checks the requested dates and work time against other approved absences and the coverage needed on those days. They also verify the relevant balance and proposed pay treatment, then consider the leave category under the applicable policy and law. A routine vacation scheduling conflict is one question; sickness, family, or another potentially protected route may call for HR review and a different decision test. A form's single “approve/decline” control does not make every category subject to the same discretion.

If two employees request overlapping time, a team can use stated criteria such as when each request arrived, which roles need coverage, or a rotation where appropriate. The reviewer should record the criterion actually applied so the employees can understand the result. These are possible administrative choices, not a universal priority order or an automatic right to refuse leave. A generic template does not establish a seniority rule or blackout period; check any such provision against policy and local law. In its UK holiday guidance, Acas advises employers to follow policy and manage requests openly, fairly, and consistently; local rules still govern what may be refused.

The written response should identify the decision maker, date, and outcome. An approval names the approved dates and hours. A refusal can explain the relevant conflict or direct the employee to the applicable rule, with the detail required by the governing process. An offered alternative remains a proposal, while a partial approval should say exactly which requested time was approved and what remains declined or unresolved. If only the first of two requested vacation days can be offered under the applicable rules, marking the whole request “approved” would misstate the decision. The response time comes from the applicable process; a template's 48-hour promise is not a universal deadline.

Caption: Illustrative administrative flow. Submission does not approve leave, and an offered alternative is still a proposal. Applicable policy and law govern eligibility, pay, notice and refusal. U.S. Office of Personnel Management, Form 71 · Acas, Asking for and taking holiday

After the decision or when plans change

After approval, send the dated response to the employee and the approved work time to the schedule owner. Anyone covering a task also needs the handoff details. The leave log or calendar should show the confirmed absence; HR can adjust the balance and pay input where the category calls for it. Colleagues arranging coverage usually need dates and responsibilities, not the employee's private reason for leave. For UK worker health information, the Information Commissioner's Office's access guidance calls for need-to-know access, a useful boundary for deciding what belongs on a shared schedule.

Record a changed plan as a new decision instead of silently overwriting the first one. Suppose Friday and Monday were approved, but the employee now asks for Monday and Tuesday. Keep the original request and dated approval traceable, mark the new dates as proposed, and record whether the earlier approval is withdrawn or replaced when the reviewer responds. Only then should the schedule and any applicable balance reflect the current approved dates. Use the same approach when the employee withdraws a request or accepts a manager's alternative: show which proposal was superseded and which dates, if any, are now approved. This is a practical record-control choice, not a fixed legal version-history rule.

If the planned absence is approaching with no response, the employee should follow up through the designated channel and, if needed, escalate under the employer's policy. Submission or a calendar hold alone should not be treated as a recorded approval. The employee can ask the reviewer to confirm the current status and next step, while following any separate notice route that applies to an unforeseen absence.

Which absences need another route or restricted information?

An advance request works well for foreseeable time away. When the absence is sudden or calls for specialist review, the employee may need to notify a different person first, and the supporting information may belong in a more restricted process.

Unplanned sickness, emergencies, and specialist leave

A scheduled vacation can go through the ordinary request and approval channel before it starts. Sudden illness, bereavement, or an emergency may leave no time for that sequence. The employee should then use the applicable notification route promptly and complete any later record or supporting step required by policy and local rules. An advance form cannot be the only reporting route for every absence. For example, in the UK Statutory Sick Pay process, GOV.UK says an employer cannot insist that sickness be reported in person or on a special form. That is a UK sickness rule, not a universal notice method for all leave.

Consider an employee who plans a vacation next month and another who wakes up ill on the day of a shift. The first can check the vacation policy, request the planned dates, and await a decision. The second follows the employer's sickness-notification route as soon as the circumstances allow, such as contacting the designated manager by an accepted method; a vacation form should not be treated as the only way to give that notice. What later documentation is needed depends on the applicable process, not on a universal proof requirement.

A potentially protected medical or family-leave request may also need HR to assess eligibility and any separate documentation. In qualifying cases involving eligible employees of covered U.S. employers, the Department of Labor's FMLA guidance explains that an employer may request medical certification for a serious health condition. That does not make certification necessary for every sick day, or turn a general form's “medical leave” checkbox into a decision about FMLA eligibility. The employee should be directed to the relevant HR route when the ordinary form cannot capture the applicable review.

Health details and access to the record

For a UK employer, the Information Commissioner's Office distinguishes a simple absence record that may say “sickness” or “accident” from a sickness or injury record that names a medical condition. Where category and duration are enough to plan coverage, the simpler record is generally less intrusive. An ordinary form therefore need not default to a diagnosis box visible to everyone handling requests or the team calendar. Context can still make even a brief entry revealing, so the category alone does not guarantee that a record is nonsensitive.

If medical details are genuinely needed, the ICO advises keeping the detailed record separate from the simpler absence record where possible and limiting access to what each person's job requires. A manager arranging cover may need the dates and effect on work, while an HR contact handling a particular health-related process may need supporting information through a controlled channel. This is a decision about purpose and access, not a blanket rule that an employer may never request medical information or that a manager may never see it.

Caption: UK ICO guidance: keep detailed sickness or injury records separate where possible, with need-to-know access. Context can make even a category revealing; necessary medical support can still be requested lawfully. UK ICO, How do we handle sickness and injury records? · UK ICO, Data protection and workers’ health information

A separate, narrower rule applies in qualifying U.S. Family and Medical Leave Act cases. The U.S. Department of Labor states that covered employers must keep FMLA medical certifications and recertifications as confidential medical records in files separate from usual personnel files. A routine time off form can identify the need for HR follow-up; it should not become the shared storage place for that certification. This FMLA file requirement does not apply to every U.S. sick-day request.

What do policy and local rules change?

The form captures a proposed absence and the response. The applicable policy, agreement, and law determine how the proposal is assessed, including notice, eligibility, pay, and any limits on refusal.

Notice, eligibility, overlapping requests, and record rules

A useful time off policy tells employees which leave types are available and where to send a request or urgent notification. It should identify the decision maker, explain the notice and response process for foreseeable leave, and point to the authoritative balance and pay rules. It can also cover staffing conflicts or blackout periods, emergency contacts, date corrections, and decision reviews. The form then collects the facts needed to apply those rules. A blank template's “paid” box, balance line, or manager signature cannot create a leave entitlement or displace a protected-leave route.

Consider two employees asking for the same Friday. Suppose an employer's applicable vacation policy says to check whether both roles can be covered and, if only one request can be accommodated, to consider the order in which otherwise comparable requests arrived. The reviewer checks the actual staffing need, records both receipt dates and the criterion used, then communicates the decision and any proposed alternative. That example shows how a stated rule can be applied and explained; it is not a universal first-come rule or a reason to apply ordinary vacation criteria to a medical or other protected request. Any seniority preference or blackout period likewise needs to fit the governing policy and local law.

The policy should also name who maintains the current request and decision record and how a changed or disputed entry is corrected. An employee needs to know where to see the dated answer, while the manager or HR contact needs to know which version governs the schedule and any balance update. Record access and retention should follow the applicable purpose, policy, and legal requirements; a downloaded form does not supply a universal retention period.

US, UK, and Germany examples of scoped rules

The same fields can sit on a form used in several countries, but the instruction beside a paid box, notice date, or approval line must reflect the rule governing that employee and leave type. These examples show different boundaries rather than one combined leave test.

United States

At the U.S. federal level, the Department of Labor explains that the Fair Labor Standards Act does not itself require payment for time not worked, including vacation. An agreement may provide paid vacation, while state or local rules, other federal protections, and requirements tied to certain government contracts can also matter. Therefore, selecting “paid vacation” on a request signals what the employer must verify; it does not establish pay by itself. Equally, the FLSA's limited vacation-pay rule is not permission to deny every absence, particularly one governed by a different protected-leave rule.

United Kingdom

For UK statutory holiday booking, GOV.UK gives a general notice rule: a worker gives at least twice the length of the requested leave plus one day, so a one-day request generally calls for three days' notice. An employer refusing or cancelling the requested dates must generally give as much notice as the amount of leave requested plus one day. Different notice terms in the contract apply, and the employer cannot prevent the worker from taking statutory holiday altogether. A holiday form's submit-by and response instructions should therefore point to the applicable terms rather than a worldwide “two weeks” rule. This framework concerns holiday booking, not sick or emergency notification.

Germany

For German statutory annual leave, §7(1) of the Federal Leave Act requires the timing decision to take the employee's holiday wishes into account. The provision identifies competing urgent operational interests or other employees' wishes that have priority on social grounds. A manager recording a refusal should therefore apply that annual-leave test to the facts; a generic “manager discretion” box does not state the whole rule. This example concerns the timing of German statutory annual leave, not every German absence category.

Which form format and controls should a team choose?

Choose a format by checking whether employees can submit it, a named reviewer can respond, and both sides can find the current decision. The format also needs access controls appropriate to the information it holds. None of these outcomes follows automatically from using a digital form.

Format	Useful when	Control to add
Paper, PDF, or Word form	Employees need a printable or fillable document, or the team handles few requests.	Name the recipient and keep the submitted copy with the dated response in a reliable file or log. A paper copy needs a filing or scanning route.
Email or shared document	A small team already works through a common inbox or document space.	Keep the request and response together, identify the decision owner, and limit who can edit or view the record.
Spreadsheet or online form, such as Google Forms	Repeated requests benefit from consistent fields and a central list.	Assign each entry to a reviewer, record its status and decision date, and preserve the response; a submitted row is still only a request.
HR portal	The organization needs routing, status visibility, or a link to its leave records.	Configure the correct approval route and access permissions, and verify that displayed balances and final states reflect the applicable rules.

Even without specialist software, a workable team process needs one submission destination, a named decision maker, and a visible distinction between submitted, approved, declined, and proposed-alternative states. The form can require identity, requested work time, and the category needed for routing while leaving fields such as employee ID or a coverage note optional unless the process uses them. Someone must update the leave log and schedule from the final response and retain the request and decision under the applicable policy. An online form, for example, may place a new entry in a spreadsheet. A manager still needs to review it, record a dated answer, and tell the employee; the automatic submission receipt is not an approval.

Give people access to the information they need for their roles. A team calendar can show approved absence and coverage without exposing a medical explanation. In the UK, the Information Commissioner's Office's worker-health guidance describes need-to-know access and separate controls for health information. A shared sheet or portal should therefore have its permissions and fields checked before it is used for such records. Retention also follows the record's purpose and applicable rules, not a fixed period printed on a generic template.

What does a completed request and response look like?

The following is an illustrative routine vacation record, not a legal template. Maya works eight-hour shifts on Thursday and Friday and wants to miss both scheduled days, 12 and 13 November 2026.

• Request submitted, 15 October 2026: Maya asks for vacation on 12–13 November: two scheduled workdays, 16 hours in total. The entry names Jordan Lee, her manager, as reviewer and notes that Avery Patel can take the client report due on 13 November after a handoff. The coverage note is useful for this role, not a field every employee must complete.
• Review and response, 16 October 2026: Jordan checks the applicable vacation policy and balance, looks for conflicting approved absences, and confirms coverage for the report. Jordan's dated response approves both requested days and 16 hours.
• Record update: Maya receives the response. The schedule and leave log show 12–13 November as approved; the balance and pay input are updated if the employer's process calls for them.

The two dates were only requested on 15 October. The manager's dated response made them approved in this example. If coverage allowed Thursday but not Friday under the applicable rules, the response could instead say “12 November approved; 13 November declined; 16 November proposed as an alternative.” Monday would remain a proposal until Maya and the manager confirmed that change through the usual process. The record should then show the current approved dates and preserve the earlier response for clarity, rather than marking the whole request approved.

A same-day illness follows a different path. If another employee wakes up sick before a scheduled shift, they use the applicable sickness-notification route and, when needed, HR follow-up. They do not wait for the routine vacation approval sequence. Any documentation, pay, or protected-leave question is handled under the rules for that absence.