ITU
Captain guide
Facilitator guide

ITU · NETP Readiness Tabletop

NETP Captain — User Guide

Practical steps for team captains (players) during a live workshop.

Before you start

You need:

  1. The exercise URL from your organiser (same wifi / LAN address or the online URL).
  2. Your username and password (passwords are created by admin and handed out — you cannot set your own).

Usernames are derived from your team name (letters and digits only, no spaces). Login is case-insensitiveGovCoord and govcoord both work.

1. Sign in

  1. Open the exercise URL in a browser (laptop, tablet, or phone).
  2. Enter your username and password.
  3. Tap Log in.

If you see “This account has no password yet”, admin has not generated passwords — wait for the organiser.

On success you land as captain of your team. Until Round 1 starts you see the lobby.

2. Lobby (waiting for Round 1)

You will see: Welcome, captain of [your team] and Waiting for admin…

There is nothing to do here. Stay signed in. When a facilitator starts the exercise (Round 1), your Play table appears automatically.

If the session is later terminated, you see a closed-table message. Wait for facilitator instructions (restart or end of day).

3. Play view

After the exercise starts, use the top nav: Play · Standings · Briefing · Cards.

Header

Top stats

Neighbour status pills

Other teams show Deciding or Turn ended. You can see who has submitted. Captains cannot open another team’s table (staff can).

Lanes and cards

Six capability tracks (lanes). Scroll the lane strip sideways on small screens.

Ring / lookMeaning
Coloured ringReady to build now
FilledBuilt already
Grey / mutedNot yet open (prerequisites missing)
Already built capability
Card G-02: Establish an NETP steering committee
✓ Built G-02
Establish an NETP steering committee
Creates the multi-stakeholder body that directs NETP development and implementation.
$100k 1 staff Step 1

Filled style with a ✓ Built badge — your team may start with cards like this already in place.

Ready to build
Card R-02: Conduct a multi-hazard telecommunications risk assessment
Ready R-02
Conduct a multi-hazard telecommunications risk assessment
Identifies geographic hazards, network vulnerabilities, dependencies and single points of failure.
$300k 1 staff Step 1
Tap to add to your plan

Coloured ring means prerequisites are met. Tap to stage it; budget and staff costs apply when the round resolves.

  1. Tap a ready card to open its detail.
  2. Use Add to plan (or remove if already staged).
  3. Staged cards appear under Your plan this turn.
  4. Write a short rationale (kept for the debrief).
  5. Tap Submit / end turn when ready.

After you submit, wait for the facilitator to advance the round. Do not refresh frantically — state syncs on its own.

Specials (Talk & trade panel)

ActionEffect (rough)
Hire a consultant−$100k · +1 person
Introduce a new tax+$100k · −1 person
Global Reserve loan+$300k · −3 people — once per game
Ask a neighbour for helpRequest money or people — facilitator decides
Offer help to a neighbourPropose giving money or people — facilitator fulfills

Specials spend budget/people immediately when allowed; the session must be running and not paused.

Event banner

When an inject hits your team, a banner appears. Read it, then Got it. Effects are already applied to budget/people as shown.

What happened so far

Your team log lists builds, trade messages, aid, and inject outcomes for the session.

4. Standings

Standings is your personal scoreboard:

Use it to plan the next investments without hunting through all lanes.

5. Briefing

Briefing is a hub with two sub-tabs:

Sub-tabContents
MapShared scenario image and description for all teams, with a type badge (Map, Organisation, Governance, or Other)
TeamYour nation’s briefing: objectives, starting context, and profile text

The scenario image is one visual chosen by staff — not three separate uploads. The badge tells you what it shows; staff may also set an optional custom image name beside the badge (required when the type is Other):

TypeMeaning
MapOperating environment / geography
OrganisationActors or entities chart (countries or national entities)
GovernanceRoles / decision structure
OtherSomething else — custom name explains what it is

Objectives live on the Team page. Captains are read-only on both. Facilitators with Library rights (or admin) can change the image and its type; captains cannot.

6. Cards

Full catalogue of capability cards (artwork and text). Useful for browsing later tiers and understanding costs.

7. Trading (X-02 gate)

Under Talk & trade → Trade with a neighbour:

Trading unlocks only when both teams have built card X-02 (Implement Tampere Convention procedures). Until then you see a locked message.

When unlocked:

  1. Agree the deal at the table (face to face).
  2. Choose partner team, buy or sell, money or people, amounts, and price ($ thousands).
  3. Send the offer.
  4. Receiving captain Accepts or Declines in their inbox.
Accepted trades cannot be undone. Negotiate carefully before accepting.

Facilitators can also move people via Specialist transfer on Session — that is separate from captain offers.

8. Neighbour aid (ask / offer)

Different from X-02 trading:

From PlayWhat happens
Ask a neighbour for helpPrompt for money or people preference → goes to facilitator Neighbour aid inbox
Offer help to a neighbourPick a neighbour and resource → facilitator must Fulfill transfer or Dismiss

You do not move resources yourselves for aid. Watch your log for “waiting for facilitator” and grant messages.

9. Phone / tablet tips

Play is usable on phones and tablets:

10. What captains cannot do

If something fails with a permission toast, ask the floor facilitator or admin — it is intentional for workshop roles.

Quick round checklist

  1. Read any inject banner (Got it).
  2. Check budget / people.
  3. Stage cards (and optional specials).
  4. Write rationale.
  5. Submit turn.
  6. Optional: trade / aid if unlocked and agreed at the table.
  7. Optional: Messages / Feedback.
  8. Wait for facilitator to advance.

Match UI labels in the live app. Source: docs/USER-GUIDE-CAPTAIN.md.