> For the complete documentation index, see [llms.txt](https://cyberpassion.gitbook.io/internal-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyberpassion.gitbook.io/internal-docs/office-rules-and-regulations/leaves-rules.md).

# Leaves Rules

#### **Advance Leave Information**

* Employees must inform management in advance before taking leave.
* Planned leave should preferably be informed at least **1 day before**.

#### **Same Day Leave Policy**

* Same day leave will be approved only in genuine medical emergencies or unavoidable situations.
* Proper medical reason or valid explanation may be required.

#### **Medical Emergency Leave**

* In case of illness or medical emergency, employees must inform management through call or message as soon as possible.
* Medical proof may be requested for extended leave.

#### **Unauthorized Absence**

* Leave without information or approval will be considered unauthorized absence.
* Repeated unauthorized leave may lead to disciplinary action.

#### **Leave Approval Requirement**

Every leave request must be approved by management or reporting authority before leave is considered valid.

#### **Work Responsibility Before Leave**

* Employees must complete urgent tasks or properly hand over pending work before leave.
* Project deadlines and important office work should not be affected due to leave.

#### **Office Availability & Communication**

* Employees should remain available on phone for important communication during emergency situations if required.

#### **Leave During Important Work**

* Employees should avoid unnecessary leave during important deadlines, meetings, or project delivery periods.

#### **Half Day & Late Coming**

* Frequent late coming may be counted as half day leave.
* Half day leave also requires prior information and approval.

#### **Professional Discipline**

* Proper communication and responsible leave management are part of professional office culture.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cyberpassion.gitbook.io/internal-docs/office-rules-and-regulations/leaves-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.