Has anybody created a squadron SOP and found it useful for their squadron? I've always wanted to write one for my squadron to collect all the random memos about policy into one source. I was curious if this is common practice for other squadrons.
We use an SOI (standard operating instruction) which is a little out of date. It is quite helpful to accumulate those little things that everyone should be doing for the squadron. Ours is a little wordy, however, so I would recommend keeping the length down if possible. 8)
Quote from: B.Kahuna on February 09, 2010, 12:22:04 AM
Has anybody created a squadron SOP and found it useful for their squadron? I've always wanted to write one for my squadron to collect all the random memos about policy into one source. I was curious if this is common practice for other squadrons.
How many policies do you have / need?
We just finalized the Cadet SOI for our unit. I wrote it and then solicited feedback from the cadet staff. They had some good ideas and suggestions.
Our main reason for writing the SOI was to formally document how things should be done in our Squadron. We would come up with ideas and policies, but often we would not follow them because the staff wasn't informed or didn't understand.
Now everything is written down and if there are any questions we simply reference the document.
You can take a look at our if you like:
http://dl.dropbox.com/u/3459581/OBCAP%20SOI.pdf
We are taking the approach the the SOI is a living document and is meant to to be changed and updated as needs and situation dictate.
A perfect example is our organization chart. As cadets get promoted and take on leadership positions we update the SOI. We are also in the process of adding a Morale and Motivation section where we explain non regulatory aspects of the squadron such as the awarding and wear of our squadron patch, challenge coins, etc.
There has been a period of adjustment as we transition to actually following the SOI, but it has made us much more organized and effective.
Your document is well put together but falls into the same trap that most Wing supplements do, which is too much reiteration of regulations
that exist elsewhere.
It doesn't break any rules, but its also unnecessary.
Supplements and procedures, etc., should be specific to a need at the level they are written, without just repeating things already in force at a higher level. The stuff about meeting times, needing a flashlight, or what positions the cadet CC can appoint are fine, but retyping grooming or CPPT rules seems redundant to me.
If I wrote it out, the one for my squadron would probably be about 2-3 pages. Examples of things I'd include are PT uniform regulations, squadron baseball caps, classroom procedures, review board policies etc.
Thanks Lt Kloehn for the link, I'll take a look at your SOI.
On the cadet side, my squadron has used a Cadet Policy Letter for nearly a decade. The most recent revision is located on our website here. (http://tx313.files.wordpress.com/2010/02/cadet-policy-letter-2-8-10.pdf)
Mostly we use it to keep continuity in scheduling and admin areas. Take a look, see what you think.
Quote from: Eclipse on February 09, 2010, 05:22:15 PM
Your document is well put together but falls into the same trap that most Wing supplements do, which is too much reiteration of regulations
that exist elsewhere.
I actually agree. Our SOI is a "living document" that is meant to be updated and and changed.
In our case, we reiterated some of the regulations because we were doing things incorrectly. Spelling out the promotion policy and explaining why things are to be done a certain way was necessary for us to correct how we did things.
A lot of the language will be removed once it becomes standard operating procedure in or Squadorn.
I did a post asking for the same stuff in Aug of 08. Here is the linky:
http://captalk.net/index.php?topic=5792.msg110357#msg110357
Everyone posted some really good stuff that I have been using ever since.