Ranks, Roles, and Responsibilities

Overview

Every corp should describe how ranks, roles, and responsibilities are assigned, earned, awarded, and related to each other in a hierarchy. EVE’s title management system is disproportionately advanced in some ways and embarrassing primitive in others, so it it can be a challenge to¬† design a good, finite set of titles for your corp. Titles must be created in a way such that:

  • You make good use of the limited number of titles you can make. It’s better to have a few unused titles than need more titles than you have
  • Members are given the privileges needed to assume their roles and uphold their responsibilities
  • Members are given clearly identifiable, hierarchical ranks and the respective privileges entitled to them
  • Members do not have access to more than they require for personal or corp use, therefore mitigating the impact of thefts or sabotage

Ranks vs Roles

  • Ranks are titles that indicate a degree of trust, seniority, and privilege.
  • Roles are cohesive sets of responsibilities and expectations granted as part of one or more warrants.
  • Warrants are an assignment of roles and responsibilities (like a job title).
    • Warrants by themselves do not indicate any degree of seniority
    • Warrant responsibilities, expectations, and privileges scale with corresponding rank. For example, a low-rank quartermaster would only be able to perform duties with lower-level hangar access than a higher-rank quartermaster.
    • Rank does not indicate competency or seniority for any specific warrant. “Ranked Warrants” should be implemented as a series of cumulative or cascading (preferred) warrants

Commissions and Warrants

Whereas warrants establish roles and responsibilities, commissions establish expectations for the warrants.

One way to break down commissions (as I’ve implemented in my corporation, Ryoga Lonely Hearts), is to establish four categories:

  • Enlisted Ranks (no commission) – there are no expectations with regards to role fulfillment. In effect, role fulfillment is entirely voluntary
  • Non-Commissioned Officer – members are expected to devote a percentage of their playtime towards role fulfillment, but there are no minimum time requirements with regards to hours per week, etc
  • Commissioned Officer – members are expected to devote a percentage of their playtime toward role fulfillment, and should satisfy minimum time requirements in doing so (eg. hours per week)
  • Flag Rank Officer – these members virtually have complete control over the corporation. Ideally, at least one should be present at any given time, and at least one should be quick to respond to communications outside of EVE if necessary. Any single one of these members would make effective CEOs in their own right, and may temporarily assume the role of CEO during the CEO’s absence.

Flag Rank Officers have the theoretical ability to usurp the corporation and/or its assets, so caution is advised when assigning heavily privileges titles or the director role.

Common Warrants typically include but are not limited to:

  • Quartermaster – responsible for ensuring bases are well stocked with supplies and premades for members to use
  • Loremaster – knowledgeable in the background and history of EVE, they help roleplayers develop characters consistent with the lore of EVE
  • Drillmaster – guide and train players in the ways of EVE. They explain the mechanics of the game, how to navigate the user interface, and direct players to useful resources for more information or future reference
  • Fittingmaster – design standard corporation fits for members to use, and offer fitting advice to members
  • Recruiter
  • Ambassador

Hangar Access

Titles specifies which hangars may be access and where those hangars may be accessed. In general, members should only have hangar access at the base they are assigned to. This severely restricts the degree to which the corp as a whole can be compromised by theft: if corp items are distributed across many bases, then the loss of a single hangar at a single base is no where near as severe as the loss of the same hangar at all of the bases by a member having that access.

One way to break down hangar access (as I’ve implemented in my corporation, Ryoga Lonely Hearts, is as follows:

  • L1 – S (T1 Frigates and Destroyers)
  • L2 – M (T1 Cruisers and Battlecruisers)
  • L3 – L (T1 Battleships)
  • L4 – T2 and Faction
  • L5 – T3 and XL (Capital Ships)
  • Donations and Input Materials
  • Blueprints

The L1-L5 hangars correspond to titles providing access to those hangars at the member’s assigned base. Note that these titles should not be cumulative: someone with the L5 title does not automatically gain access to the L1-L4 hangars. There are reasons why not all members with high level hangar access should have access to a lower level hangars: many members simply don’t require access to lower level hangars, and as such they should be closed off to mitigate the potential loss due to theft.