Resident Absence and Overnight Leave Documentation for AFHs

Resident absence and overnight leave documentation helps an Adult Family Home know who is in the home, who is temporarily away, what care responsibilities changed, and whether the resident returned as expected. A reliable record prevents a planned family visit, hospital stay, appointment, or community outing from being confused with discharge, elopement, or an unexplained absence.

This guide focuses on the operational record for temporary absences. It was reviewed on August 8, 2026. Providers should confirm current Washington requirements and use resident-specific assessments, negotiated care plans, orders, agreements, and qualified guidance.

Record when a resident is absent

The current text of WAC 388-76-10320 includes when a resident was admitted, absent from the home, and discharged among the minimum resident-record contents.

The rule does not turn every short outing into the same kind of event. The facility needs a usable policy defining which absences are logged, the minimum detail, and how the record connects to care, medications, appointments, safety, and billing without restricting resident rights.

A practical absence record includes:

• Resident and active facility
• Absence type
• Planned or unplanned status
• Departure date and time
• Expected return date and time, when known
• Actual return date and time
• Destination or contact detail only to the extent appropriate and authorized
• Person accompanying or assuming agreed responsibilities
• Transportation arrangement
• Medication and care handoff status
• Notifications and instructions
• Open follow-up tasks
• User and timestamp history

Distinguish absence types

One generic “away” status cannot safely drive every downstream workflow. Use clear categories such as:

• Community outing
• Family or representative visit
• Appointment
• Day program or regular activity
• Overnight leave
• Emergency department visit
• Hospital or nursing-facility medical leave
• Trial visit or transition activity
• Vacation
• Unplanned late return
• Unexplained absence or missing-resident event

The category should guide the form but remain editable by authorized staff. Do not use a routine absence form to downgrade an emergency or missing-resident response.

Keep absence separate from discharge

A temporary absence does not necessarily end residency. Preserve resident status, room, documents, medication history, and future care while recording that the person is away. Discharge should require its own deliberate workflow and effective date.

Likewise, returning a resident should not create a second admission record. Close the absence and resume the appropriate care schedule.

Plan the departure

For a planned absence, start the record before the resident leaves. Confirm the resident's preferences and the negotiated care plan rather than assuming every departure needs the same approval or escort.

The departure checklist can cover:

1. Departure and expected-return times.
2. Accompanying person and contact method when appropriate.
3. Transportation and mobility support.
4. Medication doses due while away.
5. Required supplies, assistive devices, diet, or instructions.
6. Appointments and follow-up paperwork.
7. Changes to in-home tasks or staffing expectations.
8. The person responsible for notifying the home of a delay.
9. Staff member completing the handoff.

Make optional fields genuinely optional when they are not needed. A resident taking a short independent walk should not be forced into a hospital-transfer form.

Coordinate medications without falsifying the MAR

An absence does not automatically mean a scheduled dose was administered, refused, held, or missed. The medication workflow must preserve what actually happened.

Before departure, identify doses scheduled during the absence and document the authorized plan. Depending on the resident, order, care plan, and applicable requirements, the plan may involve self-administration, an authorized caregiver, a properly prepared supply, a schedule adjustment based on verified instructions, or administration after return.

The absence record should link to, but not write over, the medication order and eMAR. Record:

• Medication handoff completed or not applicable
• Person receiving the supply
• Quantity and packaging when required
• Instructions and supporting document
• Scheduled doses affected
• Supply returned
• Discrepancy or follow-up

The Washington medication-records guide explains the separate medication evidence trail. Never pre-mark doses as given merely because medication left the home.

Reconcile doses when the resident returns

On return, staff should determine what is known about doses due during the absence and use the available eMAR statuses and correction process accurately. If reliable administration evidence is unavailable, do not invent it. Follow the order, facility policy, and notification process for unresolved or late doses.

Handle appointments as linked events

An appointment may create an absence, but the appointment and absence answer different questions. The appointment record contains provider, purpose, preparation, result, and follow-up. The absence record contains physical departure, expected return, custody or escort, and return.

Link the two records so staff can move between them without duplicating notes. The existing appointment tracking guide provides the appointment-specific workflow.

If the resident goes directly from an appointment to a family visit or hospital, extend or transition the absence with history instead of deleting the original plan.

Respond to an overdue return

An expected return time is an operational estimate until the resident's plan or policy makes it consequential. The system can show staged reminders without treating every delay as an emergency.

An overdue workflow should display:

• Expected return time
• Grace or escalation rules based on the resident's plan
• Last confirmed contact
• Responsible staff member
• Attempts to contact the resident or accompanying person
• Safety concerns
• Escalation and notification actions
• Revised expected return, when confirmed

If circumstances meet the facility's missing-resident or emergency criteria, open the appropriate response immediately. Do not wait for a routine reminder to expire.

Document unplanned medical leave

When a resident leaves for emergency or hospital care, staff may not know the return date. Create the absence with an open-ended expected return and link the transfer information, notifications, medication reconciliation, and follow-up tasks.

WAC 388-76-10225 contains several reporting and notification provisions. Its current text includes a twenty-four-hour notification provision involving the department's case management office when a department-paid resident is discharged for more than twenty-four hours on medical leave to a nursing home or hospital. Providers should read the current rule carefully and determine how it applies to the event.

The system should allow staff to record:

• Facility and departure destination
• Emergency versus planned transfer
• Date and time
• People and agencies notified
• Notification confirmation or reference number
• Documents and medication information sent
• Current condition updates
• Return readiness and changed orders

Do not put a sensitive clinical narrative into a broadly visible occupancy dashboard.

Complete a safe return workflow

Closing the absence should require more than clicking “returned.” Capture the actual time and check what changed.

Return reconciliation may include:

• Identity and return confirmation
• Current condition and immediate concerns
• New discharge instructions or orders
• Medication supply returned and reconciled
• Appointment paperwork received
• New equipment or property
• Care-plan or task changes
• Notifications to appropriate staff
• Follow-up owner and due date

If the resident does not return to the same facility, transition to the authorized transfer or discharge workflow rather than leaving an absence open forever.

Protect autonomy and privacy

Absence tracking should support care and safety without becoming unnecessary surveillance. Record only information that is operationally or legally needed. Restrict destinations, contact details, clinical information, and companions to appropriate roles.

Avoid language suggesting that an adult resident needs facility permission for every outing unless a lawful resident-specific arrangement actually applies. The software should reflect the resident's assessment, decision-making support, negotiated care plan, and rights.

Use neutral statuses. “Away as planned,” “return delayed,” and “return confirmed” communicate more accurately than labels implying misconduct.

Design a current occupancy view

The facility dashboard should make current presence understandable at a glance while preserving detail behind permissions. Show:

• In home
• Temporarily away
• Expected back soon
• Overnight leave
• Medical leave
• Return overdue
• Unplanned or safety escalation

Each marker should include the last update and responsible staff member. A number badge should identify open absences from a distance, but color should not be the only signal.

When a user switches facilities, clear resident context and reload the selected home's occupancy data. Direct links must enforce both authorization and facility membership.

Preserve additive history

Staff need to correct expected times, categories, and return details. Corrections should retain the original value, updated value, reason, user, and timestamp.

Never delete a completed absence solely because it was entered for the wrong date. Correct it through an amendment or, if it belongs to a different resident, use a controlled void that remains in the audit trail and requires a reason.

Create operational absence reports

Useful reports include:

• Residents currently away
• Overnight absences by date range
• Medical leaves still open
• Expected returns in the next shift
• Overdue returns and escalation status
• Absences without completed return reconciliation
• Medication handoff discrepancies
• Departures and returns by resident
• Corrected or voided absence entries
• Facility-level occupancy history

Filters should include facility, resident, absence type, status, date range, accompanying person, and responsible user. PDF output should be a formatted report with generated time, page numbers, and applied filters—not a printout of the application screen.

Test every transition

Use demonstration residents to test:

1. A short community outing with no medication impact.
2. An appointment linked to an absence.
3. An overnight family visit with medication handoff.
4. A delayed but safe return.
5. An unexplained absence escalated under policy.
6. An emergency hospital transfer with no known return date.
7. A changed medication order received before return.
8. Returned medication with a quantity discrepancy.
9. A leave converted to discharge.
10. A mistaken resident selection corrected without deletion.
11. Facility switching, direct URLs, mobile use, and offline recovery.
12. Current occupancy and historical PDF reports.

Confirm that absence changes update dashboards and alerts promptly without incorrectly changing medication outcomes or resident status.

Frequently asked questions

Does Washington require AFHs to record resident absences?

The current WAC 388-76-10320 text includes when the resident was absent from the home among required resident-record content. Verify the current rule and facility policy for implementation details.

Is an overnight leave the same as discharge?

No. A temporary leave and a discharge are distinct states. Use separate workflows and preserve the resident's active record during an authorized temporary absence.

Should the MAR show doses as given during leave?

Only if the applicable workflow has reliable evidence that the dose was administered and the entry is made by an authorized person under the relevant requirements. Absence alone is not proof of administration.

What if the resident returns later than expected?

Follow the resident-specific plan and facility escalation policy. Record contact attempts, revised timing, safety concerns, and any escalation without automatically labeling every delay an emergency.

How much destination information should staff record?

Record what is necessary for care, safety, coordination, and applicable requirements. Limit sensitive destination and contact information to authorized users.

Keep temporary leave from becoming a documentation gap

A strong absence workflow connects departure, expected return, care handoff, actual return, reconciliation, and any escalation. It preserves resident autonomy while helping each shift understand current responsibilities.

AFH Manager can connect resident absences, appointments, medication handoffs, occupancy status, return tasks, alerts, audit history, and formatted reports. Providers can test every absence type with demonstration data before using the workflow in resident care.