C2 Overview
Hierarchy And ORBAT
Build ORBAT trees, attach units to hierarchy elements, and manage slot staffing from ORBAT workflows.
Use this page to build and maintain the structure of the community.
An ORBAT is the hierarchy view of your organisation. It helps you show where units sit, how they relate to each other, and which people are assigned into each slot.
Workflow: Create And Maintain ORBAT Collections
Prerequisites
- You can open the ORBAT page.
- You know the naming convention your community uses for units or task forces.
- You are allowed to manage organisation structure.
Steps
- Open ORBAT.
- Create a new ORBAT if your community has more than one structure view.
- Give it a clear name and order it sensibly.
- Select the ORBAT you want to work on.
Expected Result
- Your community has a readable structure list that staff can follow.
- The ORBAT you are editing becomes easier to find because it has a sensible name and order.
Examples
Main Line UnitsTraining WingSpecial Operations
These names help new staff understand what the structure is for without needing a briefing.
Common Issues
- The ORBAT name is too vague, such as
TestorNew Structure, which makes it hard to know what it contains later. - Two ORBATs are named almost the same thing, so staff cannot tell which one to open.
- The order is confusing, so the most important structure is buried near the bottom.
Workflow: Add Or Remove ORBAT Elements
Prerequisites
- You have an ORBAT open.
- The units you want to place already exist in the community.
- You know whether the new element belongs under another element or should sit at the top level.
Steps
- Open an ORBAT.
- Click Add Element.
- Choose the unit you want to place in the structure.
- Pick a parent element if this unit belongs under another one.
- Set the display order so the tree reads naturally.
- Save.
- Remove an element only when you are sure the unit no longer belongs in the structure.
Expected Result
- The unit appears in the hierarchy where you placed it.
- The tree shows parent-child relationships clearly.
- Staff can understand at a glance how one unit sits under another.
What The Fields Mean
Unitis the real team or sub-team you want to place.Parentis the element above it in the structure. If a company belongs under a battalion, the battalion is the parent.Display ordercontrols which item appears first when there are multiple sibling elements. Lower numbers usually appear higher or earlier.
Common Issues
- A unit appears in the wrong place because the parent was chosen incorrectly.
- The tree looks messy because items were added in the wrong order.
- An element was removed, but it was still being used by staff, so you may need to reassign it first.
Workflow: Manage Slot Staffing From ORBAT
Prerequisites
- You have an ORBAT open and the relevant unit is visible.
- You know which slot you want to fill.
- You know which person should sit in that slot.
Steps
- Open ORBAT and select an element.
- Open slot manager for the linked unit.
- Choose a person for the slot, or clear the slot if it should be empty.
- Save the change.
- Refresh if you want to confirm the updated line-up.
Expected Result
- The unit shows the correct people in the correct slots.
- Empty slots are easy to spot when you are still filling out a team.
Examples
- A rifle squad has a
Team Leader,Automatic Rifleman, andGrenadier. - A support unit might have a
Medic,Driver, andRadio Operator. - A slot can be cleared if the person has left or is temporarily unavailable.
Common Issues
- The wrong person is selected because two profiles have similar names.
- A slot is left empty by accident, which can make the unit look incomplete.
- Someone is assigned to a slot they should not occupy yet, so double-check before saving.
Behavior Notes
- ORBATs are best used as a visual map of the community's structure.
- Keep the naming simple and consistent so new staff can learn the layout quickly.
- The ORBAT structure and the unit roster are related, but they are not exactly the same thing.
- A clean ORBAT makes staffing conversations much easier.