This is straight from the Joint Publication (JP) 3-31, Joint Land Operations:
"The Army SOP is designed to standardize the way units operate, ensuring that tasks are performed consistently and efficiently. It is a critical component of the Army’s operational planning and execution process, as it provides a clear understanding of the procedures and protocols that must be followed in various situations."
SOPs can be at any level, for any group, or any specific task. An SOP can also be different between different units for accomplishing the same task. Basically, imagine if you are 60 years old, and are writing a book about kicking ass in life. At some point you have figured out a few tasks that can be solved by using a simple problem solving approach. Your SOP might include planning stages, equipment requirements, what you are doing while out performing the job or activity, and maybe even a follow-up at the end. Your SOP might simply include basic procedures on how to navigate from point to another in your vehicle. Then, you'll make a separate SOP on that same trip but while on foot. Pretty simple, right? So what is the point of an SOP?
While we may think everything we know and do are just "common sense," it may not be common sense to everyone you are leading or working with. But, the fact remains, you know the correct or most efficient way to accomplish a task, and you need your team to be able to do it your way. So what if you are sick or injured, or just not around? Can you trust your team to perform the task, by your standards, without you being there? Most likely not. You can, however, enable them to pull out the SOP for said task, and follow those instructions. As leaders, we cannot expect our team to know everything that we know, or to perform everything exactly like we can. However, we can teach them as much as possible and then, when you are not around and they become ignorant, the SOP will become their default. Lastly, SOPs can be used as assisting people through basic tasks during times of extreme stress. This is where unit training and battle drills come in to play.
We build our tactics and battle drill SOPs by evaluating our unit capabilities, combined with analyzing the operational considerations of our environment (METT-TC). What is our job, and what are we capable of accomplishing? So first, we develop our SOPs. Next, we must test those SOPs. This is where training and sometimes, real-world testing comes into play. Hopefully we are testing our SOPs in training before the real-world does it for us, because that can suck.
In summary, we should establish SOPs for basic tasks that we can expect our team to be able to accomplish. Can we conduct a reconnaissance patrol? If so, how do we actually do it? It could come down to a simple word document with task, conditions, and standards, or just a word doc with a step by step instruction. Many unit SOPs for radio communications and first aid applications will be step by step. However, when we are talking about battlefield tactics, the SOP will become lengthier and more complicated. The bottom line is that we have to build the SOPs in the first place, and then test them to improve them.
A few examples of necessary SOPs:
1. TOC setup, organization, and duties
2. Small Unit Tactics: Patrolling, OPs, Reconnaissance, Battle Drills, etc
3. Unit training and planning
4. Communications and Radio Etiquette
5. Team structure and equipment (MTOE)
