Scribd
Upload
725 views

Standard Operating Procedure Template

This standard operating procedure document: 1. Outlines the purpose, scope, references, and responsibilities for a specific process. 2. Provides a template for describing the requirements, processes, or procedures in section 6.0 including the use of headings, sub-topics, and tables. 3. Includes an appendix for tracking revisions.

Uploaded by

AungKoMin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
725 views

Standard Operating Procedure Template

This standard operating procedure document: 1. Outlines the purpose, scope, references, and responsibilities for a specific process. 2. Provides a template for describing the requirements, processes, or procedures in section 6.0 including the use of headings, sub-topics, and tables. 3. Includes an appendix for tracking revisions.

Uploaded by

AungKoMin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

STANDARD OPERATING PROCEDURE

Title Release Date


<X> <MON-dd-yyyy>
Document Type Document Number Revision Number
<X> <X> 1

1.0 PURPOSE
1.1 <The purpose statement is succinct and describes the specific process or procedure to be
standardized.>
1.2 <This template contains sections that are prepopulated with black text that offer a starting framework
for authoring documents. The blue text offers guidance—and insertion locations—for your specific
process or procedure’s information. Replace the blue text with black text when it is appropriate. For
example, delete the blue text in this Purpose section, and type the purpose of the document in black
text.>

2.0 SCOPE
2.1 <Type the scope statement in this section. The Scope section is independent of the Purpose section
and identifies who uses the document and for which function, organization, or geography it applies.>

3.0 REFERENCES
The following documents are used to develop, to support, or are referenced within this <document type>.

Table 1 – References

Document Number Document Title


The following documents are used to develop this <document type>:
<X> <Insert Document Name>
The following documents support this <document type>:
<X> <Insert Document Name> Glossary of Terms
<X> <Insert Document Name>
The following documents are referenced within this <document type>:
<X> <Insert Document Name>

4.0 DEFINITIONS
4.1 Refer to the <Insert Document Name> Glossary of Terms for definitions, acronyms, and
abbreviations referenced within this document.
4.2 <If a term, acronym, or abbreviation requires further defining or clarification, state:>
For the purposes of this document, the definitions in Table <#> apply, in addition to any definitions in
the Glossary of Terms referenced above.

<Table 2 provides an example of the definition table format.>

Table 2 – Definitions

Term Definition
<X> <Insert Document Name>

Novatek Communications, Inc. • 500 Helendale Road, Suite 280, Rochester, NY 14609 • (585) 482-4070 • www.novatekcom.com
Page 1 of 3
STANDARD OPERATING PROCEDURE
Title Release Date
<X> <MON-dd-yyyy>
Document Type Document Number Revision Number
<X> <X> 1

5.0 RESPONSIBILITIES
5.1 <The Responsibilities section identifies those functions, job titles, departments, etc., that/who have
responsibilities defined within the document, and it provides a summary statement of those
responsibilities.>
5.2 < Job Title – Responsibility>

6.0 STANDARD REQUIREMENTS/PROCESS DESCRIPTION/PROCEDURE


6.1 <This section describes the specific requirements, processes, or procedures and is titled according
to the document type. Delete the unused titles, and change the correct title to black font.
 “STANDARD REQUIREMENTS” when authoring standards
 “PROCESS DESCRIPTION” when authoring guidance documents
 “PROCEDURE” when authoring standard operating procedures (SOPs) or work instructions>

6.2 <Each topic is stated at this level (Heading 2), with the following formatting for sub-topics:
6.2.1 Sub-topic (Heading 3)
6.2.1.1 Requirement, process step, etc. (Heading 4)
6.2.1.2 Requirement, process step, etc. (Heading 4)
OR
6.2.2 Sub-topic (Heading 3)
 Bulleted step or item (List Bullet 3)
o Additional indentation level (List Bullet 4)
 Another bulleted step or item (List Bullet 3)
6.3 <If creating a table, use the following format styles:>

Table Normal heading Table Normal heading


Table Normal text Table Normal text
 Table Normal text bulleted  Table Normal text bulleted

Novatek Communications, Inc. • 500 Helendale Road, Suite 280, Rochester, NY 14609 • (585) 482-4070 • www.novatekcom.com
Page 2 of 3
STANDARD OPERATING PROCEDURE
Title Release Date
<X> <MON-dd-yyyy>
Document Type Document Number Revision Number
<X> <X> 1

7.0 APPENDICES
Appendix 1: Revision History

Revision Release Date DAR No. Description of Change


1 <MON-dd-yyyy> <###> Initial Issue – <Originator’s name>

Novatek Communications, Inc. • 500 Helendale Road, Suite 280, Rochester, NY 14609 • (585) 482-4070 • www.novatekcom.com
Page 3 of 3

You might also like