Business Operations

SOP Writing Guide: EPA Structure, ISO 9001 7.5, Sample SOP

By Vact Published · Updated

A standard operating procedure (SOP) is, in the words of the US Environmental Protection Agency, “a set of written instructions that document a routine or repetitive activity followed by an organization.” Write one when a task recurs, errors are costly or the work changes hands. Give it a purpose, scope, roles, numbered steps, quality checks, records and a controlled revision number. Then have someone who did not write it follow it before it is approved. The EPA’s Guidance for Preparing Standard Operating Procedures (EPA QA/G-6, EPA/600/B-07/001, April 2007) sets out how, and as of November 2026 it is still on the agency’s list of quality program guidance. ISO 9001 adds the document-control rules in clause 7.5.

QuestionShort answerSource
What goes in an SOP?Title page, table of contents, procedures, quality control, referencesEPA QA/G-6, section 4
How detailed?Enough that someone with limited experience but a basic understanding can repeat it unsupervisedEPA QA/G-6, section 2.1
Who writes it?Subject-matter experts who do the work; a team for multi-task processesEPA QA/G-6, section 2.1
Who checks it?Someone other than the author tests the draft; a supervisor and quality officer approveEPA QA/G-6, section 2.2
How often is it reviewed?Periodically, for example every 1-2 years, and whenever the procedure changesEPA QA/G-6, section 2.3
What does ISO 9001 require of it?Identification, format and medium, review and approval, and controlled changesISO 9001, clause 7.5 (2015 and 2026 editions)

When a task needs an SOP

EPA’s list of benefits explains the cases where the effort pays back. An SOP “minimizes variation and promotes quality through consistent implementation of a process or procedure within the organization, even if there are temporary or permanent personnel changes.” It also works as training material, helps reconstruct what was done when no other record exists, and is “frequently used as checklists by inspectors when auditing procedures.”

For a project team, that translates into five triggers:

  • The task recurs (a release, a month-end report, a change request, a client handover).
  • A mistake has a cost in money, safety, compliance or a customer’s trust.
  • The work passes between people or teams, so each handoff can lose information.
  • New joiners keep asking the same how-to question.
  • An auditor, client or regulator may ask how the task is done and what evidence exists.

A one-off task does not need one. Neither does a task so variable that no sequence holds; there, write guidance and decision criteria instead, such as the criteria in a project kickoff checklist.

What the EPA guidance requires: the five elements

QA/G-6 says plainly that “there is no one ‘correct’ format”, and that the level of detail depends on how critical the process is, how often it runs, how many people use it and whether training is available. It then describes technical SOPs as having five elements: title page, table of contents, procedures, quality assurance and quality control, and references. Administrative SOPs (section 4.2) follow the same frame with an explicit purpose.

Title page. A title that clearly identifies the activity, an SOP identification number, the date of issue or revision, the unit the SOP applies to, and the signatures and dates of preparer and approvers. Electronic signatures are accepted.

Procedures. The guidance lists topics to include as appropriate: scope and applicability, summary of method, definitions, health and safety warnings, cautions, interferences, personnel qualifications and responsibilities, equipment and supplies, the procedure itself, and data and records management. Health and safety warnings and cautions are listed up front and again at the critical steps. Warnings cover injury; cautions cover damage or invalid results.

Quality control. QC activities “are designed to allow self-verification of the quality and consistency of the work”. The SOP states the checks, the criteria, how often they run and what to do when results fall outside limits. For administrative SOPs, the guidance says this can be as simple as running a spell-check on a finished document, or a review before a deliverable is accepted.

References. Related SOPs and documents are cited with their versions, and “citations cannot substitute for the description of the method being followed in the organization.” An SOP that says only “follow the vendor manual” fails that test.

Two more rules matter in daily use. A checklist or form attached to an SOP should be referenced at the step where it is used; the guidance’s wording is “the checklist is not the SOP, but a part of the SOP.” And an SOP that cites another SOP should either attach a copy or say where to find it, and should state any modification at the point of citation (section 3.3).

Writing style

The EPA’s style rules are specific: “concise, step-by-step, easy-to-read,” in the active voice and present tense, with the word “you” implied rather than written. “Keep it simple and short,” and use a flow chart to illustrate the process. Write “Select the previous Monday through Sunday,” not “You should then go ahead and choose the correct period.”

Choosing a format: steps, hierarchy, flowchart or checklist

QA/G-6 leaves the layout open; in the words of section 3.0, formatting “will vary with each organization and with the type of SOP being written.” What the guidance does say about form maps onto four layouts:

FormatWhat QA/G-6 says (section)Use it forRisk
Step-by-step (numbered list)Write in a “concise, step-by-step, easy-to-read format” that “clearly describes the steps in order” (1.4, 3.3)Short, routine, linear tasksConditions get buried in prose
Hierarchical (sections with sub-steps)Where possible, “break the information into a series of logical steps to avoid a long list”; procedures are “divided into significant sections” (3.0, 3.3)Long processes that would overwhelm as one listToo many levels slow the operator
Flowchart”Use a flow chart to illustrate the process being described”; flow charts “briefly summarize a series of steps” (1.4, 3.3)Processes with decision points and several outcomesHard to maintain if the chart is only an image
ChecklistUsed “to ensure that steps are followed in order” and “to document completed actions”; part of the SOP, never a substitute for it (2.4)Recording that each step was doneHides reasoning; new people need the full SOP

The “Use it for” and “Risk” columns are this site’s practical judgment, not EPA text. A usable rule of thumb: start with the simplest format that holds the task. Move to a hierarchy when a single list passes about a page, and to a flowchart where the operator must choose between outcomes. Those thresholds are practical judgment rather than anything in the standards. Hybrids are normal; a hierarchical SOP can embed a flowchart for its one decision-heavy section. Since EPA states that a checklist is part of the SOP, treat a checklist as the record that the steps were done, with the SOP carrying the reasons and exceptions.

ISO 9001 clause 7.5: document control

If the SOP supports a quality management system certified to ISO 9001, clause 7.5 (“Documented information”) sets the control requirements. As of November 2026 two editions are in use. The sixth edition, ISO 9001:2026, was published on 16 September 2026, and certificates to ISO 9001:2015 are expected to remain valid until 30 September 2029 while organizations transition. A clause-by-clause comparison of the two editions classes the 2026 changes to clause 7.5 as terminology only, so the controls below apply under either edition. ISO sells the standard; this section paraphrases the 2015 clause as explained by Auditor Training Online, and the purchased text is authoritative.

Creating and updating (clause 7.5.2). Each time documented information is created or revised, the organization makes sure of three things, to the extent appropriate (Auditor Training Online on 7.5.2):

  • it is identified and described, for example by a title, date, author or reference number;
  • it is in a fitting format (such as language, software version or graphics) and medium (paper or electronic);
  • it is reviewed and approved as suitable and adequate.

Control (clause 7.5.3). Controlled documented information has to be available and fit for use at the place and time people need it, and protected against loss of confidentiality, improper use or loss of integrity (Auditor Training Online on 7.5.3). Where they apply, the organization deals with distribution, access, retrieval and use; storage and preservation, including keeping it legible; control of changes, such as version control; and retention and disposition. Documents from outside the organization that it has decided the system needs are identified and controlled as well, and records kept as evidence of conformity are protected against unintended changes.

Two further points matter for SOP writers. Since the 2015 revision, documents and records share one term, documented information, and the standard leaves organizations, in The 9000 Store’s words, “more freedom in how, what, and when to document” than the 2008 edition did. Clause 7.5.1 covers the documented information the standard itself requires plus whatever else the organization decides its system needs to be effective, and a note to the clause says the extent can differ with the organization’s size and activities, the complexity of its processes and the competence of its people. Which tasks get an SOP is therefore largely the organization’s call.

The same controls in both documents

The EPA’s control rules (sections 1.2 and 2.2 to 2.6) and ISO clause 7.5 point at the same fields, which gives one header that satisfies both:

ControlEPA QA/G-6ISO 9001 clause 7.5
IdentificationNumbering system; short title and ID number on each pageTitle, date, author or reference number
VersionRevision number and date, “critical” where evidentiary records are involvedChange control, such as version control
CompletenessPages numbered “Page 1 of” the total, so users can check the SOP is completeFormat and medium suited to use
ApprovalSupervisor and quality assurance officer review and approveReviewed and approved as suitable and adequate
AccessCurrent copies in the work area; read-only electronic accessAvailable where and when needed; protected from misuse and loss of integrity
Retired versionsArchived so they cannot be used, kept for historical reviewRetention and disposition

Version control and review

EPA section 2.3 gives the working rules. Whenever the procedure changes, the SOP is “updated and re-approved.” If only one section changes, it is acceptable to modify just that section and record the revision number and date for that section in the table of contents and the document control notation. Beyond that, SOPs “should be also systematically reviewed on a periodic basis, e.g. every 1-2 years”, the review date is added each time, and an SOP for a process no longer followed is withdrawn and archived. The review process “should not be overly cumbersome,” so that reviews happen on time.

Section 2.6 adds a master list. It should show the SOP number, version, issue date, title, author, status, owning unit and history of past versions, and is generally kept by the QA manager or a designee. If the list is a database, it can send automatic “Review SOP” notices. The guidance also notes that read-only electronic access protects against unauthorized changes.

A change log at the end of each SOP covers the day-to-day need:

RevDateAuthorChangeApproved by
1.02026-11-16OwnerFirst issueTeam lead
1.1(date of change)OwnerStep 6: added the check against the registerTeam lead

Use a major number for changes that alter what an operator does and a minor number for wording. That convention is common practice, not from either standard. Record the walkthrough result against the version tested.

Validate before approving

EPA section 2.2 calls it “especially helpful” when draft SOPs are “tested by individuals other than the original writer before the SOPs are finalized.” A workable walkthrough:

  1. Pick a colleague who has not done the task but has the basic background.
  2. Give them the SOP and nothing else. Observe in silence and note every question.
  3. Treat each question as a defect in the document, not in the person.
  4. Revise, then repeat the affected steps with a different person.
  5. Record the version, date, environment, failed steps and changes, then approve.

Where the task can change customer data or production systems, run the walkthrough in a test environment or follow the organization’s rehearsal and approval process.

Expected formats belong at the point of entry. W3C’s form instructions tutorial recommends stating which inputs are required and showing the expected format in the label, such as “Expiration date (MM/YYYY)”. An SOP step that says “enter the date” fails the same way. Say “enter the effective date as YYYY-MM-DD.”

Worked sample: processing a project change request

The sample below shows the elements in use. It is fictional and illustrative; adapt roles, thresholds and tools to the team before use. Its sections draw on the topics the EPA lists for administrative SOPs in section 4.2: purpose, scope, definitions, responsibilities, procedure, records, quality control and references.

SOP-CR-01  Rev. 1.0  2026-11-16  Page 1 of 2
Title: Process a project change request
Owner: Project manager     Approved: Sponsor, 2026-11-16
Next review: 2027-11-16, or on any change to the contract

1. PURPOSE
   Ensure every request that changes scope, schedule or budget is
   assessed, decided and recorded before work on it starts.

2. SCOPE
   Applies to requests received after the baseline is approved.
   Does not cover defects in delivered work (see the defect SOP)
   or emergency changes (see SOP-CR-02).

3. DEFINITIONS
   Baseline: the approved scope, schedule and budget.
   Change request (CR): a written request to alter the baseline.

4. ROLES
   Requester: submits the CR.   Project manager (PM): logs and
   assesses.   Change board: PM, sponsor, technical lead; decides.

5. PREREQUISITES
   - CR form (Attachment A) completed in every field.
   - Baseline version identified on the form.

6. PROCEDURE
   6.1 PM logs the CR in the register and assigns the next
       CR number (CR-001, CR-002 ...) within 1 working day.
   6.2 If any field on the form is blank, return it to the
       requester and stop. Do not assess an incomplete request.
   6.3 PM estimates effect on scope, schedule and budget, and
       records the estimate on the form.
       6.3.1 Update the critical path dates if tasks move.
       6.3.2 Check the risk register for new or changed risks.
   6.4 PM circulates the form to the change board 2 working days
       before the next board meeting.
   6.5 The board decides: approve, reject or defer.
       IF approved  -> go to 6.6
       IF rejected  -> record the reason; notify requester; end
       IF deferred  -> record the date to reconsider; end
   6.6 PM issues a new baseline revision and updates the plan,
       budget and register. Work on the change may begin only
       after this step.
   6.7 PM notifies the requester and affected team members of the
       decision and the new baseline revision number.

7. QUALITY CHECKS
   - Register total of open CRs equals the number of open forms.
   - Each approved CR cites the baseline revision it creates.
   STOP and ask the sponsor if cumulative approved changes exceed
   10% of the original budget.

8. RECORDS
   Completed forms and the register are kept in the project
   folder for the retention period in the contract.

9. REFERENCES
   Project plan; risk register; SOP-CR-02.

Three design choices in the sample are worth copying. Step 6.2 carries an explicit stop. Step 6.5 puts the decision branches in one place, with every branch ending somewhere. And section 7 defines “done” as a check someone can perform, not as reaching the last number. The 10 percent threshold is invented for the example; the team’s contract or governance sets the real figure. Step 6.3 draws on the critical path method for schedule effects and on the risk register guide for the risk check.

Common failure points

  • One giant SOP. The EPA advises breaking information “into a series of logical steps to avoid a long list.” Split standard, emergency and exception cases into separate SOPs and cross-reference them.
  • Steps that depend on memory. “Export the usual report” fails; “select the previous Monday through Sunday in the team’s reporting time zone” can be checked.
  • Unreachable copies. The guidance says current copies need to be “readily accessible for reference in the work areas” of those doing the task. An SOP in a folder nobody opens controls nothing.
  • Never enforced. EPA warns that “the best written SOPs will fail if they are not followed”; supervisors need to review and reinforce their use.
  • No owner. Without a named owner and a review date the SOP ages silently; the master list in section 2.6 exists to prevent that.

Automation changes the content but not the need. Mechanical steps (copy a file, run a command) are candidates for a script; steps requiring judgment stay in the SOP as decisions with criteria.

Sources