IARPG Mission Design Workbench

Build a complete operation without sending the draft anywhere.

Drafts remain in this browser’s local storage. Import JSON, load the complete example, validate continuously, print the brief, and export a Level A–D mission record.

Local-only draftNo account · no API call · no external transmission

How to use this page

Create or adapt one structured Mission Brief.

The workbench is a guided editor, not the game itself. Load the complete example first, move through the stage rail, inspect validation findings, and export only when the authority, requirement, roles, evidence, risk, extraction, and debrief fields make sense together.

01
Load a starting pointChoose Load example or import a local Mission Brief JSON file.
02
Work through the stagesUse the numbered rail; complete direction before interactions and outcomes.
03
Validate and exportReview the conformance level, correct findings, then export JSON or print the brief.

Read the complete site and tool guide

Optional · restart anytime · no draft changes

Progress0%

Stage 01 / direction

Authority

Select or name the fictional organization sponsoring the operation. Authority defines resources, constraints, jurisdiction, and desired effect—not moral alignment.

Authority Authority code FOUND-03 Neutral Authority Profile →

Stage 02 / direction

Customer

Identify the decision-maker or operating body that will use the intelligence.

Intelligence customerDecision supportedFOUND-04 Intelligence Customer Requirements →

Stage 03 / direction

Mandate

State what the authority is permitted and expected to do.

MandateFOUND-02 Mandate, Customer, and Jurisdiction →

Stage 04 / direction

Jurisdiction

Declare where the operation and its authority apply, including negotiated or contested boundaries.

JurisdictionJUR-01 Evidence-Based Jurisdiction →

Stage 05 / tasking

Intelligence requirement

Ask the question the operation must answer. Avoid writing the preferred conclusion into the requirement.

Primary intelligence requirementDeadline UTCMISS-01 Intelligence Requirement →

Stage 06 / baseline

Known facts

Enter one fact per line. Facts must be currently supported by authoritative game state or reviewed evidence.

Known factsEVID-01 Evidence Types →

Stage 07 / baseline

Assumptions

Enter one assumption per line. Assumptions remain visible and reviewable.

AssumptionsANAL-01 Competing Hypotheses →

Stage 08 / analysis

Competing hypotheses

Provide at least two plausible explanations before collection narrows the field.

HypothesesANAL-01 Competing Hypotheses →

Stage 09 / cell

Roles

Select the roles assigned to the operation.

OperativeMaintains cover, enters the environment, collects observations and objects, and protects extraction options.HandlerTranslates customer requirements into tasking, manages sources and cover resources, and authorizes conversion or abort.Intelligence AnalystFuses multi-source reporting, tests hypotheses, preserves dissent, and drafts the intelligence product.Technical OperatorOperates fictional sensors, signals, cyber, imagery, and communications systems within declared mission boundaries.Counterintelligence OfficerDevelops anomaly and compromise cases, tests manipulation, and recommends protective action.Liaison OfficerControls releasability, coordinates external authorities, and records partner caveats.Logistics SpecialistCoordinates transport, safe locations, equipment, custody, and extraction support.Source HandlerRecruits, validates, briefs, protects, and debriefs human or synthetic sources.

MISS-04 Roles and Information Asymmetry →

Stage 10 / cell

Information asymmetry

Describe what roles know, what is withheld, and why.

Role-specific information planROLE-02 Information Asymmetry Disclosure →

Stage 11 / collection

Collection plan

Enter one collection action or discipline per line.

Collection planCOLL-01 Collection Discipline Selection →

Stage 12 / collection

Sources

Describe source classes, access, reliability, motivation, and handling boundaries.

Source planHUM-02 Source Reliability and Access →

Stage 13 / play

Player interactions

Enter the meaningful actions players perform, one per line.

Player interactionsGAME-01 Player Interaction →

Stage 14 / access

Cover and access

Explain why the operative can be present and what expected behavior sustains that access.

Cover and access planTRADE-01 Cover Identity and Congruence →

Stage 15 / validation

Evidence thresholds

State what is required before attribution, restriction, settlement, or mission completion.

Evidence thresholdEVID-02 Provenance and Corroboration →

Stage 16 / validation

Synthetic-source policy

Generated language may provide claims but cannot create authoritative mission state.

PolicyAI-03 Synthetic Source Claim Packets →

Stage 17 / protection

Compromise indicators

Enter observable signs that access, source safety, communications, or evidence custody may be compromised.

Compromise indicatorsMISS-07 Compromise and Abort Handling →

Stage 18 / protection

Abort conditions

Enter conditions that require abort, conversion, or emergency extraction.

Abort conditionsMISS-07 Compromise and Abort Handling →

Stage 19 / extraction

Extraction

Define primary, alternate, emergency, and remote-debrief extraction options.

Extraction planMISS-05 Success, Abort, Extraction, and Debrief →

Stage 20 / debrief

Debrief deliverable

Define the final intelligence product and what uncertainty, source impact, cover impact, access, and follow-on work it preserves.

Debrief deliverableMission titleMission IDDEBRIEF-01 Debrief Product Contract →

Continuous review

Not briefable

Complete authority, customer, mandate, jurisdiction, and intelligence requirement to reach Level A.

ABriefable

BPlayable

CAuditable

DSimulatable

Missing requirements

Mission direction is incomplete.

Generated mission JSON

{}

Search the operations design system