A Long Game Project game
15b

Procedures

What Are Procedures?

Some scenes are too complex for a single check. A negotiation isn't one roll. It has opening positions, reading the room, trading concessions, and a verdict. A crisis response moves through triage, action, communication, and stabilisation. If you collapse any of these to a single roll, you lose the texture that makes them worth playing.

Procedures are step-by-step recipes for those scenes. Each one is a numbered sequence of 4-5 phases with clear labels, specific skill checks, and decision points. The GM gets a reliable structure. The players get a shared expectation of how the scene will progress.

Running a Procedure

Every skill roll in a procedure is a normal check: D20 plus modifiers against a Dice Check (DC). As in any other check, a natural 20 is a critical success and a natural 1 is a critical failure.

Most steps name the stat and skill to roll, for example CHA (Influence). The skills are listed in Core Skills. Add your stat modifier and any ability or circumstance bonus. When a step asks for “a relevant skill check”, choose the stat and skill that fit the action, as for any other check.

When a step does not give a DC, the GM sets it with the DC Difficulty Guide. Some procedures track a named DC, such as the scepticism DC or the conviction DC. Unless the scenario or a step sets it, a named DC starts at Moderate (DC 10). The GM then moves it as the steps say.

Unless the scenario says otherwise, a procedure succeeds if most of its steps succeed.

Some steps roll against an NPC’s disposition DC. It starts at Moderate (DC 10), then moves with the NPC’s place on the disposition scale: Friendly lowers it by 1 and Unfriendly raises it by 1. Allied and Hostile have no number on the scale. An Allied NPC gives the roll advantage, and a Hostile NPC gives it disadvantage. The DC already holds the Friendly or Unfriendly modifier, so do not add it to the roll as well.

Procedures vs. Crunch Time

Crunch Time uses initiative-based turns for rapid decision-making under pressure. Every player rolls initiative (D20 + DEX modifier), then acts in order, one action per turn. The GM takes NPC and entity turns after every player has gone. Use it for scenes where the pace is fast and every second counts.

Procedures are sequential phases for scenes that unfold over multiple steps. The phases follow each other logically, not on a clock. If the scene calls for snap decisions under pressure, use Crunch Time. If it has a natural sequence of phases that need to play out, use a procedure.

The two work together. A procedure can run across multiple Crunch Time rounds: the Crisis Response procedure might occupy several rounds as pressure mounts. Or a procedure can structure a scene with no initiative order at all, such as a board meeting or a regulatory audit.

Procedures and Decision Actions

The Decision Actions in Section 3 describe what characters can attempt. When an action has multiple steps or unfolds over time, a procedure gives it the structure it needs. Negotiate, Research, Implement, Adapt, and Coordinate each map to one or more procedures here. Where a procedure is the recommended way to run an action, the procedure's introduction says so.

Category A: High-Stakes Social Encounters

These procedures cover scenes where the main challenge is human: persuasion, negotiation, de-escalation, and mediation. The outcome depends heavily on how well participants read their counterparts and adapt their approach.

This procedure works best when both sides have something to gain. If one side holds all the power, consider Stakeholder Pitch instead. The dynamic is closer to seeking approval than to exchanging value.

The Prepare step rewards players who do their homework before the scene. If players skip straight to the pitch without setting out their evidence, set the scepticism DC high to reflect the audience’s uncertainty.

Scale the number of journalist questions to the time available and the weight of the scenario. A D4 works fine for shorter scenes. The inject in step 4 is where memorable moments happen. Prepare one or two surprises in advance.

The Acknowledge step matters most. A defensive or dismissive response in step 2 makes every later step harder. Use this to reinforce the lesson that how you respond matters as much as what you finally offer.

The quality of the Hear Both Sides step sets the ceiling for the whole procedure. If the mediator skips past it or rolls poorly, the reframing will miss the mark and the agreement will be fragile.

Category B: Decision & Governance

These procedures cover formal decision-making processes: committee votes, resource competition, regulatory scrutiny, and competitive bids. The challenge is often as much about process and politics as it is about the merits of the case.

This procedure works best when players have built relationships with NPC members before the meeting. If they arrive without any prior influence work, treat all undecided members as starting Hostile.

The inject in the Allocate step, such as a sudden budget cut or a new priority that arrives mid-meeting, is particularly useful for teaching adaptive thinking under constraint.

The regulator’s starting disposition should reflect the scenario context. A routine audit starts Neutral. A triggered investigation starts Unfriendly. The Findings step gives players a final chance to correct the trajectory before the ruling locks in.

The feedback in the Award step is as important as the result. Win or lose, players should leave knowing their score on each criterion and where the winning bid outperformed them.

Category C: Crisis & Response

These procedures cover situations where something has gone wrong, is going wrong, or is at risk of going wrong. Players face uncertainty, incomplete information, and competing demands under time pressure.

The loop back to step 3 is what makes this procedure feel like a real crisis. Stabilisation takes multiple rounds of effort, not a single decisive action. Use the injects deliberately to introduce the secondary complications that real crises always produce.

Before you run this procedure, decide how much evidence exists and where the critical pieces are hidden. Players who skip the Gather step and go straight to Confront will lack the evidence needed to get past a subject’s defences.

The Protect step is where many groups make costly mistakes. They act quickly without thinking through who might infer the reporter’s identity from the investigation itself. Build in time for players to reason through the exposure risks before moving on.

The delayed consequences of the Settle step work well in multi-session exercises. Plant a seed here that blooms into a complication later. In single-session play, narrate the consequences immediately, but flag that trust takes time to rebuild.

This procedure has the most impact when players have already invested effort in the original plan before the pivot is triggered. The emotional weight of abandoning prior work is the point. Use it to teach the difference between sunk-cost thinking and genuine reappraisal.

Category D: Influence & Alignment

These procedures cover building durable alignment across independent parties. They unfold over multiple engagements and reward players who invest in preparation and relationship management.

Run step 2 as a separate scene for each potential ally. The individual conversations reveal tensions that only become apparent when players try to reconcile competing demands in step 3.

Step 5 is deliberately open-ended. For long-form exercises, have players return to this procedure across multiple rounds to reflect that advocacy is a campaign, not a single action.

Category E: Operations & Execution

These procedures structure the execution side of play: getting things done, coordinating across groups, managing risk, and building capability. They pair naturally with Crunch Time rounds and work well as multi-round sequences inside a longer exercise.

Failed checks in step 3 (Launch) set up the problems the GM brings in as injects during step 4 (Monitor). Cascading failures from one team affecting another create the most realistic and instructive execution scenarios.

This procedure works best when at least one player represents each independent group. This gives each person a stake in the negotiation at steps 1 and 2.

Step 5 is the payoff. Triggering a risk the players under-weighted in step 2 is one of the most effective teaching moments this system can produce.

Run this procedure at the end of a Crisis Response or Operational Deployment sequence. It gives the exercise a reflective closing phase that maps naturally to real-world after-action reviews.

Step 2 has no rolls by design. Removing mechanical pressure during ideation produces more candid discussion and better ideas than any dice result would.

This procedure works well as a framing device for exercises where one player takes an expert role and others are deliberately positioned as learners navigating an unfamiliar domain.

Creating Your Own Procedures

The 22 procedures above cover the most common structured scene types in business and organisational scenarios. They won’t cover everything. If your exercise involves a situation with a natural multi-step flow that doesn’t fit an existing procedure, build one.

How to design a procedure

  1. Think about what kind of scene you need. What is the situation? What makes it complex enough to need a procedure rather than a single roll? If you can resolve it in one check, you probably don’t need a procedure.
  2. Identify the natural phases. What happens first? What follows from that? Map out the sequence of events as they would unfold in real life. The procedure should feel like a stylised version of how the situation actually works.
  3. Assign relevant skill checks to each phase. Match each step to the skill from Core Skills that would genuinely matter at that moment. Avoid defaulting to CHA (Influence) for everything. Varied skill demands make procedures more interesting and reward different character builds.
  4. Keep it to 5 steps or fewer. Longer procedures lose momentum. If your draft runs to 7 or 8 steps, look for steps that can be combined or cut without losing the core experience.
  5. Playtest and adjust DCs based on how it runs. Your first draft will likely be too hard or too easy. Run it once, note where players breezed through or got stuck, and tune the DCs with the DC Difficulty Guide. Two or three playtests usually produce a solid procedure.
Go deeper
Train your team
We teach your people to run exercises for your own teams or your clients.
See training →
Question cards
PRISM
552 question cards in 11 decks, for scenario design and debrief.
Explore PRISM →
Need help?
Test a crisis plan
Want an exercise designed and run for you?
Learn more →