CRISIS COMMITTEE GUIDE

How to Run a Model UN Crisis Committee: A Complete Guide

BY MAXIMUNUPDATED AUGUST 19, 202612 MIN READ

A strong Model United Nations crisis committee feels immediate: delegates make decisions, the world reacts, and every update creates another meaningful choice. That sense of momentum is not accidental. It comes from careful preparation, a coordinated crisis team, and an operating system that keeps information moving.

This guide explains the full process for running a crisis committee. It focuses on the work behind the room: building a playable scenario, defining staff responsibilities, processing directives, maintaining a shared world state, and ending the committee with a conclusion that reflects delegate action.

KEY TAKEAWAYS

  • Start with a clear dramatic question and a world delegates can change.
  • Give every crisis-team member a defined role and one shared source of truth.
  • Process directives consistently, but preserve room for creative play.
  • Use updates to create decisions—not simply to deliver information.
  • Track consequences so the ending belongs to the committee that created it.

What makes a crisis committee different?

In a traditional committee, debate is organized around a relatively stable agenda and a decision made at a point in time. A crisis simulation models interactions across a period of time. Delegates may control characters, institutions, military units, money, intelligence, or political relationships. Their directives alter the simulated universe, and the crisis team turns those actions into consequences.

The committee operates as an input–output loop. Delegates receive public or private updates, debate the changing situation, and send directives, joint actions, or press statements back to the crisis team. The backroom reconciles those inputs, updates the simulated world, and produces the next outputs. Frontroom staff manage the visible debate while the Crisis Director connects the two systems.

  • A changing simulated universe
  • A defined crisis timeframe and pace
  • Frequent individual and joint directives
  • Public and private outputs
  • Fast coordination between frontroom and backroom

1. Define the committee’s promise

Before writing characters or updates, write one sentence that explains what delegates will get to do. A useful promise contains a setting, a source of tension, and meaningful agency. For example: “Members of a divided emergency cabinet must keep the state alive while deciding who will control it.”

This promise keeps the design focused. If an update is dramatic but gives delegates no useful choice, it probably does not serve the committee. If a mechanic is detailed but never affects the central conflict, simplify it.

  • What decisions belong to delegates?
  • What can permanently change?
  • Why must the committee act now?
  • What competing definitions of success exist?

2. Build a playable crisis arc

A crisis arc is a set of possible pressures, not a script that delegates must follow. Prepare an opening state, several actors with independent goals, resources that can change hands, and escalation options. Then design updates as modules that can be adapted to what delegates actually do.

Plan consequences in categories—political, military, economic, social, and informational—rather than predicting every directive. This makes the backroom faster and prevents the story from collapsing when delegates choose an unexpected path.

  1. Opening

    Establish the immediate problem, the available institutions, and the first decision.

  2. Escalation

    Introduce costs, competing actors, incomplete information, and time pressure.

  3. Reversal

    Reveal how earlier choices changed alliances, resources, or public confidence.

  4. Endgame

    Concentrate the consequences into a final set of decisions the committee can own.

3. Organize the crisis team

Assign responsibility before the first session. Every incoming directive should have an owner, every update should have an approval path, and every factual change should be recorded. Staff can rotate, but responsibility cannot be ambiguous.

A small committee may combine roles. A larger committee may assign staff to portfolios, factions, geographic areas, or operational functions. Whatever the structure, use a shared committee workspace so decisions are visible to the people who need them.

  • Crisis Director: continuity, pacing, difficult rulings, and final approval
  • Frontroom: debate, procedure, public clarification, and room temperature
  • Backroom reviewers: directive decisions and delegate communication
  • Update or news team: public consequences and narrative presentation
  • World-state owner: map, resources, characters, and institutional status

4. Create a directive workflow

Delegates need to know how actions are submitted, when collaboration is required, and what kind of response they can expect. Staff need a clear queue that shows what is unclaimed, under review, waiting for clarification, granted, modified, or denied.

Consistency does not mean every creative action receives the same result. It means similar claims receive similar scrutiny, costs are explained, and state changes are recorded. A good response acknowledges the idea, states what happened, and gives the delegate something actionable to consider next.

  • Identify the author, character, time, and requested action
  • Check authority, resources, feasibility, secrecy, and opposition
  • Request clarification only when the missing detail changes the decision
  • Record the ruling and any world-state change
  • Send a concise response and surface public consequences when appropriate

5. Control pacing with meaningful updates

Publish an update when the committee needs a new decision, when a consequence must become public, or when energy is falling. Do not publish simply because a schedule says another update is due. The best updates connect to delegate action and change the strategic picture.

Alternate the shape of pressure. A military emergency may be followed by a political fracture, an information leak, a resource shortage, or an unexpected offer. Variety prevents the committee from becoming a sequence of identical tactical problems.

  • What changed?
  • Why does it matter now?
  • Who gained or lost leverage?
  • What can delegates realistically do next?
  • Which earlier action caused or influenced this event?

6. Maintain one source of truth

Crisis teams often lose time because directives live in a form, decisions in a chat, resources in a spreadsheet, and updates in a document. When those sources disagree, the committee experiences continuity errors.

Keep personnel, directives, discussions, announcements, updates, maps, and resources connected. MaxiMUN is designed around this operational problem: each role sees the workflow it needs while the committee continues to share one evolving state.

7. End with consequences, then review

A memorable ending does not need to resolve every subplot. It should reveal what the committee’s most important choices produced. Use the final update to show the new balance of power, the cost of success, and the unresolved question delegates will keep discussing after the room closes.

After the conference, review directive turnaround time, continuity errors, unused mechanics, staff workload, and the moments that generated the strongest debate. Preserve the archive. Those observations are the foundation of the next committee.

Reference & further reading

Crisis Guide 3.0
Skyler Lee, Department of Diplomacy, National Chengchi University

This independent MaxiMUN editorial guide draws on the reference above alongside MaxiMUN’s product and committee-operations research. Reference does not imply endorsement.
MODEL UN CRISIS MANAGEMENT SOFTWARE

One workspace for the whole crisis.

MaxiMUN connects directors, crisis teams, and delegates through committee setup, directives, discussions, updates, maps, resources, and announcements.