The six numbers under governance
These are the six numbers whose refresh triggers this protocol. Any change to any of them is a full-sweep event.
| Number | Current value | Where it appears verbatim |
|---|---|---|
| Cases resolved (Y1) | 31 cases | Frame-lock L5 · hero page numbers strip · dashboard footer · email footers · LI post 4 |
| Debt resolved (Y1) | $1.82 million | Frame-lock L5 · hero page numbers strip · dashboard footer · email footers · LI post 4 |
| Average resolution time | 23 days | All footer envelopes · Ellen composite paragraphs · frame-lock reference |
| K10 psychological-distress drop | 52% | All footer envelopes · frame-lock numbers strip |
| Cost per case (audited average) | $1,840 | Frame-lock L5 & L8 · hero ask ladder featured tier · donate.html tier button · Meta ask cards · email ask blocks · dashboard case-conversion · LI post 4 |
| Direct-service ratio | 87c per dollar | Frame-lock L5 · all footer envelopes |
What triggers a refresh
Trigger A · Annual audit close
Full financial-year audit completed and signed. Typically Q3 (Sep–Nov) of the following year. Substitution is Y1 → Y2 numbers — a full six-number replacement.
Trigger B · Interim assurance update
Board-approved interim numbers between full audits (e.g. mid-year assurance letter). Substitution may be partial (one or two numbers). Handled per this protocol but with reduced sweep.
Trigger C · Material correction
An error is identified in a previously published number. Rare. Handled with priority and full transparency: the historical claim is retracted, the corrected number is published, and the correction is logged.
Trigger D · Regulatory disclosure requirement
ACNC or ATO requires a specific disclosure format. Numbers themselves may not change; presentation may. Governed same way.
The refresh sweep · 7 steps
The sweep runs left-to-right, no step skipped, no step re-ordered. Owned by Carla; executed collaboratively with Corrina.
| Step | Owner | What happens |
|---|---|---|
| S1 | Laurence | Refresh source (audit letter, assurance letter, correction memo) received and archived. Numbers extracted verbatim into a single Y2-numbers.txt file. Never typed twice. |
| S2 | Carla | Refresh sprint scheduled. Sprint number allocated. Sprint accent colour chosen (per Sprint 56/57/58/59/60/61/62 discipline). Backlog item created. |
| S3 | Corrina | Grep sweep of the repo. Every occurrence of any of the six numbers logged with file+line reference. Includes: hardcoded strings, image alt text, meta descriptions, D1 seed data, migration files, comments. |
| S4 | Corrina | Substitution PR built. Every occurrence replaced verbatim. New sprint accent applied to the sprint's summary artefact page. Frame-lock updated as source of truth for downstream artefacts. |
| S5 | Carla | Full artefact review. Every downstream artefact (hero, dashboard, emails, LI posts, Meta pack, dark-period one-pager, this protocol) reviewed for numbers coherence. Any drift held for restatement. |
| S6 | Laurence | Compliance envelope review across all touched files. ACL 387398, DGR-pending, ACNC-pending language re-checked for consistency with new numbers. |
| S7 | Lisa | Final sign-off. Reads the frame-lock and hero with new numbers substituted. Confirms voice still holds. Merges the PR. |
- A number is found in a place S3 did not identify. (Grep discipline failure.)
- Two different values of the same number are found in different artefacts. (Provenance failure.)
- A number appears in a screenshot / image asset. (Requires image regeneration; blocks sweep.)
What we never do
Never round the numbers "for clarity"
$1.82M is not $1.8M. $1,840 is not $1,800 or "about two thousand". 87c is not "roughly 90%". Verbatim means verbatim.
Never extrapolate from Y1 to a future projection
"On track for $3M in Y2" is not a Y1 audited number. Projections belong in board papers, not in public marketing artefacts.
Never mix aggregation windows
"31 cases resolved this year" (Y1 audited) does not become "38 cases resolved to date" (Y1 + Y2 running total) without a full protocol run. Numbers are frozen at their audit window.
Never introduce a seventh verbatim number without governance
If a new number becomes central (e.g. "K10 average pre-intervention"), it goes through a sprint before it appears anywhere. It joins the six — it does not slip in beside them.
Expected cadence
| Refresh type | Frequency | Typical timing |
|---|---|---|
| Full Y+1 audit | Annual | Q3 following financial year close. First Y2 refresh: expected Q3 2027 for FY26-27 numbers. |
| Interim assurance | Half-yearly | Optional. Typically Q1 following the half. Substitutes partial numbers only if material. |
| Correction | Ad-hoc | Within 5 business days of identification. Priority over routine sprints. |
| Regulatory-mandated | Ad-hoc | Within regulator-specified window. Priority over all non-legal work. |
What this protocol does not cover (and why)
Aggregate campaign metrics
Dashboard live totals refresh automatically from D1. Not governed by this protocol.
Financial statements themselves
Auditor-signed statements are governed by the Audit & Risk Committee, not by marketing. This protocol handles their public expression.
Verbatim quotes from beneficiaries
No verbatim beneficiary quotes are used (composite discipline). This protocol governs numbers, not narrative.
Constitutional-clause references
Constitutional references are governed by /marketing-constitutional-congruence, a separate register.