CMDP Compliance Documents


BRIGADE DISPATCH STANDARD OPERATING PROCEDURE

176th Engineer Brigade (TXARNG)


Administrative Data

| Field | Value |

|-------|-------|

| Effective Date | [DD MONTH YYYY] |

| Supersedes | [Previous SOP Date or "N/A"] |

| Review Date | [Annual Review Date] |

| Approval Authority | Brigade Commander |


1. PURPOSE

This SOP establishes brigade-level dispatch policy: releasing and recovering tactical and combat Army vehicles under this brigade with complete dispatch documentation, maintenance accountability, and safety controls IAW AR 385-10, AR 750-1, AR 58-1, DA Pam 750-8, applicable TMs, and operator qualification rules IAW AR 600-55 where they affect dispatch.

Purpose (specifics). This SOP clarifies brigade dispatch execution where Army regulation expects commands to apply requirements at the vehicle-and-movement level. One example is when AR 385-10 §13-6 calls for licensed assistant drivers or co-drivers—the factors named in that section (including duty and rest limits, extended operations, darkness, NVG, MOPP, weather, visibility, and comparable conditions). Dispatch personnel and commanders use this SOP to recognize that call at dispatch and document crew accordingly.3

Each tactical movement is handled as one dispatch from approval through recovery. An approving authority authorizes the mission; dispatch personnel finish the dispatch record in GCSS-Army, using DD Form 1970/1970-E and packet forms when manual dispatch applies. Before release, faults and PMCS on the record reflect actual equipment condition, including Circle-X only when the commander approves it for that mission. Crew assignments (for example vehicle commander and assistant driver) match what that movement requires IAW regulation and orders.

When the equipment returns, closure captures mileage, hours, fuel, oil, faults from the trip, and other required entries on DD Form 1970/1970-E and in GCSS-Army when used, so maintenance data stays accurate and the chain of command keeps accountability for the platform.

This SOP is intended to:

This SOP establishes brigade minimum standards. Subordinate units may publish more restrictive procedures.


2. APPLICABILITY

This SOP applies to all elements of 176th Engineer Brigade (TXARNG) for dispatch and recovery of tactical and combat Army vehicles (including dispatched movements supported through GCSS-Army). It applies to personnel who authorize dispatch, dispatch equipment, or close dispatch records.

Administrative (non-tactical) vehicle dispatch follows AR 58-1 and unit procedures.


3. REFERENCES

Citation system. Each superscript links to one numbered reference below.

  1. Department of the Army. (2019). Army Regulation 600-55: The Army driver and operator standardization program (selection, training, testing, and licensing). Headquarters, Department of the Army.
  2. Department of the Army. (2023). Army Regulation 750-1: Army materiel maintenance policy. Headquarters, Department of the Army.
  3. Department of the Army. (2023). Army Regulation 385-10: The Army safety and occupational health program. Headquarters, Department of the Army.
  4. Department of the Army. (2023). DA Pamphlet 385-10: Army safety and occupational health program procedures. Headquarters, Department of the Army.
  5. Department of the Army. DA Pamphlet 750-8: Functional users manual for the Army Maintenance Management System—Automated (GCSS-Army). Headquarters, Department of the Army.
  6. Department of the Army. Army Regulation 25-400-2: The Army Records Information Management System (ARIMS). Headquarters, Department of the Army.
  7. Department of the Army. Army Regulation 58-1: Management, acquisition, and use of motor vehicles. Headquarters, Department of the Army.
  8. Department of the Army. Applicable equipment technical manuals (TM –10 / –20 series and related equipment publications) for each dispatched platform.
  9. Texas Military Department. Texas Army National Guard policies and directives governing national guard forces in state and federal status, including commander oversight and inspection programs.

4. RESPONSIBILITIES

4.1 Brigade Commander

4.2 Subordinate commanders (battalion and company)

4.3 Dispatchers (appointed by the commander)

4.4 Operators, Vehicle Commanders, co-drivers, assistant drivers


5. GENERAL

Vehicle dispatch rests with the chain of command: commanders publish expectations, appoint dispatchers in writing, and remain accountable for equipment that leaves the motor pool and returns.7

Commanders ensure:

During field conditions, network outages, or GCSS-Army outages, commands still enforce qualification verification, PMCS, safety controls, and dispatch accountability. When automation is unavailable, commands execute manual dispatch (paragraph 12) so those controls remain in effect.5


6. REQUIRED SAFETY EQUIPMENT

Before rollout, dispatched vehicles carry serviceable safety and mission equipment required for that platform and movement.8


7. DISPATCH PREREQUISITES (OPERATOR QUALIFICATION)

At dispatch, authorities verify the operator is qualified on the specific dispatched platform per OF 346 / DA Form 5984-E and current operator record in GCSS-Army IAW AR 600-55.1

Commands dispatch equipment only when qualification is current, complete, in good standing, and verified at the dispatch point before keys or vehicles release.1

Learner permits: Independent tactical missions require a fully qualified primary operator IAW AR 600-55; learner supervision and progression follow AR 600-55 and unit licensing procedures.1

Readiness for verification: Commands align operator qualification data in GCSS-Army with licensing records at least annually, and again within 90 days before major convoy operations, annual training, mobilization, or large-scale tactical movements, so dispatch desks verify against reliable records.5


8. DISPATCHER REQUIREMENTS

Commanders appoint dispatchers in writing.1

Dispatcher training covers verifying operator qualification at dispatch IAW AR 600-55 and GCSS-Army; completing dispatch in GCSS-Army and through manual procedures; reviewing faults and Circle-X limits prior to release; and preparing DD Form 1970/1970-E and utilization documentation when missions require it.5

Dispatchers release vehicles only when operator qualification matches the platform; services and operator status are current; PMCS is valid for dispatch; deficiencies are corrected, authorized under Circle-X for that mission, or otherwise safe IAW maintenance and safety publications; and the dispatch packet is complete.5


9. VEHICLE COMMANDERS AND CREW (DISPATCH)

Crew composition for tactical movements carries out commander responsibilities for vehicle commanders (VCs), assistant drivers, and senior occupants IAW AR 385-10 §13-2c and mandatory procedures in DA Pam 385-10.3

9.1 When a Vehicle Commander is required before dispatch

(1) Army combat vehicles (ACVs). Each ACV has a track commander or VC IAW AR 385-10 §13-4e. Release ACV movements after that Soldier is assigned and the dispatch reflects the VC or track commander duty.3

(2) Heavy tactical wheeled (non-ACV). For dispatched tactical vehicles in the nominal 5-ton cargo capacity class or heavier (brigade definition for heavy tactical trucks), commands name a VC before movement and show that duty on dispatch documentation.9

(3) Commander-directed. The approving commander may require a VC for any tactical dispatch the commander judges high-risk.9

9.2 Vehicle commander (VC)

Operator license. The VC holds a valid operator license on the dispatched platform IAW AR 600-55.1

Movement duties (dispatch-relevant). The VC leads crew-level safety for the movement: dispatch compliance, PMCS awareness at roll-out, convoy discipline, ground guides when required, fatigue awareness, and halting unsafe operation.3

VC compared with assistant driver/co-driver. VC duty and assistant-driver/co-driver duty are not the same duty. Assignment as VC does not assign assistant-driver or co-driver duty. The VC may serve as VC without also being assigned assistant driver or co-driver unless regulation or the commander also assigns assistant-driver or co-driver duty on the dispatch.3

9.3 Assistant driver / co-driver

Assignment. Commands assign licensed assistant drivers or co-drivers when AR 385-10 §13-6 calls for them—duty and rest limits, extended operations, darkness, NVG, MOPP, weather, reduced visibility, and similar factors—or when the approving commander documents assistant-driver or co-driver requirements on the dispatch.3

Co-driver compared with VC. A Soldier assigned only as assistant driver or co-driver does not perform VC duties unless the dispatch also designates that Soldier as VC for that movement.3

9.4 When VC is required vs when assistant driver/co-driver may be required without VC

VC required: When paragraph 9.1 applies (§13-4e for ACVs, heavy tactical wheeled rule (2), or commander-directed VC (3)).3

Assistant driver or co-driver without VC: When §13-6 or commander-directed crew rules call for an assistant driver or co-driver and that vehicle/movement does not trigger any VC requirement in this SOP (§13-4e, heavy tactical wheeled VC rule (2), or commander-directed VC (3)).3

9.5 Senior occupant

VC or driver authority rests on dispatch designation and qualification, not on rank or seating position alone. When a senior occupant serves as VC or driver, the dispatch names that duty for the movement, and the Soldier meets licensing rules—including holding the correct operator license when acting as driver.1


10. OPERATOR FATIGUE (LIMITS AT DISPATCH)

Commanders enforce AR 385-10 §13-6: operators receive at least 8 consecutive hours of rest during any 24-hour period and limit driving to 10 hours in a duty period; assign qualified assistant drivers when mission length or conditions require.3


11. CIRCLE-X PROCEDURES

Circle-X grants one-time mission relief for deficiencies assessed as acceptable risk under maintenance rules and GCSS-Army procedures.5

Only commanders or designated representatives authorize Circle-X. Approvers review faults, document risk decisions, set restrictions and mission limits, and confirm the movement stays within safe bounds.3

Circle-X applies to a single mission. When the mission ends, authorization expires, equipment returns to normal deadline rules, and required repairs stay on the books, scheduled IAW maintenance procedures.2

Circle-X applies only to fault categories that maintenance and safety publications identify as eligible for mission relief.8 Brake, steering, tire, fuel leak, fire suppression, seat belt, visibility, weapon-safety, TM-non-mission-capable, and similar unsafe categories must be corrected before dispatch under those publications.8

Record Circle-X approval, authority, restrictions, and effective date/time on DD Form 1970/1970-E and in GCSS-Army dispatch fields IAW unit procedures.5


12. MANUAL DISPATCH PROCEDURES

Commands use manual dispatch when GCSS-Army or supporting networks are unavailable, or during sustained field or disconnected operations.5

Manual packets still capture qualification verification, PMCS and fault review, release authorization, mileage and hour accountability, fuel tracking where required, and later upload into GCSS-Army when connectivity returns.5

Manual dispatch carries forward every substantive requirement from electronic dispatch: qualification checks, PMCS, Circle-X limits, safety rules, and records obligations.5


13. GARRISON VS FIELD DISPATCH

Garrison. Units follow full administrative controls and standard GCSS-Army dispatch workflows consistent with home-station accountability.5

Field. Commanders may approve streamlined workflows when dispatch personnel still capture who authorized the movement, who is qualified to operate, equipment faults and PMCS status, safety limits (including Circle-X boundaries), and overall equipment accountability expected by maintenance and higher headquarters.9


14. DISPATCH CLOSING

Operators record mileage and equipment hours, fuel and oil as publications require on DD Form 1970/1970-E and in GCSS-Army when close-out is electronic; record faults observed during the mission; and return dispatch materials promptly after recovery.5

Equipment records and dispatch personnel validate that entries are complete, update GCSS-Army without undue delay, close the dispatch record, and route new faults into maintenance records when maintenance handoff is required.5

Close dispatch entries using verified operational data. Commander-approved exceptions for estimated readings apply only when the commander documents operational necessity and follows unit procedures for correction.5


15. COMMONLY MISSED DISPATCH REQUIREMENTS


16. RECORDS MANAGEMENT

Commands retain dispatch-related records IAW AR 25-400-2 (ARIMS), DA Pam 750-8, and applicable maintenance retention schedules.6


17. SUBORDINATE UNIT RESPONSIBILITIES

Battalion and company SOPs spell out how dispatch desks run day to day: hours of operation, key control, dispatch packets, motor pool support, convoy documentation, and related local practices. This brigade SOP states minimum tactical dispatch standards for combat equipment; unit procedures meet or exceed those standards, and commanders coordinate through the brigade before adopting anything looser.9


18. ACCIDENT AND INCIDENT REPORTING

Commands report accidents and incidents IAW AR 385-10, DA Pam 385-10, and Texas Army National Guard supplemental guidance (including aid, notifications, scene preservation, required reports, and routing statements through command channels).3


APPROVAL:9

[LAST NAME, FIRST NAME MI.]

[RANK, BRANCH, COMPONENT]

Brigade Commander


CMDP Reference: 10(2)-29