Artificial Intelligence Policy Tracker

Keep and run a protocol to detect suicidal ideation and self-harm and refer users to crisis resources

Download: JSON · MarkdownUnder Washington AI companion chatbot law (ESHB 2225), ESHB 2225 (Chapter 168, Laws of 2026), sec. 5(1) and (2)

Pending review · linked to the official source, waiting for a reviewer to confirm it (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
Record updated on 12 Nov 2026 · Summary · official source last checked
On this page 8 sections

In brief

Keep and run a protocol to detect suicidal ideation and self-harm and refer users to crisis resources is a legal requirement under the Washington AI companion chatbot law (ESHB 2225) in Washington State (United States) (ESHB 2225 (Chapter 168, Laws of 2026), sec. 5(1) and (2)). It applies from 1 January 2027. The record carries 2 evidence examples.

Nature
Legal requirement
Source reference
ESHB 2225 (Chapter 168, Laws of 2026), sec. 5(1) and (2)
Applies from
1 January 2027
Who it binds
Provider / developer, Deployer / user organisation
Evidence examples
2
Controls that meet it
2
Official source
Open official text
Verification
Pending review · source-linked

What does it require?

An operator may not make available or deploy an AI companion chatbot unless it maintains and implements a protocol for detecting and addressing users' suicidal ideation or expressions of self-harm. The protocol must include reasonable methods to identify expressions of suicidal ideation or self-harm, eating disorders included; give automated or human-mediated responses that refer users to appropriate crisis resources such as a suicide hotline or crisis text line; and include reasonable measures to prevent the chatbot generating content that encourages self-harm or describes how to do it.

Practical action

Write the protocol down before launch: detection methods that cover eating disorders, a referral response naming crisis lines, and output safeguards against self-harm instructions or encouragement; test it and keep it in operation.

Who does it apply to?

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • supportsTechnical measureAI security or safety lead · at launch and on material change
    Adversarial and red-team testing for generative AI

    Serves 12 recorded duties · evidence: Red-team exercise report, Red-team rules of engagement and scenario library, Adversarial findings tracker

    Testing detection of self-harm expressions and that the model will not encourage or describe self-harm.

  • supportsProcessIncident coordinator · continuous
    AI incident management and regulatory reporting

    Serves 16 recorded duties · evidence: AI incident response playbook, AI incident record, Incident report to an authority

    An escalation path for crisis events, where the protocol uses human-mediated responses.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
The written protocol, with its detection methods and referral messagesdocument
Test results for detection, referral and blocking of self-harm contentdocument

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under Washington AI companion chatbot law (ESHB 2225) (ESHB 2225 (Chapter 168, Laws of 2026), sec. 5(1) and (2)).

When does this obligation apply?

It applies from 1 January 2027.

What evidence shows compliance?

A reviewer would expect: The written protocol, with its detection methods and referral messages; Test results for detection, referral and blocking of self-harm content.

Which controls satisfy this obligation?

Adversarial and red-team testing for generative AI; AI incident management and regulatory reporting.

What should an organisation do in practice?

Write the protocol down before launch: detection methods that cover eating disorders, a referral response naming crisis lines, and output safeguards against self-harm instructions or encouragement; test it and keep it in operation.

Cite this record

AIPolicyTracker (2026). “Keep and run a protocol to detect suicidal ideation and self-harm and refer users to crisis resources (Washington AI companion chatbot law (ESHB 2225))” [AIPT-OBL-0126, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0126 (accessed 12 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0126: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Washington State Legislature: HB 2225 (2025-26) bill summary, Washington State Legislature, https://lawfilesext.leg.wa.gov/biennium/2025-26/Pdf/Bills/Session%20Laws/House/2225-S.SL.pdf.

BibTeX
@misc{aipolicytracker2026_keepandrunaprotocoltodet,
  author       = {{AIPolicyTracker}},
  title        = {{Keep and run a protocol to detect suicidal ideation and self-harm and refer users to crisis resources (Washington AI companion chatbot law (ESHB 2225))}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-washington-eshb-2225-self-harm-protocol}},
  url          = {https://aipolicytracker.org/obligations/us-washington-eshb-2225-self-harm-protocol},
  urldate      = {2026-11-12},
  note         = {Data licensed CC BY 4.0. Accessed 12 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.