> ## Documentation Index
> Fetch the complete documentation index at: https://www.planmyrounds.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How leave management works in PlanMyRounds

> Understand how leave requests flow through PlanMyRounds — from a doctor submitting a request, through admin approval, to it appearing on the duty roster.

Leave management is where your team records when doctors are unavailable, so the scheduler can plan around them. Once a leave request is approved, the doctor is automatically taken out of duty assignments on those dates — no manual edits to the roster needed.

## What you can record

> **Leave requests**
>
> Dates a doctor cannot work — annual leave, sick leave, maternity leave, or any other category your organisation defines.

> **Shifts to avoid**
>
> Soft preferences — dates a doctor would rather not work. The scheduler tries to honour these, but they're not a hard block.

## How a leave request moves through the system

**1. Submit**

An admin or a doctor [submits a request](/docs/leave/applying-for-leave) with the dates, leave type, and shift.

**2. Review**

The request lands in **Leave Applications** with a **Pending** status, waiting for admin review.

**3. Decide**

An admin [approves or rejects](/docs/leave/approval-workflow) the request. Approved dates are immediately excluded from scheduling.

**4. Adjust**

Plans change. Pending requests can be [cancelled](/docs/leave/cancelling-leave); approved ones can be reversed by an admin.

## Leave statuses

Every leave entry sits in one of four statuses:

| Status | What it means |
| - | - |
| **Pending** | Submitted and waiting for admin review. |
| **Approved** | Accepted by an admin. The doctor is excluded from scheduling on this date. |
| **Rejected** | Declined by an admin. The doctor stays available for scheduling. |
| **Removed** | Cancelled by the doctor or an admin. Cannot be restored. |

> [!NOTE]
>
> A leave request only affects scheduling once it's **Approved**. Pending and rejected entries are ignored when a roster is generated.

## Who can do what

| Action | Doctor (linked account) | Admin |
| - | :-: | :-: |
| View own leave history | ✓ | ✓ |
| View all team leave | — | ✓ |
| Submit own leave request | ✓ | ✓ |
| Submit leave for another doctor | — | ✓ |
| Approve or reject requests | — | ✓ |
| Cancel a pending request | ✓ (own only) | ✓ (any) |
| Create or edit leave types | — | ✓ |

## Where to find leave features

> **Leave Applications**
>
> Admin view of every leave entry across the team. Filter, review, approve, or reject from here.

> **My Leaves**
>
> A doctor's personal view of their own leave history and upcoming requests.

> **[Leave Calendar](/docs/leave/calendar)**
>
> A month-by-month calendar of everyone's leave, with filters by department, pod, doctor, and seniority.

> **[Leave Types](/docs/leave/leave-types)**
>
> The categories your organisation uses to classify time off — set up and managed by admins.

## Next steps

> **[Set up your leave types](/docs/leave/leave-types)**
>
> Define the categories your team will use — Annual Leave, Sick Leave, and more.

> **[Submit a leave request](/docs/leave/applying-for-leave)**
>
> Walk through how to add a leave entry as an admin or a doctor.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.