1
Start with the decision you need to support
Why: So every later step ties back to a real reporting or governance question.
Define the program, who will read the information, and what the output must be safe to support.
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.
CIIS is a product of The Lab
Trust by design. Integrity by default.
Claims → metrics → evidence
Claims
What we say we achieve
Metrics
How we measure it
Evidence
What proves it
Operator contract
1. Current state
Where we are and what's known.
2. Safe use
How the claim can be used responsibly.
3. Risk
What could mislead or be misunderstood.
4. Next action
What to do, by whom, next.
5. Evidence trail
Where every claim is traced and stored.
CIIS by design
- Permission: With limitations
- Human review: Required
- Framework alignment: Interpretation, not proof
Transparent. Accountable. Evidence-governed.
You → CIIS → you decide
Six steps. Each one answers what you are doing and why it matters before you move on.
2
Bring in your evidence
Why: So conclusions stay linked to source material, not orphaned numbers.
Use CSV-first bulk import, scoped document workflows, manual entry, or APIs where enabled. Source context stays attached.
3
Structure outcomes and measures
Why: So teams share one view of progress instead of competing spreadsheets.
Turn raw evidence into clear outcome statements, indicators, and assumptions that can be inspected instead of guessed.
4
Review what the evidence supports
Why: So weak or missing evidence is visible before outsiders see the report.
Surface quality signals, gaps, cautions, and limits before the material goes to boards, funders, or partners.
5
See what is ready to share
Why: So you send information that matches the audience, evidence strength, and review status.
Prepare evidence-supported outputs such as the CIIS Executive Impact Summary, with other outputs only where scoped.
6
You decide what happens next
Why: Because software should support judgement, not replace accountability.
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
Request a guided pilot conversation to see how the workflow maps to your outcomes and reporting context.
Test your weakest claim