DEVCOM - Game Pre-Launch Planning Process

This is the Document Release Information
Article Number:	7CAV-DR-059
Scope:	Game Pre Launch Planning Process
Version:	1.0
Effective Date:	22JUN25
Last Modified Date:	27JUN25
Approving Authority:	Regimental Reserve & Development Commander
Point of Contact:	DEVCOM 1iC

Development Command Game Pre-Launch Planning Process

The Development Command (DEVCOM) is the organisation responsible for the identification, planning, launch and support of new Areas of Operation in the 7th Cavalry Regiment. This page lays out the process for game launch planning conducted by the Future Concepts Centre and DEVCOM Lead.

Intent

The intent of the DEVCOM 1iC is to ensure there is a structured and repeatable process for the successful public launching of games which become new Areas of Operation in the 7th Cavalry Gaming Regiment. This shall be achieved by utilising a consistent and robust checklist which ensures all departments are engaged after the game is green-lit at proposal stage. By utilising a clear and publicly declared process all chains of command, including secondary and regimental departments can engage with the Commander’s intent and ensure that the process undergoes continuous improvement as we learn from experience game-to-game. The DEVCOM 2iC and DEVCOM Leads are accountable to the DEVCOM 1iC for achieving his intent.

Launch Checklist

• All Department Engagement will be performed by Support Clerks. If this cannot be done, the Chain of Command will be utilised as follows, in addition to resolving any escalations from a Support Clerk as necessary:
  

DEVCOM Support Clerk → DEVCOM Lead Support Clerk → DEVCOM 2iC → DEVCOM 1iC → R&DC Commander

• All Department Engagements will include the 1iC and 2iC of the supporting Department (S1, S2 etc..)
  

The following Launch Checklist will be planned in a Forum Post:

Unit	Action	Details
S1	Notification of new-game + Coordination PM	The S1 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
S2	Notification of new-game + Coordination PM	The S2 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
S3	Notification of new-game + Coordination PM	The S3 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit. Note that no action is expected from this department initially, but the comms infrastructure is established for any early discussion.
S5	Notification of new-game + Coordination PM	The S5 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
S6	Notification of new-game + Coordination PM	The S6 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
S7	Notification of new-game + Coordination PM	The S7 team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit. Note that no action is expected from this department initially, but the comms infrastructure is established for any early discussion.
RRD	Notification of new-game + Coordination PM	The RRD team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
RTC	Notification of new-game + Coordination PM	The RTC team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
NCOA	Notification of new-game + Coordination PM	The NCOA team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit. Note that no action is expected from this department initially, but the comms infrastructure is established for any early discussion.
ODS	Notification of new-game + Coordination PM	The ODS team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit. Note that no action is expected from this department initially, but the comms infrastructure is established for any early discussion.
WAG	Notification of new-game + Coordination PM	The WAG team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
MP	Notification of new-game + Coordination PM	The MP team will be notified of a new-game to prepare their tracking systems or create awareness. They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
Line Unit Battalions & ACD	Notification of new-game + Coordination PM	The Line Unit Battalions and ACD HQ teams will be notified of a new-game to ensure their awareness which will . They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
SECOPS	Notification of new-game + Coordination PM	The SECOPS HQ team will be notified of a new-game to ensure their awareness which will . They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
ROO	Notification of new-game + Coordination PM	The ROO HQ team will be notified of a new-game to ensure their awareness which will . They require the game acronym in this communication to prevent branching naming conventions (i.e. GZW versus GW) A Coordination PM will be sent by the Lead Support Coordinator or his delegate including the DEVCOM 1iC, 2iC and Lead Support Coordinator as well as the HQ team of this unit.
DEVCOM	Public Announcement – Game Selected	24 hours after Departments & Line Units have been informed of the Game Selection for Launch, the DEVCOM 1iC or 2iC will post in Public Announcements that a game has been selected for Official Support. They shall clarify in this announcement that enlistments will open in 7 Days to allow for admin preparations.
Line Unit Battalions & ACD	Transfers-In Notification	For any Trooper transferring from their current Primary Billet to a DEVCOM Starter Platoon, the DEVCOM 1iC, 2iC or Lead Support Coordinator will confirm the list of troopers transferring in the Coordination PM. A separate PM for each individual trooper will be sent capturing every leader in the trooper’s chain of Command from Trooper to Battalion This enables clear and concise communication about the transferees, and allows Leaders transferring in (ASL+) to have a planned succession to prevent disruption to daily 7Cav operations. This serves as “top-down” communication of a leader-transfer.
Line Unit Battalions & ACD	Transfers-In PAFs	Leaders (ASL+) who are transferring into a Starter Platoon must submit PAFs to initiate formal transfer. The DEVCOM Lead will inform the trooper if this is necessary. This serves as “bottom-up” communication of a leader-transfer, ensuring every member of the trooper’s chain of command is aware and involved in the process.
Discord Team	New channels & roles	The DEVCOM Lead Support Coordinator, 2iC or 1iC will communicate using a Discord Request ticket on the Discord app to initiate new roles, permissions and channels as required.
S6	New forums & roles	If the A-D/SP/ACD forums experience technical issues or require amendment / expansion, then the DEVCOM Lead shall submit a S6 Ticket on the website clearly articulating what the desired state and current state are, so that S6 can easily comprehend what must be done to amend the forums.
WAG	New Supported Game – Front-page	The Lead Support Coordinator (or delegate) shall submit a ticket to WAG to change the front-page of the Wiki to show a new supported game, providing an image as required, and any public server information to be included as required.
WAG	New Supported Game – DEVCOM page	The Lead Support Coordinator (or delegate) shall submit a ticket to WAG to change the DEVCOM-page of the Wiki to show a new supported game, providing an image as required and the unit designation that the game has been attributed to.
S1	Ready For Enlistments (RFE) check	The Lead Support Coordinator (or delegate) shall request a timeline for when S1 will be RFE and await confirmation that they are RFE. (Performed in Coordination thread).
S2	Ready For Enlistments (RFE) check	The Lead Support Coordinator (or delegate) shall request a timeline for when S2 will be RFE, and await confirmation that they are RFE. (Performed in Coordination thread).
RRD	Ready For Enlistments (RFE) check	The Lead Support Coordinator (or delegate) shall request a timeline for when RRD will be RFE, and await confirmation that they are RFE. (Performed in Coordination thread).
RTC	Ready For Enlistments (RFE) check	The Lead Support Coordinator (or delegate) shall request a timeline for when RTC will be RFE, and await confirmation that they are RFE. (Performed in Coordination thread).
RRD	Instruct Enlistments are Open	The Lead Support Coordinator (or delegate) shall (once RRD, RTC, S1 and S2) are RFE, instruct them to open enlistments and announce this in Public Announcements.
DEVCOM	Public Announcement – Enlistments Open	24 hours after instructing RRD to open enlistments, The DEVCOM 1iC or 2iC will post in Public Announcements that a game has been selected for Official Support. They shall clarify in this announcement that enlistments will open in 7 Days to allow for admin preparations.
DEVCOM	Transfers Start	The DEVCOM 2iC or 1iC shall inform the Regiment when all planned transfers-in commence.
Line Unit Battalions & ACD	Transfers Complete notification	The DEVCOM 2iC or 1iC shall inform the Battalions when all planned transfers-in have been completed to signal the end of any disruption.
DEVCOM	First Roll-Call	The DEVCOM Lead shall post the first Roll Call in the unit designation’s area.
S5	Public Relations Strategy	The Lead Support Coordinator (or delegate) shall develop a PR strategy with S5 and offer them the support of DEVCOM HQ + the RDC Commander in execution, for example establishing a 7Cav presence on Reddit, Discord etc. The Lead Support Coordinator will request via the ticket/request process any S5 Media works required.
RRD	Recruiting Strategy	The Lead Support Coordinator (or delegate) shall develop a Recruiting strategy with RRD and offer them the support of DEVCOM HQ + the RDC Commander in execution, for example setting up recruiting events, resources and techniques.
RTC	Briefing & Boot Camp Strategy	The Lead Support Coordinator shall confirm in writing the intention to operate a “Briefing Only” posture until a Boot Camp is developed for the new game, unless a historic one exists and was approved. The Lead Support Coordinator shall offer the support of DEVCOM HQ + the RDC Commander in execution, for example delivering briefings to add to the DI capacity, by receiving the briefing script.

Plan submission, review and approval

The DEVCOM Lead will submit the Pre-Launch Plan (with dates for when each event is required) for the approval of the DEVCOM Lead Support Coordinator, 2iC and 1iC. The DEVCOM Lead will allow 72 hours for review and approval of the plan before the first date of action is required. This ensures that the reviewers are aware of their responsibilities to support the plan before it is enacted. The DEVCOM Lead may submit this plan prior to receiving a green-light from the Regimental CO/XO on the Game Proposal. The DEVCOM 1iC, 2iC or Lead Support Coordinator may request changes prior to approval as required. They may delegate their review and approval if on LOA and their responsibilities must be covered in their absence where indicated in the plan.

Conclusion

This DEVCOM Game Pre-Launch Planning Process serves as a descriptive guide to the DEVCOM scope of launch planning operations, and the third key event in game development in the 7th Cavalry Gaming Regiment.