Background Check Tracking for Adult Family Home Staff

Background check tracking for Adult Family Home staff should show who requires which check, when authorization was submitted, what access is permitted while results are pending, when results were received, whether follow-up is required, and when a new check becomes due. It should not turn sensitive background information into a broadly visible staff profile.

This guide organizes the current Washington framework into a practical tracking workflow. It was reviewed on August 8, 2026. Washington had active background-check rulemaking in 2026, so providers should confirm current WAC, DSHS instructions, and Background Check Central Unit procedures before relying on any person category or deadline.

Use current Washington sources

Washington Adult Family Home background-check provisions are located in WAC 388-76-10160 through 388-76-10181. The current rules address the types of checks, people who need them, access restrictions, fingerprint checks, renewal, conditional employment, disqualifying information, and related procedures.

The Washington Department of Social and Health Services issued a January 12, 2026 Adult Family Home provider letter clarifying current requirements for AFH settings. DSHS also maintains its Background Checks resource page for authorization forms, process materials, and Background Check Central Unit resources.

Software should link to source versions and review dates instead of embedding a permanent eligibility decision tree that may become outdated.

Build a person-to-requirement matrix

The current WAC distinguishes among applicants and affiliates, caregivers, entity representatives, resident managers, household members, volunteers, students, and noncaregiving staff who may have unsupervised access. A system should begin with the person's actual role and access conditions.

Track:

• Person and facility
• Employment, contract, household, volunteer, student, or ownership relationship
• Role start and end dates
• Whether the person may have unsupervised resident access
• Washington name-and-date-of-birth check requirement
• National fingerprint check requirement
• Authorization submission status
• Result status and result-letter reference
• Access restriction while pending
• Review or suitability process when applicable
• Renewal or recheck date
• Supporting document location
• Authorized reviewer and audit history

Do not infer the requirement only from a job title. Two people called “assistant” may have different resident access and therefore different requirements.

Preserve the rule basis

Store the applicable WAC or DSHS source, source date, and staff determination. When rules change, the home can identify which active people were evaluated under an earlier version and need review.

Separate each check and its lifecycle

A single “background check complete” checkbox hides important states. Track the Washington state check and national fingerprint check separately when both apply.

Useful statuses include:

• Not started
• Authorization requested
• Authorization received
• Submitted
• Pending
• Result received
• Review required
• Cleared under applicable process
• Restricted or not eligible
• Expiring
• Renewal submitted
• Superseded

Each status needs a timestamp and responsible user. The result record should preserve the source document and not allow a later result to overwrite earlier history.

Track identifiers without exposing reports

Operational dashboards usually need a confirmation number, result-letter date, check type, status, and next action—not the full report. Store sensitive result documents behind narrow permissions and prevent them from appearing in general scheduling, caregiver, or facility exports.

Control unsupervised access while checks are pending

Background-check status must affect access decisions, not merely produce an administrative reminder. The current rules include restrictions on unsupervised access for specified individuals while required results are unavailable.

Configure an access state such as:

• No resident access
• Supervised access only
• Access allowed under documented conditional process
• Full role access after completed review
• Access suspended pending review

The scheduling and facility-access systems should read this state. They should not independently recalculate eligibility from incomplete data.

If a person is assigned to a shift that conflicts with their restriction, show the reason to an authorized scheduler and block or escalate according to policy. Do not display sensitive criminal-history detail to other caregivers.

Manage two-year state-check renewal

The current text of WAC 388-76-10165 describes the Washington state name-and-date-of-birth background check as valid for two years from the initial date and requires a new authorization submission every two years for individuals listed in WAC 388-76-10161. It also addresses validity of national fingerprint checks under the stated conditions.

The system should calculate upcoming dates from the authoritative completion or initial-conducted date defined by current instructions, not from when a user uploaded a scan.

Use reminders such as:

• Review upcoming
• Authorization needed
• Submission due
• Result pending
• Current check approaching expiration
• Check no longer current

Allow administrators to configure reminder intervals. The due date should remain visible until a qualifying result is recorded and reviewed.

Do not treat fingerprint checks like ordinary renewals

The current WAC treats national fingerprint validity differently from the two-year state check. Model them as separate requirements so the software does not generate a false recurring fingerprint deadline.

Because laws and DSHS procedures can change, store a policy review task rather than hard-coding “indefinite” as an unchangeable product assumption.

Process results through a controlled review

Result received is not the same as hiring approved. An authorized reviewer should confirm the person, check type, result-letter date, source, facility relationship, and required follow-up.

The review record should include:

• Result document identifier
• Received date
• Person identity match
• Check type
• Reviewer
• Review date
• Outcome category
• Restriction or effective date
• Related character, competence, or suitability review when applicable
• Decision evidence and reason
• Notification and access changes

Do not let a user select “clear” without a supporting result. Do not let removal of an uploaded letter silently restore access.

Handle disqualifying or negative information privately

WAC provisions and DSHS processes address disqualifying convictions, pending charges, negative actions, and other review pathways. Software should route these cases to a tightly controlled queue.

Limit permissions for:

• Viewing result documents
• Recording review decisions
• Conducting suitability review
• Changing access restrictions
• Exporting background-check data
• Correcting a completed decision

The operational status can say “not eligible for assignment” or “administrative review required” without broadcasting why. Record employment and legal actions in the appropriate personnel workflow.

Connect background checks to personnel records

WAC 388-76-10198 addresses Adult Family Home personnel records, including criminal-history disclosure and background-check results. Its current text also addresses availability to authorized department staff during employment and for at least two years following employment.

The background-check module should link to the staff record while keeping sensitive documents in a protected category. The existing staff credential tracking guide explains the wider credential workflow; background checks need their own rules, result states, and access controls.

When employment ends, preserve the record and retention calculation. Deactivating the user account must not delete the personnel evidence.

Support multi-facility organizations safely

A person may work in several homes, while some background-check evidence may be organization-level and access decisions remain facility-specific. Separate:

• Person identity
• Check and result
• Organization employment relationship
• Facility assignment
• Role and access restriction

Reusing a valid result should require an authorized determination under current rules, not a drag-and-drop copy from another facility. Preserve which source letter was relied on, who accepted it, and when.

Facility switching should never show another home's household members or applicants merely because the administrator can manage both homes.

Create useful reports

Recommended reports include:

• People missing a required check
• State checks due within a selected date range
• Pending results by submission age
• People restricted from unsupervised access
• Fingerprint requirement and completion status
• Results awaiting authorized review
• Current staff without accessible supporting documents
• Separated staff approaching retention milestones
• Facility assignment conflicts
• Corrections and audit history

Reports should allow filters for facility, role, relationship type, check type, status, due date, reviewer, and access state. Export only the minimum necessary columns for the report's purpose.

Test the complete tracking flow

Use demonstration people to test:

1. A newly hired caregiver requiring both check types.
2. A household member requiring the applicable state check.
3. A volunteer who may have unsupervised access.
4. A person restricted to supervised access while pending.
5. A result that requires authorized review.
6. A two-year state-check renewal.
7. A prior fingerprint result considered under current procedures.
8. A worker assigned to multiple facilities.
9. An expired or invalid check blocking assignment.
10. Employment termination with record retention.
11. Additive correction of an incorrect date.
12. Facility switching, direct URLs, reports, and mobile layouts.

Verify that alerts update after a qualifying result is reviewed and that unauthorized users cannot discover sensitive outcome details.

Frequently asked questions

Who needs a background check in a Washington AFH?

Current WAC 388-76-10161 identifies several categories, including applicants and affiliates, specified workers, household members, volunteers, students, and certain noncaregiving staff. Review the complete current rule and DSHS guidance for each person.

How long is a Washington name-and-date-of-birth check valid?

The current WAC 388-76-10165 text states two years from the initial date it is conducted and describes a two-year authorization-submission cycle. Confirm the current rule and BCCU procedure.

Should caregivers see background-check reports?

Generally, operational users should see only the assignment or access status they need. Restrict source reports and review details to authorized roles.

Can the software automatically decide whether someone is eligible?

It can enforce configured restrictions and surface required reviews, but an authorized person should apply current rules and DSHS procedures to the actual result.

What happens when rules change?

Store the source version, review date, and affected population. Update the requirement matrix and create reassessment tasks without rewriting historical decisions.

Make clearance status actionable and private

Reliable background-check tracking connects the correct person category, required check, submission, result, authorized review, access restriction, renewal, personnel record, and audit history. It helps prevent expired evidence and unsafe assignments without spreading sensitive information.

AFH Manager can help providers track background-check requirements, due dates, restrictions, supporting documents, facility assignments, alerts, and formatted reports. Test the workflow with demonstration staff and verify current Washington instructions before production use.