How to read a Meridian report, and what stands behind each part of it.
A Meridian report is written to support a decision and to withstand later scrutiny.
This page sets out how a Meridian report is put together and how to read it.
Every report follows one method: an agreed question, defined requirements, gathered evidence, findings mapped to that evidence, independent review, a fixed final record. A report on an export-control programme and a report on a supply chain share the same logic.
What changes between reports is the subject. What does not change is the discipline: findings grounded in traceable evidence, confidence stated openly, and an independent check before anything reaches you.
A report is organised so you can move from the headline position down to the detail:
| Part of the report | What it gives you |
|---|---|
| Executive summary | The position in brief, what was asked, what was found, and what it means, written for the person who carries the decision. |
| Scope and basis | What the engagement covered, what it did not, and the standards or reference points the work was measured against. |
| Findings | The substantive results, each grounded in evidence and marked with the confidence it carries. |
| Observations | Matters noted outside the core scope that a reasonable reader would want to be aware of. |
| Recommended actions | Where relevant, clear next steps, what to do, and why it follows from the findings. |
| Sources and basis of confidence | How the findings are grounded, and how their confidence was arrived at, so the reasoning can be checked. |
Each finding states what was found, the evidence it rests on, and the confidence attached to it. Where evidence was expected but not found, the gap is reported as a finding, not omitted. What a report cannot establish is often as important as what it can.
Every finding is evidenced, marked for confidence, and reviewed before delivery.