1. An SOP standardizes routine procedures. This saves time and reduces detailed orders.

An SOP covers only those operations which lend themselves to standardized procedures.

An SOP establishes common coordination measures between subordinate units. An SOP addresses only those areas where one subordinate unit interacts with another. SOPs should be carefully written to avoid interfering with the command prerogatives of junior leaders or the internal workings of subordinate units. SOPs should allow subordinate leaders the latitude need to carry out their tasks with initiative.

4. What an SOP is NOT:

a. An SOP is NOT restrictive. An SOP does not replace tactical judgment, leadership, or common sense. All leaders are expected to make reasonable decisions even if those decisions contradict the SOP. An SOP is never an excuse for failing to act.

b. An SOP is NOT all-inclusive. Operations which differ each time they are executed have no SOP.

c. An SOP is NOT a regurgitation of published manuals. Standard definitions and standard procedures are NOT repeated.

An SOP is NOT a checklist. An SOP is NOT doctrine. An SOP does NOT tell subordinate commanders how to act or suggest the “best” techniques as defined by HQ.

This SOP applies to all operations and to all Battalion units, platforms or modes executed.

Company SOPs will conform to this Battalion SOP.

This SOP is continuously updated. Submit recommendations and changes to the Battalion Operations Officer.


Return to Table of Contents