Bereavement Leave Request Form
Use this bereavement leave request form to capture the employee details, dates, travel needs, and coverage notes HR needs to approve time away with less back-and-forth.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Education · Retail · Manufacturing · Professional Services
Overview
This bereavement leave request form captures the information HR and managers need to review a leave request without asking for unnecessary detail. It includes employee information, the relationship to the deceased, the dates requested, funeral or memorial timing, travel needs, coverage notes, supporting documentation, and a consent acknowledgment.
Use this template when an employee needs time away after a death and your process requires a documented request, especially if approval depends on relationship, duration, or travel. The form works well for both full-day and partial-day leave, and it supports conditional logic so you only show travel or documentation fields when they apply.
Do not use this form as a general grief intake or counseling questionnaire. It is not meant to collect personal background, medical information, or detailed circumstances of the loss. Keep the request focused on leave administration, follow your policy for what documentation is allowed, and make sure the employee understands what happens after submission, who reviews it, and how coverage will be handled.
Standards & compliance context
- Keep data collection aligned with GDPR data minimization by asking only for the fields needed to process the leave request.
- If the form is used in a workplace with accessibility requirements, label fields clearly and ensure it meets WCAG 2.1 AA expectations for keyboard use, contrast, and error handling.
- Avoid collecting sensitive personal details beyond what is necessary for leave administration, and treat supporting documentation as confidential HR data.
- If your policy requires documentation, explain the purpose of the request and retain the record according to your internal HR retention rules.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Employee Information
This section identifies the employee and routes the request to the right manager and HR owner.
- Employee name
-
Employee ID
Optional if your HR team uses employee IDs for routing.
- Department
- Manager name
Bereavement Details
This section captures the relationship and reason so HR can apply the correct leave policy.
- Relationship to the deceased
-
Relationship details
Optional additional context if needed for policy review.
-
Date of passing
Optional. Provide only if needed for leave verification or policy review.
- Reason for leave
- Other reason details
Leave Dates
This section defines the exact time away from work and prevents scheduling errors.
- Leave start date
- Leave end date
- Number of full days requested
- Do you need a partial day?
- Partial day details
Funeral and Travel Information
This section helps HR understand whether the leave needs to align with a service or travel schedule.
- Funeral or memorial date
- Funeral or memorial location
- Will travel be required?
-
Travel details
Include destination and estimated travel time if relevant.
Coverage and Supporting Information
This section records handoff notes, documentation, and consent so the request can be processed cleanly.
-
Coverage notes
Optional: share urgent tasks, handoff instructions, or contacts for coverage.
-
Supporting documentation
Optional: upload any documentation your policy requires.
- Consent and acknowledgement
How to use this template
- 1. Add your company’s bereavement policy language, required fields, and any conditional logic for relationship type, travel, or documentation.
- 2. Configure the employee information section so the request is tied to the correct person, manager, and department for routing and recordkeeping.
- 3. Set up the leave dates section with date picker fields, a partial-day option, and clear validation for start and end dates.
- 4. Route the form to HR and the manager for review, and define what coverage notes or approvals are needed before the leave is finalized.
- 5. Publish a short instruction line that explains what happens after submission, including response timing, documentation review, and any follow-up steps.
Best practices
- Use conditional logic to show travel details only when travel is required, so the form stays short and relevant.
- Mark required and optional fields clearly, and keep the request limited to the minimum information needed to approve leave.
- Use date picker fields for all dates and numeric or checkbox inputs where they fit, rather than free-text fields that create cleanup work.
- Include a plain-language consent acknowledgment that explains how supporting documentation and PII will be handled.
- Ask for partial-day details whenever the employee does not need a full day off, because that is where scheduling errors often happen.
- Add a clear post-submit message that tells the employee who will review the request and whether they should wait for approval before taking leave.
- Keep coverage notes focused on handoff instructions, deadlines, and backup contacts instead of personal explanations.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this bereavement leave request form?
Employees use it to request time off after a death in the family or another close relationship. HR and managers use it to review the request, confirm dates, and coordinate coverage. It is especially useful when the leave may include partial days, travel, or a funeral or memorial event.
What situations does this template cover?
This template covers standard bereavement leave requests, including requests tied to a family relationship, an extended relationship, or another reason the employee wants to explain. It also supports funeral or memorial timing, travel requirements, and partial-day needs. If your policy has different rules for immediate family, non-family relationships, or international travel, this form can be adapted with conditional logic.
How often is this form typically used?
It is used whenever an employee needs bereavement leave, so there is no fixed cadence. Some organizations use it only for formal leave requests, while others use it for every bereavement-related absence to keep records consistent. If your policy allows self-service submission, the form can be reused each time without changing the workflow.
What should HR ask for, and what should it avoid collecting?
Collect only the fields needed to evaluate the leave request and coordinate coverage, such as relationship, dates, and travel needs. Under GDPR data minimization and the minimum-necessary principle, avoid asking for unnecessary PII or sensitive details about the death. If supporting documentation is requested, explain why it is needed and keep the request limited to what your policy requires.
Can employees submit this form anonymously?
No, not for a leave request that must be tied to an employee record and approved by a manager. The form should identify the employee so HR can verify eligibility, record the absence, and update payroll or attendance systems. If you need a separate confidential channel for feedback about the process, use a different form with anonymous submission enabled.
What are the most common mistakes when using this form?
The biggest issues are unclear dates, missing partial-day details, and vague relationship descriptions that leave HR guessing about policy eligibility. Another common problem is collecting too much information, such as unnecessary medical or family history. The form should also include a clear note about what happens after submission so employees know who reviews it and when.
How can this form be customized for different policies?
You can add conditional logic for immediate family versus extended family, domestic versus international travel, or full-day versus partial-day leave. Some organizations add a policy acknowledgment field, a manager approval step, or a documentation upload only when required. You can also rename fields to match your handbook language so employees see the same terms they read in policy.
What systems does this form usually connect to?
It often connects to HRIS, payroll, calendar, and ticketing or case-management tools. Those integrations help route the request to the manager, record approved leave, and create an audit trail. If your workflow uses approvals, the form can also trigger notifications when supporting documentation is added or when the leave dates change.
How should we roll this out to employees?
Start by aligning the form with your bereavement policy, then test the fields with HR and a manager before publishing. Make sure the instructions explain who should submit it, when to submit it, and what happens after submission. A short rollout note in your employee handbook or intranet helps reduce incomplete requests and repeated follow-up.
Related templates
Ready to use this template?
Get started with MangoApps and use Bereavement Leave Request Form with your team — pricing built for small business.
