-
Vehicles 147
-
Light vehicles
-
Armoured vehicles
-
Tiltrotor aircraft
-
Naval craft
-
Vehicle-mounted weapons
-
-
Planning and Execution 155
-
Theatres and Campaigns
-
-
FMDG Communications
-
Radio Comms (Staging)
-
Reports (Staging)
-
FMDG Field Leadership
-
-
FMDG Rotary Wing
-
Loadout (Temp)
-
UNIHELP
Every role card
Command & Control
Ground Operations
-
Core Infantry 13
- Assistant Automatic Rifleman Verified
- Rifleman Verified
- Ammo Bearer Verified
- Grenadier Verified
- Automatic Rifleman Verified
- Interpreter Verified
- Assistant Machinegunner Verified
- Assistant Machinegunner, Heavy Verified
- Machinegunner, Medium Verified
- Machinegunner, Heavy Verified
- SF Operator Verified
- SF Gunner Verified
- Rifleman (Leadership Observer) Verified
-
Cavalry 12
- Light Vehicle Crewman (Driver) Verified
- Light Vehicle Crewman (Gunner) Verified
- Light Vehicle Crewman (Commander) Verified
- Light Vehicle Section Commander Verified
- AFV Crewman (Driver) Verified
- AFV Crewman (Gunner) Verified
- AFV Crewman (Commander) Verified
- AFV Section Commander Verified
- MBT Crewman (Driver) Verified
- MBT Crewman (Gunner) Verified
- MBT Crewman (Commander) Verified
- MBT Section Commander Verified
Air Operations
Support Operations
Scenario Operations
-
Mission Support 11
- War Correspondent Verified
- Civillian Roleplayer Verified
- Assistant Game Master Verified
- Mission Support Observer Verified
- Game Master (≤15) Verified
- Game Master (≤32) Verified
- Game Master (≤64) Verified
- OPFOR Roleplayer Verified
- Lead Game Master (≤15) Verified
- Lead Game Master (≤32) Verified
- Lead Game Master (≤64) Verified
FM/BG-1626 · v1.01
The Chain of Responsibility
- Code
- FM/BG-1626
- Kind
- Guide
- Version
- v1.01 7mos ago
- Views
- 127
- Platforms
- As its document
- Published by
- LtCol James 28 Feb 2026
- Last material change
- v1.00
No words changed between v1.00 and v1.01.
v1.00
Every Roadmap item has a Chain of Responsibility, a set of roles that defines who's involved and what they're responsible for. This makes it clear, for every item, who's leading the work, who has the final say, who's contributing, and who's being kept informed.
The four roles are:
Pointman - Leads this item forward.
Authority - Has final authority to approve or reject.
Contributors - Provide input, expertise, and hands-on help.
In the Loop - Kept updated on progress and decisions.
There's also the Originator, the person who originally submitted the item. The Originator isn't a responsibility role as such, but they're always visible on the item and can post updates and respond to questions throughout the process.
How roles get assigned
Roles are assigned as the item progresses. Typically, when an item is first picked up from Received, a Pointman is assigned. The Authority is usually determined by the area the item falls under. Contributors and In the Loop members are added as the conversation develops and it becomes clear who should be involved.
Roles can be assigned to individual people or to entire teams. When a team is assigned, all members of that team take on that role for the item.
Some item types have default roles pre-configured by J11, so the Chain of Responsibility may be partially filled in from the moment of submission.
Why it matters
Having clear roles means there's never any confusion about who's doing what. If you want to know who's driving a particular item, check the Pointman. If you want to know who needs to approve it, check the Authority. If you want to get involved, the Chain of Responsibility tells you who to talk to.
v1.01
Every Roadmap item has a Chain of Responsibility, a set of roles that defines who's involved and what they're responsible for. This makes it clear, for every item, who's leading the work, who has the final say, who's contributing, and who's being kept informed.
The four roles are:
Pointman - Leads this item forward.
Authority - Has final authority to approve or reject.
Contributors - Provide input, expertise, and hands-on help.
In the Loop - Kept updated on progress and decisions.
There's also the Originator, the person who originally submitted the item. The Originator isn't a responsibility role as such, but they're always visible on the item and can post updates and respond to questions throughout the process.
How roles get assigned
Roles are assigned as the item progresses. Typically, when an item is first picked up from Received, a Pointman is assigned. The Authority is usually determined by the area the item falls under. Contributors and In the Loop members are added as the conversation develops and it becomes clear who should be involved.
Roles can be assigned to individual people or to entire teams. When a team is assigned, all members of that team take on that role for the item.
Some item types have default roles pre-configured by J11, so the Chain of Responsibility may be partially filled in from the moment of submission.
Why it matters
Having clear roles means there's never any confusion about who's doing what. If you want to know who's driving a particular item, check the Pointman. If you want to know who needs to approve it, check the Authority. If you want to get involved, the Chain of Responsibility tells you who to talk to.
Every Roadmap item has a Chain of Responsibility, a set of roles that defines who's involved and what they're responsible for. This makes it clear, for every item, who's leading the work, who has the final say, who's contributing, and who's being kept informed.
The four roles are:
Pointman - Leads this item forward.
Authority - Has final authority to approve or reject.
Contributors - Provide input, expertise, and hands-on help.
In the Loop - Kept updated on progress and decisions.
There's also the Originator, the person who originally submitted the item. The Originator isn't a responsibility role as such, but they're always visible on the item and can post updates and respond to questions throughout the process.
How roles get assigned
Roles are assigned as the item progresses. Typically, when an item is first picked up from Received, a Pointman is assigned. The Authority is usually determined by the area the item falls under. Contributors and In the Loop members are added as the conversation develops and it becomes clear who should be involved.
Roles can be assigned to individual people or to entire teams. When a team is assigned, all members of that team take on that role for the item.
Some item types have default roles pre-configured by J11, so the Chain of Responsibility may be partially filled in from the moment of submission.
Why it matters
Having clear roles means there's never any confusion about who's doing what. If you want to know who's driving a particular item, check the Pointman. If you want to know who needs to approve it, check the Authority. If you want to get involved, the Chain of Responsibility tells you who to talk to.
Where it appears
Lives in
FM/G363 Chain of ResponsibilityOn role cards
No role card holds this passage yet.