You compose with what your members can actually hold.
It all starts with the member. Each one declares their characters — class, specialisation, realm, level, professions — picks a main, and above all states the roles they are able to hold on a run, including the ones they don't usually play. The backup tank who won't say it out loud in voice chat, you find in the sheet rather than the moment you're a tank short.
Gear level is declared by the member or imported from their SimC export — no magic sync with the game, the data comes from them.
- Several characters per member, with a designated main
- Holdable roles declared, beyond the usual one
- Gear declared or imported from a SimC file
- Visible activity: runs, attendance rate, next commitment

Your rosters, once — not before every run.
A roster isn't an attendance list, it's a team: who belongs to it, with which character, in which slot. The Planner keeps them current group by group, with the slots you defined — ranged DPS, melee DPS, healer, support, or whatever your game calls them.
For every member placed you see their character, class and spec, what else they can hold, and their score. Target and actual composition compare at a glance: you know you're a healer short before you even open the calendar.

Every run: who's actually coming, and does it hold together?
On the day, the Planner opens on the sign-ups. You validate the list, and the coverage rate tells you immediately whether the composition stands: how many to place, how many still without a role, where the holes are.
That's the moment most orgs discover the problem too late. Here it surfaces while you can still call someone.

The tactical map moves live, for everyone.
The composition goes onto a map: your zone background, your tokens, your sequences. A briefing is organised in steps — phase one, phase two, the burn — which you duplicate and run through like slides.
And it is genuine real time: several officers can build the map at once, every move is merged and rebroadcast to the others. A member reading the map sees it move while you build it. Nobody waits for a screenshot export.
- Sequences and steps: a briefing unfolds, it doesn't fit on one image
- Your own map background, cropping, viewing angles
- Simultaneous editing, merged server-side
- Visible live even to those only watching
- Export to share outside the app

Presentation mode: three tools that steer attention.
When it's time to explain, the interface steps back and all that remains is the map and three tools. They are what separates this from any whiteboard bolted next to your Discord.
The ephemeral pencil — you draw the move, the stroke stays long enough to be read then erases itself, receding from where it started. Nothing to clean up, nothing accumulating, and the stroke never enters the document: neither saved nor exported. The ping points at a spot without drawing anything. The spotlight makes one token stand out and dims all the others — "he leaves first" becomes obvious without a sentence.
These three are used while you share your screen in voice: they steer the attention of the people watching you.

MMO or military: one mode, chosen for your game.
Game Org doesn't impose one way of running an operation. Operation composition has two modes, and your org enables only one: the Planner for MMO raids and runs, Mission Control for units that think in order of battle and military missions. Both build on the Events module.
If you run Star Citizen operations, milsim sessions or structured RP, Mission Control is the one to look at — it tells the same story in your universe's vocabulary.
The tactical map isn't reserved for the Planner: both modes have it. What changes is the grammar around it — rosters and compositions on one side, order of battle and missions on the other.

FAQ