S2 Department - Engaging a Recruit’s Chain of Command

This is the Document Release Information
Article Number:	7CAV-DR-064
Scope:	S2 Department - Engaging a Recruit’s Chain of Command
Version:	Version 1.0
Effective Date:	08JUL25
Last Modified Date:	DDMMMYYYY
Approving Authority:	Regimental Security Operations Officer
Point of Contact:	S2 1IC

Objective

To define a structured and auditable process for S2 Investigators when communication with a recruit's Chain of Command (CoC) is necessary during an investigation.

Procedure

Step 1: Initial Request

• The assigned Investigator determines the need to engage with a recruit’s Chain of Command.
• The Investigator must submit a formal request to their Senior Investigator. This request must be posted in the recruit’s investigation folder comment section and should clearly include:
  • The reason for contact.
  • The intended message or inquiry.
  • Any supporting context or relevant findings.

Step 2: Review by Senior Investigator

• The Senior Investigator reviews the request to ensure it is:
  • Justified,
  • Clearly written,
  • Aligned with investigative protocols.
• If approved, the Senior escalates the request to the S2 Lead Investigator.
• If denied, the Senior provides feedback and guidance for revision or alternative approaches.

Step 3: Escalation to Lead Investigator

• The S2 Lead Investigator evaluates the request and makes the final decision based on:
  • Strategic need,
  • Sensitivity of the case,
  • Potential impact on the department or ongoing investigations.
• The Lead Investigator may approve, deny, or request clarification.
• Note: S2 HQ (1IC or 2IC) retains the authority to override or review decisions made by the Lead Investigator and the, including issuing approvals, denials, or clarification requests when deemed necessary.

Step 4: Execution of Contact

• Upon approval, one of the following occurs:
  • The Lead Investigator communicates directly with the recruit’s CoC.
  • The task is delegated to the Senior Investigator or original Investigator, depending on sensitivity and complexity.
• Communication must be professional, factual, and limited to necessary information only.

Step 5: Documentation Requirements

• All requests, approvals/denials, and resulting actions must be recorded in the investigation folder and in the appropriate S2 communication platform (e.g., S2 PM or S2 tracker).
• Documentation must include:
  • The rationale behind the contact,
  • A summary of what was communicated,
  • Any response or outcome received from the CoC.

Step 6: Post-Action Review

• A brief debrief should be conducted between the Investigator and their Senior (or S2 HQ if involved) to review:
  • The outcome of the communication,
  • Any follow-up required,
  • Lessons learned to inform future engagements.

Step 7: Compliance

• All actions must comply with:
  • Departmental SOPs,
  • 7th Cavalry General Orders,
  • Operational security guidelines.
• All communication must be professional and should never bring the department or regiment into disrepute.

Step 8: Timelines & Response Expectations

• Senior Investigators should review and respond to requests within 48 hours.
• The S2 Lead Investigator or S2 HQ should respond to escalated requests within 72 hours whenever possible.
• Any anticipated delays must be communicated to the originating Investigator with an estimated timeline.

Step 9: Priority Situations

• In situations requiring timely action, the S2 Lead Investigator or S2 HQ may expedite contact with the recruit's Chain of Command, bypassing normal review steps if appropriate.
• These actions should be reserved for clearly justified cases and must be documented thoroughly for review by S2 HQ afterward.