Conditional SOP Structure Template

This SOP is allows for flexible process outcomes and presents branching options based on conditional logic.

Introduction:

Summary:

Details:

Step 1 [Rename to reflect action]

Step 2

Step 3

Step 4

[Conditional task]

Step 5

Overview:

Related Checklists:

Introduction:

This conditional standard operating procedure (SOP) template was developed to provide a strong foundation from which to build your own procedures.

To get started, you simply add this template to your Process Street account and you'll have the freedom to edit the design in however way best suits your needs.

We offer features such as:

Editing, rearranging, adding, and deleting tasks
Ability to add text or rich media to your tasks if needed
Use of form fields to easily gather necessary data
Role assignments feature to work together with your peers on procedures
Option of applying conditional logic to offer dynamic, alternative outcomes
Syncing the template with your other softwares to better automate your processes

The Process Street platform offers a wide scope of features, but this template will focus on the most important steps when building procedures.

You'll find, throughout the template, forms fields to add necessary information.

The template will offer contextual information to help develop your understanding of the process as you move along, and will also provide clear, actionable steps.

After preparing your template, you can either run it as a checklist within Process Street's platform, or you can export the template as a PDF if you prefer a standalone document.

Further information about SOPs

Basics of SOPs and building processes

SOPs and adherence to management standards

Using Process Street for SOPs

What is the "Conditional 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 how various different outcomes can be proactively prepared for, and will be displayed to the person following the SOP based on whatever criteria you set (i.e. if the response to a form field is "yes" instead of "no").

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

In the final section of this template, you'll find a list of SOP templates we've created that are applicable for those in industries spanning from accounting, to marketing, to agile management, to design, etc.

All of the procedure templates are publicly available. You can simply add any of them to your Process Street account and you'll be able to customize the design in whichever way best suits 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

[Conditional task]

This is a conditional task that only shows up if Option 1 is selected from the multi choice field.

Not all processes are as simple as getting from point A to point B.

Our Conditional Logic feature allows you to build realistic and dynamic checklists with if/then logic that can adapt to the user's changing needs.

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: