Skip to main content
Command Center, the dashboard, answers one question at the start of a working session: what do our checks actually establish about the content we produced, and what needs a person’s decision now? Every figure is computed from recorded verification and review results for the selected window of 7, 30, or 90 days. Nothing is estimated. For production volume, success rates, and quality scores, use Analytics.

Assurance posture

Coverage counts violations as decided, so it measures how much verification reached a verdict, not how much content passed. Source wording match shows that a citation’s words appear in its source; it does not establish that the claim is true. An undecided object is a separate outcome, never a pass.
Export posture downloads these figures as a JSON assurance report for audit or internal reporting.

Evidence over time

The evidence trend reports daily counts of verified, violating, and undecided objects, with verification coverage on a 0–100% scale. Object counts differ from finding counts: one object can carry several findings. Days are UTC calendar dates of content creation; a 7-day window covers seven dates including today. A day with nothing to measure is reported as a gap, never as a pass or an interpolated value.

Work that needs a decision

Overdue reviews, validity scans that found broken sources, coverage gaps, and policy exposure are reported together, most urgent first: breached review windows, broken sources, and near-term deadlines come before informational gaps. Each item states its severity, the review qualification it needs where one applies, and the action that resolves it. Review workload is summarised by role, with pending and overdue counts; overdue reviews are a subset of pending. Work them in the Review Queue.

Posture by vertical

For every vertical in the catalog, Command Center reports its enforcement mode, active verifiers, pooled coverage, documents produced, violations stopped, and undecided objects. A vertical with no documents in the window has no history to report. Advisory verticals report violations without blocking publication, and their stopped count is marked as advisory so it is not read as a clean blocking result.

Getting started

New workspaces have a four-step checklist: create a first draft in Studio, add a brand voice from a writing sample, connect a publishing destination, and publish a reviewed piece. Each step is marked complete from saved workspace activity, and the checklist closes when all four are done.

Using Command Center

1

Clear what is urgent

Resolve overdue reviews and broken sources first. These are the items most likely to hold a release or put published content at risk.
2

Read coverage before scores

A high pass rate on low coverage means little was decided. Check coverage by vertical before treating results as broad assurance.
3

Follow evidence problems to the documents

Use Evidence Exposure to find content built on revoked or superseded sources, and each document’s dossier for its full record.

Limits

  • Command Center reports what recorded checks decided. Content generated before verification was recorded, or in a vertical without verifiers, contributes nothing to coverage.
  • Reviewer qualifications are declared by workspace administrators; Command Center counts reviews against them but cannot confirm a person’s professional credentials.

Analytics

Reliability, quality, and throughput over the same windows.

Decision Log

The record of governance decisions across the workspace.
Last modified on October 25, 2026