PTO request system

PTO request software that closes the loop

PTO request software keeps the request, approval, balance, and calendar connected. Cabana lets employees submit from Slack or Microsoft Teams, gives managers decision buttons, and adds approved time off to the team calendar.

$4 per user per month · No credit card

One request, one decision trail, one calendar your team can trust.

1RequestPrivate chat
/pto request

Request PTO

Leave type

Vacation

Start date

Nov 9

End date

Nov 13

Note

Sam is covering support

Submit
2ApproveManager's chat

Cabana APP

New PTO request from Maya Patel

Employee

Maya Patel

Leave type

Vacation

Dates

Nov 9 to Nov 13

Days

5

Note

Sam is covering support

ApproveDenyOpen in Cabana
3Everyone knows#general

Cabana APP

🌴 Out today — Monday, Nov 9

  • • Maya Patel
  • • Chris Okafor

Posted each morning, plus a Monday digest of the week ahead. Names only — no notes or balances.

Use one recorded request from start to finish. Your office manager should be able to see what was requested, who decided, and which dates are approved without piecing together an email, a DM, and a spreadsheet.

Follow one request from Tuesday morning to the calendar

Use a specific request to judge whether a system actually closes the loop. Follow the employee's submission through the manager's decision, then inspect the balance and shared calendar. Each checkpoint should reflect the same dates and status, with no separate reminder needed to copy the result into another record.

Here's a worked example: on Tuesday, October 27, Alex asks for Vacation on Thursday, November 5 and Friday, November 6. Alex has seven days available and adds “Sam will cover the inbox.” Maya is the sole approver; both requested dates are working days with no public holiday.

CheckpointInformal DM and spreadsheet processThe same request in Cabana
Tuesday morning: Alex asks“Can I take next Thursday and Friday?” Maya has to establish the actual dates and leave type.Alex selects Vacation, November 5–6, and adds the note in the request form.
Before Maya decidesSomeone checks the spreadsheet and remembers any requests not entered yet.The two requested days are reserved. Alex has five available while the request is pending.
Maya reviews coverageMaya searches earlier messages and asks whether Sam is available.Maya reads the request note and checks the team calendar for approved absences. She still confirms Sam's handoff.
Maya approvesA “yes” in the DM must be copied into the leave record and calendar.Approve records the decision. The employee is notified, and approved leave appears on the team calendar.
The team plans that weekThe calendar is useful once someone remembers to update it.Alex's approved dates are on the calendar; enabled channel posts include the absence on their schedule.
Alex checks the balanceThe employee asks whether the spreadsheet has caught up.Five days remain. Approval changes the days from pending to used without deducting them again.

The employee and dates are illustrative. The test is practical: make a request, decide it, then look for the same result everywhere the team relies on it.

Give employee time off requests a clear starting point

Choose one official submission path and teach it during onboarding. Employees need a leave type, exact dates, and a way to add useful context. A conversation can settle the handoff, but the submitted request should hold the dates and status that the manager, employee, and office manager work from.

Cabana offers these entry points:

Where the employee worksHow to startWhat they submit
Slack/pto request, or Request time off on Cabana's Home tabRequest PTO form: leave type, start date, optional end date, note.
Microsoft TeamsSend request in a private Cabana chat, or choose Request time off on the welcome cardRequest card: leave type, start date, optional end date, note.
Cabana web appRequests → New requestWeb request form, including half-day and coverage options when applicable.

For a single day, leave the end date blank in the chat form. Use the web form for a morning or afternoon request; the current Slack and Teams forms don't have a half-day selector.

Keep the note useful: “Sam will cover the inbox” tells a manager more than “PTO.” Confirm the arrangement with Sam rather than treating a name in a field as an accepted handoff.

Keep pending requests in the balance calculation

Reserve requested days when the employee submits, then change their status when the decision arrives. That gives the employee an available balance that includes requests already in flight. A pending request hasn't become approved time off, but its days are already spoken for while the manager reviews it.

In Alex's example, the allowance is ten days and three have already been used. The two-day request changes the available figure from seven to five. After approval, used days become five and pending days become zero; available days stay at five.

Employees can check privately with /pto balance in Slack or balance in the personal Teams chat. Unlimited leave types show days used rather than an allowance remaining. Your admin manages the underlying accrual and carryover rules in Cabana.

Route the decision to a named manager

Give every request an accountable approver and make the outcome visible to the employee. Cabana sends the assigned manager a request message with Approve, Deny, and Open in Cabana. The message carries the dates, leave type, day count, and any note, so the decision belongs to that recorded request.

Maya chooses Approve in Alex's example. A policy with additional approval levels continues to the next manager before final approval. If the usual approver is on approved full-day leave, Cabana can route to an available delegate, up the reporting line, or to an admin. See the manager PTO approval checklist for the decision itself.

For a specific denial explanation, the manager uses Open in Cabana and enters a reason on the web request page. The Slack and Teams Deny buttons record fixed platform reasons rather than asking the manager to type one in chat.

Make the calendar the record of approved plans

Publish approved dates to the shared calendar and leave pending requests out of it. Colleagues planning a handoff or meeting should see confirmed absences. Managers reviewing a new request should inspect that calendar for overlap and use the request record for its current approval status and any unresolved decision.

Cabana's Calendar shows approved time off. Out today and Monday digest can post availability to your chosen Slack or Teams channel. These are scheduled updates, not an immediate channel announcement every time someone submits or approves a request.

Google Calendar and Outlook can subscribe to Cabana's private, read-only feed. It is a subscription, not two-way sync: your calendar app controls refresh timing, and editing its copy doesn't change a Cabana request.

Handle changed plans through the same request record

Keep changes attached to the original decision so nobody has to guess which dates still apply. In Cabana, open the request from Requests to cancel pending or approved leave. Canceling releases reserved days or restores used days, and canceled leave no longer appears on the team calendar.

To move the dates, cancel and submit a new request; there isn't an in-place date edit on the existing request. A subscribed external calendar reflects the change when that app refreshes its feed.

Choose a form when you can own the manual handoff

Use a form or structured email when you can reliably maintain the decision and calendar yourself. The fields still matter: employee, leave type, exact dates, and the manager's recorded answer. Assign an owner for updating the balance and shared calendar so a completed form doesn't become an unfinished process.

The Free PTO request form template gives you a consistent intake record. The Time off request email templates help employees send a complete request. Either can work without paid request software when someone keeps the records current.

Choose software when you want those records connected and the workflow in your team's daily tools. Compare the full category in PTO tracking software for small teams.

Use Cabana as your time off request system

Choose Cabana for employee requests and manager decisions in the chat tool your team already uses. Both PTO tracking in Slack and PTO tracking in Microsoft Teams connect that daily workflow to balances, policies, and the team calendar.

One plan costs $4 per user per month, with a $20/month minimum. The 30-day free trial needs no credit card. Start by taking one request through submission, decision, and calendar visibility with your own team.

Start your 30-day free trial.

Frequently asked questions

What should a time off request system record?

A time off request system should record the employee, leave type, exact dates, duration, approval status, and decision-maker. Useful context belongs with the request rather than in a separate conversation. The balance and calendar should reflect the decision so employees know what remains available and colleagues can plan around approved dates.

Do employees have to submit through the web app?

No. Employees can use `/pto request` in Slack or send `request` in a private Cabana chat in Microsoft Teams. Both open a form for leave type, dates, and a note. The web request form remains available and includes options such as half days that the current chat forms don't expose.

Does a submitted request immediately appear on the team calendar?

No. The shared team calendar shows approved leave, so a request requiring manager approval appears only after the required decisions are complete. Its days are reserved against the employee's balance while pending. In a multi-step approval chain, completing the first step doesn't yet turn the requested absence into approved time off.