Pre-Publication Review Gate
Direct answer. A pre-publication review gate is a control placed between authoring and serving: an asset cannot go live until a named reviewer has approved that exact artefact, and the approval is recorded as metadata bound to the asset rather than as correspondence about it. A team can choose this control when its publishing policy calls for named approval and retained evidence; this definition does not establish that a gate is required for any organisation, industry or page. Its systems consequence is that publishing stops being a one-way write and becomes a workflow with a queue, an owner and a retained output.
A gate is a publishing control, not an inbox approval
A pre-publication review gate binds a decision to the exact artefact that could be served. The record identifies the artefact version, reviewer, decision, decision time, limitations and release state. An email that says “looks good” without a version or retained output is correspondence; it is not the same control.
Governance frameworks describe policies, processes, documentation and assigned roles as ways to manage risk [nist_ai_rmf] [nist_ai_rmf_playbook]. They do not prescribe this exact gate for every organisation or page.
Minimum retained fields
- Artefact identity. A path, content digest or release identifier points to the reviewed output.
- Named decision owner. The workflow records who can approve, reject or request repair.
- Evidence and limitation check. Factual and outcome-shaped claims are bound to evidence or removed. FTC substantiation policy is relevant context for objective advertising claims, but the applicable legal standard must be determined for the specific organisation and jurisdiction [ftc_substantiation].
- Visible-content check. Structured data describes only what a visitor can see [google_structured_data].
- Release state. The system distinguishes draft, approved, published and superseded artefacts.
- Provenance link. The approval record can be associated with the entity, activity and agent involved [w3c_prov_o].
Where the gate sits
The control belongs between a candidate build and public release. It can cover source, rendered HTML, metadata, schema and links. The Content, Knowledge & AI Visibility Systems guide owns that broader architecture; the gate is one supporting entity inside it.
The diagnostic buyer-path guide shows the specific checks around a diagnostic content cluster. The publishing-pipeline guide explains the retained-record mechanics, while production launch gate is a sibling control with a broader release boundary.
What this control can and cannot establish
| The record can establish | The record cannot establish on its own |
|---|---|
| Which exact artefact was reviewed | That every factual statement is true |
| Who made the recorded decision | That the reviewer had every required legal or domain qualification |
| Which sources and limitations were attached | That a regulator, provider or search system accepted the page |
| Which release state followed the decision | That publication produced rankings, traffic, AI citations or commercial outcomes |
Parent, siblings and next step
Browse the parent Glossary, the D4 systems domain, and sibling definitions for data retention boundary and claim-evidence block. Use Revenue Scan only when the next step is the public diagnostic; this term does not create another form or diagnostic owner.
Claim boundary
This is a systems-control definition, not a statement that a universal review or retention duty exists. It is not legal advice, a compliance conclusion or proof that a published claim is substantiated. Organisation-specific obligations require organisation-specific review.
Source and evidence notes
-
nist_ai_rmfNIST, "Artificial Intelligence Risk Management Framework (AI RMF 1.0)." Governance and risk-management context. Limitation: A voluntary framework; it does not impose this exact control or establish legal compliance. -
nist_ai_rmf_playbookNIST, "AI RMF Playbook." Suggested actions for applying the AI RMF functions. Limitation: Suggested practices only; applicability and implementation remain organisation-specific. -
ftc_substantiationU.S. Federal Trade Commission, "Advertising Substantiation Policy Statement." Context for reasonable basis before disseminating objective advertising claims. Limitation: U.S. policy context, not a universal rule, legal advice or conclusion about any particular claim or organisation. -
google_structured_dataGoogle Search Central, "General structured data guidelines." Visible-content and representation guidance. Limitation: Search-feature eligibility guidance only; it does not establish legal sufficiency or guarantee display. -
w3c_prov_oW3C, "PROV-O: The PROV Ontology." A vocabulary for representing provenance entities, activities and agents. Limitation: A representation model, not a mandated storage design or proof that a decision was correct.