A Funeral Home Internet Outage Plan: Keep Working, Then Reconcile the Records

This is a continuity workflow to adapt to the firm's operating and safety procedures. It does not authorize bypassing required identity checks, documents, approvals or equipment safeguards. The plan should make those dependencies clearer during a disruption.

Distinguish the kind of outage

Start by determining whether the problem affects one device, the building connection, electrical power or a specific online service. Avoid asking every employee to repeatedly retry a transaction while nobody records what has happened. A small incident log can capture the first observed failure and the checks already made.

Name one coordinator and a second contact. The coordinator communicates the current approach, checks service information through an available channel and decides when to activate the temporary process. Employees should not have to make conflicting assumptions about whether the team is working online or on paper.

Record the start time and affected functions. “Internet down” may conceal different effects: office telephones could still work, mobile access may be available, and one vendor may be unavailable while another remains reachable. Test the actual dependencies rather than assuming every tool has failed.

Identify the work that cannot wait

List the firm's essential activities and the information each needs. These may include responding to first calls, coordinating transfers, contacting families and confirming near-term arrangements. The business should decide which activities can safely continue and which require unavailable information or approvals.

FEMA's continuity guidance discusses essential functions, dependencies and alternative communications. The following funeral-home worksheet is an application of that planning approach, not a claim that a generic template meets every local obligation.

Avoid filling the temporary kit with stale case information that nobody maintains. Define what is kept available, how often it is refreshed and who can access it.

Build a small offline kit

Keep approved blank intake and action forms, an outage log, staff contact arrangements and relevant vendor contact details in a known location. A kit that requires online sign-in to open is not sufficient for a complete connectivity loss.

The blank forms should capture a temporary reference, date, time, employee and source of each instruction. Include a field for the eventual case number. This allows staff to connect the temporary record to the correct existing case instead of creating a duplicate later.

Store the kit appropriately. Emergency access does not mean unrestricted access to personal information. The FTC's information-security guide provides general guidance on physical records and staff handling. Do not place card numbers or passwords in a broadly accessible continuity binder.

Decide what a backup connection can support

A mobile hotspot or second connection may allow essential access, but test it before an incident. Verify coverage, business approval, device configuration and which functions are available. A backup connection does not help if the unavailable element is the software service itself.

Ask each important vendor about service-status information, incident communication, supported browsers and any documented offline behavior. Do not assume a cached page can safely save new records. Seeing a previously loaded screen does not prove that an update was accepted.

This guide does not claim that FuneralHQ operates offline. Ask the team to demonstrate the supported behavior for the actual outage scenario, including what the user sees if a save or payment request is interrupted. Record the answer in your continuity plan.

Keep transaction uncertainty visible

If a payment request times out, do not immediately repeat the charge based only on an error message. Check the processor's transaction record through an approved available route before deciding the next step. Record the uncertainty and assign an owner if verification must wait.

Apply the same principle to documents and messages. A staff member may not know whether a request was sent before access failed. Mark it as needing verification rather than treating it as definitely sent or definitely absent. Repeating a signing request unnecessarily can confuse the family about which packet applies.

For every interrupted action, keep three pieces of information: what was attempted, what confirmation was observed and what remains uncertain. That is more useful at recovery than a general note saying the system was slow.

A fictional two-hour disruption

At 10 a.m., the office loses its connection. The duty manager checks that the problem affects the building, activates the intake sheets and tells staff which phone route remains available. One director records a first call with temporary reference O-01. Another records an arrangement change against an existing case reference.

At noon, access returns. The first director checks whether O-01 matches an existing case before creating a new one. The second compares the recorded change with the current case instructions and completes the appropriate review. Both temporary sheets receive the final case reference and reconciliation status.

The office lead separately checks a payment attempt that was interrupted at 9:59. Its uncertainty is resolved through the processor record, rather than by charging again from memory. The incident closes only after these exceptions have owners and outcomes.

Reconcile before declaring normal service

Use a recovery checklist. Account for every temporary reference, locate its final record, enter the relevant events with their actual occurrence time and record when the entry was made. Preserve the difference between an event that happened during the outage and a record entered afterward.

Check for duplicates, contradictory instructions, repeated requests and unresolved transactions. A recovered connection does not automatically mean the business records are complete. Staff may have worked through several separate channels while the outage continued.

Keep the temporary material under the firm's reviewed retention process after reconciliation. Do not simply shred the notes because the online entry exists. The business should decide what supporting record must remain and how it is stored.

Practice a short exercise

Choose a fictional scenario and ask the covering employee to locate the kit, record a first call, identify an interrupted transaction and explain how the team would recover. Use invented information rather than real family details in the exercise.

Record practical gaps: a phone number unavailable offline, an unclear decision owner, a form with no temporary identifier or a recovery step that assumes the original employee is present. Fix those gaps and repeat the relevant part of the exercise after the process changes.

Use the blank outage reconciliation log. Bring one outage scenario to a FuneralHQ demo alongside your usual case workflow. Understanding how work resumes is part of evaluating a cloud system, just as important as understanding how it behaves on a normal day.