<aside>
đź’ˇ You can also make a copy of our Google Doc template here.
</aside>
[SOP] {Title Goes Here}
| Purpose/Objective |
{Define what the end result or the goal is for the SOP you are writing} |
| Program/App/Tool |
{List the application/program/tools associated with the SOP} |
| Department/Role |
{If there is a specific department or role that this SOP applies to put it here. Example, Marketing, Assistant, Project management } |
| Resources |
{You can include links to other applicable SOP’s or anything the reader may find useful. } |
| Date Created |
{Include the date the SOP was made as well as revision dates. This allows you to know if it is up to date or out of date easily} |
| Creator/Author |
{Include your name. This way if anyone has a question they will know who to go to for clarification} |
NOTE ABOUT CREATING SOPs:
Each SOP should include:
- A clear objective (what is the end goal?)
- Tools needed to accomplish the task.
- Step-by-step instructions on how to complete a process. Be as detailed as possible. When writing an SOP you should do so without the expectation that the reader has background knowledge about the process. You of course can simplify this by adding links to reference materials. Providing instruction in written and visual formats will also help all different learning styles.
- Written instructions with screenshots
- Video tutorials
- Process Flow chart
- Links to additional documentation (if needed)
Step-by-Step Process of {Title of SOP}
{Include screenshots/videos where applicable}
The following is a list of things to keep in mind when writing your SOP. These can really help guide your SOP creation.
- This step-by-step guide can be a checklist, a flowchart of the process, screenshots with short descriptions, a hierarchy of steps where you have the main step, and then subtasks under each main step. The more broken down the process the easier it will be to follow.
- Include all necessary and additional details that are needed to complete each step. Discuss decisions that need to be made, possible blockers, and any other “what if” scenarios that may arise.
- Clarification of terminology, including acronyms and phrases that may not be familiar to your audience. Try to use plain language as much as possible.
- A complete list of all items that are needed, where to find them, and when each will be needed.
- A troubleshooting section to cover things that can go wrong, what types of things the reader should look for, and what may interfere with the final outcome.
Additional Documentation
{Links with brief description titles go here. This can include links to apps/tool/program tutorials, links to videos you have created that cater to this SOP, links to other SOP’s that may be useful}
Review, Test, Edit, Repeat