Intro to Standard Operating Procedure (SOP) Template:

Standard Operating Procedure (SOP) Template Structure

The purpose of this standard operating procedure (SOP) template is to provide the necessary structure from which to create your own procedures.

Add this template to your Process Street account and you can customize all aspects of its design, including:

  • Adding or removing tasks
  • Adding explanatory text or rich media
  • Adding form fields to gather information
  • Assigning the procedure to other members of your organization
  • Adding conditional logic to create different pathways for execution
  • Connecting the template with the other software you use to enable automations.

Process Street has a broad range of functions and features but this structure focuses on the core purpose of creating procedures. 

Within the structure of the template you will see prompts for where to add information. 

Some sections operate as header information. Other sections are completable tasks which constitute the steps of the procedure. 

You can either run this template as a checklist inside Process Street for your team to follow, or you can export the template as a PDF.

Read on through the template to see what information should be included where. 

More information about standard operating procedures

We have three different areas of interest which we'll provide further content for below:

  • Standard operating procedures and the basics of building processes
  • Standard operating procedures and adherence to standards like ISO
  • How to make the most out of Process Street for standard operating procedures
Standard operating procedures and the basics of building processes
Standard operating procedures and adherence to standards like ISO
How to make the most out of Process Street for standard operating procedures

At the end of this template you will find links to a range of example standard operating procedures. We have included a large number of procedures which may be used by a marketing agency. From marketing procedures to accounting procedures, to design procedures, to agile management procedures. 

These procedures can act as useful examples for best practice within the Process Street platform. 

They are all publicly available procedures, meaning you can add any of them directly to your Process Street account and edit them accordingly to suit your needs. 

Summary:

Edit this template to change the text in this section

[Procedure Title]

Revision:

DateYou can enter the date manually or use the date form field

Doc Number:

ScopeDescribe when the procedure starts, when it finishes, and what other limitations are applied to the expected workflow.

PurposeDescribe the output of the procedure and explain why it is constructed the way it is.

Details:

Edit this template to change the text in this section

Revision and Approval
  • [revision number] - [date] - [nature of changes] - [approved by]
  • [revision number] - [date] - [nature of changes] - [approved by]
  • [revision number] - [date] - [nature of changes] - [approved by]
  • [revision number] - [date] - [nature of changes] - [approved by]

ResponsibilityNote who is responsible for this procedure and why it is their responsibility.

Definitions: Use this section to explain any acronyms or technical terms which are used throughout the procedure. You can use bullet points.

  • TT - Technical terminology
  • ISK - Industry specific knowledge
  • ETC - Et cetera

Step 1 [Rename to reflect action]

Rename the title of this step to reflect the action required.

A good first step at the beginning of a procedure is to include some of the details of who is undertaking the task.

See the example form fields below:

Including information like this at the beginning means people are held accountable for their work.

Step 2

A task may include subtasks. 

For subtasks you could use bullet points:

  • Step 1
  • Step 2
  • Step 3

However, a more actionable route might be to use the subtask field:

  • 1
    Step 1
  • 2
    Step 2
  • 3
    Step 3

Step 3

Tasks in a procedure should not contain too much information. 

For some tasks explanatory work instructions are important. 

You can use image or video fields to display rich media if that will help the employee complete the task to the best of their ability.

An example image

Step 4

If the standard operating procedures will be completed inside Process Street, it is wise to use form fields to collect information.

Below you can see 3 example styles of fields you can use:

  • Long text fields
  • Dropdown fields
  • Multi choice fields
  • 1
    Option 1
  • 2
    Option 2
  • 3
    Option 3

Step 5

If your employees are following standard operating procedures inside Process Street, then you can also add other features. 

You could add conditional logic so that the linear order of the procedure changes based on the information entered into the checklist.

You could add Stop Tasks which enforce the order of a procedure and prevent the user from continuing with the process until the right steps have been completed in the right order. 

Or you could connect with Zapier to automate actions in other apps and webapps based on the completion of items in your Process Street checklist. Via Zapier, Process Street integrates with over 1,000 other products.

You can see some examples below:

Overview:

Include a diagram here to illustrate the flow of the process. See the example uploaded below.

Standard operating procedure workflow diagram example

Sign up for a FREE account and
search thousands of checklists in our library.

Sign up for a FREE account and search thousands of checklists in our library.