> ## 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.

# Applying for leave

> Submit a leave request in PlanMyRounds, add shifts to avoid, attach supporting notes, and resolve roster conflicts — as an admin or a doctor.

There are two ways a leave request can be created in PlanMyRounds:

* An **admin** can add leave on behalf of any doctor.
* A **doctor** with a linked account can submit their own request from **My Leaves**.

The form is the same in both cases — only the starting point changes.

## Submit a request as an admin

**1. Open the doctor or Leave Applications**

Go to **Doctors** in the sidebar and open the doctor's profile, or navigate to **Leave Applications**.

**2. Start a new entry**

Select **Add Leave**.

**3. Pick the leave type**

Choose a **Leave Type** — for example, *Annual Leave* or *Sick Leave*. Only [active leave types](/docs/leave/leave-types) appear here.

**4. Choose the dates**

Select a **From** date and a **To** date. You can request up to **90 days** in a single range.

**5. Choose a shift type**

Pick **Full day**, **Day shift**, or **Night shift** depending on what's being covered.

**6. Add a reason (optional)**

Add a brief **Reason** if helpful — up to 50 characters.

**7. Stage and submit**

Select **Add Leave Request** to stage the entry, then select **Send for Approval** to submit it.

> [!NOTE]
>
> You can stage **multiple date ranges** in the same submission — keep adding entries before hitting **Send for Approval**.

## Submit a request as a doctor

If you have a linked PlanMyRounds account, you can request your own leave:

1. Go to **My Leaves** in the sidebar.
2. Select **Add Leave**.
3. Fill in the same fields described above and submit.

Your request goes straight to **Pending** and waits for admin approval.

## Mark shifts to avoid

In the same form there is a separate section called **Shifts to Avoid**. Use this for dates when a doctor would *prefer* not to be on duty but isn't strictly unavailable — for example, a family event or a study day.

Select a date range and a shift type, then select **Add Shift to Avoid** before submitting.

> [!TIP]
>
> Shifts to avoid are **soft preferences**. The scheduler tries to honour them where possible but they are not a hard block, unlike approved leave.

## What happens after you submit

Your request appears under **Leave Applications** with a **Pending** status.

* An admin reviews it and either [approves or rejects](/docs/leave/approval-workflow) the request.
* Once approved, those dates are automatically excluded from future duty assignments.
* If plans change before review, the request can be [cancelled](/docs/leave/cancelling-leave).

## If there's a date conflict

> [!WARNING]
>
> If a date you submit already has a pending or approved entry, a conflict warning appears. You can either submit only the non-conflicting dates or cancel and revise your request.

This stops duplicate entries from cluttering the team's leave history.

## Next steps

> **[Approve or reject leave](/docs/leave/approval-workflow)**
>
> Review pending requests from the admin side.

> **[Cancel a pending request](/docs/leave/cancelling-leave)**
>
> Withdraw a request before it's reviewed.


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