Multi-Facility Adult Family Home Management Software

Managing several Adult Family Homes requires two views at once. Each home needs a clear local workspace for its residents, caregivers, medications, documents, and daily work. The operator also needs portfolio visibility across facilities without blending records or weakening the responsibility of the person managing each home.

Multi-facility Adult Family Home software should provide that separation and oversight deliberately. A facility selector alone is not enough. The system needs tenant boundaries, facility-specific roles, safe switching, resident isolation, scoped reports, attributable actions, and useful cross-home summaries.

This guide explains how to evaluate multi-facility design, including Washington considerations, daily navigation, permissions, medications, pharmacy access, reports, onboarding, and testing.

Multi-facility does not mean one combined chart

An operator may own or oversee multiple homes, but every resident belongs to a specific licensed setting and care workflow. The application should keep the resident record inside the correct facility while allowing authorized portfolio users to move between homes or view approved summaries.

The design should answer these questions on every important screen:

• Which facility is active?
• Which resident belongs to that facility?
• Which role is the current user exercising?
• Will this action affect one home or several?
• Can the user see the source facility behind a count or alert?

A global search that returns residents from every home without strong facility identification creates risk. A cross-home dashboard that shows a total but cannot open the filtered source records creates limited value.

Understand Washington's management boundary

Washington providers should review the current official rules and Department resources when structuring multi-home operations. WAC 388-76-10036 addresses multiple Adult Family Home management. It states that when more than one home is licensed to a provider, each home must have one person responsible for managing overall care delivery, and the responsible person is designated to manage only one home at a given time.

Software should not flatten that organizational responsibility into an anonymous portfolio account. It can show the designated local manager, clarify facility assignments, and support centralized oversight while keeping facility-level accountability visible.

The Washington DSHS provider resources include current forms and materials, including management-agreement and negotiated-care-plan resources. Technology can organize the work; providers must determine how their structure meets current requirements.

Design the active facility control

The facility selector should be visible, searchable, keyboard accessible, and understandable on desktop and mobile. Search can use authorized facility name or ID. Results may include city or another non-sensitive distinguishing detail when names are similar.

Switching should be an explicit action. After the switch:

• Resident lists come only from the new facility.
• Resident-specific drafts are cleared or deliberately reassigned through a safe workflow.
• Medication, incident, document, appointment, and task filters reset appropriately.
• Page headings and breadcrumbs display the new facility.
• Old browser history cannot silently apply an action to the prior context.

The system may preserve nonresident information such as a generic medication search result when useful, but it should require a new resident selection and clear confirmation before saving.

Separate permissions by facility and function

A user can hold different roles in different homes. Someone may be an owner across the portfolio, a manager in one facility, and have no access to another. The authorization model should support that reality instead of assigning one universal role.

A permission matrix can include:

| Role example | Facility scope | Typical capabilities | | --- | --- | --- | | Portfolio owner | All authorized homes | Cross-home summaries, users, reports, configuration | | Resident manager | One home | Local residents, caregivers, review, documents, reports | | Caregiver | Assigned home or homes | Authorized daily resident work | | Pharmacy user | Approved facility relationships | Resident-specific medication orders and refills | | Family user | Approved resident relationship | Limited resident communication or records |

Test permissions in the underlying action, not only the navigation. A user should not retrieve another facility's record by changing a URL or reopening an old tab.

Keep resident identifiers facility-specific

Resident names are not unique. Internal identifiers must connect every note, medication, document, incident, task, appointment, and report to the correct resident and facility.

Use two fictional residents with the same name in two test homes. Search, create records, export reports, change facilities, and use Back. Confirm that the system never merges results or retains the wrong person.

Cross-facility transfer is different from accidental reassignment. A deliberate transfer workflow should preserve the prior home's history, create the correct destination context, define which current information carries forward, and record authorized actions. Simply changing a facility field may damage historical meaning.

Make local dashboards actionable

The facility dashboard should show work for that home: medication exceptions, overdue tasks, expiring documents, upcoming appointments, incident follow-up, caregiver coverage, and other actionable items. Counts must link to filtered records and update when the underlying work changes.

Do not crowd the local dashboard with portfolio statistics a caregiver cannot act on. Owners can use a separate cross-home view.

Tabbed lists often communicate work better than a wall of cards. Prioritize current actions, then trends and totals.

Give portfolio users drill-down visibility

A portfolio dashboard may summarize:

• Active residents and capacity by facility
• Today's medication exceptions by facility
• Overdue care tasks
• Open incident follow-up
• Caregiver coverage gaps
• Expiring staff, resident, or facility documents
• Upcoming appointments
• Pharmacy orders and refills needing action
• Recent access or audit events

Every total should identify its scope and generated time. Selecting a count should open the corresponding facility-filtered list. Cross-home users need a way to compare without losing the facility source.

Avoid ranking homes from raw counts alone. A facility with more residents or different needs may naturally produce more events. Operational review requires context.

Manage caregivers across homes without shared accounts

One caregiver may work in several authorized homes. Use one individual identity with explicit facility memberships and role assignments. This preserves accountability while avoiding duplicate logins.

The caregiver's schedule can show assignments across authorized homes, but opening a shift should activate or clearly identify the correct facility. Resident information from other homes should not appear in the same daily workspace unless intentionally designed and authorized.

When employment or assignment changes, remove the relevant facility access without erasing historical shifts, medication administrations, notes, or incidents.

The caregiver scheduling software guide explains open shifts, availability, time records, and access relationships in more detail.

Protect medication workflows

Medication actions require especially strong context. Prescription entry, Give Medication, PRN follow-up, late corrections, refill requests, incoming pharmacy orders, and MAR reports should all display facility and resident.

An operator viewing a cross-home alert should land in the correct facility before documenting. The system should prevent an administration event from being recorded for a resident who is not in the active facility.

For pharmacy users, the active facility control must search only authorized relationships. Switching facilities clears the resident. An incoming medication order requires facility acceptance before it creates an active prescription and future MAR events.

Use the pharmacy and AFH coordination guide for the complete multi-facility pharmacy boundary.

Scope documents and deleted items

Facility licenses, policies, drills, maintenance records, staff documents, and resident files need appropriate scopes. A global template may be shared, while the completed record or signed document belongs to a specific home or resident.

Deleted items should retain facility context. Restoration must return the record to the correct place. Permanent deletion should require appropriate permission and deliberate confirmation.

Portfolio users can see expiration summaries across homes, but local managers should not receive unrelated facility files.

Build reports for local and portfolio use

Local reports need resident, facility, date, status, and staff filters appropriate to the record. Portfolio reports may compare or combine facilities only for authorized users.

A cross-home report should:

• State which facilities are included
• Preserve the facility column on every row
• Explain filters and time zone
• Group or subtotal appropriately
• Avoid combining residents with matching names
• Respect facility permissions at generation time
• Produce a clean PDF or structured export

Reports should not rely on the dashboard's visual layout. Print and PDF should generate the report itself.

Onboard one facility at a time

Even when the platform supports bulk setup, phased onboarding can reduce risk. Configure the portfolio structure, then validate each facility's residents, medications, caregivers, documents, and reports.

Use the AFH software migration checklist for data inventory, medication reconciliation, testing, cutover, and downtime.

Do not copy a facility configuration blindly. Shared templates can accelerate setup, but resident needs, staff assignments, pharmacies, documents, and local workflows require review.

Demonstration scenarios

Ask the vendor to perform these tests:

1. Create two facilities with similar names and display distinct IDs.
2. Assign one manager to each and show the portfolio owner's view.
3. Give a caregiver access to one home, then both, with different roles.
4. Create residents with the same name in each facility.
5. Start a resident medication draft, switch homes, and show what clears.
6. Open an old resident URL after the switch.
7. Submit a pharmacy order to one home and confirm the other cannot see it.
8. Resolve a medication alert and verify local and portfolio counts update.
9. Export local and cross-home reports with facility attribution.
10. Remove one facility membership while preserving historical activity.
11. Delete and restore a document in the correct facility.
12. Demonstrate what support personnel can access and how that access is recorded.

Use ordinary caregiver and pharmacy accounts, not only a super-administrator.

Security and operational questions

Ask how the platform separates facility data, validates authorization, handles cached information, protects exports, records facility switching, and tests tenant isolation. Review authentication, session timeout, account recovery, audit history, backups, incident response, and deletion.

Determine which users can run cross-facility searches or exports. Those capabilities should be uncommon, visible, and attributable.

The product should also remain understandable during partial failures. A failed facility switch must not leave the header showing one home while the body displays another.

Frequently asked questions

Can one owner manage several Adult Family Homes in one account?

Software can support authorized portfolio oversight, but each facility's residents, roles, records, and management responsibilities must remain clear. Review current licensing and organizational requirements.

Should a caregiver have a separate login for every home?

Not necessarily. One accountable identity can hold separate facility memberships and permissions. The application must keep the active facility explicit.

Can portfolio reports combine resident information?

Authorized reports can summarize or group data across homes, but every record should preserve facility and resident attribution. Permissions must apply when the report is generated.

What should happen when switching facilities during a draft?

Resident-specific context should not carry over. The application can warn, save within the original facility, or discard safely. Generic draft information may be preserved only with a clear new resident confirmation.

Does multi-facility software replace local management?

No. It can support oversight, communication, and records. It does not eliminate facility-level roles or provider responsibilities.

Centralize oversight without mixing homes

Good multi-facility software creates a clean hierarchy: portfolio, facility, resident, and record. It lets authorized leaders see patterns while local users work inside the correct home. Every switch, search, alert, medication, document, and report retains its source.

AFH Manager supports explicit facility navigation, facility-scoped residents and roles, pharmacy relationships, local workspaces, and portfolio reporting. Operators can test it with similarly named facilities and residents to verify the boundaries before onboarding multiple homes.