Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
Annual-Report CSV: What CompanionGuard's Export Contains and How to Use It
The short answer
On Pro and Team, the referral metrics dashboard exports an annual-report CSV — the operator's referral counts for a reporting period, drawn from the counts-only metrics and the runtime's sealed decisions, with runtime evidence included in the same export family. It exists for one named purpose (California's annual crisis-referral report, from 1 July 2027) and serves every other evidence request along the way. The file contains counts and classes — never user identities or message text, because the underlying records hold none.
What is the annual-report CSV?
The annual-report CSV is a dashboard export (Pro and Team) that renders a period's crisis-referral record as a spreadsheet-ready file: referral counts accumulated as counts only, backed by the runtime's per-decision evidence (signal classes, actions, timestamps) which exports alongside it. It is the filing input for SB 243's annual report duty and the standard answer to 'show us your referral numbers'.
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.
From events to a file: the pipeline
The export is only ever as honest as its sources, so trace the pipeline. At the bottom: referral events recorded as counts only at the moment they occur (component shown, component clicked), and runtime decisions sealed per event in the hash chain. In the middle: the dashboard aggregating those into period views — referrals by period, class distribution, break enforcements, disclosure coverage. At the top: the CSV, a flat rendering of the period's aggregates, with the runtime evidence exportable in the same flow so the counts can be traced back to sealed decisions.
That traceability is the export's real value. A bare CSV of totals is a claim; a CSV whose totals recompute from a verified chain is evidence. When you rehearse the export quarterly (you should), verify the chain in the same sitting, so the habit pairs the number with its proof while both are small.
What is in the file — and what cannot be
Contents follow the records: period referral counts and the aggregates the dashboard tracks, with runtime evidence fields where the decision-level export is included — signal class, action, timestamp, session reference, hashes. The cannot-be list matters more: no names, no user IDs, no IPs, no message text, no parent contacts — not redacted from the file, but absent from the records the file is drawn from. Redaction is a process that can fail; absence is a property that cannot.
That property simplifies every conversation the file enters. Filing it does not expose users. Sharing it with a partner does not require a data-processing negotiation about its contents. Archiving it for years does not accumulate a sensitive-data liability. The export inherits the privacy architecture whole — the privacy guide explains the design it inherits from.
Rehearsal: the quarterly export drill
The teams that file calmly in July 2027 will be the ones who exported in October 2026 and hated the surprises early. The drill: export the quarter, reconcile totals against the dashboard's live view, verify the underlying chain segment, file the export with a dated note (period, definition version, verification result), and log any discrepancy as a bug with the same seriousness as a product defect. Discrepancies found in rehearsal are gifts — usually a counting-definition ambiguity or a wiring gap — and both are cheap in rehearsal and expensive at filing.
Pin your counting definition to the drill: which events count as referrals, stated once, versioned, and referenced in every export note. The definition guide works through the candidate events and their edge cases; the annual-report guide covers the duty the drill serves.
Beyond California: the export's second life
Even for builders outside California's reporting duty, the CSV becomes the standard artefact for safety questions: app-store reviews, partner diligence, insurer conversations, press enquiries after an incident elsewhere in the industry. In each case the file's virtues are the same — period counts that trace to sealed decisions, in a format a non-technical reviewer can open, containing nothing that endangers a user. Build the export habit before anyone asks, because the asking rarely comes with a deadline you chose.
Keep the exports themselves under the same discipline as the chain: stored in your own infrastructure, dated, unedited after the fact (a corrected export is a new export with a note, never a silent overwrite). The archive of quarterly exports becomes, over time, the longitudinal story of your guardrail — referrals rising with audience, class ratios shifting with your user base, disclosure coverage unbroken. That story, boring and continuous, is what trust actually looks like on paper.
Five actions for an export that files itself
- Export quarterly from the first quarter you have runtime data — rehearsal is where format surprises belong.
- Reconcile each export against the dashboard totals and verify the underlying chain segment in the same sitting; log discrepancies as bugs.
- Attach a dated note to every export: period, counting-definition version, verification result.
- Confirm the file's field list on sight: counts, classes, actions, timestamps, hashes — and no identity or text fields, ever.
- Archive exports unedited in your own storage; corrections are new exports with notes, never silent overwrites.
Worked example: four rehearsals and a boring filing
A fictional companion, Solstice, begins quarterly exports in Q4 2026. The first rehearsal finds a real discrepancy: dashboard totals for October exceed the CSV by 11 referrals. The cause, once traced, is definitional — the dashboard's live view counts component clicks from the protocol page, while the export's definition counted runtime decisions only. The team does not 'fix the numbers'; it fixes the definition document (both lines, reported separately), notes version 2 in the export log, and re-exports.
By the July 2027 window, Solstice has four clean rehearsals, a stable definition and a year of counts that reconcile three ways: component metrics, runtime decisions, filed totals. The filing work is an afternoon of verification. The story is invented; the export, the dashboard and the duty are the product's own.
Frequently asked questions
What does the annual-report CSV contain?
The period's referral counts and dashboard aggregates, with the runtime's decision evidence (signal class, action, timestamp, session reference, hashes) exportable in the same flow — drawn from counts-only metrics and the sealed evidence chain.
Does the CSV contain any user information?
No. The records beneath it hold counts, classes, actions, timestamps and one-way hashes — no names, user IDs, IPs or message text exist to export. The absence is architectural, not a redaction step.
Which plans include the CSV export?
The referral metrics dashboard and annual-report CSV export are Pro ($29/month) and Team features. Referral counting itself starts with the free kit's component metrics.
How do the counts trace back to evidence?
Runtime decisions are sealed per event in the hash chain; the export's decision-level totals recompute from those entries, and the chain verifies by recompute-and-compare. Rehearse both together quarterly.
Is the CSV the SB 243 filing itself?
It is the filing input: the counts the California pack's annual report (from 1 July 2027, to the Office of Suicide Prevention) requires. Verify the filing's exact current requirements against the enrolled text or with counsel — CompanionGuard is a toolkit, not legal advice.
Keep going
Related guides: SB 243 Annual Report: Counting Crisis Referrals Before July 2027 · What Counts as a Crisis Referral? Defining the Event Your Reports Depend On · Counts-Only Referral Metrics: What the Dashboard Shows and Why It Shows Nothing Else
Put it to work: Create the free kit · Eval harness · Scenario tests · Crisis runtime · Disclosure packs · Pricing · All CompanionGuard guides