PTO & leave request portal with manager approval

A PTO and leave request portal is where employees ask for time off, managers approve or decline each request with a reason, and HR sees everyone's leave on one calendar.

Pattern: Requests

Describe it to Pory

“Our 40-person company needs a place where employees request time off, their manager approves or declines, and HR sees everyone's leave.”

Viewing as

My leave requests

My leave requests

Powered by Pory

In plain English

How Pory sets it up

Pory gives every employee, manager and HR a sign-in of their own. Each employee sees only their own leave requests. It covers submit → manager approval. Leave requests, leave paperwork, key dates and team live in Pory's own database, so there's no spreadsheet to keep in sync.

What it does

01

Employees ask for time off in a form, not a Slack message

Leave requests used to arrive as DMs, emails and hallway asks, and someone copied them into a spreadsheet. In Pory an employee picks the type and the dates, adds a reason, and the request lands as Pending. They can see where every request they've made stands, so nobody has to ask twice.

Forms to submit a recordDone by: Employee
02

Managers decide in one click, with the reason kept on the request

A manager opens the request, reads the dates, the reason and who covers, and approves or declines. A decline carries a note on the request itself, so the employee knows why and what to try instead. No more "did you see my email about Friday?"

Approve / reject with a reasonDone by: Manager
03

HR sees who's out, when, on one calendar

Planning coverage meant cross-checking three people's inboxes. Every request sits on a month view, colored by whether it's pending, approved or taken, so HR can spot a clash before it's approved. Click any entry to open the request behind it.

CalendarDone by: HR

Who sees what in a PTO & leave requests portal

Every person signs in to their own view. This is what each role in the demo gets.

Employee

Sees only their own leave requests.

Pages
Home, My leave requests, My paperwork, Team calendar, Leave policy
Can start
Request leave, New leave request, Upload a form

Manager

Sees every leave request in the portal.

Pages
Home, Leave requests, Team calendar, Team directory
Decides
Marks leave requests Approved or Declined, with a reason

HR

Sees every leave request in the portal.

Pages
Home, Team calendar, Leave requests, Paperwork, Team directory, Leave policy

What’s in the PTO & leave requests portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Leave requests

  • Summary (text)
  • Leave type (choice: Vacation, Sick, Personal, Parental, Unpaid)
  • Start date (date)
  • End date (date)
  • Reason (long text)
  • Status (choice: Pending, Approved, Taken, Declined)
  • Workdays (number)
  • Employee (link)
  • Backup (link)
  • Manager's note (long text)

Leave paperwork

  • Document (text)
  • Kind (choice: Sick leave form, Doctor's note, Return-to-work form, FMLA certification, Handoff notes)
  • Needed by (date)
  • Status (choice: Requested, Uploaded, Checked)
  • File (file)
  • Employee (link)
  • Notes (long text)

Key dates

  • What (text)
  • Date (date)
  • Kind (choice: Deadline, Company holiday, Office closed)
  • Note (text)

Team

  • Name (text)
  • Role (text)
  • Department (choice: Design, Engineering, Operations, People)
  • Manager (link)

The parts behind this portal

Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal

Collect

1 part
  • Forms

    Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Decide

1 part
  • Approve / reject with a reason

    Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Share

1 part
  • Calendar

    Records on a month or week view, by date.

Control

3 parts
  • Who sees which records

    Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

An employee signs in with a link sent to their email and lands on Home. They see Home, My leave requests, My paperwork, Team calendar and Leave policy, and only the leave requests that are theirs. From there they can use “Request leave”, “New leave request” and “Upload a form”.

Manager decide: they mark each one Approved or Declined and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your PTO & leave requests portal with Pory

Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited employees.

See pricing · How Pory builds a portal