Bereavement Leave Request Form

This template is for employees requesting leave after the death of a family member or other close relation. It captures the relationship, dates, funeral or memorial timing, and any travel needs so HR can review the request consistently. If your policy has different rules for immediate family, extended family, or domestic partners, this form can be adjusted with conditional logic.

The employee should complete the request, and HR or the employee’s manager should review it according to company policy. In some organizations, the manager handles coverage planning while HR confirms eligibility and leave classification. The form is designed to support that handoff by collecting both employee details and operational context in one place.

It is used whenever an employee needs bereavement leave, so it is typically an on-demand intake form rather than a recurring workflow. Some employers also reuse the same structure for follow-up requests if the leave dates change or if additional time is needed. Keeping the fields consistent helps reduce back-and-forth during a difficult time.

Only require the fields needed to make a leave decision and coordinate coverage, such as employee identity, relationship, dates, and whether travel is involved. Supporting documentation and detailed explanations should usually be optional unless your policy or local law requires them. This supports GDPR data minimization and avoids collecting more PII than necessary.

Yes, if your policy does not require documentation for every request. Many employers use an attestation field first and ask for supporting documentation only when policy, jurisdiction, or a specific case requires it. If you do collect documents, include a clear disclosure about how they will be used and who can access them.

Keep the form focused on leave administration and avoid collecting unnecessary medical or family history details. Use progressive disclosure so employees only see travel or documentation fields when relevant, and include a clear note about what happens after submission. If anonymous submission is not appropriate for this workflow, make that clear rather than implying it is available.

A common mistake is making every field required, which creates friction and can feel insensitive. Another is using free-text fields for dates or counts when a date picker or structured field would be more accurate. Teams also sometimes forget to define who approves the request, what happens after submission, and how coverage notes are used.

You can tailor the relationship options, documentation requirements, and approval routing to match your policy and local rules. Conditional logic can show travel fields only when travel is needed and hide service details when there is no funeral or memorial. You can also add department-specific coverage prompts or manager acknowledgment fields if your workflow needs them.

Yes, it can be connected to HRIS, ticketing, or workflow tools so the request creates a case, notifies the manager, and records an audit trail. Common integrations include calendar tools for leave dates, document storage for supporting files, and approval workflows for routing. The key is to map only the fields you actually use downstream.