Authorship, operation and institutional authority are different responsibilities.

The Programme can remain coherent only if those responsibilities are visible and no role expands through implication. A name, platform, memorandum, logo or technical check does not create authority that has not been granted in a controlling instrument.

  1. Creator
  2. Programme
  3. Operator
  4. Issuer
  5. Assurer
  6. Relying institution

Governance principles

Attribute origin accurately

The Creator and Intellectual Author is credited for the origin and integrity of the concept. Authorship does not become legal operation, record issuance or specialist authority.

Keep specialist authority with the competent institution

Every material decision must identify the entity authorised to make it. Programme coordination cannot substitute for academic, professional, regulatory, safeguarding, editorial or issuing authority.

Keep independent assurance independent

Each assurance organisation performs only the check set out in its own instrument. Its letter or digital statement carries its own scope, source, date, status, limitation, authorised signatory and correction route.

The planned number of assurance organisations is not published until the final entities, scopes and instruments are approved. One assurance does not confirm another, and several assurances do not create accreditation by accumulation.

Controlled relationship architecture

The intended structure uses a multilateral framework memorandum supported by a separate role schedule for each participating organisation. Brand permission, data responsibility and public communications require their own records.

The framework should define shared principles and coordination. It should not erase the parties’ separate legal identity, specialist independence, right to suspend or withdraw, or responsibility for their own statements.

Public use of names and marks

An organisation’s name or logo may appear only where a written permission identifies the exact use, page, language, format, duration and withdrawal rule. Marks should appear inside the organisation’s own bounded record or assurance—not as a general wall of implied endorsement.

Version status

The integrated web baseline follows the Programme Owner’s recorded approval. The public journey remains unnumbered so that no disputed operating sequence is presented as authoritative.

Until a promotion and supersession record identifies the controlling source, approver, effective date and affected material:

  • the approved integrated web baseline governs the public information architecture;
  • the journey is described by meaning rather than a disputed stage count;
  • each live service still requires its own legal, operational, privacy, security and release decision;
  • design approval does not by itself activate a pathway, partner, record or service.

Decision records

Every material governance decision should identify:

  • the question decided;
  • the controlling source and version;
  • the person or body authorised to decide;
  • the scope and exclusions;
  • the effective and review dates;
  • the evidence considered;
  • the pages, systems, records or organisations affected;
  • whether the decision concerns content, design, engineering, operation or public release.

Review policies and controls Understand the Programme

Coordination, original issuance, independent review, relying decisions and correction remain separate responsibilities.
Coordination, original issuance, independent review, relying decisions and correction remain separate responsibilities.