ITU
Facilitator guide
Captain guide

ITU · NETP Readiness Tabletop

NETP Facilitator — User Guide

Workshop ops for facilitatora / facilitatorb / facilitatorc. Admin differences are called out at the end.

1. Sign in

Usernames (always lowercase in the system):

  1. Open the exercise URL.
  2. Enter username (any casing works — input is lowercased) and the password admin generated.
  3. Log in.

You land on Master Dashboard by default.

If you see “This account has no password yet”, ask admin to open Admin → Generate passwords and share yours.

There is no facilitator forgot-password flow. Re-issue passwords via admin.

2. Default workshop permissions

New facilitator accounts get this floor (admin can tighten or widen toggles):

On by defaultOff by default
Activate injects on SessionAdmin tab
Start / pause / terminateScenarios
Advance / restartCreate cards
Break / debrief timingInjects (edit definitions)
Resources (±budget / people, specialist transfer)Generate passwords
Play for captains (proxy play)

If a button is missing or you get “You don't have permission…”, ask admin to flip the matching toggle on that facilitator row.

3. Pre-flight (who does what)

Typical room setup:

  1. Admin selects scenario under Setup → Scenarios (Use this scenario), generates passwords, shares sheets.
  2. Captains log in and wait in lobby.
  3. Facilitator fills This exercise city + country on Session.
  4. Facilitator taps ▶ Start exercise (Round 1).

You can re-check team status on Standings before starting. Advance actions stay gated until the exercise has started.

4. Master Dashboard

Session controls

ControlUse
▶ Start exercise (Round 1)Opens Play for captains; starts the clock
+5 minExtends the current round timer
Advance all to next round →After submissions (or timeout forfeit); archives rationales
Pause / ResumeFreezes captain actions mid-round
■ Terminate sessionCloses captain tables
↺ Restart exerciseResets play (confirm carefully)
Break / Debrief minutes + start phaseTimed reflection windows between / after rounds

Also set City and Country under This exercise. Use Save current play & start a new exercise when archiving a completed group and beginning another.

Online presence

Next to each team name, staff see a small status: green dot + online when that team's captain is signed in, or a gray dot + offline otherwise (default until a heartbeat connects). Admin also sees the same online/offline labels next to facilitator and captain usernames on Admin → User accounts. Captains do not see these indicators.

Grants (± budget / people)

On each team card:

Use these for table adjudications and fulfilled aid decisions.

Specialist transfer

Move 1 person between teams:

  1. Pick donor and recipient.
  2. Set negotiated fee ($ thousands) or leave default.
  3. Sell (fee charged) or Donate free — goodwill inject.

Instant sell/donate is facilitator-driven. Captain buy/sell offers appear under Team trade offers (X-02 gate applies to both teams).

Open table →

Sit at that nation’s Play view (proxy only if Play captains is granted; otherwise treat as observation / guidance).

5. Inject panel (per team)

On each team card (requires Activate):

  1. Choose inject…
  2. Round mode: This round or Next round (queues until advance).
  3. Effect: Auto, or force 25 / 50 / 75 / 100%.
  4. Read the preview (scaled $ and people impact).
  5. Activate →

Labels in the preview / toasts:

LabelMeaning
queued Round NArmed for a later round; applies on advance into that round
already appliedFired for that team this session — restart to re-arm
Double-fire blockedToast: already applied or already queued — do not spam Activate

Inject codes (F1–F3 style) are admin-visible; facilitators usually see titles without codes.

Inject calendar on Session lists scheduled / flexible injects and their status.

Editing inject definitions is Setup → Injects — needs Library / manage-injects rights (ask admin). To create one: open Setup → Injects, use Add / Create new inject (or + New inject), fill code / title / effects (and optional prepared variants), then Create inject.

6. Neighbour aid inbox

Captains send Ask / Offer from Play. Inbox on Session:

KindYour actions
RequestGrant +$100k, Grant +1 person, or Dismiss
OfferFulfill transfer (moves the committed resources) or Dismiss

Fulfill only after captains have agreed face to face. Dismissed items log a decline on the team.

7. Debrief pack (rationales)

Bottom of Session (also mirrored on Admin): Debrief pack — turn rationales.

Prompt captains to fill the rationale box before submit.

8. Standings

Standings → all teams: budget, people, Built / Ready / In plan / Locked, turn state, Open →.

Same Advance all to next round → control appears here when permitted.

9. Scenario

Scenario is a hub with two sub-tabs:

Sub-tabContents
OverviewRegion Scenario image and description entry, plus per-team profile pages
TeamsStaff team tables (same Open-table style browsing as before)

Deep links still work: open a country profile or region view from Overview; Back to Scenario returns to the hub.

Scenario image (one image + type)

Each scenario has a single scenario image (not three separate media slots). A required type is shown as a badge on Scenario Overview / Profiles (and on the captain Briefing → Map view); an optional Image name (custom title) appears next to that badge when set. When type is Other, Image name is required.

TypeMeaning
MapOperating environment / geography
OrganisationActors or entities chart (countries or national entities)
GovernanceRoles / decision structure
OtherSomething else — set Image name so viewers know what it is

Change image / set type appears only if you have Library (scenarioLibrary) — Admin always can. Use either:

  1. Live Scenario view (Overview → region page): image type select + Change image, or
  2. Setup → Scenarios → Basics & rounds → Scenario image (same one visual + type; save the scenario to keep Library edits).

Without Library: read profiles for facilitation; ask admin to update artwork.

10. Setup (Scenarios / Injects / Cards)

Top nav shows a single Setup tab whenever you are in Scenarios, Injects, or Cards. Sub-tabs under the header are permission-gated:

Sub-tabDefault facilitatorNotes
ScenariosHiddenAsk admin for Library — editing includes Basics → Scenario image (one image + Map / Organisation / Governance / Other type)
InjectsHiddenNeeds manage-injects and/or Library — Add / Create new inject at the top of the list (create/edit needs manageInjects)
CardsVisibleCatalogue for everyone; create/edit needs Create cards

Opening Setup lands on the first available sub-tab (Scenarios if permitted, else Injects, else Cards).

On Setup → Injects, use Add / Create new inject+ New inject to open the editor (code, label/title, effects, prepared/unprepared, required cards). Save with Create inject.

Do not change the active scenario mid-group unless admin directs it. Prefer fixing play issues with grants, injects, and session controls.

11. Trading (room coaching)

Remind tables:

12. Typical round loop

  1. Start (or already running) — watch timer.
  2. Coach tables; grant/aid/inject as the narrative needs.
  3. When all submitted (or time up), Advance.
  4. Optional break / debrief phase.
  5. Repeat through the planned rounds.
  6. Close with Debrief pack; terminate or restart for the next cohort as needed.

Admin extras (short)

Admin (admin, bootstrap password until changed) has everything facilitators might lack:

Facilitators should not rely on SMTP recovery — use admin for credential issues.

What facilitators normally do not handle

Unless admin grants the toggle:

Match UI labels in the live app. Source: docs/USER-GUIDE-FACILITATOR.md. Admin: use this guide (Admin extras section) plus optional Captain guide.