Bereavement Family Follow-Up Log
A bereavement family follow-up log for documenting condolence outreach, contact preferences, support needs, and next steps after a death. Use it to keep follow-up respectful, consistent, and traceable.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Hospice And Palliative Care · Human Resources · Patient Relations
Overview
The Bereavement Family Follow-Up Log is a workplace form for recording condolence outreach after a death, along with the family’s contact preferences, support needs, and any urgent concerns that require action. It is designed for teams that need a clear record of who was contacted, when the contact happened, what method was used, and what follow-up is still open.
Use this template when your organization provides bereavement support, family care coordination, patient relations follow-up, or HR outreach after an employee death. It is especially useful when several people may touch the case and you need one shared audit trail with assigned ownership and a next follow-up date. The structure supports progressive disclosure: if no urgent concern is present, you do not need to open extra fields; if support needs are identified, you can capture only the resources that were actually provided.
Do not use this form as a general incident report or as a place to store unnecessary personal details. Keep to the minimum-necessary principle and collect only the PII needed to complete the follow-up. If the family requests no further contact, the log should record that clearly and stop additional outreach. This template is not for clinical documentation, legal investigation, or broad case narrative; it is for respectful, traceable bereavement follow-up.
Standards & compliance context
- Limit collection to the minimum necessary PII and contact details needed to complete bereavement follow-up.
- If the form is public-facing or family-accessible, make required fields and consent language clear to support WCAG 2.1 AA accessibility and informed submission.
- Respect do-not-contact requests and preferred contact methods to align with consent-based outreach practices.
- Use an audit trail for assigned_to, follow-up status, and internal notes so the record supports internal review without exposing unnecessary sensitive information.
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
Death Record and Case Context
This section anchors the record to the correct person, date, and program so follow-up is tied to the right case.
-
Patient or case identifier
Use the internal case ID or other minimum-necessary identifier. Do not enter SSN or other unnecessary PII.
- Date of death
- Program or service
- Primary family contact relationship
Consent and Contact Preferences
This section prevents unwanted outreach by documenting permission, preferred contact method, and any do-not-contact request.
- Permission to contact family for bereavement follow-up confirmed
- Preferred contact method
-
Preferred contact window
Example: weekday mornings, evenings after 6 PM, or no preference.
-
Do not contact requested
Select if the family requested no bereavement follow-up contact.
Follow-Up Contact Log
This section creates the core audit trail of each condolence contact attempt and what was actually communicated.
- Contact date
- Contact time
- Contact method
- Contact outcome
-
Condolence message delivered
Check if condolences were shared during this contact.
-
Contact notes
Document only relevant follow-up details. Avoid unnecessary personal or clinical information.
Bereavement Needs and Support
This section captures what the family needs next so support can be matched to the situation without over-collecting details.
- Support needs identified
- Urgent concern present
-
Urgent concern details
Describe the concern and any immediate escalation taken. Keep details limited to what is necessary.
- Resources provided
Follow-Up Plan and Audit Trail
This section assigns ownership, sets the next action date, and shows the current status of the case.
- Next follow-up date
-
Assigned to
Enter the staff member or role responsible for the next action.
- Follow-up status
-
Internal notes
For internal coordination only. Do not include unnecessary PII.
How to use this template
- 1. Enter the death record and case context, including the decedent identifier, date of death, program or service, and the primary contact relationship.
- 2. Confirm whether contact permission has been granted, then record the preferred contact method, preferred contact window, and any do-not-contact request.
- 3. Log each outreach attempt with the contact date, time, method, outcome, condolence message delivered, and concise contact notes.
- 4. Capture any support needs identified, mark whether an urgent concern is present, and list only the resources that were actually provided.
- 5. Assign the next follow-up date, name the staff member responsible, and update the follow-up status so the case can be handed off cleanly.
- 6. Review internal notes for accuracy, remove unnecessary PII, and close the log only after the follow-up action is complete or no further contact is requested.
Best practices
- Use structured fields for contact method, outcome, and support needs so the log stays searchable and easy to audit.
- Mark required fields clearly and leave optional fields optional to avoid forcing staff to collect information the family did not volunteer.
- Record the family’s preferred contact window before scheduling another call, especially when grief, work hours, or religious observances affect availability.
- Keep condolence notes brief and factual; do not turn the log into a narrative summary of the death.
- Use conditional logic so urgent-concern details appear only when an urgent concern is marked yes.
- Document the exact resource names provided, such as grief counseling, chaplaincy, social work, or community support, rather than writing generic phrases.
- Update the follow-up status immediately after each contact so ownership does not get lost during shift changes or case handoffs.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this bereavement family follow-up log used for?
This template records post-death contact with a family member or primary contact, including whether permission to contact was confirmed, what was discussed, and what support was offered. It helps teams keep outreach consistent, respectful, and easy to review later. The log also creates an audit trail for internal handoffs and follow-up ownership.
Who should complete this log?
It is usually completed by the staff member responsible for bereavement outreach, case management, patient relations, or another designated support role. If multiple people may contact the family, one person should own the record and update the follow-up status. That reduces duplicate calls and helps preserve a clear contact history.
How often should follow-up be logged?
Log each contact attempt and each completed conversation as it happens, rather than waiting until the end of the day. If the family requests a later check-in, record the next follow-up date and any preferred contact window. This keeps the record current and prevents missed commitments.
What should be included in the contact notes?
Keep notes focused on what was actually said, what support needs were identified, and what resources were provided. Avoid unnecessary PII and do not record sensitive details that are not needed for follow-up. If the family declines contact or requests no further outreach, document that clearly in the do-not-contact field.
How does this template handle consent and contact preferences?
The template includes fields for confirming contact permission, preferred method, preferred contact window, and any do-not-contact request. That supports respectful outreach and reduces the risk of contacting someone in a way they did not want. If your process allows anonymous submission or third-party reporting, keep that separate from family follow-up records.
What are common mistakes when using this log?
Common issues include leaving the contact outcome vague, skipping the next follow-up date, and collecting more personal information than the team will actually use. Another frequent mistake is using free-text notes instead of structured fields for contact method, support needs, and urgent concerns. Clear field validation and required-vs-optional labeling help avoid those gaps.
Can this template be customized for different programs or services?
Yes. You can add the specific program or service involved, adjust support-needs options, and tailor the resources list to your organization’s bereavement process. If your workflow includes escalation to social work, chaplaincy, HR, or a patient advocate, add conditional logic so those branches appear only when relevant.
What systems does this log integrate with?
It can be used alongside case management, CRM, HR case tracking, or patient support systems, depending on your workflow. The key is to preserve the audit trail and avoid duplicating sensitive details across multiple tools. If you sync data, map only the fields you need and keep the rest out of downstream systems.
How is this better than ad-hoc notes or email threads?
A structured log makes it easier to see who contacted the family, when it happened, what was discussed, and what still needs attention. Ad-hoc notes often miss consent, follow-up ownership, or the next action date. This template turns a sensitive process into a repeatable record that is easier to review and hand off.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
Ready to use this template?
Get started with MangoApps and use Bereavement Family Follow-Up Log with your team — pricing built for small business.
