1 · Intake
- outcomes_q2.csv
- Youth wellbeing survey
- Case notes extract
How it works
How CIIS works, from your data to your decision
A practical path: bring in evidence, review what it supports, check what is ready to share, then act with the limits visible.
CIIS is for teams that must explain what the evidence supports, what should stay internal, and why something is ready to share (or not yet). The workflow keeps source evidence, interpretation, and limits visible.
Today the path is guided: demos and pilots are scoped to your reporting context rather than offered as a generic self-serve signup.
You → CIIS → you decide
Scroll through an illustrative walkthrough of how evidence moves from intake to a governed summary, with people still accountable for what is shared.
2 · Structure
Outcomes
Measures
Evidence
3 · Review
Our program improved youth wellbeing.
- Outcome named without source or scope
- Causality stated or implied without design support
4 · Permission
Report-eligible
With limitations
Internal only
Blocked
5 · Decide
Survey and attendance data suggest improved self-reported wellbeing among participants who completed the program, with limits on comparability.
Human approve
Sample illustration only. A guided pilot uses your evidence, review context, and governance rules, not this demo.
ciis · evidence workspace · illustrative preview
CIISPilot projectYouth wellbeing Q2
Scene 1 of 5: Intake. Sample illustration only. A guided pilot uses your evidence, review context, and governance rules, not this demo.
- Step 1: Start with the decision you need to support. Define the program, who will read the information, and what the output must be safe to support.
- Step 2: Bring in your evidence. Use CSV-first bulk import, scoped document workflows, manual entry, or APIs where enabled. Source context stays attached.
- Step 3: Structure outcomes and measures. Turn raw evidence into clear outcome statements, indicators, and assumptions that can be inspected instead of guessed.
- Step 4: Review what the evidence supports. Surface quality signals, gaps, cautions, and limits before the material goes to boards, funders, or partners.
- Step 5: See what is ready to share. Prepare evidence-supported outputs such as the CIIS Executive Impact Summary, with other outputs only where scoped.
- Step 6: You decide what happens next. CIIS supports the decision record. It does not decide what to fund, prioritise, or approve.
Every claim gets a permission status
After review, each outcome statement carries one of four statuses, so teams know exactly what can leave the building and what cannot.
Report-eligible
Supported and safe to include.
With limitations
Usable, but caveats must stay visible.
Internal only
Useful for learning, not external reporting.
Blocked
Not ready to claim.
See the full evidence stack model on the What CIIS does page.
What CIIS will not do
- Replace executive, clinical, policy, or program oversight judgement.
- Turn weak evidence into certainty.
- Pretend a synthetic product view is a deployed client record.
- Make compliance claims that depend on your organisation's processes.
Walk through your use case
Scope a CIIS pilot to see how the workflow maps to your outcomes and reporting context.
Scope a CIIS pilot