Variable SOP Structure Template

This SOP is an example of a procedure containing fixed and variable tasks.

Introduction:

Summary:

Details:

Step 1 [Rename to reflect action]

Step 2

Step 3

Step 4

Step 5

Overview:

Related Checklists:

Introduction:

This variable standard operating procedure (SOP) template was developed specifically to provide a baseline structure for you to be able to utilize to create your own company procedures.

Simple add this template directly to your Process Street account, and you'll have access to all of our features to edit the template in whichever way best suits your needs. Some of our editing capabilities include:

Adding/deleting tasks
Form fields to record data
Ability to add descriptive text or media to tasks
Assigning team member roles to collaborate on procedures
Using conditional logic to offer variable pathways depending on decisions made along the way
Syncing the template with your existing software for better workflow automation

We've included, throughout the structure, explanatory information to help build context for you as you move through the procedure, and also provided clear, completable tasks which make up the steps of the procedure. For example, you'll find form fields that you'll be able to use to gather necessary information.

When you've edited the template to your liking, you can either run it as a checklist within Process Street, or you can export the template as a PDF if you prefer a standalone or physical document.

Further info related to standard operating procedures

The basics of building standard operating procedures

Adherence to standard operating procedures and ISO standards

Using Process Street to get the most out of your standard operating procedures

What is the "Variable SOP Structure Template"?

This SOP template is part of a series of innovative SOP structure templates, designed to make building, implementing, and following SOPs easier for everyone involved.

The name of this template refers to the combination of fixed and variable instructions. Some parts of this template will be fixed (i.e. stuff you know will need to be done every time) while certain steps will be variable (i.e. the "variable" daily tasks you may not know until you start the process).

Check out our article for more SOP examples, and to see the other templates for SOP innovation.

At the end of this procedure, we've provided a list of the different standard operating procedure examples we've created. We've also made sure to include procedures that can be used by companies throughout various industries.

All of the listed SOP procedures are publicly available. So that just means you can add any of them to your Process Street account and customize them to better suit you and your company's needs.

Summary:

Edit this template to change the text in this section.

[Procedure Title]

Revision:

Date: You can enter the date manually or use the date form field

Doc Number:

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

Purpose: Describe 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]

Responsibility: Note 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:

Who is following this procedure?

What is the start date?

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.

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

This is a long text field

This is a dropdown field

This is a multi choice field

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: