Alliance

Reports

Alliance reports turn technical work, market learning and programme outcomes into material that others can use.

For
Prospective members, partners and stakeholders
Last reviewed
2026-08-05
Review cycle
Review every 6 months

What the collection contains

Alliance reports turn technical work, market learning and programme outcomes into material that others can use. They should state who produced the report, the evidence base, publication date, review status and whether conclusions represent the Alliance or a contributing group.

Select by the question you need to answer

Readers can use reports to understand a problem, compare evidence or inform a decision, but should not treat an undated summary as a substitute for a specification or current provider statement.

What a useful report should disclose

1. Scope

Begin with the question, audience, system boundary and claims the report is intended to support.

2. Evidence

Link primary sources and distinguish measurements, expert judgement, programme observations and future expectations.

3. Currency

Show publication and review dates, version significant updates and keep time-sensitive product or policy claims easy to verify.

Evidence, status and currency

Reports may describe a particular implementation, workload or programme. Do not generalise the result to every CHERI system without supporting evidence.

Use the Alliance’s current governance, membership and programme pages for organisational facts. Distinguish formal decisions from explanatory material.

Publication routes

Browse the evidence

Choose a report by the decision it supports, then follow its references to the underlying specification, data or implementation.

Browse reports and white papers