Alternative communication location

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

The request needs a usable destination

Current 45 CFR 164.522 permits a covered entity to condition a reasonable accommodation on specification of an alternative address or other contact method. Record the exact destination, communication types, effective date, safe verification route, limitations, and change process.

Capture unit, post box, attention line, portal account, office, or other details needed for reliable delivery. Confirm the destination through a method the individual identifies as safe. Explain which communications are covered and whether the alternative applies to mail, packages, electronic notices, or all selected categories.

Keep the confidential location distinct from home, service, guarantor, and general account addresses. An ordinary demographic update can create unintended propagation or erase the special handling rule.

Location rules should follow the communication

Map statements, appointment notices, clinical correspondence, billing mail, authorization letters, surveys, record deliveries, collections, and vendor messages. A profile address can remain valid for other operational purposes while confidential communications use a separate destination.

Include envelope windows, return addresses, external fulfillment, payer correspondence, and returned-mail workflows. Suppress unsafe fallback. Decide how staff should handle an invalid address without contacting the former location or exposing the request.

Validate mail and electronic location rules

Run controlled tests from each sender and inspect the final artifact, destination, envelope, preview, and vendor file. Confirm that corrected addresses propagate without changing unrelated records. Review batches and queued communications created before the effective date.

Record returned mail, failed portal delivery, retry, safe outreach, and final outcome. Version later changes or termination with effective times and downstream confirmations.

Example across mail sources

Six systems produce mailed communications. Five route to the alternative location; one billing export still selects the household address. Location-control completion is 5 of 6 systems. The old route requires suppression and review of any misdirected mail.

Pause the billing batch, correct the export mapping, and inspect items produced during the gap. The request is approved, while implementation remains incomplete until a six-route test passes and any incident is reviewed.

Location checklist

• Capture a complete usable destination and safe verification route.
• Define communication categories, effective date, and failure handling.
• Separate confidential location from demographic and billing addresses.
• Map internal, payer, vendor, batch, and manual senders.
• Suppress unsafe fallback and inspect queued communications.
• Test artifacts, envelopes, previews, returns, and retries.
• Version changes and retain implementation and incident evidence.

Owner controls

The HHS Audit Protocol supports procedure testing. Separate residential, billing, service, and confidential-contact fields; limit workforce visibility; test vendor files; record returned mail; and verify changes through a safe channel. Never confirm the request using the destination identified as unsafe.

Monitor sender coverage, misroutes, returns, vendor lag, and unsafe fallback. Re-test after address, billing, portal, print, and fulfillment changes.

Use data governance that prevents a demographic merge from overwriting the confidential location. Define which field each sender consumes, who may view or edit it, how identity merges behave, and what happens during duplicate-record cleanup. Protect the request itself in screen labels and exports. Staff who need a mailing destination may not need the reason or historical unsafe address.

Audit real output from each sender rather than trusting the master profile. Sample envelope windows, batch files, portal notifications, records packages, and returned-mail events. Investigate any item sent to an unsafe destination and review nearby batch members. Keep continuity instructions for printer outage, vendor failure, and manual mail. When the person changes the location, version the request and confirm every downstream sender before retiring the earlier rule.

Review address normalization carefully because software may replace a post box, attention line, or alternate location with a standardized household address. Preserve both entered and normalized values and validate the printed result. Include couriers, certified mail, bulk mail, and return processing in the source map. If a destination becomes unusable, hold affected communications and seek a safe update rather than reverting automatically. Measure requests approved, routes implemented, returned items, misroutes, vendor delays, and time to correction. Limit dashboard visibility to staff who need the sensitive handling information.

Create an exception path for split households, temporary addresses, custody-related contacts, and records with several authorized recipients. Apply the reviewed rule to each communication instead of copying one destination across every relationship. Preserve why a route was selected, but keep sensitive context out of mailing labels and ordinary demographic screens.

Audit every exception through supported evidence.