← Go back

Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team

The 2026–2027 Roadmap: SB 243, EU Grace End, Colorado and the First Annual Report

The short answer

Five dates govern a companion builder's next year, all stated in CompanionGuard's own materials: California SB 243 operative 1 January 2026; EU AI Act Article 50 duties applied from 2 August 2026, with California's AI Transparency Act operative the same date; the EU legacy grace period ending 2 December 2026; Colorado's Chatbot Safety Act joining 1 January 2027; and the first SB 243 annual crisis-referral report from 1 July 2027. This roadmap sequences the work so each date is met by records that already exist.

What is the 2027 compliance roadmap?

The roadmap is the chronological ordering of the duties CompanionGuard tracks — California (2026, reporting 2027), the EU (2026, grace ending December 2026), Colorado (2027) — against the build order the product implies: disclosure and protocol first (free), testing second (free, then harness), evidence third (runtime), reporting last (exports of records kept all along).

Create the free safety kit Next guide All guides

CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.

The calendar, exactly as the product states it

DateEvent (as the product states it)What it demands of you
1 Jan 2026California SB 243 operativeDisclosure, protocol, referral, minor reminders — already owed
2 Aug 2026EU AI Act Article 50 duties applied · California AI Transparency Act operativeTransparency live on both sides of the Atlantic
2 Dec 2026EU legacy grace period endsImplementation claims become operating-evidence questions
1 Jan 2027Colorado Chatbot Safety Act joinsSecond US pack live; records must evidence from day one
1 Jul 2027SB 243 annual crisis-referral report beginsA year of counts, filed to the Office of Suicide Prevention

Two of these dates are already past as this guide is published (November 2026): SB 243 has been operative for ten months and the August transparency dates for three. The roadmap is therefore partly a catch-up plan — and the honest framing for late builders is that the remaining dates reward starting now in a specific way: the December and January dates are near enough that records started today will be young but real, and the July report will consume whatever counting discipline exists by then.

Phase one (now): the free surface, everywhere

Whatever your dates, the first phase is identical and free: kit created, snippet embedded and fresh-visitor-verified, protocol page published with locale-correct resources, minor mode decided and on where minors can reach you, all 12 scenarios passing on real replies. This phase answers SB 243's visible duties and both August transparency regimes' core ask. It is also the phase with no excuses: it costs an afternoon and no money, and every week it is postponed is a week of operation without the artefacts the earliest duties name.

Builders already past this phase should re-verify it against the calendar rather than assuming it: pack wording current, resources re-checked against publishers, scenario set re-run after the year's persona changes. The roadmap's later phases build on this floor; a cracked floor invalidates the storeys above it in a reviewer's eyes.

Phase two (before December): evidence that operates

The December grace expiry and the January Colorado start share one requirement: operating evidence, not implementation intent. That is the runtime phase — Pro's session lifecycle wired, disclosure state tracked per session, minor caps configured, flags routed to humans, exports rehearsed. Sequenced before December, the evidence chain accumulates history across both dates, so a reviewer asking 'show me January' receives a chain that began in November rather than a switch flipped at midnight.

This phase also includes the pack work: Colorado's pack reviewed beside California's, the union of duties documented, banner variants correct per jurisdiction, and the enrolled-text verification the Colorado pack itself demands ('per secondary sources — verify enrolled text') scheduled with counsel before reliance.

Phase three (2027): the reporting year runs itself

With counting running since phase one and decisions sealed since phase two, 2027's work is cadence, not construction: quarterly CSV rehearsals with chain verification, the counting definition frozen and versioned, enforce_break and class-ratio reviews monthly, harness baselines gating every change. When the July window opens, the annual report is the year's exports plus verification — the least dramatic filing in your company's history, which is the entire point.

Keep the roadmap's last row in view all year: every phase's discipline is ultimately in service of a report that does not exist yet, about referrals that have not happened yet, for users who have not met your bot yet. Building records for strangers' future safety questions is the job; the dates just make it schedulable. CompanionGuard remains, at every phase, a toolkit and not legal advice — counsel verifies the law; this roadmap sequences the engineering.

Five actions, one per date on the calendar

  1. SB 243 (live now): confirm the free surface — banner, protocol, referral behaviour, minor reminders — is in place and scenario-tested today, not 'in progress'.
  2. August transparency (live now): audit EU- and California-facing surfaces for disclosure that operates at the interaction, including partner embeds and screenshots.
  3. December 2026: have the runtime wired and the evidence chain accumulating before the EU grace ends, so post-grace questions meet operating records.
  4. January 2027: run the Colorado pack's union-of-duties review with counsel against the enrolled text before the Act joins.
  5. July 2027: arrive with four quarterly CSV rehearsals, a frozen counting definition and a verified chain — the report as an export, not a project.

Worked example: a late starter's nine-month plan

A fictional companion team, Secondwave, discovers this calendar in November 2026 with only a free kit half-configured. Their plan concedes the past honestly (SB 243 duties were owed from January; the record will show the kit's real start date, and they do not backfill claims) and sequences the rest: week one, the free surface completed and scenarios green; weeks two to four, Pro wired — runtime live before December, Colorado pack review booked with counsel for mid-December.

Through 2027 they run the cadence: January's Colorado start met by a chain six weeks old; quarterly exports in January, April; counting definition frozen in January as version 1 with its late start disclosed in the definition note itself. July's report covers the period their records honestly cover. The retrospective line in their plan is the roadmap's thesis: 'We could not recover 2026. We made sure we would never have to recover another year.' The story is invented; every date in it is the product's own.

Frequently asked questions

What are the key dates for companion bot compliance in 2026–2027?

SB 243 operative 1 January 2026; EU Article 50 duties applied and California's AI Transparency Act operative 2 August 2026; EU legacy grace ends 2 December 2026; Colorado's Chatbot Safety Act joins 1 January 2027; the first SB 243 annual report from 1 July 2027 — all as stated in CompanionGuard's own materials.

I am starting late — what matters most?

Sequence by evidence value: complete the free surface now, wire the runtime before December so the chain accumulates across the year-end dates, and start counting immediately — the July 2027 report consumes whatever counting discipline exists by then.

What changes when the EU grace period ends on 2 December 2026?

The review question shifts from implementation intent to operating evidence. Per-session disclosure state and a running evidence chain are the artefacts that answer the post-grace question.

What should be verified with counsel rather than from this roadmap?

The law itself: Colorado's pack is drawn from secondary sources with an instruction to verify the enrolled text, and the SB 243 filing's exact requirements should be confirmed before filing. CompanionGuard is a toolkit, not legal advice.

Does the annual report cover a period before my records started?

Your report can only honestly cover what your records cover. Counting from the free kit starts at creation; runtime decisions from integration. Disclose your record's actual start in the counting definition rather than estimating a past you did not record.

Keep going