How to Structure Your ERLC Department Hierarchy

Decide how many departments your server needs before assigning any ranks. Common ERLC department models include:

• Single-department: One unified law enforcement or emergency services group. Best for smaller servers (under 50 active members).
• Multi-department: Separate divisions for police, fire, EMS, civilian, and government. Requires more coordination but enables specialization.
• Hybrid: A core department with sub-units. For example, a police department with a separate detective division.

Start smaller than you think you need. Merging departments is easier than splitting them later.

Every department needs a vertical rank structure. Organize ranks into three clear tiers:

• Enlisted ranks: Entry-level members with limited authority. Examples: Cadet, Recruit, Probationary Officer.
• Officer ranks: Active members who handle day-to-day operations and can direct enlisted members. Examples: Officer, Corporal, Sergeant.
• Command ranks: Leadership responsible for policy, training, and department direction. Examples: Lieutenant, Captain, Chief.

Limit rank tiers to what you can realistically fill. Five to seven ranks is sufficient for most servers.

Each rank tier must have defined authority — what they can and cannot do. Document this clearly:

• Enlisted members follow orders, do not issue directives to peers.
• Officer ranks can direct enlisted, approve minor decisions, and lead patrols.
• Command ranks set policy, approve promotions, and handle appeals.

Avoid rank authority gaps — situations where no one has authority to make a decision. Assign a default decision-maker for each scenario.

If you have multiple departments, define how they interact:

• Which departments can issue cross-department orders, and in what circumstances?
• Who coordinates multi-department responses during events?
• How are disputes between departments escalated?

Create a simple chain of command document. A text-based org chart shared in your Discord is more effective than a complex graphic.

A hierarchy that cannot adapt will create structural problems as your server grows:

• Build in promotion review intervals — monthly or bi-weekly evaluations prevent stagnation.
• Reserve command roles until you have members qualified to fill them. An empty rank creates confusion.
• Document every structural change with a dated announcement. Members need to understand why the hierarchy changed, not just that it did.

A hierarchy only functions if members understand it:

• Publish a rank guide in a pinned Discord channel — rank name, role color, responsibilities.
• Include hierarchy structure in your onboarding material for new members.
• Revisit and update documentation after any structural change.