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

# Leave Management

> How students and guardians apply for leave, and how centre staff review, approve, or reject leave requests for the batches they teach.

Leave management keeps absences intentional rather than accidental. A student or guardian applies for planned time off, staff review the request, and the outcome is recorded, so an approved absence is never mistaken for a no-show.

## Roles and responsibilities

| Role                            | Responsibility                                        |
| ------------------------------- | ----------------------------------------------------- |
| **Student**                     | Applies for their own leave                           |
| **Guardian / Parent**           | Applies for leave on behalf of a child                |
| **Academics User / Instructor** | Reviews pending requests and approves or rejects them |

## Applying for leave

<Steps>
  <Step title="Open My Leave">
    A student or guardian opens **My Leave** from their sidebar.
  </Step>

  <Step title="Choose the batch and dates">
    Select the relevant batch and the dates the student will be away, with a reason.
  </Step>

  <Step title="Submit the application">
    The request goes to staff for review.
  </Step>
</Steps>

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/bizaxloptimizationsllp/images/placeholder-tuition-my-leave.png" alt="Leave application form with batch, dates, and reason" />
</Frame>

## Reviewing requests

Staff open **Leave Requests** to see applications waiting for a decision, then approve or reject each one.

<Steps>
  <Step title="Open Leave Requests">
    From the staff sidebar, choose **Leave Requests**.
  </Step>

  <Step title="Review pending applications">
    See who has applied, for which batch, and for which dates.
  </Step>

  <Step title="Approve or reject">
    Record the decision. The applicant can see the outcome.
  </Step>
</Steps>

## Leave field guide

| Field                     | Purpose                        |
| ------------------------- | ------------------------------ |
| **Student**               | The learner who will be absent |
| **Batch / student group** | The class the leave applies to |
| **Dates**                 | The period of absence          |
| **Reason**                | Why leave is requested         |
| **Status**                | Applied, approved, or rejected |

## Upstream and downstream dependencies

* **Upstream**: leave needs a [student](/education/tuition-centre/students-and-guardians) in a [batch](/education/tuition-centre/batches-and-enrolment).
* **Downstream**: an approved leave gives context to [attendance](/education/tuition-centre/timetable-and-attendance), so a planned absence is understood rather than treated as an unexplained one.

## Best practices

* **Apply in advance.** Leave is most useful when requested before the absence, not after.
* **Give a clear reason.** A short reason helps staff make a quick, fair decision.
* **Decide promptly.** A pending request leaves the family unsure; approve or reject without delay.