Standards
Methodology
Status
Public

Report
methodology.

How to read a Meridian report, and what stands behind each part of it.

§ A · Purpose

Built to be acted on,
and defended.

A Meridian report is designed to be acted on and, if needed, defended. This overview explains how it is structured and why.

This document sets out, for clients and their stakeholders, how a Meridian report is put together and how to read it. It describes the shape of the deliverable and the reasoning behind that shape. It is not a manual for reproducing the work; it is an account of what you can expect on the page and what stands behind it.

§ B · How a report is built

One method,
whatever the subject.

Every report is the product of the same underlying method, whatever the subject. The work moves from an agreed question, through defined requirements and gathered evidence, to findings that are mapped to that evidence, independently reviewed, and then fixed as a final record. Because the method is common to all our work, a report on an export-control programme and a report on a supply chain share the same logic and the same reliability, even though their content differs.

The common thread

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.

§ C · How a report is structured

From headline
to detail.

A Meridian report is organised so that a reader can move from the headline position to the underlying detail without losing the thread. In broad terms, you can expect:

Part of the reportWhat it gives you
Executive summaryThe position in brief, what was asked, what was found, and what it means, written for the person who carries the decision.
Scope and basisWhat the engagement covered, what it did not, and the standards or reference points the work was measured against.
FindingsThe substantive results, each grounded in evidence and marked with the confidence it carries.
ObservationsMatters noted outside the core scope that a reasonable reader would want to be aware of.
Recommended actionsWhere relevant, clear next steps, what to do, and why it follows from the findings.
Sources and basis of confidenceHow the findings are grounded, and how their confidence was arrived at, so the reasoning can be checked.
§ D · How to read the findings

What we cannot establish,
we still report.

Each finding is written to stand on its own: a clear statement of what was found, the evidence it rests on, and the confidence attached to it. Where a finding is firmly established, it is marked as such; where it rests on a more limited or indirect basis, that is stated plainly. Gaps, places where evidence was expected but not found, are reported as findings in their own right, not omitted. This is deliberate: what a report cannot establish is often as important to the reader as what it can.

§ E · What a report is, and is not

A defensible account,
not a certificate.

  • It is a diagnostic and evidentiary document, a defensible account of a position at a point in time.
  • It is not a legal opinion, a classification decision, or a licensability determination. Those rest with the client and, where required, counsel or the regulator.
  • It is not a certificate. Meridian aligns to recognised standards but does not certify against them.

A report you can act on today and defend tomorrow.