Resident Roster and Contact Information Records for Washington AFHs

A Washington Adult Family Home resident roster should provide a current, facility-specific view of who lives in the home and which room each resident occupies. The complete contact-information record goes further, supporting current resident and representative contact details and the specific ombuds request workflow established in the 2026 rule.

This guide focuses on WAC 388-76-10231 and the software evidence needed to maintain, produce, and audit these records. It was reviewed on August 8, 2026. Providers should verify the current rule, DSHS instructions, privacy requirements, and secure-delivery procedures.

Apply the current 2026 rule

WAC 388-76-10231 became effective March 15, 2026. Its current text requires the home to create and regularly maintain a current resident roster containing the name and room number of each resident.

The rule also addresses providing a written roster to a long-term care ombuds after an in-person request during a visit, and maintaining current, accurate, complete contact information for residents and resident representatives. It describes a written ombuds request for complete contact information, specific request content, a forty-eight-hour period or agreed reasonable time, and secure email or fax delivery.

The operational system should distinguish the limited roster from the more detailed contact-information dataset. They have different fields and disclosure risks.

Separate roster and contact data

Use two related views:

Current resident roster

The roster contains:

• Facility
• Resident name
• Current room number or room identifier
• Roster generation date and time

Keep it concise and printable. Do not automatically add diagnosis, medication, payer, admission notes, phone numbers, representatives, or care information.

Complete resident contact information

The current rule lists resident name, room number or identifier, available phone number, available email address, and, when a representative exists, the representative's name, relationship, phone number, available email, and available mailing address.

Store these fields in structured form so they can be validated, updated, filtered, and exported without copying them from daily notes.

Maintain one authoritative resident identity

The roster should derive from the resident's active facility placement, not from a manually typed spreadsheet. A resident record needs:

• Stable resident identifier
• Legal or preferred display name under facility policy
• Current facility
• Current room assignment
• Residency status
• Effective start and end dates
• Contact details
• Current representative relationship

Room and status changes should flow to the roster only after the underlying transaction becomes effective. The system should preserve historical placements without showing former residents on the current roster.

The broader resident management software guide explains the whole profile. This article remains focused on the roster and contact-information record.

Update the roster through controlled events

Roster changes commonly occur at:

• Admission
• Room assignment or room move
• Transfer between facilities
• Temporary leave that does not end residency
• Discharge
• Death
• Correction of a name or room identifier

Use effective-dated events instead of directly overwriting the displayed room. For every change, record the prior value, new value, effective date and time, reason, responsible user, and related workflow.

A temporary absence should not remove the resident from the current roster unless the applicable residency status actually changes. Show presence in an occupancy view, not by rewriting who resides in the home.

Prevent duplicate active placement

The system should flag a resident who appears active in two facilities or two rooms at the same effective time. Resolution must preserve history and require an authorized user; it should not silently delete one placement.

Maintain current contact information

WAC 388-76-10231 requires updates when the resident or representative provides new or updated contact information. The workflow should make the source and effective timing visible.

For each contact field, support:

• Value
• Type
• Primary or alternate status
• Date received
• Effective date
• Source person
• Verification status
• Communication preference
• Previous value history
• Correction reason

An unavailable phone number or email should be represented as unavailable, declined, or not provided rather than a fake placeholder. Avoid using one family member's contact details as the resident's own details.

Verify representative information

The roster-contact rule calls for relationship and contact fields when a representative exists. The software should also link to the underlying authority or designation record without asserting that contact information alone proves decision-making authority.

Track separately:

• Representative identity
• Relationship label
• Contact details
• Authority type and scope
• Supporting legal or resident-designation document
• Effective, expiration, or revocation dates
• Notification preferences

If contact details change, preserve the authority record. If authority ends, stop displaying the person as the current representative while retaining the historical relationship.

Support the in-person ombuds roster request

The current WAC describes a written copy of the resident roster after an in-person request from a long-term care ombuds at the visit and no later than the conclusion of the visit.

A purpose-built workflow should let authorized staff:

1. Verify the requester's ombuds role under current procedure.
2. Record the visit, facility, request date, and request type.
3. Generate the current limited roster.
4. Review the output before release.
5. Record who provided it and when.
6. Preserve the roster version or manifest that was produced.
7. Record acknowledgement or delivery evidence.

Do not route this request through a general resident-record export that exposes far more information than the roster requires.

Make the roster available during a visit

Because the rule ties production to the visit, the facility needs a reliable print or secure local output even if an administrator is away. Assign trained roles, test printer availability, and maintain an appropriate downtime procedure.

The generated roster should be clean black-and-white, show the facility and generation time, and contain only the required fields.

Process a written ombuds contact-information request

The complete contact-information request is a separate workflow. The current rule describes a written request that references RCW 70.128.155 and relevant ombuds functions and duties, followed by electronic delivery to the secure email address or fax number supplied in the request within forty-eight hours or another reasonable time agreed with the requesting ombuds.

Capture:

• Request document
• Request received date and time
• Requester identity and verification
• Required legal reference present
• Facility scope
• Secure email or fax destination supplied
• Calculated deadline
• Agreed alternate date, if any
• Assigned owner
• Dataset generation time
• Review and approval
• Delivery channel and confirmation
• Failed delivery and retry history
• Completion date

Do not hard-code a normal email address. Use the secure destination in the verified written request and protect it from unauthorized editing.

Build deadline and escalation controls

Calculate the due time from the recorded receipt timestamp and applicable rule configuration. Show:

• Time remaining
• Missing verification or request content
• Owner
• Production status
• Review status
• Delivery status
• Agreed extension

Escalate before the deadline. An internal alert is not proof of fulfillment; completion requires the generated dataset and delivery evidence.

If the requester agrees to another reasonable time, record who agreed, when, the new date, and the communication evidence. Do not simply edit the original due date.

Protect privacy and least privilege

The complete contact dataset contains resident and representative identifiers. Limit viewing, generation, and delivery to authorized roles. Use secure storage, export logging, and short retention for temporary output files according to policy.

Operational staff may need to update a phone number without gaining permission to export every resident's contact information. Separate permissions for:

• View roster
• Print limited roster
• Edit resident contact fields
• Edit representative fields
• Verify ombuds request
• Generate complete contact export
• Approve delivery
• View audit history

The resident record-access request guide covers resident and representative access. Ombuds roster and contact requests should remain a distinct request type.

Design facility boundaries first

Every roster and contact request must be bound to one facility unless the verified request lawfully covers more. The active facility should appear beside generate, print, fax, and send actions.

When switching facilities:

• Clear resident and room filters
• Reload authorized data
• Discard or explicitly save unsent exports
• Recalculate the roster
• Revalidate the request scope

Direct URLs, browser history, and cached exports must enforce the same boundary. A multi-facility administrator should not accidentally send a combined organization roster in response to a single-home request.

Preserve an audit-ready evidence trail

For every produced roster or contact export, retain:

• Request identifier
• Facility
• Requester
• Source record versions or manifest
• Generation timestamp
• User generating and reviewing
• Applied filters
• Output identifier
• Delivery action and destination
• Delivery confirmation
• Correction or resend reason

Completed records should be read-only except for additive correction. A resend should link to the original and identify whether content changed.

Create focused reports

Useful operational reports include:

• Residents missing room identifiers
• Active residents with duplicate room assignments
• Missing resident phone or email status
• Representatives missing required contact fields
• Recently updated contact information
• Ombuds roster requests during a date range
• Written contact-information requests by deadline
• Requests awaiting review or delivery
• Failed or retried deliveries
• Roster corrections and audit activity

Reports should support facility, request status, date range, responsible user, and completion filters without exposing full contact data unnecessarily.

Test every workflow

Use demonstration data to test:

1. Admit a resident and confirm immediate roster inclusion.
2. Change a room with a future effective date.
3. Record a temporary absence without removing the resident.
4. Transfer a resident between facilities.
5. Update resident and representative contact information.
6. End one representative relationship and add another.
7. Produce the limited roster during a simulated ombuds visit.
8. Receive and fulfill a written complete-contact request.
9. Record an agreed alternate delivery time.
10. Fail a secure delivery and retry it.
11. Correct a room assignment without deleting history.
12. Test direct links and cached exports across facilities.
13. Verify mobile, desktop, printer, fax, and secure-email paths.

Confirm the printed roster excludes private fields and the complete export contains only the correct facility's current records.

Frequently asked questions

What must the current Washington AFH roster contain?

The current WAC 388-76-10231 text identifies resident name and room number. Review the full rule and its effective date before relying on it.

Is the roster the same as the complete contact-information list?

No. The rule describes a limited roster and a more detailed resident and representative contact-information dataset with a separate written-request workflow.

Should a resident on overnight leave disappear from the roster?

Not solely because of a temporary absence. The roster should reflect current residency and room assignment; presence status belongs in the appropriate occupancy workflow.

Can the complete contact list be sent through ordinary email?

The current rule describes secure email or fax information supplied in the written ombuds request. Verify the requester and use the required secure channel.

What proves the request was completed?

Keep the verified request, exact dataset or manifest, generation time, reviewer, delivery destination, delivery timestamp, and confirmation or retry history.

Keep the roster current and the disclosure controlled

A reliable workflow connects residency, room assignment, current contact information, representative history, verified ombuds requests, deadlines, secure delivery, and audit evidence. It makes a simple roster quickly available without turning it into an uncontrolled resident directory.

AFH Manager can help providers maintain current rosters, contact information, representative records, facility boundaries, ombuds requests, deadlines, secure exports, and formatted reports. Test the complete process with demonstration residents before production use.