Skip to content

Commit

Permalink
fix: edit content leave & request (#42)
Browse files Browse the repository at this point in the history
  • Loading branch information
innnotruong authored Aug 20, 2024
1 parent 78c9a6c commit f5d70e4
Showing 1 changed file with 24 additions and 29 deletions.
53 changes: 24 additions & 29 deletions guides/leave-request.md
Original file line number Diff line number Diff line change
@@ -1,55 +1,50 @@
---
title: Leave Request
date: 2019-02-21
date: 2024-08-20
description: A consistent on leave process prevents a company from being accidentally disrupted when an employee request to be absent.
authors:
- duy
- innno_
- minh_cloud
tags:
- employee
- handbook
- operations
---

A consistent leave process prevents a company from being accidentally disrupted when an employee requests to be absent.
To keep everything running smoothly, it’s important that we all follow a clear process when requesting leave. Whether you’re planning a half-shift or a full day off, we want to make sure your absence doesn’t disrupt the team or the project.

At our workplace, every time an employee submits a request for leave, whether it is for a half-shift or a full-day absence, the process must follow these steps:
By following these steps, you help ensure that everyone is on the same page and that your work is covered while you're away:

### Before Request Submission
Employees need to discuss with the client and the team in advance to align tasks so their absence affects the project as little as possible.

### Request Submission
We segment the requests based on the urgency:

- Urgent request: Notify the project manager, account manager, and project lead immediately.
- Non-urgent request: Notify at least double the time of the absence.
- Holiday request: Notify 1 to 2 weeks in advance.

For every request, employees must log in to Basecamp, go to Woodland channel and create a ticket on the On-leave Request list, assigning the ticket to the project manager, account manager, and project lead, with the following format:

- List: On-Leave Requests
- Ticket format: Name | Type of absence (off) | Date | Shift (if any)
- Assign to: Mentor or Product Manager
Discuss your leave with the client and team in advance to align tasks and minimize the impact on the project.

### How To Submit Request
- [ ] Log in to Basecamp.
- [ ] Create a ticket in the Woodland channel > On-Leave Request list.
- [ ] Use the format: Name | Type of absence (off/remote) | Date | Shift (if any).
- [ ] Assign to: Project Manager, Account Manager, and Project Lead.
- Timing:
- **Urgent**: Immediate
- **Non-urgent**: 2x absence duration
- **Holiday**: 1-2 weeks in advance

For example, if Thanh Pham plans to have his day off on both Jul 9th to 12th, the request must be submitted 8 days in advance, on Jul 1st. If Thanh Pham's mentor is Han Ngo, the request should be formatted as follows:

![](assets/leave-request_clean-shot-2024-08-01-at-17-34-52-2x.webp)

### Verification & Notification
After submitting the request, the line manager and leader will discuss the request with the employee, align the workload and resources, and design a working process to prevent interruption.
After submitting the request, the line manager and leader will discuss the request with you. They will work with you to align the workload and resources to ensure the project remains on track. A working process will be designed to prevent any interruptions during your absence.

### Approval/ Denial
If the request is approved, the manager will mark the ticket as done and note the employee's return date. Basecamp will inform the everyone involved via an email of approval, along with a Google Calendar schedule. Since the client can't receive Basecamp notification, employee or manager must send an email to inform client about the leave request.
### Approval/Denial
If your request is approved, the manager will mark the ticket as done and note your return date. Basecamp will send an approval email to everyone involved, and the Google Calendar will be updated.

If the request is denied, the manager or lead is required to note the reason in the ticket.
Since the client doesn't receive Basecamp notifications, you or the manager must inform the client via email. If denied, the manager or lead will note the reason in the ticket.

### Announcement
After approval, a short informal message should be delivered to the related team channel to notify other team members. On the client side, the employee must announce their leave to the client's communication channel and remind them before the leave.

### Holiday
1-2 weeks before the holiday starts, Operations will send an official announcement via email to all clients about the holiday period. 2-3 days before the holiday starts, the Project Manager or Leader needs to remind clients informally via Slack or other communication channels.

**Note**: During holidays or days off, unless stated as URGENT, we should NOT respond to clients on that day.


Once your request is approved, a short informal message should be delivered to the related team channel to notify other team members. On the client side, you must announce your leave to the client’s communication channel and remind them before the leave.

### Holiday Notifications
1-2 weeks before the holiday starts, Operations will send an official email announcement to all clients about the holiday period. Then, 2-3 days before the holiday begins, your Project Manager or Leader will remind clients informally via Slack or other communication channels.

**Note**: During holidays or days off, unless stated as URGENT, we should NOT respond to clients on that day.

0 comments on commit f5d70e4

Please sign in to comment.