Back to all templates
PTO & Time Off Management

Vacation Request Form Template

Capture vacation requests in a structured workflow with manager approval, coverage planning, and policy acknowledgment — without the spreadsheet drift, lost Slack DMs, or HRIS lock-in. Built for distributed teams where statutory minimums and PTO policies vary by country, state, and convenio.

Free — included in every plan

Vacation Request Form Template

Live preview — try the fields below.

No fields to preview.

Who this template is for

Vacation requests sound simple until you watch them sprawl across Slack DMs, manager emails, three calendar apps, and a shared Google Sheet that no one trusts. This template structures the request itself — dates, type of leave, coverage plan, manager approval, policy acknowledgment — and gives you a single source of truth for who is out, when, and whether someone covered the gap. It is the lightweight option teams reach for before committing to a full HRIS like BambooHR, Rippling, Workday, or Gusto Time Off, and the structured option teams reach for after Slack PTO bots like Vacation Tracker or PTO Ninja stop scaling. Designed for distributed teams where US 'unlimited PTO' policies, Spain's 30 calendar days statutory minimum under the Estatuto de los Trabajadores, and Brazil's 30-day CLT férias with constitutional 1/3 bonus all need to coexist in one workflow.

From request to approved time off in one structured flow

Employee submits the request with start date, end date, leave type (vacation, personal, sick, bereavement, parental, jury duty, military), coverage plan, and acknowledgment of the company PTO policy. The form auto-calculates business days excluding US federal holidays, regional public holidays, and weekends. A coverage field requires naming a teammate who has agreed to cover, with optional Slack handoff notes. The direct manager receives an email and Slack DM with one-click approve/deny links and a calendar conflict preview showing other approved requests that overlap. Requests longer than a configurable threshold (typically 10 business days, or 2 weeks for senior roles) auto-route to a second approver — HR for compliance review, or the manager's manager for budget impact. Approved requests can post to a shared Slack channel (#out-of-office), sync to Google Calendar or Microsoft 365 as an all-day event, and update a public team availability page. Denied requests return to the employee with a required reason. Every state change — submitted, approved, denied, rescinded, modified — is timestamped and logged, which is the audit trail you need when someone disputes whether they actually requested those days off.

What's included

Every field exists because a team has been burned by its absence. Vacation tracking is one of those workflows where the small details — coverage assignment, advance-notice windows, public-holiday overlap, second-level approval thresholds, balance acknowledgment — are exactly what causes the disputes three months later when someone insists they had five days left.

Teams using vacation request forms

  • Distributed startups (25–250 people)

    The sweet spot — too big for Slack DMs to scale, too small to justify a $20/seat/month HRIS. Engineering managers approve their own teams, HR approves cross-team transfers, and finance needs a quarterly report on PTO liability for the audit. Coverage plans matter because there is no bench.

  • Cross-border teams (US + EU + LATAM)

    One workflow that respects US 'unlimited PTO' (no statutory minimum, manager discretion), Spain's 30 calendar days under Estatuto de los Trabajadores Art. 38 plus convenio additions, Brazil's CLT 30-day férias with the 1/3 constitutional bonus and 3-period split limits, and the right-to-disconnect rules under LOPDGDD Art. 88 (Spain) and France's loi El Khomri. Without a unified form, country-specific quirks become payroll disputes.

  • Agencies and professional services

    Billable utilization tracking means PTO is not just about coverage — it is about pipeline. Account managers need to know which client teams have leave overlap before promising delivery dates. The form captures client-facing impact (active projects, handover plan) alongside the time-off dates.

  • Manufacturing, retail, hospitality (shift-based)

    Coverage is non-negotiable — a missing shift is operational risk. The form requires a named replacement who has explicitly accepted the swap, integrates with shift-scheduling systems like Deputy, When I Work, or 7shifts, and respects collective bargaining agreement (CBA) or convenio colectivo provisions on advance notice and blackout periods (peak retail, end-of-month manufacturing closes).

  • Field services and healthcare practices

    Independent dental practices, clinics, veterinary offices, and field-service crews where one person being out reshapes the daily schedule. Manager approval is paired with a patient/client rebooking checklist, and the form blocks requests during prescheduled peak periods (Q4 dental insurance benefits surge, year-end checkups, school physical season).

  • Brazilian companies under CLT

    The 'período aquisitivo' (acquisition period) and 'período concessivo' (concession period) make Brazilian vacation distinct from US PTO. The form respects the 30-day advance request window, validates split rules (max 3 periods, one ≥ 14 days, none under 5 days post-Lei 13.467/2017), captures the 'abono pecuniário' election (selling up to 10 days back), and exports the data your folha de pagamento system (Senior Sistemas, TOTVS RH, Convenia, Pontotel, Sólides) needs for the eSocial S-2230 event.

Tailor it to your PTO policy

Every team's PTO policy has its own edge cases. Add a 'leave type' dropdown with your specific categories — bereavement (and the relationship-based day limits), jury duty, military leave under USERRA (US), maternity/paternity under FMLA (US), permiso retribuido (Spain), licença-maternidade and licença-paternidade (Brazil's expanded under Lei 14.457/2022), wedding leave (CLT 'gala'), or 'mental health day' if your culture treats those as separate. Add a 'paid vs. unpaid' indicator if you offer unpaid leave for extended travel, sabbaticals, or caregiving. Configure advance-notice rules per leave type — bereavement bypasses the 14-day notice, sabbaticals require 60 days. Add manager second-approval triggers for requests over 10 business days, 2 weeks, or spanning a fiscal quarter close. Toggle whether the form posts to Slack #out-of-office automatically or only after approval. Add a 'balance acknowledgment' read-only field that pulls from your HRIS or accrual tracker so employees see their current balance before requesting. Integrate with Google Calendar, Microsoft 365, or Calendly to block the employee's calendar automatically on approval. For Brazilian teams, add the 'abono pecuniário' (sell-back) checkbox and the 13th-month-salary advance election ('adiantamento do 13º') that often pairs with vacation timing.

Vacation request FAQs

Those are full HRIS platforms — they handle PTO as one feature inside payroll, benefits, performance, and onboarding. Pricing is $8–$15+ per employee per month, with most charging extra for international payroll modules. This template handles the request workflow itself — dates, coverage, approval, audit trail — without committing to the broader HRIS lock-in. Most teams under 100 people do not need a $15K/year platform to manage who is out next Tuesday. If you outgrow this and move to a real HRIS later, the structured request data exports cleanly. The teams that stay on this approach permanently are the ones that already have their HRIS or payroll provider (Gusto, Justworks, ADP Workforce Now, Senior Sistemas, Factorial HR) and just need the request workflow layer that those tools handle poorly.
Those tools are great for the Slack-first interaction model — type '/pto' and you're done — but they tend to break down when you need (1) structured coverage assignment, (2) multi-level approval routing, (3) audit-grade documentation for compliance (Spain's Estatuto de los Trabajadores documentation requirements, Brazil's eSocial S-2230 event, CCPA/CPRA records of HR data processing), or (4) integration with non-Slack workflows like a written policy acknowledgment that needs to be timestamped for legal defensibility. The form-based approach gives you the documentation layer; you can still post to #out-of-office on approval if you want the Slack visibility. Many teams run both — Slack bot for casual day-off requests, this form for vacations over a threshold.
Most teams use the 'highest common denominator' approach in policy — everyone gets at least the Spanish 30-calendar-day / 22-working-day minimum (Estatuto de los Trabajadores Art. 38) or the Brazilian CLT 30-day standard, which usually exceeds US norms. The form does not enforce balances directly — it captures the request, and your HRIS or accrual tracker (BambooHR, Rippling, Factorial HR, Convenia, Pontotel) enforces the math. What the form does enforce is policy compliance: advance notice windows (CLT requires 30 days of advance notice; US is usually 2 weeks; Spanish convenios vary), public holiday calendars (US federal, Spanish festivos including regional autonómicos, Brazilian feriados including the religious holidays in Bahia and Pernambuco that catch out-of-state managers), and split rules (Brazilian férias max 3 periods, one ≥ 14 days). Country-specific fields appear conditionally based on the employee's location.
Yes, and the requirements are stricter than most US-centric teams realize. In Spain, RDL 8/2019 requires employers to maintain daily working-time records, and vacation records are part of that audit trail (Inspección de Trabajo can request 4 years of records). In Brazil, the eSocial S-2230 event requires vacation registration through the federal system, and the CLT requires the 'aviso de férias' to be delivered in writing at least 30 days in advance with employee signature. Under CCPA/CPRA, vacation records are HR data subject to retention disclosure and deletion rights (with payroll exceptions). The form's timestamped audit trail — submitted, approved/denied, modified, who acted — is the documentation you would produce in an Inspección audit, an ANPD investigation in Brazil, or a wrongful termination dispute in the US. Without it, the dispute comes down to 'he said, she said' over Slack screenshots.
Yes — on approval, the workflow can create an all-day calendar event on the employee's calendar marked as 'Out of Office' (which auto-replies to incoming meetings in Google Calendar and Outlook), post to a shared team calendar, and update a #out-of-office Slack channel. For teams using Microsoft 365 with the Out-of-Office assistant, the form captures the auto-reply text the employee wants set so it does not require a separate step before leaving. For Brazilian companies using Outlook with the 'agenda corporativa' shared by area, the form respects the area-level visibility settings. For agencies using project-management tools like Asana, Linear, or Jira, the integration can flag tasks owned by the employee that fall within the leave window so the manager can reassign before the absence.

Related templates

Performance review form — built for the way reviews actually work in 2026

Performance review form template with self-assessment, manager review, OKR-based goal tracking, and calibration support.

View template

Exit interview form — capture departure signal that's actually actionable

Exit interview form template with structured departure reasons, manager-attribution suppression mitigation, post-exit 30-60 day follow-up, and aggregated

View template

Internship application template — built for student programs, not general hiring

Online internship application form template for student programs. Captures school, program, availability, CV, portfolio, and work-authorization (OPT/CPT).

View template

Ready to build forms that work for you?

Create your first form in minutes. Your submissions will thank you.

Be first in lineLimited early accessSet up in 2 minutes