Team Lead — Leave Management User Guide

Version: 1.0
Last updated: December 10, 2025

Table of Contents


1. Welcome to Leave Management

Welcome to the Team Lead Leave Management System! This guide will help you understand how to review, approve, and manage leave requests from your team members.

What is this system?

The Leave Management system is where you review leave requests submitted by your team members. As a team lead, you play a crucial role in the leave approval workflow:

  • You receive leave requests from your team
  • You review team member availability and workload
  • You approve or reject requests based on team needs
  • You document your decisions
  • You communicate approval status to your team members

Your role in the approval process:

Employee Submits Leave Request
        ↓
[YOU - Team Lead Reviews]
        ↓
Approve / Reject / Request More Info
        ↓
Request sent to HR for final approval
        ↓
Employee notified of final status

2. What You Can Do

As a Team Lead, you can:

View all leave requests from your team members ✅ Review detailed information about each request ✅ Approve leave requests you support ✅ Reject leave requests that create team issues ✅ Add comments explaining your decision ✅ Check employee leave balance before approving ✅ Filter requests by status, date, or employee ✅ Search for specific team member requests ✅ Export leave data for your records ✅ Track leave patterns and trends

What you cannot do:

❌ Cannot change HR leave policies ❌ Cannot modify approved leave dates after HR approval ❌ Cannot override HR final decisions ❌ Cannot access other team leads' team requests ❌ Cannot delete leave requests (only cancel as employee) ❌ Cannot adjust employee leave balance manually


3. How to Access Leave Management

Method 1: From the Main Menu

  1. Log in to the DTR System
  2. Click on TL Dashboard in the main navigation
  3. Click on Leave Management or Leave Requests
  4. You're now viewing the Leave Management system

Method 2: Direct URL

URL: /tl/leave-request

Method 3: From Dashboard

  1. Log in to DTR System
  2. Click on TL Dashboard
  3. Look for "Pending Leave Requests" card
  4. Click "View All" or "View More"
  5. Redirected to Leave Management system

4. Understanding the Leave Request List

Page Overview

The Leave Request List is your main page showing all leave requests from your team members in a table format.

Page Layout:

┌─────────────────────────────────────────────────────────────┐
│ FILTER & SEARCH SECTION (Top)                               │
│ Date Range | Status | Employee | Leave Type | [Filter Btn]  │
├─────────────────────────────────────────────────────────────┤
│ LEAVE REQUEST TABLE (Main Content)                           │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ ID | Employee | Type | Dates | Duration | Status | ... │ │
│ ├─────────────────────────────────────────────────────────┤ │
│ │ Row 1: Jane Doe | Vacation | Dec 10-15 | 5 days | Pend...│ │
│ │ Row 2: John Smith | Sick | Dec 20 | 1 day | Pending     │ │
│ │ Row 3: Alice Brown | Personal | Dec 5 | 1 day | Approved│ │
│ └─────────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ PAGINATION (Bottom)                                          │
│ Showing 1-10 of 25 requests | [< Previous] [1] [2] [Next >] │
└─────────────────────────────────────────────────────────────┘

Top Section: Filters & Quick Actions

Filter Controls:

  • From Date (calendar input):

    • Start date for filtering requests
    • Default: First day of current month
    • Use to find requests in specific period
    • Format: YYYY-MM-DD or use date picker
  • To Date (calendar input):

    • End date for filtering requests
    • Default: Current date
    • Format: YYYY-MM-DD or use date picker
    • Validation: Must be after From Date
  • Status Filter (dropdown):

    • All (default) — Show all requests
    • Pending — Waiting for your approval
    • Approved — You approved these
    • Rejected — You rejected these
    • HR Approved — HR approved (final status)
    • HR Rejected — HR rejected (final status)
  • Employee Filter (dropdown/searchable):

    • All Employees (default)
    • List of your team members
    • Search by name if long list
    • Searchable: Type to find employee
  • Leave Type Filter (dropdown):

    • All Types (default)
    • Vacation
    • Sick Leave
    • Personal Leave
    • Maternity/Paternity
    • Bereavement Leave
    • Unpaid Leave
    • Other

Action Buttons:

  • Filter Button:

    • Applies all selected filters
    • Updates table with matching requests
    • Shows filtered count: "Showing 5 of 25 results"
  • Clear Filters Button:

    • Resets all filters to default
    • Shows all requests again
    • Clears date range back to current month
  • Export Button (optional):

    • Downloads leave data
    • CSV or Excel format
    • Uses current filters
    • Includes selected columns
  • Refresh Button:

    • Manually refresh data
    • Updates with latest requests
    • Shows any new submissions

Leave Request Table

Columns Displayed:

Column What It Shows Example
Request ID Unique request number LR-001234
Employee Team member name + ID + avatar Jane Doe (EMP-001)
Leave Type Type of leave requested Vacation, Sick Leave
Date Range Start date - end date Dec 10 - Dec 15, 2025
Duration Number of days requested 5 days
Submitted When request was submitted Dec 5, 2025 at 2:30 PM
Status Current approval status Pending, Approved, Rejected
Reason Why employee needs leave Family vacation, Doctor appointment
Actions View details or edit View, Edit, Delete

Status Badges (Color-Coded):

[Yellow Badge]  PENDING      — Waiting for your approval
[Green Badge]   APPROVED     — You approved this
[Red Badge]     REJECTED     — You rejected this
[Blue Badge]    HR APPROVED  — HR approved (final)
[Dark Red]      HR REJECTED  — HR rejected (final)
[Gray Badge]    CANCELLED    — Employee cancelled

Table Features:

  • Pagination: 10-25 requests per page (configurable)
  • Sorting: Click column header to sort (optional)
  • Row styling:
    • Pending: Light yellow background
    • Approved: Light green background
    • Rejected: Light red/pink background
    • HR Approved: Darker green background
    • Hover effect: Highlight row for clarity
  • Clickable row: Click row to view details
  • Inline actions: Edit and view buttons on right side

Empty State

If no requests match your filters:

No leave requests found

Try:
- Clearing filters
- Changing date range
- Selecting different status
- Searching different employee

5. Viewing Detailed Leave Requests

How to Access Details Page

Steps:

  1. From the Leave Request List
  2. Find the request you want to review
  3. Click the eye icon or "View Details" button
  4. Or click anywhere on the row
  5. Details page opens with full information

Details Page Layout

The details page shows complete information about a single leave request.

Page Structure:

┌──────────────────────────────────────────┐
│ EMPLOYEE INFO (Top Card)                 │
│ [Avatar] Jane Doe (EMP-001)              │
│ Department: App Tech | Position: Senior Dev
│ Manager: John Smith | Email: jane@...   │
├──────────────────────────────────────────┤
│ LEAVE REQUEST DETAILS (Middle Section)   │
│ Leave Type: Vacation                     │
│ Dates: Dec 10 - Dec 15, 2025             │
│ Duration: 5 working days                 │
│ Reason: Family vacation                  │
│ Status: Pending                          │
│ Submitted: Dec 5, 2025 at 2:30 PM       │
├──────────────────────────────────────────┤
│ LEAVE BALANCE (If Available)             │
│ Total Days: 20 | Used: 12 | Remaining: 8│
│ Requesting: 5 days ✓ (Sufficient)        │
├──────────────────────────────────────────┤
│ ATTACHMENTS (If Available)               │
│ - doctor_note.pdf                        │
│ - medical_certificate.pdf                │
├──────────────────────────────────────────┤
│ COMMENTS & HISTORY                       │
│ Previous comments on this request        │
├──────────────────────────────────────────┤
│ YOUR DECISION (Bottom Section)           │
│ [Approve Button] [Reject Button]         │
│ Comment: [Your decision reason]          │
│ [Submit Button]                          │
└──────────────────────────────────────────┘

Section 1: Employee Information

Displays:

  • Employee's profile picture
  • Full name
  • Employee ID
  • Department
  • Position/Job Title
  • Manager name
  • Contact email
  • Hire date (optional)

Purpose: Confirm you're reviewing the correct employee

Example:

┌─────────────────┐
│  [Avatar] Jane  │
│  Jane Doe       │
│  EMP-001        │
│  App Tech       │
│  Senior Dev     │
│  Manager: John  │
└─────────────────┘

Section 2: Leave Request Details

Displays:

  • Leave Type (Vacation, Sick, Personal, etc.)
  • Start Date
  • End Date
  • Duration (number of days)
  • Reason for leave
  • Submission date and time
  • Current status

Example:

Leave Type:        Vacation
Start Date:        December 10, 2025
End Date:          December 15, 2025
Duration:          5 working days
Reason:            Family vacation in Europe
Status:            Pending
Submitted:         December 5, 2025 at 2:30 PM

Section 3: Leave Balance

If Available, Shows:

  • Total leave days allocated
  • Days already used this year
  • Remaining balance
  • Days being requested
  • Sufficient/insufficient indicator

Example:

Leave Balance Analysis:
├─ Total Annual Leave:  20 days
├─ Already Used:        12 days
├─ Remaining:           8 days
├─ Requesting:          5 days
└─ Status:              ✓ Sufficient balance

What to check:

  • Does employee have enough balance?
  • Will approval bring them below zero?
  • Are there concerns about balance?

Section 4: Attachments

If Employee Provided:

  • Medical certificates (for sick leave)
  • Doctor's notes
  • Travel itineraries
  • Supporting documents
  • Evidence of emergency

How to view:

  1. Click on attachment name
  2. Download or preview the file
  3. Review for verification

Why it matters:

  • Verify medical conditions for sick leave
  • Confirm emergency for bereavement leave
  • Check documentation for extended leave

Section 5: Comments & Discussion History

Shows:

  • Previous comments on this request
  • Who made comments (employee, manager, HR)
  • Timestamps of each comment
  • Full comment text

Example:

Manager (John Smith) - Dec 5, 2025 at 3:00 PM:
"Project deadline is Dec 20, so this timing works."

HR Specialist (Alice Brown) - Dec 5, 2025 at 3:15 PM:
"Checking leave balance..."

Purpose: See discussion context before making decision

Section 6: Your Decision Section

For Approval:

  1. Click "Approve" button
  2. (Optional) Add comment explaining approval
  3. Comment examples:
    • "Team coverage is adequate"
    • "Project timeline allows this"
    • "Employee has sufficient balance"
  4. Click "Submit" or "Confirm"
  5. System sends approval to HR and employee

For Rejection:

  1. Click "Reject" button
  2. Required: Add reason for rejection
  3. Reason examples:
    • "Critical project deadline during this period"
    • "Insufficient team coverage"
    • "Please provide medical certificate"
  4. (Optional) Add additional comments
  5. Click "Submit" or "Confirm"
  6. System notifies employee with your reason

Reasons for Common Rejections:

  • Project conflict: "We have critical deliverable Dec 15"
  • Coverage issue: "Need 2 more team members"
  • Documentation missing: "Medical certificate required"
  • Timing conflict: "Other team members already off then"
  • Insufficient balance: "Not enough leave days available"

6. Filtering and Searching

Quick Filters

By Status:

Filter: Status = "Pending"
└─ Shows requests waiting for YOUR approval
   Action needed: Review and decide

Filter: Status = "Approved" (by you)
└─ Shows requests you approved
   Next step: Sent to HR for review

Filter: Status = "Rejected" (by you)
└─ Shows requests you rejected
   Employee notified of your decision

Filter: Status = "HR Approved"
└─ Shows final approvals (HR approved)
   Status: Final, no more action needed

Filter: Status = "HR Rejected"
└─ Shows final rejections (HR rejected)
   Status: Final decision made by HR

By Employee:

  1. Click Employee dropdown
  2. Select specific team member
  3. Shows all their requests (all statuses)
  4. Use to review one person's leave history

By Date Range:

  1. Set From Date (start of period)
  2. Set To Date (end of period)
  3. Shows requests within that period
  4. Use to review specific months or quarters

By Leave Type:

  1. Click Leave Type dropdown
  2. Select type (Vacation, Sick, etc.)
  3. Shows only that type of leave
  4. Use to analyze trends by type

Combining Multiple Filters

Example Scenario: "Show all pending vacation requests from Jane in December"

Steps:

  1. Employee: Select "Jane Doe"
  2. Leave Type: Select "Vacation"
  3. Status: Select "Pending"
  4. From Date: December 1, 2025
  5. To Date: December 31, 2025
  6. Click "Filter"
  7. Table shows only matching requests

Clear All Filters

To reset all filters:

  1. Click "Clear Filters" button (if visible)
  2. Or manually reset each field
  3. Table returns to showing all requests

7. Common Tasks & Step-by-Step Guides

Task 1: Review Your Team's Pending Leave Requests

Objective: See all requests waiting for your approval

Time needed: 5-10 minutes

Steps:

  1. Navigate to Leave Management page
  2. Status filter: Select "Pending"
  3. Employee filter: Select "All Employees" (shows your team only)
  4. Click "Filter"
  5. Table shows pending requests from your team
  6. Review list:
    • How many are pending?
    • What are the dates?
    • Any conflicts?

Example:

Results: 3 pending leave requests
├─ Jane Doe: Vacation Dec 10-15 (5 days)
├─ John Smith: Sick Leave Dec 20 (1 day)
└─ Alice Brown: Personal Dec 5 (1 day)

Next: Click each one to review in detail


Task 2: Approve a Leave Request

Objective: Approve an employee's leave request

Time needed: 3-5 minutes per request

When to approve:

  • ✓ Team has sufficient coverage
  • ✓ No critical project deadline
  • ✓ Employee has leave balance
  • ✓ Proper advance notice given
  • ✓ Documentation complete

Steps:

  1. Find the leave request in the list
  2. Click "View Details" or row
  3. Details page opens
  4. Review all information:
    • Employee name and role
    • Leave type and dates
    • Duration and reason
    • Employee's leave balance
    • Any attachments
  5. Check team impact:
    • Will team have enough coverage?
    • Any critical deadlines?
    • Are other team members off?
  6. If everything looks good:
    • Scroll to bottom
    • Click "Approve" button
  7. (Optional) Add comment:
    • Example: "Team coverage confirmed"
    • Example: "Project timeline allows absence"
    • Example: "Balance verified - sufficient"
  8. Click "Submit" or "Confirm"
  9. Success message appears
  10. Employee and HR notified

Confirmation Message:

✓ Approval submitted successfully

Jane Doe's vacation request (Dec 10-15)
has been APPROVED.

Request sent to HR for final review.
Employee will be notified.

Task 3: Reject a Leave Request

Objective: Decline a leave request with clear reason

Time needed: 3-5 minutes per request

When to reject:

  • ✗ Team would be understaffed
  • ✗ Critical project deadline during dates
  • ✗ Employee has insufficient balance
  • ✗ Missing required documentation
  • ✗ Leave would impact critical operations

Steps:

  1. Find the leave request in the list
  2. Click "View Details" or row
  3. Details page opens
  4. Review all information
  5. If you need to reject:
    • Scroll to bottom
    • Click "Reject" button
  6. Required: Add reason
    • Be specific and professional
    • Avoid vague reasons
    • Explain business impact
  7. Reason examples:
    • "Critical project deadline Dec 12. Team cannot spare developer now. Suggest alternative dates Dec 20-24."
    • "Need 50% team presence minimum. Two others already approved for this period. Please request different dates."
    • "Medical certificate required for 3+ day sick leave. Please provide documentation."
    • "Insufficient leave balance (5 days requested, only 3 remaining)."
  8. (Optional) Add additional comments
  9. Click "Submit" or "Confirm"
  10. Success message appears
  11. Employee notified with your reason

Rejection Message Sent to Employee:

Your leave request has been REJECTED

Request: Vacation - Dec 10-15, 2025
Reason: Critical project deadline Dec 12.
        Team cannot spare developer now.
        Suggest alternative dates Dec 20-24.

Please contact your manager (John Smith)
to discuss alternative dates.

Employee next steps:

  • Can contact you to discuss alternatives
  • Can resubmit with different dates
  • Can appeal through HR if needed

Task 4: Find a Specific Employee's Request

Objective: Quickly locate one person's leave request

Time needed: 1-2 minutes

Steps:

  1. Open Leave Management page
  2. Employee filter: Type/select employee name
  3. (Optional) Add status filter if needed
  4. Click "Filter"
  5. Table shows only that employee's requests
  6. Review their leave history
  7. Click to view specific request details

Example:

"Find all of Jane Doe's requests"

1. Employee filter: Select "Jane Doe"
2. Click "Filter"
3. Shows: 5 total requests
   - Dec 10-15: Vacation (Approved)
   - Dec 20: Sick Leave (Pending - your approval needed)
   - Jan 5-10: Vacation (Pending - your approval needed)
   - Feb 14: Personal (Rejected by you)
   - Mar 1-5: Vacation (Pending)
4. Click on Dec 20 request to review sick leave

Task 5: Check Team Coverage for Specific Dates

Objective: See who's off during a period to assess coverage

Time needed: 5-10 minutes

Steps:

  1. Open Leave Management page
  2. From Date: Set to period start
  3. To Date: Set to period end
  4. Status: Select "Approved" or "Pending"
  5. Click "Filter"
  6. Review who's off during this period
  7. Assess team coverage:
    • How many team members off?
    • What roles will be missing?
    • Can remaining team handle workload?

Example:

"Check coverage for December 10-15"

From: Dec 10, 2025
To: Dec 15, 2025
Status: Approved (already approved leaves)

Results: 2 team members off
├─ Jane Doe: Dec 10-15 (Developer) - APPROVED
└─ John Smith: Dec 12-14 (QA) - APPROVED

Coverage Impact:
├─ 2 of 5 team members off (40%)
├─ Missing: 1 Developer, 1 QA
├─ Remaining: 1 Dev, 1 QA, 1 Manager
└─ Assessment: Tight but manageable with priority shift

Decision for Alice Brown's request (Dec 10-15):
REJECT - Cannot afford 3rd person off during this week

Task 6: Respond to a Request Needing More Info

Objective: Ask for additional information before deciding

Steps:

  1. View the request details
  2. Identify what's missing:
    • Medical certificate for sick leave
    • Project justification
    • Backup plan details
  3. Add comment requesting information:
    • "Please provide medical certificate for 3-day leave"
    • "Can you explain how project will be covered?"
  4. Click "Submit" (leave status as Pending)
  5. Employee receives notification with your request
  6. Employee adds information/comment
  7. Return to review when ready

Note: Different systems handle this differently:

  • Some allow requesting info without approving/rejecting
  • Others require you to reject and resubmit workflow
  • Check your system's specific workflow

Task 7: Export Team Leave Data

Objective: Download leave requests for records or sharing

Time needed: 2-3 minutes

Steps:

  1. Set filters for data you want:
    • Date range (e.g., Dec 2025)
    • Status (All, Pending, Approved, etc.)
    • Employee (All or specific)
  2. Click "Export" button
  3. Choose format:
    • CSV (for spreadsheets)
    • Excel (.xlsx) (formatted)
    • PDF (for printing/sharing)
  4. File downloads to your computer
  5. Open file to verify data
  6. Print or share as needed

What's included:

  • Request ID
  • Employee name and ID
  • Leave type
  • Date range
  • Duration
  • Status
  • Your approval/rejection
  • Comments

Use cases:

  • Share with manager for visibility
  • Keep records for compliance
  • Generate monthly reports
  • Submit to HR for processing
  • Maintain team leave calendar

Task 8: Monitor Leave Trends

Objective: Identify patterns in team's leave usage

Time needed: 10-15 minutes

Steps:

  1. Set date range (full quarter or year)
  2. Status: "Approved" (actual leaves taken)
  3. Filter without selecting specific employee
  4. Review all approved requests
  5. Look for patterns:
    • Who takes most leave?
    • When is peak leave period?
    • Any suspicious patterns?
  6. Analyze:
    • Is distribution fair?
    • Any coverage gaps?
    • Any employees not taking leave?

Example Analysis:

Q4 2025 Leave Analysis:

Month   Requests   Peak Days    Pattern
Oct     3 requests Oct 10-20    Mid-month spike
Nov     2 requests Nov 1-5      Post-holiday
Dec     5 requests Dec 20-31    Year-end spike

Observations:
├─ Jane takes leave spread throughout
├─ John clusters all at year-end
├─ Alice takes minimal leave (4 days total)
├─ Coverage looks balanced overall
├─ No major issues identified

Action: Consider encouraging Alice
to use leave before expiration.

8. Understanding Leave Types

Vacation Leave

What it is: Planned time off for holidays, relaxation, or personal travel

Typical duration: 3-30 days per request

Advance notice needed: Usually 2 weeks or more

Approval criteria:

  • ✓ Team has coverage
  • ✓ No critical deadlines
  • ✓ Proper advance notice
  • ✓ Employee has balance

What to check:

Before approving vacation:
1. Is there a 2+ week notice?
2. Do we have team coverage?
3. Are there project deadlines?
4. Does employee have balance?
5. Are other team members off?

Common reasons to reject:

  • "Team understaffed - critical project deadline"
  • "Already approved 2 others for same period"
  • "Insufficient notice given"

Color code: Usually blue or light blue

Example:

Request: Jane Doe - Vacation
Dates: Dec 10-15, 2025
Duration: 5 working days
Reason: Family reunion in Europe

Your checklist:
├─ Notice given: Dec 5 (5 days notice) ✓
├─ Team size: 5 people
├─ Others off Dec 10-15: None
├─ Projects: All low priority
├─ Balance: 8 days (requesting 5) ✓
├─ Coverage: 4 people remains ✓

DECISION: APPROVE
Comment: "Team coverage adequate,
project timeline allows absence"

Sick Leave

What it is: Time off due to employee's illness or medical appointment

Typical duration: 1-5 days per request (varies by policy)

Advance notice needed: Often same-day (emergency) or next day

Approval criteria:

  • ✓ Employee has balance
  • ✓ Documentation if multiple days
  • ✓ No pattern concerns

What to check:

Before approving sick leave:
1. Is this legitimate illness/medical?
2. Medical certificate for 3+ days?
3. Any pattern (Mondays/Fridays)?
4. Frequency reasonable?
5. Does employee have balance?

Medical certificate requirements:

  • Usually required for: 3+ consecutive days
  • Exception: Some policies require day 1
  • Contains: Doctor's name, dates, diagnosis (optional)

Regarding patterns:

  • Watch for: Always Monday or Friday
  • Watch for: Always after/before holidays
  • Watch for: Clustered absences
  • If concerning: Discuss with employee
  • Document conversation

Common reasons to reject:

  • "Medical certificate required - please provide"
  • "Three absences this week - need medical verification"
  • "This is your 4th Monday off in 6 weeks"

Color code: Usually green or light green

Example:

Request: John Smith - Sick Leave
Dates: Dec 20, 2025
Duration: 1 day
Reason: Flu/cold (fever)

Your checklist:
├─ Advance notice: Same day ✓
├─ Duration: 1 day (cert not required) ✓
├─ Medical cert: Not needed
├─ Frequency: First sick day in 6 weeks ✓
├─ Balance: 5 days available ✓
├─ Pattern concern: None ✓

DECISION: APPROVE
Comment: "No concerns, standard sick leave"

Personal Leave

What it is: Time off for personal matters (family issues, appointments, etc.)

Typical duration: 1-3 days per request

Advance notice needed: Usually 1 week

Approval criteria:

  • ✓ Team has coverage
  • ✓ Reasonable reason provided
  • ✓ Employee has balance
  • ✓ Advance notice given

What to check:

Before approving personal leave:
1. Is reason legitimate?
2. Team coverage available?
3. Advance notice given?
4. Balance sufficient?
5. Frequency reasonable?

Acceptable reasons:

  • Family emergency (child, spouse, parent)
  • Dependent care issues
  • Legal appointment (court, property)
  • Moving/relocation
  • Home emergency (repair, etc.)
  • School/education related

What NOT to approve:

  • Vague: "Personal reasons" (ask for detail)
  • Frivolous: "Felt like day off" (not valid)
  • Excessive: 10+ times per year
  • Consecutive: Multiple days without reason

Common reasons to reject:

  • "Please provide reason for personal leave"
  • "Team cannot spare coverage this week"
  • "Excessive personal leave usage"

Color code: Usually yellow or orange

Example:

Request: Alice Brown - Personal Leave
Dates: Dec 5, 2025
Duration: 1 day
Reason: Family appointment (urgent)

Your checklist:
├─ Advance notice: 2 days ✓
├─ Reason: Valid (family appointment) ✓
├─ Duration: 1 day ✓
├─ Balance: 3 days available ✓
├─ Coverage: 4 team members remain ✓
├─ Frequency: 2nd personal day this year ✓

DECISION: APPROVE
Comment: "Legitimate personal need,
team coverage adequate"

Maternity/Paternity Leave

What it is: Extended leave for birth of child

Typical duration: 8-16 weeks

Advance notice needed: Usually 2-3 months

Approval criteria:

  • ✓ Advance notice provided
  • ✓ Documentation (birth certificate)
  • ✓ Follows legal requirements
  • ✓ HR has coverage plan

What to check:

Before approving maternity/paternity:
1. Is it documented (expected date)?
2. Is notice 2-3 months?
3. Any company policies?
4. Long-term coverage planned?
5. Benefits continuation verified?

Special notes:

  • Usually auto-approved (legal requirement)
  • Your role: Acknowledge and support
  • HR handles most logistics
  • Coordinate team coverage planning
  • Keep communication open

Your response:

  • "Request received and approved"
  • "Congratulations!"
  • "HR will contact for coverage planning"
  • "Let's discuss team transitions"

Color code: Often pink or special color

Example:

Request: Carol White - Maternity Leave
Dates: Jan 1 - Mar 31, 2026 (12 weeks)
Reason: Birth of child (expected Jan 5)

Your checklist:
├─ Advance notice: 6 weeks (good) ✓
├─ Duration: 12 weeks ✓
├─ Documentation: Expected date ✓
├─ Legal requirement: Yes ✓
├─ HR contact: Needed ✓

DECISION: APPROVE
Comment: "Congratulations on baby!
HR handling coverage planning.
Will schedule transition meeting."

Bereavement Leave

What it is: Time off due to death of family member

Typical duration: 3-5 days (varies by relationship)

Advance notice needed: Usually same-day (emergency)

Approval criteria:

  • ✓ Legitimate family death
  • ✓ Proper documentation (optional)
  • ✓ Reasonable duration

What to check:

Before approving bereavement:
1. Death in immediate family?
2. Reasonable duration?
3. Offering condolences?
4. Documentation available?
5. Flexibility for follow-up needs?

Relationships covered:

  • Immediate family: Parent, spouse, child
  • Extended: Sibling, grandparent
  • Other: Depends on company policy

Duration by relationship:

  • Parent/spouse/child: 5 days
  • Sibling/grandparent: 3 days
  • Aunt/uncle/cousin: 1-3 days

Your approach:

  • Be empathetic and respectful
  • Auto-approve (almost always)
  • Offer flexibility if needed
  • Don't question the loss

Color code: Often dark gray or black

Example:

Request: David Lee - Bereavement Leave
Dates: Dec 18-22, 2025 (5 days)
Reason: Death of father

Your checklist:
├─ Immediate family: Yes (father) ✓
├─ Duration: 5 days (standard) ✓
├─ Documentation: Optional
├─ Team coverage: Can arrange ✓

DECISION: APPROVE
Comment: "My sincere condolences.
Approved. Flexible on exact dates
if needed for arrangements."

Unpaid Leave

What it is: Extended time off without salary payment

Typical duration: Days to weeks (varies by policy)

Advance notice needed: Usually 2-4 weeks

Approval criteria:

  • ✓ Business impact acceptable
  • ✓ Advance notice given
  • ✓ Coverage plan exists
  • ✓ Policy allows it

What to check:

Before approving unpaid leave:
1. What's the reason?
2. Can business absorb absence?
3. Advance notice adequate?
4. Is coverage planned?
5. Payroll implications understood?

Common reasons:

  • Extended sabbatical
  • Study/education leave
  • Personal project
  • Family care (long-term)
  • Voluntary break

Approval conditions:

  • "Approved on condition: Coverage found"
  • "Approved with understanding of salary impact"
  • "Approved - 2 week notice given to HR"

Rejection reasons:

  • "Cannot spare this person for this duration"
  • "Notice too short"
  • "Business impact too significant"

Color code: Often dark or neutral

Example:

Request: Emma Thompson - Unpaid Leave
Dates: Jan 15 - Feb 28, 2026 (6 weeks)
Reason: Educational sabbatical

Your checklist:
├─ Advance notice: 4 weeks ✓
├─ Reason: Valid (education) ✓
├─ Business impact: High (specialist role)
├─ Coverage: Need to plan
├─ Payroll: 6 weeks unpaid

DECISION: CONDITIONAL APPROVAL
Comment: "Approved pending coverage plan.
Please work with HR on temporary
replacement/workload distribution.
Need plan finalized by Dec 20."

9. Leave Balance & Tracking

Understanding Leave Balance

What is leave balance?

Leave balance is the number of days an employee has available to take as time off.

Leave Balance Formula:

Annual Allocation (e.g., 20 days)
  ├─ Minus: Days already taken
  ├─ Plus/Minus: Adjustments (carrover, forfeit)
  └─ Equals: Remaining Balance

Example:
20 days (allocated)
- 12 days (already taken)
= 8 days (remaining)

Where to see balance:

  • On the leave request details page
  • In employee profile
  • On approval workflow page
  • In HR reports

Checking Balance Before Approving

Steps:

  1. Open leave request details
  2. Look for "Leave Balance" section
  3. Review:
    • Total days allocated
    • Days already used
    • Days remaining
    • Days being requested

Example:

Leave Balance Analysis:

Total Annual Vacation Days:    20 days
Days Already Used:             12 days
Remaining Balance:             8 days
Currently Requesting:          5 days
After Approval:                3 days remaining

Status: ✓ Sufficient balance

What to approve:

  • ✓ Balance sufficient for request
  • ✓ Employee has enough days
  • ✓ After approval, positive or acceptable balance

What to consider rejecting:

  • ✗ Insufficient balance (request exceeds available)
  • ✗ Would go negative (unless policy allows)
  • ✗ Last remaining days (ensure employee awareness)

Balance Concerns

Insufficient Balance Scenario:

Employee: John Smith
Requesting: 5 days vacation
Available: Only 3 days remaining

OPTIONS:
1. REJECT: Not enough days
   Comment: "Only 3 days balance remaining.
             Please request for those dates instead."

2. CONDITIONAL APPROVE: Unpaid overflow
   Comment: "Approved for 3 paid + 2 unpaid days.
             Confirm acceptance of unpaid portion."

3. CHECK POLICY: May have carry-over
   Contact HR: Can balance be adjusted?

Negative Balance Scenario:

Employee: Alice Brown
Balance: -2 days (from previous year overage)
Requesting: 3 days vacation

ACTION: Refer to HR policy
Comment: "Employee currently has negative balance
         from previous year. Approving would require
         HR adjustment. Forwarding to HR with request."

Year-End Leave Considerations

Important timing:

  • Employees often take leave end of year
  • Balance may be about to expire
  • Carry-over limits apply (varies by policy)
  • Forfeiture dates approach
  • Planning required for Q1 coverage

Your role:

  • Watch for bulk year-end requests
  • Plan team coverage carefully
  • Approve requests following policy
  • Document decisions
  • Coordinate with other team leads

10. Approval & Rejection Workflow

The Complete Approval Journey

Understand the flow:

Employee Submits Request
        ↓
[TEAM LEAD STAGE - YOUR ROLE]
├─ You receive notification
├─ Review request details
├─ Check team impact
├─ Make decision (Approve/Reject/Comment)
├─ Add reasoning
└─ Submit decision
        ↓
HR Review Stage
├─ HR receives submission
├─ HR verifies balance
├─ HR checks policies
├─ HR makes final decision
└─ HR notifies employee
        ↓
Final Status
├─ Approved by HR: Leave can proceed
├─ Rejected by HR: Leave denied
└─ Employee notified via email + system

Your Approval Responsibilities

When approving, you're confirming:

  1. ✓ Team has adequate coverage
  2. ✓ No critical project conflicts
  3. ✓ Proper notice given
  4. ✓ Reasonable request
  5. ✓ No staffing emergencies

You are NOT confirming:

  • ✗ Leave balance (HR verifies)
  • ✗ Policy compliance (HR checks)
  • ✗ Final approval (HR decides)
  • ✗ Payroll processing (Payroll handles)

When to Reject

Clear rejection reasons:

Reason Example
Coverage shortage "Only 2 people left in 5-person team"
Critical deadline "Major project launch Dec 15"
Insufficient notice "3 days notice for week-long leave"
Missing information "Medical certificate required"
Policy violation "Cannot exceed 10 consecutive days"

Don't reject for:

Bad Reason Why
"I don't want to" Personal preference (invalid)
"No specific reason" Vague, not professional
"Because I said so" Autocratic, breeds resentment
"That time is mine" Team decision, not personal

When to Seek More Information

Ask for clarification on:

  • Medical certificates (if required)
  • Coverage plans (for long absences)
  • Reasons (if vague)
  • Project impact (if unclear)
  • Backup arrangements

How to request more info:

  1. Don't reject immediately
  2. Add comment requesting information
  3. Set deadline for response
  4. Revisit request after response

Example request:

"Thank you for submitting your leave request.
Before I can approve, I need:

1. Medical certificate for 3-day absence
2. Plan for project coverage (John can handle?)
3. Handover list for pending tasks

Please provide by Dec 7 so I can finalize decision.
Thanks!"

Communicating Decisions

Approval message to employee:

APPROVED ✓

Your leave request has been approved!

Details:
- Dates: Dec 10-15, 2025
- Type: Vacation
- Duration: 5 days
- Your Manager: Approved

Next: HR will review for final approval.
You'll be notified of final status by Dec 8.

Rejection message to employee:

REJECTED ✗

Your leave request has been declined.

Request: Vacation Dec 10-15, 2025

Reason: Critical project deadline Dec 15.
Team requires full capacity this week.

Alternative: Would Dec 20-24 work instead?
Please discuss with me.

Next: You can resubmit with different dates,
or contact HR to discuss further.

11. Important Information About Approvals

Before Approving

Create your checklist:

□ Employee info verified
  - Correct person?
  - Active employee?

□ Leave details reviewed
  - Correct dates?
  - Accurate duration?

□ Balance checked
  - Sufficient days?
  - Positive balance after?

□ Team coverage analyzed
  - How many off this period?
  - Critical roles covered?
  - Minimum staffing met?

□ Project impact assessed
  - Any critical deadlines?
  - Major milestones?
  - Key deliverables?

□ Notice evaluated
  - Advance warning given?
  - Reasonable notice?

□ Documentation complete
  - All attachments?
  - Medical certs if needed?

□ Policy compliance checked
  - Follows company policy?
  - No conflicts?

After Approving

What happens:

  1. Your approval recorded in system
  2. Request forwarded to HR
  3. HR receives notification
  4. HR verifies balance
  5. HR checks company policies
  6. HR makes final decision
  7. Employee notified

Your visibility:

  • Request status changes to "Approved by TL"
  • HR can see your comments
  • Employee can see your approval
  • You can monitor status

Employee's next expectations:

  • "My manager approved!"
  • But still awaiting HR final approval
  • May receive HR's request for additional info
  • Will get final notification

Employee Impact If You Reject

What employee experiences:

  1. Rejection notification received
  2. Your reason displayed
  3. Can contact you to discuss
  4. Can resubmit new request with different dates
  5. Can appeal through HR if appropriate

For employee's planning:

  • If rejected: Needs to find alternative dates
  • Or explore other leave types
  • Or handle issue without leave (if possible)
  • May need to make arrangement changes

Professional courtesy:

  • Be specific with reasons
  • Offer to discuss alternatives
  • Show you understand difficulty
  • Help find solutions if possible

Tracking Status

Where to find request status:

  • Leave Management system
  • Your dashboard (if showing approvals)
  • Employee can also track
  • Notifications via email

Status indicators:

PENDING          → Waiting for your action
TL APPROVED      → You approved, HR reviewing
TL REJECTED      → You rejected
HR APPROVED      → Final approval, leave confirmed
HR REJECTED      → Final rejection, leave denied
CANCELLED        → Employee cancelled

12. Common Scenarios and Solutions

Scenario 1: Employee Requests Leave During Critical Period

Situation:

Jane requests 2 weeks vacation Dec 10-25 (your busiest season). Your product launch is Dec 15. Team is already stretched.

Analysis:

Project: Major launch Dec 15
Team size: 5 people
Currently off: 1 person (Dec 5-10)
Jane's request: Dec 10-25 (2 people overlap)
Coverage: Would leave only 3 people
Assessment: INSUFFICIENT COVERAGE

Your options:

Option 1: Reject with alternative

"I understand you'd like Dec 10-25 off.
Unfortunately, we have major product launch
Dec 15 and cannot spare you during this week.

I CAN approve Dec 20-25 (after launch).
Or Dec 5-10 (before launch).

Can either of these dates work instead?"

Result: Employee considers alternatives

Option 2: Partial approval

"I can approve Dec 20-25 (after launch).
But cannot approve Dec 10-15 (launch week).

Can you adjust your trip to start Dec 20?
This way you get your leave + team has coverage."

Result: Find compromise

Option 3: Reject with explanation

"Approved: NO

Reason: Critical product launch Dec 15.
Cannot spare development team during this week.
Only 3 of 5 people would remain.
Business impact: Too significant.

Alternative: Please request Dec 20-31 instead.
Or if dates fixed: Discuss with me about
unpaid leave possibility or contingency plan.

Next: Happy to discuss in person."

Result: Clear decision, door open for discussion

Scenario 2: Multiple Requests for Same Dates

Situation:

Jane, John, and Alice all request Dec 20-22 off. You only need 1 person minimum staff.

Analysis:

Requests: Dec 20-22 (3 days)
Requestors: Jane, John, Alice (all approved)
Team size: 5 people
Minimum needed: 2 people

If all 3 approved: Only 2 people work
If only 2 approved: 3 people work (acceptable)
If only 1 approved: 4 people work (comfortable)

Decision: Can approve maximum 2, reject 1

Your approach:

Option 1: First-come-first-served

Process in order received:
1. Jane (submitted Dec 5) → APPROVE
2. John (submitted Dec 6) → APPROVE
3. Alice (submitted Dec 8) → REJECT

Message to Alice:
"Dec 20-22 approved requests limit reached
(2 colleagues already approved for those dates).
Maximum coverage we can spare is 2 people.

Can you choose different dates?
Or discuss alternatives?"

Option 2: Priority-based

Evaluate by importance:
- Jane: Critical role, project lead → APPROVE
- John: Backup role, can cover → APPROVE
- Alice: Cross-trained, flexible → REJECT

Message to Alice:
"Dec 20-22 has coverage limits due to other
approved leaves. Your role is more flexible
to defer. Could you choose Dec 27-29 instead?"

Option 3: Collaborate approach

Send message to all three:
"Three concurrent requests for same dates.
Team can accommodate 2 but not all 3.

Options:
1. Two approve Dec 20-22, one takes different dates
2. Stagger: Two Dec 20-22, one Dec 25-27
3. Discuss with me to find solution

Who wants to discuss scheduling?"

Scenario 3: Excessive Sick Leave Pattern

Situation:

David took sick leave:

  • Dec 2 (Monday)
  • Dec 5 (Friday)
  • Dec 9 (Tuesday)
  • Now requesting Dec 12 (Friday)

Pattern: Always ends near weekends

Analysis:

Pattern Assessment:
├─ Frequency: 4 times in 2 weeks (high)
├─ Days: Mix of Monday/Friday (suspicious)
├─ Trend: Increasing (concerning)
└─ Documentation: Medical certs provided? (check)

Concern Level: MEDIUM TO HIGH
Action needed: Discussion required

Your approach:

For current request:

CONDITIONAL APPROVAL

"I approve your sick leave Dec 12.
However, I need to discuss the frequency
of recent absences.

Four sick days in two weeks is concerning.
Are you okay? Is there a health issue I
should know about?

Let's meet Friday afternoon to discuss.
If ongoing health concern, HR can help
with accommodations or medical leave options.

Please confirm meeting time."

Document the conversation:

Meeting with David - Dec 12, 2:00 PM

Discussion: Pattern of frequent sick leave
├─ Dec 2, 5, 9, 12 (4 days in 2 weeks)
├─ Pattern noted: Often near weekends
├─ Employee states: Recurring flu symptoms
├─ Medical verification: Provided for some days
└─ HR involvement: Recommended

Outcome:
├─ Monitor closely for next 2 weeks
├─ Require medical cert for any future 3+ day absences
├─ HR to discuss health accommodations
└─ Follow-up conversation in 2 weeks

Don't assume:

  • ✗ Don't assume employee is faking
  • ✗ Don't deny leave without evidence
  • ✗ Don't threaten discipline
  • ✓ Do approach with concern
  • ✓ Do request documentation
  • ✓ Do involve HR if pattern continues
  • ✓ Do follow company policy

Scenario 4: Employee Requests Leave During Year-End

Situation:

Dec 20-Jan 10 vacation requested (20+ days). Multiple team members requesting similar timeframe. It's already Dec 8.

Analysis:

Request: Dec 20 - Jan 10 (20+ days)
Timing: Submitted Dec 8 (12 days notice)
Other requests: Multiple for Dec 20-Jan 5
Team size: 5 people
Expected coverage: Very thin

Business closure: Check if company closes
Policy limits: Check max consecutive days
Approval deadline: HR needs 5 days

Assessment: COMPLEX, requires care

Your decision framework:

1. Check company policy
   ├─ Does company close Dec 25-Jan 1? (affects coverage)
   ├─ Max consecutive days allowed? (policy limit)
   └─ Approval deadlines? (time to process)

2. Assess business impact
   ├─ Can team operate with 1-2 people?
   ├─ Any ongoing support needed?
   └─ Any urgent projects?

3. Evaluate fairness
   ├─ Have others already taken year-end?
   ├─ Is this person's turn?
   └─ Can multiple take this long?

4. Make decision
   ├─ APPROVE: With coverage plan
   ├─ PARTIAL APPROVE: Modified dates
   ├─ CONDITIONAL APPROVE: On coverage setup
   └─ REJECT: With clear alternative

Approval with conditions:

"CONDITIONALLY APPROVED

Your request for Dec 20 - Jan 10 is approved
with the following conditions:

1. Coverage verification:
   Please confirm who will handle your critical tasks
   (Project X, Client Y support, etc.)

2. Handover documentation:
   Prepare transition document by Dec 18

3. Emergency contact:
   Establish contact person for critical issues

4. HR processing:
   Must be approved by HR by Dec 15

If these conditions can be met by deadlines,
your vacation is confirmed. Otherwise,
we may need to adjust dates.

Let me know your plan by tomorrow. Thanks!"

Scenario 5: Retroactive Leave Request

Situation:

Employee submitted leave request for Dec 5-8 (already happened, it's now Dec 10).

Analysis:

Request: Dec 5-8 (already passed)
Submission date: Dec 10 (5 days after)
Reason: Personal emergency
Documentation: None yet

Question: Why submit now?
Possible: Emergency that required time off
Problem: Difficult to verify now
Policy: Usually not allowed

Assessment: REQUIRES CAREFUL REVIEW

Your approach:

Step 1: Understand why

Contact employee:
"I see you submitted leave for Dec 5-8
(dates that already occurred).

Can you explain:
1. Why the leave is being submitted now?
2. What was the emergency/situation?
3. Do you have any documentation?
4. Why wasn't notice given beforehand?

Please provide details ASAP."

Step 2: Evaluate legitimacy

Scenarios:

LEGITIMATE reasons:
├─ Family emergency (accident, hospitalization)
├─ Personal health crisis (hospitalized)
├─ Major family issue (death in family)
└─ System/HR error (request "lost")

QUESTIONABLE reasons:
├─ "Forgot to submit"
├─ "Thought it would be denied"
├─ "Didn't think it mattered"
├─ Vague/unclear explanations

ILLEGITIMATE:
├─ "Just wanted time off"
├─ "Wanted long weekend"
├─ "Didn't want to ask upfront"

Step 3: Make decision

IF legitimate emergency:
CONDITIONAL APPROVAL

"Approved for retroactive Dec 5-8 given
the family emergency circumstances.

Please:
1. Provide documentation (hospital, death cert, etc.)
2. Ensure HR receives this by Friday
3. Understand no pay adjustment for past days
   (verify with HR/Payroll)

Contact HR immediately to process."

---

IF questionable:
DISCUSS FIRST

"Before I can approve, we need to discuss
the circumstances. This request came 5 days
after the dates, which is unusual.

Let's meet today so I understand what happened.
We'll determine next steps together.

Can you come to my office at 2pm?"

---

IF clearly inappropriate:
REJECT

"I cannot approve retroactive leave for
Dec 5-8 without advance notice or
emergency circumstances.

Company policy requires leave requests
submitted before or immediately after
unexpected emergencies.

This appears to be submitted well after
the fact. This request is REJECTED.

If there are circumstances I'm unaware of,
please discuss with me and HR."

13. Tips for Effective Leave Management

Tip 1: Respond Promptly

Why it matters:

  • Employees are planning around your response
  • Delays cause stress and anxiety
  • Prompt decisions build trust
  • Slow responses overwhelm inbox

Best practice:

  • Review pending requests daily
  • Approve or reject within 24-48 hours
  • Don't let requests pile up
  • Set calendar reminder if needed

Example routine:

Morning: Check for new leave requests
Afternoon: Review and approve/reject
End of day: Ensure all pending resolved

This: Takes 15-20 minutes daily
Result: Employees know status quickly

Tip 2: Be Consistent

Why it matters:

  • Employees notice preferential treatment
  • Inconsistency breeds resentment
  • Creates perception of favoritism
  • Can invite complaints or challenges

Best practice:

  • Apply same criteria to all requests
  • Don't approve casual friends, deny others
  • Document your reasoning
  • Reference past similar decisions

Example consistency:

Policy: No more than 2 people off same week

Request 1 (Jane): Dec 10-15 (2 people already off)
Decision: REJECT (would be 3 people)

Request 2 (John): Jan 5-10 (1 person off)
Decision: APPROVE (only 2 people off)

Request 3 (Alice): Jan 5-10 (1 person off)
Decision: APPROVE (only 2 people off)
But reject if would exceed 2 person limit

Consistency: Applied same 2-person rule to all

Tip 3: Provide Clear Reasons

Why it matters:

  • Employee understands your decision
  • Removes confusion about rejection
  • Helps them plan alternatives
  • Maintains professional relationship

Bad reasons:

❌ "No" (no explanation)
❌ "Denied" (not helpful)
❌ "I said so" (autocratic)
❌ Vague: "Timing doesn't work"

Good reasons:

✓ "Approved - team coverage confirmed for Dec 10-15"

✓ "Rejected - project deadline Dec 12 requires
   your participation. Would Dec 20-24 work?"

✓ "Need more info - medical cert required
   for 3-day absence. Please provide by Friday."

✓ "Conditional approval - once you confirm
   backup for Project X, this is approved."

Tip 4: Check Leave Balance First

Why it matters:

  • Prevents approval of impossible requests
  • Shows professionalism
  • Avoids HR having to reject after you approve
  • Protects employee from surprise

Process:

  1. Always verify balance BEFORE approving
  2. Show employee the balance
  3. Warn if nearly exhausted
  4. Discuss options if insufficient

Example check:

Jane requests 5 days vacation
You check balance: 8 days remaining

Message: "Approved your 5-day vacation.
Note that you'll have 3 days remaining
for rest of year. Plan end-of-year coverage."

Result: Employee informed and grateful

Tip 5: Plan Coverage

Why it matters:

  • Prevents team overload
  • Ensures project continuity
  • Demonstrates you care about team
  • Makes leaves actually work

Coverage planning:

Before approving, ask:
1. Who will handle their work?
2. What are critical tasks?
3. Who has capacity to cover?
4. Need temporary backfill?
5. Can workload be deferred?

Make approval conditional:
"Approved pending coverage plan"

Example coverage plan:

Jane: Dec 10-15 vacation
Critical responsibilities:
├─ Project X: John will cover
├─ Client Y support: Alice to handle
├─ Weekly reports: Manager will do
└─ Scheduled meetings: Postpone or delegate

Approval: CONDITIONAL on plan confirmation
Message: "Please confirm John and Alice
can cover before I finalize approval."

Tip 6: Keep Documentation

Why it matters:

  • Legal protection for you and company
  • Audit trail for HR/compliance
  • Reference for future decisions
  • Protects against disputes

What to document:

  • Your approval/rejection decision
  • Reasons given
  • Coverage plans confirmed
  • Any discussions or modifications
  • Attachments or evidence reviewed

How system helps:

  • Comments field (document your reasoning)
  • Decision recorded automatically
  • Timestamp of approval
  • Email notifications preserve trail

Personal records:

Keep a brief log:
Date | Employee | Request | Decision | Reason
Dec 5 | Jane Doe | Dec 10-15 | Approved | Coverage OK
Dec 5 | John Smith | Dec 20 | Approved | Standard sick
Dec 8 | Alice B | Dec 10-15 | Rejected | Too many off

Time investment: 2 minutes per request
Value: Protection if questioned later

Tip 7: Communicate Changes

Why it matters:

  • Keeps everyone informed
  • Prevents confusion
  • Shows respect for team
  • Enables proper planning

When to communicate:

  • Approving significant time off
  • Changes to plans affecting team
  • Coverage adjustments needed
  • Project timeline shifts

Example communication:

Team Announcement - Approved Leaves

Hi Team,

Wanted to give you visibility into approved
leaves for December:

Dec 5-10: Carol White (vacation)
Dec 10-15: Jane Doe (vacation)
Dec 20-22: John Smith & Dave Lee (approved)

Coverage Plan:
- Carol's work: Deferred until return
- Jane's work: John covering, Alice backup
- Dec 20-22: Only 3 core team remaining

Please plan accordingly. Happy to discuss
any concerns or coverage questions.

Thanks,
John (Team Lead)

Tip 8: Monitor Trends

Why it matters:

  • Identifies issues early
  • Catches problematic patterns
  • Enables preventive management
  • Shows data-driven leadership

What to monitor:

Trends to track:
├─ Frequency per person
├─ Clustering (same person, different times)
├─ Timing patterns (Mondays, Fridays)
├─ Seasonality (peak times)
├─ Fairness distribution
└─ Comparison to prior periods

Example monitoring:

Monthly leave summary:

Name        Nov   Dec   Trend      Notes
Jane        3     5     ↑ UP       Increased
John        2     1     ↓ DOWN     Using less
Alice       0     2     ↑ NEW      Taking after none
Dave        6     4     → SAME     Consistent

Observations:
- Jane using more frequently (check if OK)
- Alice starting to use (good - was unused)
- Overall usage reasonable

Action: Nothing urgent, continue monitoring

Tip 9: Be Flexible When Possible

Why it matters:

  • Improves employee satisfaction
  • Shows you value them
  • Increases morale and loyalty
  • Demonstrates trust in team

Where to be flexible:

  • Minor date shifts: "Could you move 1-2 days?"
  • Partial approvals: "Could you take 3/5 days?"
  • Alternative options: "Would this week work instead?"
  • Emergency modifications: "Let's adjust as needed"

Where to be firm:

  • Critical project deadlines (non-negotiable)
  • Coverage minimums (required)
  • Policy violations (company rules)
  • Unfair patterns (consistency required)

Flexible communication:

SCENARIO: Employee needs specific dates but
tight coverage for that period

FLEXIBLE approach:
"I understand Dec 10-15 is important for you.
Let me check if we can make it work with some
creative coverage. Can you give me till Friday
to confirm? This might require John to shift
some deliverables, but let me explore it."

Result: Employee feels heard, appreciated

Tip 10: Involve HR Early on Complex Cases

When to escalate to HR:

  • Retroactive leave requests
  • Leave balance questions
  • Policy interpretation
  • Unusual circumstances
  • Potential# Team Lead — Leave Management User Guide

Version: 1.0
Last updated: December 10, 2025

Table of Contents


1. Welcome to Leave Management

Welcome to the Team Lead Leave Management System! This guide will help you understand how to review, approve, and manage leave requests from your team members.

What is this system?

The Leave Management system is where you review leave requests submitted by your team members. As a team lead, you play a crucial role in the leave approval workflow:

  • You receive leave requests from your team
  • You review team member availability and workload
  • You approve or reject requests based on team needs
  • You document your decisions
  • You communicate approval status to your team members

Your role in the approval process:

Employee Submits Leave Request
        ↓
[YOU - Team Lead Reviews]
        ↓
Approve / Reject / Request More Info
        ↓
Request sent to HR for final approval
        ↓
Employee notified of final status

2. What You Can Do

As a Team Lead, you can:

View all leave requests from your team members ✅ Review detailed information about each request ✅ Approve leave requests you support ✅ Reject leave requests that create team issues ✅ Add comments explaining your decision ✅ Check employee leave balance before approving ✅ Filter requests by status, date, or employee ✅ Search for specific team member requests ✅ Export leave data for your records ✅ Track leave patterns and trends

What you cannot do:

❌ Cannot change HR leave policies ❌ Cannot modify approved leave dates after HR approval ❌ Cannot override HR final decisions ❌ Cannot access other team leads' team requests ❌ Cannot delete leave requests (only cancel as employee) ❌ Cannot adjust employee leave balance manually


3. How to Access Leave Management

Method 1: From the Main Menu

  1. Log in to the DTR System
  2. Click on TL Dashboard in the main navigation
  3. Click on Leave Management or Leave Requests
  4. You're now viewing the Leave Management system

Method 2: Direct URL

URL: /tl/leave-request

Method 3: From Dashboard

  1. Log in to DTR System
  2. Click on TL Dashboard
  3. Look for "Pending Leave Requests" card
  4. Click "View All" or "View More"
  5. Redirected to Leave Management system

4. Understanding the Leave Request List

Page Overview

The Leave Request List is your main page showing all leave requests from your team members in a table format.

Page Layout:

┌─────────────────────────────────────────────────────────────┐
│ FILTER & SEARCH SECTION (Top)                               │
│ Date Range | Status | Employee | Leave Type | [Filter Btn]  │
├─────────────────────────────────────────────────────────────┤
│ LEAVE REQUEST TABLE (Main Content)                           │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ ID | Employee | Type | Dates | Duration | Status | ... │ │
│ ├─────────────────────────────────────────────────────────┤ │
│ │ Row 1: Jane Doe | Vacation | Dec 10-15 | 5 days | Pend...│ │
│ │ Row 2: John Smith | Sick | Dec 20 | 1 day | Pending     │ │
│ │ Row 3: Alice Brown | Personal | Dec 5 | 1 day | Approved│ │
│ └─────────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ PAGINATION (Bottom)                                          │
│ Showing 1-10 of 25 requests | [< Previous] [1] [2] [Next >] │
└─────────────────────────────────────────────────────────────┘

Top Section: Filters & Quick Actions

Filter Controls:

  • From Date (calendar input):

    • Start date for filtering requests
    • Default: First day of current month
    • Use to find requests in specific period
    • Format: YYYY-MM-DD or use date picker
  • To Date (calendar input):

    • End date for filtering requests
    • Default: Current date
    • Format: YYYY-MM-DD or use date picker
    • Validation: Must be after From Date
  • Status Filter (dropdown):

    • All (default) — Show all requests
    • Pending — Waiting for your approval
    • Approved — You approved these
    • Rejected — You rejected these
    • HR Approved — HR approved (final status)
    • HR Rejected — HR rejected (final status)
  • Employee Filter (dropdown/searchable):

    • All Employees (default)
    • List of your team members
    • Search by name if long list
    • Searchable: Type to find employee
  • Leave Type Filter (dropdown):

    • All Types (default)
    • Vacation
    • Sick Leave
    • Personal Leave
    • Maternity/Paternity
    • Bereavement Leave
    • Unpaid Leave
    • Other

Action Buttons:

  • Filter Button:

    • Applies all selected filters
    • Updates table with matching requests
    • Shows filtered count: "Showing 5 of 25 results"
  • Clear Filters Button:

    • Resets all filters to default
    • Shows all requests again
    • Clears date range back to current month
  • Export Button (optional):

    • Downloads leave data
    • CSV or Excel format
    • Uses current filters
    • Includes selected columns
  • Refresh Button:

    • Manually refresh data
    • Updates with latest requests
    • Shows any new submissions

Leave Request Table

Columns Displayed:

Column What It Shows Example
Request ID Unique request number LR-001234
Employee Team member name + ID + avatar Jane Doe (EMP-001)
Leave Type Type of leave requested Vacation, Sick Leave
Date Range Start date - end date Dec 10 - Dec 15, 2025
Duration Number of days requested 5 days
Submitted When request was submitted Dec 5, 2025 at 2:30 PM
Status Current approval status Pending, Approved, Rejected
Reason Why employee needs leave Family vacation, Doctor appointment
Actions View details or edit View, Edit, Delete

Status Badges (Color-Coded):

[Yellow Badge]  PENDING      — Waiting for your approval
[Green Badge]   APPROVED     — You approved this
[Red Badge]     REJECTED     — You rejected this
[Blue Badge]    HR APPROVED  — HR approved (final)
[Dark Red]      HR REJECTED  — HR rejected (final)
[Gray Badge]    CANCELLED    — Employee cancelled

Table Features:

  • Pagination: 10-25 requests per page (configurable)
  • Sorting: Click column header to sort (optional)
  • Row styling:
    • Pending: Light yellow background
    • Approved: Light green background
    • Rejected: Light red/pink background
    • HR Approved: Darker green background
    • Hover effect: Highlight row for clarity
  • Clickable row: Click row to view details
  • Inline actions: Edit and view buttons on right side

Empty State

If no requests match your filters:

No leave requests found

Try:
- Clearing filters
- Changing date range
- Selecting different status
- Searching different employee

5. Viewing Detailed Leave Requests

How to Access Details Page

Steps:

  1. From the Leave Request List
  2. Find the request you want to review
  3. Click the eye icon or "View Details" button
  4. Or click anywhere on the row
  5. Details page opens with full information

Details Page Layout

The details page shows complete information about a single leave request.

Page Structure:

┌──────────────────────────────────────────┐
│ EMPLOYEE INFO (Top Card)                 │
│ [Avatar] Jane Doe (EMP-001)              │
│ Department: App Tech | Position: Senior Dev
│ Manager: John Smith | Email: jane@...   │
├──────────────────────────────────────────┤
│ LEAVE REQUEST DETAILS (Middle Section)   │
│ Leave Type: Vacation                     │
│ Dates: Dec 10 - Dec 15, 2025             │
│ Duration: 5 working days                 │
│ Reason: Family vacation                  │
│ Status: Pending                          │
│ Submitted: Dec 5, 2025 at 2:30 PM       │
├──────────────────────────────────────────┤
│ LEAVE BALANCE (If Available)             │
│ Total Days: 20 | Used: 12 | Remaining: 8│
│ Requesting: 5 days ✓ (Sufficient)        │
├──────────────────────────────────────────┤
│ ATTACHMENTS (If Available)               │
│ - doctor_note.pdf                        │
│ - medical_certificate.pdf                │
├──────────────────────────────────────────┤
│ COMMENTS & HISTORY                       │
│ Previous comments on this request        │
├──────────────────────────────────────────┤
│ YOUR DECISION (Bottom Section)           │
│ [Approve Button] [Reject Button]         │
│ Comment: [Your decision reason]          │
│ [Submit Button]                          │
└──────────────────────────────────────────┘

Section 1: Employee Information

Displays:

  • Employee's profile picture
  • Full name
  • Employee ID
  • Department
  • Position/Job Title
  • Manager name
  • Contact email
  • Hire date (optional)

Purpose: Confirm you're reviewing the correct employee

Example:

┌─────────────────┐
│  [Avatar] Jane  │
│  Jane Doe       │
│  EMP-001        │
│  App Tech       │
│  Senior Dev     │
│  Manager: John  │
└─────────────────┘

Section 2: Leave Request Details

Displays:

  • Leave Type (Vacation, Sick, Personal, etc.)
  • Start Date
  • End Date
  • Duration (number of days)
  • Reason for leave
  • Submission date and time
  • Current status

Example:

Leave Type:        Vacation
Start Date:        December 10, 2025
End Date:          December 15, 2025
Duration:          5 working days
Reason:            Family vacation in Europe
Status:            Pending
Submitted:         December 5, 2025 at 2:30 PM

Section 3: Leave Balance

If Available, Shows:

  • Total leave days allocated
  • Days already used this year
  • Remaining balance
  • Days being requested
  • Sufficient/insufficient indicator

Example:

Leave Balance Analysis:
├─ Total Annual Leave:  20 days
├─ Already Used:        12 days
├─ Remaining:           8 days
├─ Requesting:          5 days
└─ Status:              ✓ Sufficient balance

What to check:

  • Does employee have enough balance?
  • Will approval bring them below zero?
  • Are there concerns about balance?

Section 4: Attachments

If Employee Provided:

  • Medical certificates (for sick leave)
  • Doctor's notes
  • Travel itineraries
  • Supporting documents
  • Evidence of emergency

How to view:

  1. Click on attachment name
  2. Download or preview the file
  3. Review for verification

Why it matters:

  • Verify medical conditions for sick leave
  • Confirm emergency for bereavement leave
  • Check documentation for extended leave

Section 5: Comments & Discussion History

Shows:

  • Previous comments on this request
  • Who made comments (employee, manager, HR)
  • Timestamps of each comment
  • Full comment text

Example:

Manager (John Smith) - Dec 5, 2025 at 3:00 PM:
"Project deadline is Dec 20, so this timing works."

HR Specialist (Alice Brown) - Dec 5, 2025 at 3:15 PM:
"Checking leave balance..."

Purpose: See discussion context before making decision

Section 6: Your Decision Section

For Approval:

  1. Click "Approve" button
  2. (Optional) Add comment explaining approval
  3. Comment examples:
    • "Team coverage is adequate"
    • "Project timeline allows this"
    • "Employee has sufficient balance"
  4. Click "Submit" or "Confirm"
  5. System sends approval to HR and employee

For Rejection:

  1. Click "Reject" button
  2. Required: Add reason for rejection
  3. Reason examples:
    • "Critical project deadline during this period"
    • "Insufficient team coverage"
    • "Please provide medical certificate"
  4. (Optional) Add additional comments
  5. Click "Submit" or "Confirm"
  6. System notifies employee with your reason

Reasons for Common Rejections:

  • Project conflict: "We have critical deliverable Dec 15"
  • Coverage issue: "Need 2 more team members"
  • Documentation missing: "Medical certificate required"
  • Timing conflict: "Other team members already off then"
  • Insufficient balance: "Not enough leave days available"

6. Filtering and Searching

Quick Filters

By Status:

Filter: Status = "Pending"
└─ Shows requests waiting for YOUR approval
   Action needed: Review and decide

Filter: Status = "Approved" (by you)
└─ Shows requests you approved
   Next step: Sent to HR for review

Filter: Status = "Rejected" (by you)
└─ Shows requests you rejected
   Employee notified of your decision

Filter: Status = "HR Approved"
└─ Shows final approvals (HR approved)
   Status: Final, no more action needed

Filter: Status = "HR Rejected"
└─ Shows final rejections (HR rejected)
   Status: Final decision made by HR

By Employee:

  1. Click Employee dropdown
  2. Select specific team member
  3. Shows all their requests (all statuses)
  4. Use to review one person's leave history

By Date Range:

  1. Set From Date (start of period)
  2. Set To Date (end of period)
  3. Shows requests within that period
  4. Use to review specific months or quarters

By Leave Type:

  1. Click Leave Type dropdown
  2. Select type (Vacation, Sick, etc.)
  3. Shows only that type of leave
  4. Use to analyze trends by type

Combining Multiple Filters

Example Scenario: "Show all pending vacation requests from Jane in December"

Steps:

  1. Employee: Select "Jane Doe"
  2. Leave Type: Select "Vacation"
  3. Status: Select "Pending"
  4. From Date: December 1, 2025
  5. To Date: December 31, 2025
  6. Click "Filter"
  7. Table shows only matching requests

Clear All Filters

To reset all filters:

  1. Click "Clear Filters" button (if visible)
  2. Or manually reset each field
  3. Table returns to showing all requests

7. Common Tasks & Step-by-Step Guides

Task 1: Review Your Team's Pending Leave Requests

Objective: See all requests waiting for your approval

Time needed: 5-10 minutes

Steps:

  1. Navigate to Leave Management page
  2. Status filter: Select "Pending"
  3. Employee filter: Select "All Employees" (shows your team only)
  4. Click "Filter"
  5. Table shows pending requests from your team
  6. Review list:
    • How many are pending?
    • What are the dates?
    • Any conflicts?

Example:

Results: 3 pending leave requests
├─ Jane Doe: Vacation Dec 10-15 (5 days)
├─ John Smith: Sick Leave Dec 20 (1 day)
└─ Alice Brown: Personal Dec 5 (1 day)

Next: Click each one to review in detail


Task 2: Approve a Leave Request

Objective: Approve an employee's leave request

Time needed: 3-5 minutes per request

When to approve:

  • ✓ Team has sufficient coverage
  • ✓ No critical project deadline
  • ✓ Employee has leave balance
  • ✓ Proper advance notice given
  • ✓ Documentation complete

Steps:

  1. Find the leave request in the list
  2. Click "View Details" or row
  3. Details page opens
  4. Review all information:
    • Employee name and role
    • Leave type and dates
    • Duration and reason
    • Employee's leave balance
    • Any attachments
  5. Check team impact:
    • Will team have enough coverage?
    • Any critical deadlines?
    • Are other team members off?
  6. If everything looks good:
    • Scroll to bottom
    • Click "Approve" button
  7. (Optional) Add comment:
    • Example: "Team coverage confirmed"
    • Example: "Project timeline allows absence"
    • Example: "Balance verified - sufficient"
  8. Click "Submit" or "Confirm"
  9. Success message appears
  10. Employee and HR notified

Confirmation Message:

✓ Approval submitted successfully

Jane Doe's vacation request (Dec 10-15)
has been APPROVED.

Request sent to HR for final review.
Employee will be notified.

Task 3: Reject a Leave Request

Objective: Decline a leave request with clear reason

Time needed: 3-5 minutes per request

When to reject:

  • ✗ Team would be understaffed
  • ✗ Critical project deadline during dates
  • ✗ Employee has insufficient balance
  • ✗ Missing required documentation
  • ✗ Leave would impact critical operations

Steps:

  1. Find the leave request in the list
  2. Click "View Details" or row
  3. Details page opens
  4. Review all information
  5. If you need to reject:
    • Scroll to bottom
    • Click "Reject" button
  6. Required: Add reason
    • Be specific and professional
    • Avoid vague reasons
    • Explain business impact
  7. Reason examples:
    • "Critical project deadline Dec 12. Team cannot spare developer now. Suggest alternative dates Dec 20-24."
    • "Need 50% team presence minimum. Two others already approved for this period. Please request different dates."
    • "Medical certificate required for 3+ day sick leave. Please provide documentation."
    • "Insufficient leave balance (5 days requested, only 3 remaining)."
  8. (Optional) Add additional comments
  9. Click "Submit" or "Confirm"
  10. Success message appears
  11. Employee notified with your reason

Rejection Message Sent to Employee:

Your leave request has been REJECTED

Request: Vacation - Dec 10-15, 2025
Reason: Critical project deadline Dec 12.
        Team cannot spare developer now.
        Suggest alternative dates Dec 20-24.

Please contact your manager (John Smith)
to discuss alternative dates.

Employee next steps:

  • Can contact you to discuss alternatives
  • Can resubmit with different dates
  • Can appeal through HR if needed

Task 4: Find a Specific Employee's Request

Objective: Quickly locate one person's leave request

Time needed: 1-2 minutes

Steps:

  1. Open Leave Management page
  2. Employee filter: Type/select employee name
  3. (Optional) Add status filter if needed
  4. Click "Filter"
  5. Table shows only that employee's requests
  6. Review their leave history
  7. Click to view specific request details

Example:

"Find all of Jane Doe's requests"

1. Employee filter: Select "Jane Doe"
2. Click "Filter"
3. Shows: 5 total requests
   - Dec 10-15: Vacation (Approved)
   - Dec 20: Sick Leave (Pending - your approval needed)
   - Jan 5-10: Vacation (Pending - your approval needed)
   - Feb 14: Personal (Rejected by you)
   - Mar 1-5: Vacation (Pending)
4. Click on Dec 20 request to review sick leave

Task 5: Check Team Coverage for Specific Dates

Objective: See who's off during a period to assess coverage

Time needed: 5-10 minutes

Steps:

  1. Open Leave Management page
  2. From Date: Set to period start
  3. To Date: Set to period end
  4. Status: Select "Approved" or "Pending"
  5. Click "Filter"
  6. Review who's off during this period
  7. Assess team coverage:
    • How many team members off?
    • What roles will be missing?
    • Can remaining team handle workload?

Example:

"Check coverage for December 10-15"

From: Dec 10, 2025
To: Dec 15, 2025
Status: Approved (already approved leaves)

Results: 2 team members off
├─ Jane Doe: Dec 10-15 (Developer) - APPROVED
└─ John Smith: Dec 12-14 (QA) - APPROVED

Coverage Impact:
├─ 2 of 5 team members off (40%)
├─ Missing: 1 Developer, 1 QA
├─ Remaining: 1 Dev, 1 QA, 1 Manager
└─ Assessment: Tight but manageable with priority shift

Decision for Alice Brown's request (Dec 10-15):
REJECT - Cannot afford 3rd person off during this week

Task 6: Respond to a Request Needing More Info

Objective: Ask for additional information before deciding

Steps:

  1. View the request details
  2. Identify what's missing:
    • Medical certificate for sick leave
    • Project justification
    • Backup plan details
  3. Add comment requesting information:
    • "Please provide medical certificate for 3-day leave"
    • "Can you explain how project will be covered?"
  4. Click "Submit" (leave status as Pending)
  5. Employee receives notification with your request
  6. Employee adds information/comment
  7. Return to review when ready

Note: Different systems handle this differently:

  • Some allow requesting info without approving/rejecting
  • Others require you to reject and resubmit workflow
  • Check your system's specific workflow

Task 7: Export Team Leave Data

Objective: Download leave requests for records or sharing

Time needed: 2-3 minutes

Steps:

  1. Set filters for data you want:
    • Date range (e.g., Dec 2025)
    • Status (All, Pending, Approved, etc.)
    • Employee (All or specific)
  2. Click "Export" button
  3. Choose format:
    • CSV (for spreadsheets)
    • Excel (.xlsx) (formatted)
    • PDF (for printing/sharing)
  4. File downloads to your computer
  5. Open file to verify data
  6. Print or share as needed

What's included:

  • Request ID
  • Employee name and ID
  • Leave type
  • Date range
  • Duration
  • Status
  • Your approval/rejection
  • Comments

Use cases:

  • Share with manager for visibility
  • Keep records for compliance
  • Generate monthly reports
  • Submit to HR for processing
  • Maintain team leave calendar

Task 8: Monitor Leave Trends

Objective: Identify patterns in team's leave usage

Time needed: 10-15 minutes

Steps:

  1. Set date range (full quarter or year)
  2. Status: "Approved" (actual leaves taken)
  3. Filter without selecting specific employee
  4. Review all approved requests
  5. Look for patterns:
    • Who takes most leave?
    • When is peak leave period?
    • Any suspicious patterns?
  6. Analyze:
    • Is distribution fair?
    • Any coverage gaps?
    • Any employees not taking leave?

Example Analysis:

Q4 2025 Leave Analysis:

Month   Requests   Peak Days    Pattern
Oct     3 requests Oct 10-20    Mid-month spike
Nov     2 requests Nov 1-5      Post-holiday
Dec     5 requests Dec 20-31    Year-end spike

Observations:
├─ Jane takes leave spread throughout
├─ John clusters all at year-end
├─ Alice takes minimal leave (4 days total)
├─ Coverage looks balanced overall
├─ No major issues identified

Action: Consider encouraging Alice
to use leave before expiration.

8. Understanding Leave Types

Vacation Leave

What it is: Planned time off for holidays, relaxation, or personal travel

Typical duration: 3-30 days per request

Advance notice needed: Usually 2 weeks or more

Approval criteria:

  • ✓ Team has coverage
  • ✓ No critical deadlines
  • ✓ Proper advance notice
  • ✓ Employee has balance

What to check:

Before approving vacation:
1. Is there a 2+ week notice?
2. Do we have team coverage?
3. Are there project deadlines?
4. Does employee have balance?
5. Are other team members off?

Common reasons to reject:

  • "Team understaffed - critical project deadline"
  • "Already approved 2 others for same period"
  • "Insufficient notice given"

Color code: Usually blue or light blue

Example:

Request: Jane Doe - Vacation
Dates: Dec 10-15, 2025
Duration: 5 working days
Reason: Family reunion in Europe

Your checklist:
├─ Notice given: Dec 5 (5 days notice) ✓
├─ Team size: 5 people
├─ Others off Dec 10-15: None
├─ Projects: All low priority
├─ Balance: 8 days (requesting 5) ✓
├─ Coverage: 4 people remains ✓

DECISION: APPROVE
Comment: "Team coverage adequate,
project timeline allows absence"

Sick Leave

What it is: Time off due to employee's illness or medical appointment

Typical duration: 1-5 days per request (varies by policy)

Advance notice needed: Often same-day (emergency) or next day

Approval criteria:

  • ✓ Employee has balance
  • ✓ Documentation if multiple days
  • ✓ No pattern concerns

What to check:

Before approving sick leave:
1. Is this legitimate illness/medical?
2. Medical certificate for 3+ days?
3. Any pattern (Mondays/Fridays)?
4. Frequency reasonable?
5. Does employee have balance?

Medical certificate requirements:

  • Usually required for: 3+ consecutive days
  • Exception: Some policies require day 1
  • Contains: Doctor's name, dates, diagnosis (optional)

Regarding patterns:

  • Watch for: Always Monday or Friday
  • Watch for: Always after/before holidays
  • Watch for: Clustered absences
  • If concerning: Discuss with employee
  • Document conversation

Common reasons to reject:

  • "Medical certificate required - please provide"
  • "Three absences this week - need medical verification"
  • "This is your 4th Monday off in 6 weeks"

Color code: Usually green or light green

Example:

Request: John Smith - Sick Leave
Dates: Dec 20, 2025
Duration: 1 day
Reason: Flu/cold (fever)

Your checklist:
├─ Advance notice: Same day ✓
├─ Duration: 1 day (cert not required) ✓
├─ Medical cert: Not needed
├─ Frequency: First sick day in 6 weeks ✓
├─ Balance: 5 days available ✓
├─ Pattern concern: None ✓

DECISION: APPROVE
Comment: "No concerns, standard sick leave"

Personal Leave

What it is: Time off for personal matters (family issues, appointments, etc.)

Typical duration: 1-3 days per request

Advance notice needed: Usually 1 week

Approval criteria:

  • ✓ Team has coverage
  • ✓ Reasonable reason provided
  • ✓ Employee has balance
  • ✓ Advance notice given

What to check:

Before approving personal leave:
1. Is reason legitimate?
2. Team coverage available?
3. Advance notice given?
4. Balance sufficient?
5. Frequency reasonable?

Acceptable reasons:

  • Family emergency (child, spouse, parent)
  • Dependent care issues
  • Legal appointment (court, property)
  • Moving/relocation
  • Home emergency (repair, etc.)
  • School/education related

What NOT to approve:

  • Vague: "Personal reasons" (ask for detail)
  • Frivolous: "Felt like day off" (not valid)
  • Excessive: 10+ times per year
  • Consecutive: Multiple days without reason

Common reasons to reject:

  • "Please provide reason for personal leave"
  • "Team cannot spare coverage this week"
  • "Excessive personal leave usage"

Color code: Usually yellow or orange

Example:

Request: Alice Brown - Personal Leave
Dates: Dec 5, 2025
Duration: 1 day
Reason: Family appointment (urgent)

Your checklist:
├─ Advance notice: 2 days ✓
├─ Reason: Valid (family appointment) ✓
├─ Duration: 1 day ✓
├─ Balance: 3 days available ✓
├─ Coverage: 4 team members remain ✓
├─ Frequency: 2nd personal day this year ✓

DECISION: APPROVE
Comment: "Legitimate personal need,
team coverage adequate"

Maternity/Paternity Leave

What it is: Extended leave for birth of child

Typical duration: 8-16 weeks

Advance notice needed: Usually 2-3 months

Approval criteria:

  • ✓ Advance notice provided
  • ✓ Documentation (birth certificate)
  • ✓ Follows legal requirements
  • ✓ HR has coverage plan

What to check:

Before approving maternity/paternity:
1. Is it documented (expected date)?
2. Is notice 2-3 months?
3. Any company policies?
4. Long-term coverage planned?
5. Benefits continuation verified?

Special notes:

  • Usually auto-approved (legal requirement)
  • Your role: Acknowledge and support
  • HR handles most logistics
  • Coordinate team coverage planning
  • Keep communication open

Your response:

  • "Request received and approved"
  • "Congratulations!"
  • "HR will contact for coverage planning"
  • "Let's discuss team transitions"

Color code: Often pink or special color

Example:

Request: Carol White - Maternity Leave
Dates: Jan 1 - Mar 31, 2026 (12 weeks)
Reason: Birth of child (expected Jan 5)

Your checklist:
├─ Advance notice: 6 weeks (good) ✓
├─ Duration: 12 weeks ✓
├─ Documentation: Expected date ✓
├─ Legal requirement: Yes ✓
├─ HR contact: Needed ✓

DECISION: APPROVE
Comment: "Congratulations on baby!
HR handling coverage planning.
Will schedule transition meeting."

Bereavement Leave

What it is: Time off due to death of family member

Typical duration: 3-5 days (varies by relationship)

Advance notice needed: Usually same-day (emergency)

Approval criteria:

  • ✓ Legitimate family death
  • ✓ Proper documentation (optional)
  • ✓ Reasonable duration

What to check:

Before approving bereavement:
1. Death in immediate family?
2. Reasonable duration?
3. Offering condolences?
4. Documentation available?
5. Flexibility for follow-up needs?

Relationships covered:

  • Immediate family: Parent, spouse, child
  • Extended: Sibling, grandparent
  • Other: Depends on company policy

Duration by relationship:

  • Parent/spouse/child: 5 days
  • Sibling/grandparent: 3 days
  • Aunt/uncle/cousin: 1-3 days

Your approach:

  • Be empathetic and respectful
  • Auto-approve (almost always)
  • Offer flexibility if needed
  • Don't question the loss

Color code: Often dark gray or black

Example:

Request: David Lee - Bereavement Leave
Dates: Dec 18-22, 2025 (5 days)
Reason: Death of father

Your checklist:
├─ Immediate family: Yes (father) ✓
├─ Duration: 5 days (standard) ✓
├─ Documentation: Optional
├─ Team coverage: Can arrange ✓

DECISION: APPROVE
Comment: "My sincere condolences.
Approved. Flexible on exact dates
if needed for arrangements."

Unpaid Leave

What it is: Extended time off without salary payment

Typical duration: Days to weeks (varies by policy)

Advance notice needed: Usually 2-4 weeks

Approval criteria:

  • ✓ Business impact acceptable
  • ✓ Advance notice given
  • ✓ Coverage plan exists
  • ✓ Policy allows it

What to check:

Before approving unpaid leave:
1. What's the reason?
2. Can business absorb absence?
3. Advance notice adequate?
4. Is coverage planned?
5. Payroll implications understood?

Common reasons:

  • Extended sabbatical
  • Study/education leave
  • Personal project
  • Family care (long-term)
  • Voluntary break

Approval conditions:

  • "Approved on condition: Coverage found"
  • "Approved with understanding of salary impact"
  • "Approved - 2 week notice given to HR"

Rejection reasons:

  • "Cannot spare this person for this duration"
  • "Notice too short"
  • "Business impact too significant"

Color code: Often dark or neutral

Example:

Request: Emma Thompson - Unpaid Leave
Dates: Jan 15 - Feb 28, 2026 (6 weeks)
Reason: Educational sabbatical

Your checklist:
├─ Advance notice: 4 weeks ✓
├─ Reason: Valid (education) ✓
├─ Business impact: High (specialist role)
├─ Coverage: Need to plan
├─ Payroll: 6 weeks unpaid

DECISION: CONDITIONAL APPROVAL
Comment: "Approved pending coverage plan.
Please work with HR on temporary
replacement/workload distribution.
Need plan finalized by Dec 20."

9. Leave Balance & Tracking

Understanding Leave Balance

What is leave balance?

Leave balance is the number of days an employee has available to take as time off.

Leave Balance Formula:

Annual Allocation (e.g., 20 days)
  ├─ Minus: Days already taken
  ├─ Plus/Minus: Adjustments (carrover, forfeit)
  └─ Equals: Remaining Balance

Example:
20 days (allocated)
- 12 days (already taken)
= 8 days (remaining)

Where to see balance:

  • On the leave request details page
  • In employee profile
  • On approval workflow page
  • In HR reports

Checking Balance Before Approving

Steps:

  1. Open leave request details
  2. Look for "Leave Balance" section
  3. Review:
    • Total days allocated
    • Days already used
    • Days remaining
    • Days being requested

Example:

Leave Balance Analysis:

Total Annual Vacation Days:    20 days
Days Already Used:             12 days
Remaining Balance:             8 days
Currently Requesting:          5 days
After Approval:                3 days remaining

Status: ✓ Sufficient balance

What to approve:

  • ✓ Balance sufficient for request
  • ✓ Employee has enough days
  • ✓ After approval, positive or acceptable balance

What to consider rejecting:

  • ✗ Insufficient balance (request exceeds available)
  • ✗ Would go negative (unless policy allows)
  • ✗ Last remaining days (ensure employee awareness)

Balance Concerns

Insufficient Balance Scenario:

Employee: John Smith
Requesting: 5 days vacation
Available: Only 3 days remaining

OPTIONS:
1. REJECT: Not enough days
   Comment: "Only 3 days balance remaining.
             Please request for those dates instead."

2. CONDITIONAL APPROVE: Unpaid overflow
   Comment: "Approved for 3 paid + 2 unpaid days.
             Confirm acceptance of unpaid portion."

3. CHECK POLICY: May have carry-over
   Contact HR: Can balance be adjusted?

Negative Balance Scenario:

Employee: Alice Brown
Balance: -2 days (from previous year overage)
Requesting: 3 days vacation

ACTION: Refer to HR policy
Comment: "Employee currently has negative balance
         from previous year. Approving would require
         HR adjustment. Forwarding to HR with request."

Year-End Leave Considerations

Important timing:

  • Employees often take leave end of year
  • Balance may be about to expire
  • Carry-over limits apply (varies by policy)
  • Forfeiture dates approach
  • Planning required for Q1 coverage

Your role:

  • Watch for bulk year-end requests
  • Plan team coverage carefully
  • Approve requests following policy
  • Document decisions
  • Coordinate with other team leads

10. Approval & Rejection Workflow

The Complete Approval Journey

Understand the flow:

Employee Submits Request
        ↓
[TEAM LEAD STAGE - YOUR ROLE]
├─ You receive notification
├─ Review request details
├─ Check team impact
├─ Make decision (Approve/Reject/Comment)
├─ Add reasoning
└─ Submit decision
        ↓
HR Review Stage
├─ HR receives submission
├─ HR verifies balance
├─ HR checks policies
├─ HR makes final decision
└─ HR notifies employee
        ↓
Final Status
├─ Approved by HR: Leave can proceed
├─ Rejected by HR: Leave denied
└─ Employee notified via email + system

Your Approval Responsibilities

When approving, you're confirming:

  1. ✓ Team has adequate coverage
  2. ✓ No critical project conflicts
  3. ✓ Proper notice given
  4. ✓ Reasonable request
  5. ✓ No staffing emergencies

You are NOT confirming:

  • ✗ Leave balance (HR verifies)
  • ✗ Policy compliance (HR checks)
  • ✗ Final approval (HR decides)
  • ✗ Payroll processing (Payroll handles)

When to Reject

Clear rejection reasons:

Reason Example
Coverage shortage "Only 2 people left in 5-person team"
Critical deadline "Major project launch Dec 15"
Insufficient notice "3 days notice for week-long leave"
Missing information "Medical certificate required"
Policy violation "Cannot exceed 10 consecutive days"

Don't reject for:

Bad Reason Why
"I don't want to" Personal preference (invalid)
"No specific reason" Vague, not professional
"Because I said so" Autocratic, breeds resentment
"That time is mine" Team decision, not personal

When to Seek More Information

Ask for clarification on:

  • Medical certificates (if required)
  • Coverage plans (for long absences)
  • Reasons (if vague)
  • Project impact (if unclear)
  • Backup arrangements

How to request more info:

  1. Don't reject immediately
  2. Add comment requesting information
  3. Set deadline for response
  4. Revisit request after response

Example request:

"Thank you for submitting your leave request.
Before I can approve, I need:

1. Medical certificate for 3-day absence
2. Plan for project coverage (John can handle?)
3. Handover list for pending tasks

Please provide by Dec 7 so I can finalize decision.
Thanks!"

Communicating Decisions

Approval message to employee:

APPROVED ✓

Your leave request has been approved!

Details:
- Dates: Dec 10-15, 2025
- Type: Vacation
- Duration: 5 days
- Your Manager: Approved

Next: HR will review for final approval.
You'll be notified of final status by Dec 8.

Rejection message to employee:

REJECTED ✗

Your leave request has been declined.

Request: Vacation Dec 10-15, 2025

Reason: Critical project deadline Dec 15.
Team requires full capacity this week.

Alternative: Would Dec 20-24 work instead?
Please discuss with me.

Next: You can resubmit with different dates,
or contact HR to discuss further.

11. Important Information About Approvals

Before Approving

Create your checklist:

□ Employee info verified
  - Correct person?
  - Active employee?

□ Leave details reviewed
  - Correct dates?
  - Accurate duration?

□ Balance checked
  - Sufficient days?
  - Positive balance after?

□ Team coverage analyzed
  - How many off this period?
  - Critical roles covered?
  - Minimum staffing met?

□ Project impact assessed
  - Any critical deadlines?
  - Major milestones?
  - Key deliverables?

□ Notice evaluated
  - Advance warning given?
  - Reasonable notice?

□ Documentation complete
  - All attachments?
  - Medical certs if needed?

□ Policy compliance checked
  - Follows company policy?
  - No conflicts?

After Approving

What happens:

  1. Your approval recorded in system
  2. Request forwarded to HR
  3. HR receives notification
  4. HR verifies balance
  5. HR checks company policies
  6. HR makes final decision
  7. Employee notified

Your visibility:

  • Request status changes to "Approved by TL"
  • HR can see your comments
  • Employee can see your approval
  • You can monitor status

Employee's next expectations:

  • "My manager approved!"
  • But still awaiting HR final approval
  • May receive HR's request for additional info
  • Will get final notification

Employee Impact If You Reject

What employee experiences:

  1. Rejection notification received
  2. Your reason displayed
  3. Can contact you to discuss
  4. Can resubmit new request with different dates
  5. Can appeal through HR if appropriate

For employee's planning:

  • If rejected: Needs to find alternative dates
  • Or explore other leave types
  • Or handle issue without leave (if possible)
  • May need to make arrangement changes

Professional courtesy:

  • Be specific with reasons
  • Offer to discuss alternatives
  • Show you understand difficulty
  • Help find solutions if possible

Tracking Status

Where to find request status:

  • Leave Management system
  • Your dashboard (if showing approvals)
  • Employee can also track
  • Notifications via email

Status indicators:

PENDING          → Waiting for your action
TL APPROVED      → You approved, HR reviewing
TL REJECTED      → You rejected
HR APPROVED      → Final approval, leave confirmed
HR REJECTED      → Final rejection, leave denied
CANCELLED        → Employee cancelled

12. Common Scenarios and Solutions

Scenario 1: Employee Requests Leave During Critical Period

Situation:

Jane requests 2 weeks vacation Dec 10-25 (your busiest season). Your product launch is Dec 15. Team is already stretched.

Analysis:

Project: Major launch Dec 15
Team size: 5 people
Currently off: 1 person (Dec 5-10)
Jane's request: Dec 10-25 (2 people overlap)
Coverage: Would leave only 3 people
Assessment: INSUFFICIENT COVERAGE

Your options:

Option 1: Reject with alternative

"I understand you'd like Dec 10-25 off.
Unfortunately, we have major product launch
Dec 15 and cannot spare you during this week.

I CAN approve Dec 20-25 (after launch).
Or Dec 5-10 (before launch).

Can either of these dates work instead?"

Result: Employee considers alternatives

Option 2: Partial approval

"I can approve Dec 20-25 (after launch).
But cannot approve Dec 10-15 (launch week).

Can you adjust your trip to start Dec 20?
This way you get your leave + team has coverage."

Result: Find compromise

Option 3: Reject with explanation

"Approved: NO

Reason: Critical product launch Dec 15.
Cannot spare development team during this week.
Only 3 of 5 people would remain.
Business impact: Too significant.

Alternative: Please request Dec 20-31 instead.
Or if dates fixed: Discuss with me about
unpaid leave possibility or contingency plan.

Next: Happy to discuss in person."

Result: Clear decision, door open for discussion

Scenario 2: Multiple Requests for Same Dates

Situation:

Jane, John, and Alice all request Dec 20-22 off. You only need 1 person minimum staff.

Analysis:

Requests: Dec 20-22 (3 days)
Requestors: Jane, John, Alice (all approved)
Team size: 5 people
Minimum needed: 2 people

If all 3 approved: Only 2 people work
If only 2 approved: 3 people work (acceptable)
If only 1 approved: 4 people work (comfortable)

Decision: Can approve maximum 2, reject 1

Your approach:

Option 1: First-come-first-served

Process in order received:
1. Jane (submitted Dec 5) → APPROVE
2. John (submitted Dec 6) → APPROVE
3. Alice (submitted Dec 8) → REJECT

Message to Alice:
"Dec 20-22 approved requests limit reached
(2 colleagues already approved for those dates).
Maximum coverage we can spare is 2 people.

Can you choose different dates?
Or discuss alternatives?"

Option 2: Priority-based

Evaluate by importance:
- Jane: Critical role, project lead → APPROVE
- John: Backup role, can cover → APPROVE
- Alice: Cross-trained, flexible → REJECT

Message to Alice:
"Dec 20-22 has coverage limits due to other
approved leaves. Your role is more flexible
to defer. Could you choose Dec 27-29 instead?"

Option 3: Collaborate approach

Send message to all three:
"Three concurrent requests for same dates.
Team can accommodate 2 but not all 3.

Options:
1. Two approve Dec 20-22, one takes different dates
2. Stagger: Two Dec 20-22, one Dec 25-27
3. Discuss with me to find solution

Who wants to discuss scheduling?"

Scenario 3: Excessive Sick Leave Pattern

Situation:

David took sick leave:

  • Dec 2 (Monday)
  • Dec 5 (Friday)
  • Dec 9 (Tuesday)
  • Now requesting Dec 12 (Friday)

Pattern: Always ends near weekends

Analysis:

Pattern Assessment:
├─ Frequency: 4 times in 2 weeks (high)
├─ Days: Mix of Monday/Friday (suspicious)
├─ Trend: Increasing (concerning)
└─ Documentation: Medical certs provided? (check)

Concern Level: MEDIUM TO HIGH
Action needed: Discussion required

Your approach:

For current request:

CONDITIONAL APPROVAL

"I approve your sick leave Dec 12.
However, I need to discuss the frequency
of recent absences.

Four sick days in two weeks is concerning.
Are you okay? Is there a health issue I
should know about?

Let's meet Friday afternoon to discuss.
If ongoing health concern, HR can help
with accommodations or medical leave options.

Please confirm meeting time."

Document the conversation:

Meeting with David - Dec 12, 2:00 PM

Discussion: Pattern of frequent sick leave
├─ Dec 2, 5, 9, 12 (4 days in 2 weeks)
├─ Pattern noted: Often near weekends
├─ Employee states: Recurring flu symptoms
├─ Medical verification: Provided for some days
└─ HR involvement: Recommended

Outcome:
├─ Monitor closely for next 2 weeks
├─ Require medical cert for any future 3+ day absences
├─ HR to discuss health accommodations
└─ Follow-up conversation in 2 weeks

Don't assume:

  • ✗ Don't assume employee is faking
  • ✗ Don't deny leave without evidence
  • ✗ Don't threaten discipline
  • ✓ Do approach with concern
  • ✓ Do request documentation
  • ✓ Do involve HR if pattern continues
  • ✓ Do follow c…