Failed electronic notice fallback

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Known failure activates the fallback

Under 45 CFR 164.520, a paper copy must be provided when the covered entity knows the email transmission failed. Record electronic-notice agreement, notice version, send time, failure event, safe address, paper-send date, return status, and owner.

Define which signals establish known failure in the delivery system, such as a permanent bounce or rejected destination. Preserve raw failure evidence and the time the entity knew. Do not mark the electronic task complete merely because the send job ran. Route confirmed failure immediately to a paper-delivery owner.

Transient delays, spam placement, and confirmed rejection may require different operational handling, while the legal conclusion should follow current policy and qualified review. Keep every attempt and final disposition.

Address safety still matters

A default household address can conflict with a confidential-communication request or known safety concern. Check current restrictions and approved contact routes before mailing. Route an unknown or unsafe address for privacy review rather than marking the notice complete.

Verify the individual's current paper route, alternative location, personal-representative status, and returned-mail history. Avoid calling or emailing through an unsafe channel to ask for an address. Use the current NPP version and accessible format, and preserve mailing evidence.

Control unresolved fallback cases

When no safe mailing route is available, create a restricted exception with owner, age, safe outreach plan, and escalation. Hold the unsafe send while continuing reasonable efforts. Record why a route was rejected and any later address update.

Returned paper is another failure event. Do not silently file it. Review the envelope, address, confidential-contact controls, and safe next step. Link any misdirected communication to the incident process.

Example with failed sends

Five NPP emails return known failure signals. Four receive paper copies through verified routes; one has no safe mailing address and remains assigned for clarification. Fallback completion is 4 of 5 failures.

If one of the four paper copies returns undelivered, final supported delivery falls to three until the case is resolved. Paper sent, paper returned, and paper delivered are different states. Keep the event denominator fixed at five known electronic failures.

Fallback checklist

• Preserve electronic agreement, notice version, send, and known failure evidence.
• Create a paper-delivery task when the entity knows email failed.
• Check confidential communication, restriction, representative, and safety records.
• Verify a safe address without using the unsafe route.
• Send the current paper notice and retain mailing evidence.
• Track returned mail, retry, exception age, and incident review.
• Close only after a supported disposition.

Owner controls

HHS guidance describes email delivery and the paper fallback. Monitor bounces, distinguish transient from confirmed failure under policy, verify addresses, integrate confidential-contact controls, retain mail evidence, and age every unresolved case.

Measure known failures, fallback tasks, safe-address validation, paper sends, returns, successful dispositions, and overdue exceptions. Test integrations after email, print, address, or vendor changes and sample cases from failure logs into paper evidence.

Map the event pipeline from email service to privacy case. Preserve provider message ID, recipient, send time, notice version, bounce code, classification, knowledge time, task creation, and paper outcome. Monitor delays and dropped webhooks. A vendor summary count cannot replace event-level ownership when the entity knows a particular transmission failed. Reconcile provider failures to created tasks daily or at another risk-appropriate cadence.

Design continuity for print or mail outages. Use an approved alternate printer or fulfillment route, preserve chain of custody, and prevent a backlog from using an obsolete notice after revision. Review duplicate paper sends for privacy impact rather than suppressing retries blindly. When the individual supplies a corrected email, update the electronic route separately from the paper fallback already required for the known failure. Retain communication and version history so later reviewers can reconstruct the full sequence.

Use a clear final-state model for reconciliation. Useful states include paper sent, returned and readdressed, returned without a safe alternative, delivered through a verified representative, and still open with an escalation owner. Do not erase the known electronic failure when paper succeeds; both events form the compliance record. Sample closed cases to confirm that the address came from an approved source, confidential-contact preferences were honored, the current version was mailed, and vendor completion data matched the practice record. Correct systemic mismatches before closing the affected batch.

Retain unresolved cases on an aging report with a named decision owner and the next permitted action, even when no safe destination is currently available.