Communication-preference records should help an Adult Family Home share information with each resident in a form, language, pace, and channel the resident can use. They should also identify who may receive notifications, what authority that person has, and when an accommodation needs review.
This guide concerns documentation and workflow, not a clinical communication assessment or legal determination of decision-making authority. It was reviewed on August 8, 2026. Providers should verify current federal and Washington requirements and follow resident choices, assessments, care plans, rights, privacy duties, and qualified guidance.
Separate preference, need, and authority
Do not combine three different questions into one “contact preference” field:
- Preference: how the resident wants routine communication
- Accessibility need: what support makes communication effective
- Authority: who may receive information or act for the resident
A resident may prefer text reminders, need large print for documents, and still make their own decisions. A representative's contact information does not automatically mean that every message should bypass the resident.
Store each item with source, effective date, reviewer, and status. Keep assumptions out of the record.
Build a resident-centered communication profile
Relevant structured fields can include:
- Preferred spoken and written language
- Interpreter need and preferred qualified service
- Preferred name, pronouns, and pronunciation
- Reading format and text size
- Hearing, vision, speech, cognitive, or motor accommodations
- Assistive device used for communication
- Best time, pace, and environment for discussion
- Preferred routine channels
- Channels not permitted or not reliable
- Consent for voicemail, email, text, or portal use as applicable
- People the resident wants involved or notified
- Topics or situations requiring a different method
- Review date and change history
WAC 388-76-10320 requires resident records to include identifying information and contact information for representatives, health care providers, significant family members, and other individuals the resident wants involved or notified. The communication profile adds operational detail without replacing formal authority records.
Document the source and resident participation
Record whether a preference or need came from the resident, representative, assessment, care plan, practitioner, speech or occupational specialist, or another verified source. Capture the date and staff member.
Whenever possible, confirm the profile directly with the resident and document how the resident participated. Do not label a resident “unable to communicate” merely because staff have not provided an effective accommodation.
If information conflicts, show the conflict and route it for review. Do not silently choose the newest entry when authority or resident rights may be involved.
Connect accommodations to daily workflows
The record matters only if it appears at appropriate action points. Show concise, relevant guidance in:
- Medication explanation and refusal documentation
- Care-plan and assessment meetings
- Appointment preparation and follow-up
- Incident response and notifications
- Consent and signature workflows
- Daily notes and behavior tracking
- Emergency and evacuation communication
- Family portal and secure messaging
- Complaints, grievances, and record requests
Avoid displaying the entire profile in every dialog. Use a short accommodation cue with access to the verified detail. High-impact warnings should require acknowledgement when policy calls for it.
Use accessible formats as documented deliverables
When the home provides a document in an accessible format, record:
- Document and version
- Format provided
- Language
- Delivery date and channel
- Recipient
- Interpreter or assistance used
- Confirmation or questions
- Follow-up needed
Examples may include large-print, read-aloud, plain-language, translated, electronic, or other resident-specific formats. Do not mark a checkbox for “accessible” without naming what was provided.
The record should retain the original source document and the accessible version so later updates can be synchronized.
For recurring documents, store the accessible-format requirement as a reusable preference but record each actual delivery separately. A future care plan or notice may have a different version, recipient, or delivery result. Templates can reduce repeated entry, yet the user should confirm the resident, language, format, and current authority before sending. If a translation or conversion is delayed, keep an open task with an owner and due date rather than marking the source document delivered.
Manage interpreters and communication assistance
For an interpreted interaction, capture the language, modality, interpreter or service identifier as appropriate, date, participants, document or topic, and any communication limitation.
Do not expose sensitive resident information to an informal contact merely because that person speaks the language. Follow the home's authorization and qualified-interpreter process.
For assistive devices, document device type, resident assignment, availability, maintenance or charging needs, and backup approach. Device status belongs in operations; the resident's communication preference belongs in the resident record.
Keep notification recipients and permissions precise
Create recipient records with:
- Name and relationship
- Contact channels
- Topics the person may receive
- Legal or resident-granted authority source
- Effective and expiration dates
- Priority order when applicable
- Time or channel restrictions
- Verification date
- Revocation or superseded status
Do not treat “emergency contact,” “representative,” “family,” and “authorized portal user” as interchangeable. The resident roster and contact records guide covers the underlying contact registry; this workflow governs how communication choices and accommodations are applied.
Prevent unsafe or confusing message routing
Before sending, the system should show resident, facility, topic, recipient, authority, selected channel, and relevant preference. Server-side rules must enforce access and facility boundaries.
Useful safeguards include:
- No automatic recipient carryover after switching residents
- Warning for expired or revoked authority
- Separate routine and urgent communication paths
- Secure-link delivery instead of sensitive details in ordinary email
- Delivery, failure, retry, and acknowledgement status
- Alternative channel after a documented failure
- Audit history for manual recipient changes
A “sent” status means transmission was attempted, not that the resident understood the information. Record delivery and follow-up separately.
Respect changes and refusals
Residents may change preferences or decline a proposed communication method. Add a new effective-dated record rather than overwriting the old one. Capture what changed, source, date, staff member, and affected workflows.
When a resident declines an accommodation, document the offer, response, and any follow-up without using the refusal to deny future access. Review again when needs or circumstances change.
If authority is revoked, remove future access promptly while preserving past messages and audit evidence.
Protect confidentiality and minimize display
WAC 388-76-10315 requires confidentiality and protection of resident records. Communication profiles may disclose disability, language, relationships, and contact information. Show only what a role needs.
When HIPAA applies, HHS explains that covered entities must provide effective communication access for people with limited English proficiency and disabilities under applicable federal civil-rights requirements. The exact duties depend on the organization and situation; providers should obtain qualified guidance rather than relying on a software label.
Review communication effectiveness
Useful review signals include:
- Preference not reviewed within facility policy
- Interpreter need with no documented service
- Accessible document promised but not delivered
- Failed message with no alternate-channel follow-up
- Recipient authority expired
- Conflicting communication instructions
- Accommodation unavailable during an important event
- Resident or representative reports that communication was ineffective
Review outcomes should lead to a documented update, task, or explanation. Avoid repeated alerts for one unresolved case.
Create focused communication reports
Authorized reports can show accommodation coverage, interpreter use, accessible-document delivery, failed communications, expired permissions, and review status. Filter by facility, resident, need, channel, recipient status, event type, and date range.
A resident-facing summary should be understandable and omit internal risk flags. An administrative report can show operational gaps. PDF exports should be clean, paginated, color independent, and restricted to authorized residents.
The family communication portal guide explains broader portal features. A portal must still honor the resident-specific recipient and accessibility record.
Test real communication scenarios
Use demonstration residents to test:
- Large-print document delivery.
- Interpreter-supported care-plan meeting.
- Hearing accommodation during medication explanation.
- Resident who prefers direct contact before family notification.
- Representative with authority limited to defined topics.
- Revoked portal access.
- Failed email followed by an approved alternate channel.
- Conflicting preference and contact instructions.
- Facility transfer without recipient leakage.
- Mobile layout with large text and assistive technology.
- Change history and an accessible resident summary.
- Unauthorized user attempting to export the profile.
Confirm that switching residents clears recipients, draft messages, attachments, and accessibility prompts from the prior profile.
Frequently asked questions
Is an emergency contact automatically a resident representative?
No. Store relationship, notification role, and authority separately and verify the source for each.
Should the resident still receive information when a representative is involved?
Follow the resident's rights, choices, capacity context, and applicable authority. Do not assume representative involvement means communication should bypass the resident.
Is a preferred language field enough?
No. Record spoken and written needs, interpreter or accessible-format requirements, source, review date, and how those needs apply in actual workflows.
Can staff use a family member as an interpreter?
Use the home's applicable authorization and qualified-interpreter process. Language ability alone does not establish privacy permission or suitability.
What happens when a preference changes?
Add an effective-dated update, preserve prior history, revise affected workflows, and remove access promptly when a permission is revoked.
Turn preferences into usable access
A strong communication record connects resident choice, accessibility need, authority, actual delivery, effectiveness, change history, and secure routing.
Explore AFH Manager to organize resident communication preferences, authorized contacts, accessible document delivery, secure messages, follow-up tasks, and reports. Test the workflow with residents and representative scenarios before production use.