How to Track Vacation in Microsoft Teams

To track vacation in Teams, use an Outlook group calendar for agreed dates, Planner or Lists for a manual record, or Shifts for schedule-based time-off requests. Keep one place where approval is recorded and one reliable PTO balance. Out of office status helps colleagues see availability, but it does not approve a vacation.

Choose your Teams shared vacation calendar approach¶

For an office manager who handles PTO alongside payroll, the right option is the one that stays correct after someone changes plans. Decide who owns the approval, the shared view, and the balance before setting up another tab.

The table compares a basic setup of each tool. A custom workflow can extend it, but someone still needs to maintain that workflow.

If your current process already approves requests reliably, a shared calendar may be enough. If nobody can explain which message counted as approval, solve that first. A new calendar will only make the uncertainty more visible.

Set up a shared Outlook vacation calendar¶

Use an existing Microsoft 365 group's calendar when the goal is team visibility. Microsoft's group vacation calendar instructions explain how to add an absence without sending an invitation to everyone.

In new Outlook for Windows:

1. Open the group calendar. Go to Calendar, then select the right group under Groups. Confirm that the coworkers who need it can access it.
2. Create the entry. Choose New event and select the group calendar in the event's calendar field. Use a clear title such as “Jordan — vacation.”
3. Enter the absence. Set the start and end dates, use All day for full-day leave, set availability to Free, and turn off reminders. This is the shared awareness entry.
4. Save and share the location. Save without inviting everyone unless notifications are part of your process. Share the calendar link in your Teams channel so colleagues know where to look.

Keep your own calendar blocked separately. The shared entry's Free setting avoids reserving colleagues' time; your personal absence should show that you are unavailable.

Where it breaks down: someone must add, change, and remove entries after decisions. Give that job to the employee or process owner explicitly. If a request is canceled but its calendar entry remains, your team plans around an absence that no longer exists.

Use Planner for a manual vacation request board¶

Planner is useful when your team already coordinates work through cards. Microsoft documents shared plans and their views, including a Board view grouped by bucket. Treat the following as a proposed PTO process, rather than a built-in vacation template.

1. Create a shared plan. Open Planner in Teams, select New plan, and choose a basic blank plan. Give it a clear name and associate it with the intended Microsoft 365 group so it is shared with the right team.
2. Create decision buckets. Use Requested, Approved, Declined, and Canceled. Assign a manager to review new cards.
3. Create a card per request. Put the employee's name and absence dates in the title. Record the requested start and end dates in the card, add handoff details, and assign the reviewing manager.
4. Record the outcome. The manager moves the card to its decision bucket. Agree who updates the shared calendar and balance record after approval or cancellation.

Where it breaks down: a task's completion state and a vacation's approval state mean different things. Marking a handoff complete should not silently approve the absence. Keep your bucket convention visible and retain the decision when a card changes.

If every change requires your office manager to update several places, Planner may be better kept as the handoff board. Use the PTO policy guide for small business to define the decision rule before adding more automation.

Build a vacation tracker with Microsoft Lists¶

Lists is the strongest manual option here when you need a consistent record rather than a loose card. Start in the desktop or web app: Microsoft's Lists in Teams guide covers creating a list in a channel and explains where the underlying data lives.

1. Create the list. In your Teams channel, select Add a tab, choose Lists, then create a blank list called Vacation requests.
2. Add a small field set. Use the suggested schema below. Keep personal explanations out of the team-visible record.
3. Create a calendar view. Follow Microsoft's calendar view instructions: choose Add view, select Calendar, and map your start and end date columns. Use the employee or request title as the label.
4. Separate requests from availability. Keep a request queue and an approved-only view for planning. If the channel tab does not show the view you need, open the list in SharePoint and share that view's link with the team. Check access with a regular employee account.
5. Assign the upkeep. Name who records approval and cancellation. Decide who can edit decision fields before opening the list to everyone.

A starter field set you can copy¶

Where it breaks down: a Status field records a decision; it does not establish who is allowed to make it. A working PTO list needs an editing-permission plan and a clear owner. Add a separate balance calculation only when someone can explain and maintain its assumptions about working days, accruals, and carryover.

Request and approve vacation in Shifts¶

Shifts is the native option to test first when your team already works from a shift schedule. It includes employee time-off requests and manager decisions. Ask your team owner to confirm the schedule and request settings before moving employees over from an existing process.

For desktop and web, Microsoft's Shifts request guide gives this route:

1. Open Shifts. Select Requests, then New request and Time off.
2. Enter the absence. Set start and end dates, choose full-day or partial-day time as needed, select the reason, and add an optional note.
3. Send the request. Select Send request and keep it in the request queue until a manager decides.
4. Review as the manager. Open the pending request, inspect its details, and choose Approve or Deny. Microsoft's manager instructions explain the decision and schedule update.

The employee receives the outcome in the Teams Activity feed. Use the request's recorded status to confirm the decision.

Where it breaks down: request handling and allowance accounting are separate requirements. Before relying on Shifts for your full policy, test how your team will maintain balances, carryover, and changes to approved leave. Avoid promising those calculations simply because the request button is available.

Review the Shifts privacy settings too. Managers can limit whether coworkers see time-off reasons and notes. Shared availability rarely needs the explanation behind an absence.

Set your Teams out of office status after approval¶

Schedule your out of office message after the vacation is confirmed so coworkers know when you are unavailable. In Teams, open your profile picture, choose Set status message, then Schedule out of office. Enable automatic replies, enter a message, set the time range, and save.

Microsoft explains that Teams out of office settings connect with Outlook automatic replies. Those replies communicate availability. Keep the approval decision in your chosen request system and check your personal calendar's availability separately.

Use a simple message: “I'm on vacation through my return date. Contact Morgan for urgent client questions.” Colleagues need a backup and a return expectation, not the details of your trip.

Test the whole process before rollout¶

Ask an employee and manager to walk through the same test request. Confirm approval, then change the dates, and finally cancel it. Inspect the shared view and the balance record after each change.

Use these checks for every method:

• Can an employee distinguish a submitted request from confirmed leave?
• Does the manager know who covers the work before approving?
• Can coworkers find the final dates without searching messages?
• Does a cancellation clear the old entry and correct the balance?

If a step depends on someone remembering a second update, document that handoff. That may be entirely workable for your team. The problem is leaving the handoff unnamed.

For example, Casey has an approved Friday off, then asks to move it to Monday. The manager needs to decide the replacement dates, the team view needs the old Friday removed, and the balance record needs the original booking corrected before the replacement is recorded. Ask who owns each update, including what happens if Monday is declined.

Write down the result: “Casey keeps the original approved dates until the manager confirms a change. The process owner replaces the shared entry and checks the leave record after confirmation.” That rule prevents an edited calendar event from becoming an accidental approval. Run the same check when your usual approver is away so the backup knows which record to update.

How Cabana handles vacation in Microsoft Teams¶

Cabana connects requests, approvals, and visibility to PTO tracking software for small teams. Employees use a private Teams chat for their own leave; managers receive a decision card, and the team can check who's away.

After your admin connects the Microsoft 365 directory, links employees, and installs the app, try this sequence:

Have employees and approvers open a private Cabana chat and send help before testing.

1. Request. Send request privately to Cabana. Choose the leave type, start date, optional end date, and note, then select Submit.
2. Decide. The assigned approver selects Approve or Deny on the request card in Teams. Final approval puts the absence on Cabana's team calendar.
3. Check availability. Send whosout, or use @Cabana whosout in a channel where the app is installed. Use balance privately for your own figures.

The complete PTO tracking in Microsoft Teams guide covers installation and channel announcements. For Outlook visibility, subscribe to Cabana's read-only calendar feed; changes stay in Cabana and Outlook controls refresh timing.