Skip to end of banner
Go to start of banner

SOP01-T1: SOP Template

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

SG-SOP01-T1: SOP Template

Revision Date: 2023.09.29


SG-SOP[##]: [Title]

Revision Date: [yyyy.mm.dd]

Table of Contents

I.  Description

(Italicized text is instructions, which get deleted from the template.)

This section should answer the question, “Why is this procedure in place?”  This should be concise to allow the reader to easily identify the content.  This section should be brief, but background can be provided when needed.  Do not include minor details in this section.

II.  Objectives

Include a list of objectives that will be accomplished through the procedure.  After reading the procedure, the audience should be able to understand the document’s objectives.

III.  Scope

Specify or describe the extent to which teams, people, work functions, or operations this SOP applies.  

IV.  Definitions & Acronyms

List and define the terms and acronyms used uniquely in this document. List in alphabetical order.

V.  Authorities/Responsibilities

OPTIONAL FOR RMs - Identify the stakeholders and briefly describe their roles.  Highlight roles who have pivotal responsibilities and authority to interpret organizational policies and/or determine the content and structure of the SOP.

VI.  Procedures

For RMs, the “Procedures” title can be relabeled for descriptive purposes, based on the purpose of the document.  

List and explain the steps required to fulfill the Objectives of the SOP within the Scope defined above.  Use direct, succinct, instructive language (e.g., do not use the word “please”).  Use the clearest means necessary for explaining the work, including bullets, numbered lists or tables.

When possible, embed screenshots, decision charts or flow diagrams when visuals provide additional context or detail to understand how to complete the work.

Additional Section Headers should be added if helpful to overall document organization.

Formatting limitations in Confluence include two types of lists only:

  1. Numbered lists up to six levels with format as 1 / a / i / 1 / a / i

  2. Bulleted lists up to four levels, with format as solid / open circle / square / solid.

VI.  Associated Documents and Resources

OPTIONAL FOR RMs.  List any documents related to this RM.

 (Whenever possible, reference any associated documents directly into preceding sections rather than listing them independently here.)

VIII.  Revision History

Provide the history in table format. Example:

Version #, Date

Description

V1, 2023.03.06

New Document

V2, 2023.09.29

Updated to clarify formatting restrictions in Confluence. See Instructions in section VI.

  • No labels