Update leave-request.md (#41)

* Update leave-request.md

* Update leave-request.md

guides/leave-request.md

@@ -10,43 +10,46 @@ tags:
   - operations
 ---
 
-A consistent on leave process prevents a company from being accidentally disrupted when an employee request to be absent. 
+A consistent leave process prevents a company from being accidentally disrupted when an employee requests to be absent.
 
-At our woodland, every time an employee submit a request for on leave or remote work, whether it is for half-shift or all day absence, the process shall be required to follow these following steps:
+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:
 
-### Before request submission
-Employee needs to discuss with the client and the team ahead to align tasks so their absence affect project as little as possible. 
+### 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:
 
-### Request submission
-We segment the request based on the urgency of the request. 
-- Urgent request: Notify project manager, account manager and project lead immediately.
-- Not urgent request: You need to notify double the time of absence 
-- Holiday requeset: This request need to notify 1 to 2 week ahead.
+- 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, employee must log in on the company's Basecamp channel and create a ticket on **On-leave Request** list and assign the ticket to project manager, account manager and project lead, with the detailed format as below:
+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:
 
-![](assets/leave-request_clean-shot-2024-08-01-at-17-33-57-2x.webp)
+- List: On-Leave Requests
+- Ticket format: Name | Type of absence (off) | Date | Shift (if any)
+- Assign to: Mentor or Product Manager
 
-For example, if engineer Khiem Vo is planning to have his day off on both Jan 4th and Jan 5th, the request must be submitted 4 days in advance, which is Jan 1st. And the mentor of Khiem Vo is Huy Nguyen. The request should be:
+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)
 
-### Notify and verification
-The mentor should notify Project Manager by email and cc Operation Department for their counsel of approval. 
-In case the responsibility of this employee is involved in any project, a contingency strategy should be applied in order to prevent the working process from being interrupted or blocked. 
+### 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.
 
 ### Approval/ Denial
-After the approval/ denial decision has been made, Basecamp will inform the employee with an email of approval, along with a Google Calendar schedule. 
+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. 
 
-The manager will also mark done on the ticket which was assigned to him previously, and note down the employee's return date (if the request is approved) or the reason (if the request is denied)
+If the request is denied, the manager or lead is required to note the reason in the ticket.
 
 ### Announcement
-An email of announcement should be sent from the mentor to the employee, Project Manager and Operation for confirmation. In addition, a short message can be delivered informally to the related-team channel to notify other team members. 
-
-At the client side, employee must annouce to clients via email or communication channel. 
+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 holiday starts, Operation will send official announcement via email to all clients about the holiday period. After that 2-3 days before holiday starts, Project Manager or Leader of the project need to remind clients again informally via Slack or other communication channels of that project.
+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.
+
+
+
 
-Note: During Holiday day or day off, unless it's stated as URGENT, we should NOT response to client on that day