I always use this format/outline for my text procedures. Take a look at as many as you can and create one that works for you. You may decide to use flow charts in some situations. We use both, depending upon the subject matter and the expertise level of the intended audience. If you perform a forums search with the words "process interaction" or "process mapping" you will see examples of flow charts varying in complexity. I have been much enlighted in those threads!
This is how I begin to write procedures: Talk to the people who manage and perform the activity(ies) and write down what you do right now, (the good, the bad, and the ugly) regardless of conformance to the requirement. Then compare the standard to what you do now and fill in the unaddressed shalls. Personally, I assign each shall a number and then number a sheet of paper and for each shall I note where in the procedure it is addressed, or that it is not addressed. Then I go back to the people with the requirements that are not addressed and brainstorm ideas for the most simple yet effective way of meeting these requirements. A lot of times when I go back to the people and explain an unaddressed requirement, they say "Oh, we do that already." You have to draw out the information and put it on paper in a suitable format. I have found that this team review of a procedure is also a great way to identify and get rid of any activities that do not add value.
I can't figure out how to attach more than one document, here come two more.
