Stage 04 of 06 · Review

Review: every scene traced to its source, and checked.

A trace link binds one scene to one paragraph of one revision of one source document. Objectives, requirements and test questions are linked the same way. Your people review, approve and publish, and nobody approves their own work.

  • Approval to produce is refused until every scene cites a source
  • A procedural step is never verified on narration alone
  • Every decision on the audit trail

What Review covers

Each requirement checked against evidence. The customer decides.

Traceability per scene

Traceability per scene, not per video. The citation for whatever is playing sits on the player, and approval to produce is refused until every scene cites a source.

  • Numbered objectives (LO-001…) and requirements (REQ-001…), each with a source locator and acceptance criteria
  • Mandatory procedural steps are tracked one by one — a requirement covering six steps can’t be “covered” while two are missing
  • Traceability matrix exports to Excel and CSV, at scene and at script-line level

TRACEABILITY MATRIX · excerpt · synthetic

Req.SourceScenesVerified
REQ-006Rev C §3.2.3S03Verified
REQ-007Rev C §3.2.4S04Verified
REQ-008Rev C §3.2.5S05 S06Pending review
REQ-009Rev C §3.3.1—Gap

Illustrative · synthetic data

Reviewer verification & SME approval

Each requirement checked against evidence. The customer decides.

  • Reviewer verification per requirement — never on narration alone
  • SME approval of every question
  • Customer gates enforced by the platform, with criteria recorded

Reviewer approval

Your people review, approve and publish.

Designers, subject-matter experts and approvers share the work with clear lines of responsibility. Every approval is tied to the exact content it approved, and nobody approves their own work.

Approvals & separation of duties

After approval, an approver publishes to your organization’s catalog. Nobody approves their own work.

  • A scene stores the content fingerprint it was approved at; edit it afterwards and the approval is visibly stale, never silently carried
  • Instructional designers, producers, SMEs, customer reviewers, QA and auditors each see what their role needs — and refusals name who can act
  • Every transition, decision and refusal is recorded with who, when and against which version

Independent validator

Source-grounded drafting: one model writes, and a separate model validates the result against your sources, so the check is not the writer marking its own work.

  • Reviewers verify each requirement against confirmed evidence
  • A procedural step is never verified on narration alone

Collaboration & workspaces

Everything a person creates starts as a private draft, shared with named colleagues when it’s ready. Colleagues comment and review in place.

  • SMEs review and approve, with the history kept and every decision on the audit trail
  • Reopen an approved or published training for revision, with a reason; the published version stays available meanwhile
  • Start from your own templates, reuse from a shared library, and see the version history of every training

See your own source material become traceable training.

Bring a manual, an SOP or a policy. We’ll walk it through the lifecycle with you.