sop

Dr. James Wilson

Queens, New York

Introduction

Ask any pharmaceutical inspector what they look for first, and the answer will often involve procedures. Are they current? Are they followed? Do they match what people actually do on the floor? Standard Operating Procedures (SOPs) are the written backbone of a GMP environment. They translate regulatory requirements and company policy into instructions that people can follow the same way every time.

SOP Development, Yet SOPs are also among the most common sources of inspection observations. Procedures may be too vague to guide action, too long to read, outdated, contradictory, or simply ignored. A poorly written SOP is worse than none at all, because it creates the appearance of control without the substance.

This article describes what makes a strong SOP, how to develop and manage one from start to finish, and how to build a procedure system that supports compliance and daily work.

1. What Is an SOP and Why Does It Matter?

A Standard Operating Procedure is a written, approved set of instructions describing how to perform a routine or repetitive task consistently. In pharmaceutical operations, SOPs cover activities such as equipment cleaning, material sampling, gowning, calibration, deviation handling, change control, laboratory testing, and batch record review.

SOPs matter for several reasons:

• Consistency. They ensure that different people, on different shifts, perform the same task the same way.
• Regulatory compliance. GMP regulations require written procedures for a wide range of activities, and they expect those procedures to be followed.
• Training. SOPs form the basis for training new employees and verifying competence.
• Accountability. They define who is responsible for what.
• Risk reduction. Clear instructions reduce errors, mix-ups, and contamination.
• Knowledge retention. They capture organizational knowledge so it does not leave when experienced staff do.
• Investigation support. When something goes wrong, SOPs provide the baseline against which actual practice is compared.

Regulators expect firms to establish written procedures and to follow them. Under US regulations, for example, written procedures must be established and followed, and deviations must be recorded and justified. EU GMP similarly requires that instructions be written in clear, unambiguous language, specifically applicable to the facilities provided.

2. Where SOPs Fit in the Documentation Hierarchy

SOPs do not stand alone. They sit within a hierarchy of documents, and understanding this structure prevents duplication and confusion.

1. Quality policy and quality manual. High-level statements of commitment and system structure.
2. Site master file and validation master plan. Overviews of site operations and validation approach.
3. SOPs. Procedures describing how processes and activities are carried out.
4. Work instructions and forms. More detailed, task-level instructions, templates, checklists, and log sheets.
5. Records. Completed batch records, logbooks, test results, and reports that show the procedure was followed.

Each layer should have a clear purpose. A common mistake is to put extremely detailed step-by-step instructions in an SOP that should instead be a work instruction, or to place policy-level statements in an SOP that operators need as a practical guide. Good design keeps each document at the right level.

3. Core Principles of a Good SOP

Before getting into the development process, it helps to understand what separates effective SOPs from ineffective ones.

Clear. Language should be simple, direct, and unambiguous. A reader should not have to interpret what is meant.

Accurate. The SOP must reflect what actually happens, consistent with regulatory requirements and approved processes.

Usable. It should be organized logically so the user can find what they need quickly, even under time pressure.

Complete, but not bloated. It should contain what is needed to perform the task correctly and nothing that obscures it.

Consistent. Format, terminology, and structure should be uniform across the SOP library.

Controlled. Only approved, current versions should be available, with changes tracked.

Followed. A procedure that is not followed is a compliance risk, regardless of how well it is written.

A useful test: could a newly trained operator perform the task correctly using only the SOP? If not, the SOP needs work.

4. Planning: Deciding What Needs an SOP

Not every activity requires an SOP. Over-proceduralization creates a library too large to manage and too dense to follow. Consider writing an SOP when an activity:

• Is required by regulation or a guideline to be governed by a written procedure.
• Has a direct impact on product quality, patient safety, or data integrity.
• Carries high risk if performed incorrectly.
• Is performed by multiple people or across shifts and sites.
• Is complex, with multiple steps or decisions.
• Must be repeated consistently over time.

Applying a risk-based lens helps prioritize. High-risk activities need detailed, tightly controlled procedures. Lower-risk tasks may be adequately covered by a brief instruction, a checklist, or a training note.

It is also worth reviewing the existing SOP library for gaps, overlaps, and obsolete documents before adding new ones. A mapped inventory linked to processes and regulatory requirements makes this easier.

5. A Step-by-Step Approach to Developing an SOP

Step 1: Define Purpose and Scope

State clearly why the SOP exists, what it covers, and what it excludes. A precise scope prevents misapplication and overlap with other procedures. For example, an equipment cleaning SOP might specify which equipment, which areas, and whether it applies to product changeover, batch-to-batch cleaning, or both.

Step 2: Assemble the Right Team

The best SOPs are written with the people who do the work. Involve subject matter experts such as operators, supervisors, analysts, and engineers, along with quality assurance and, where relevant, regulatory affairs and safety. Procedures written in isolation by someone who has never performed the task tend to be unrealistic.

Step 3: Gather Information

Collect relevant inputs:

• Regulatory requirements and guidelines.
• Company policies and quality manual requirements.
• Validation reports, equipment manuals, and process descriptions.
• Existing related SOPs.
• Risk assessments.
• Current practice, observed directly.

Walk through the process in person. Watching the task being done often reveals steps, workarounds, and hazards that no one thought to mention.

Step 4: Draft the Procedure

Write the first draft using an approved template. Keep it focused and logical, following the sequence in which tasks are performed. Use short sentences and active voice.

Step 5: Review

Circulate the draft to the working team and other stakeholders. Reviewers check technical accuracy, regulatory alignment, clarity, and consistency with related procedures. Collect comments systematically and resolve conflicts openly.

Step 6: Test the Draft

Where possible, have someone unfamiliar with the task follow the draft in a walkthrough or trial. Gaps and ambiguities quickly become obvious. This is one of the most valuable and most neglected steps in SOP development.

Step 7: Approve

Quality assurance and the responsible department head approve the final version, confirming that it is accurate, compliant, and ready for use. Signatures should be dated, and electronic approvals must comply with data integrity requirements.

Step 8: Train Before Implementation

The SOP should not become effective until affected personnel are trained. Training records should confirm that staff read and understood the procedure, and ideally that they can perform it correctly. Set an effective date that allows time for training.

Step 9: Distribute and Implement

Make the current version available at the point of use, through controlled paper copies or an electronic document management system. Withdraw superseded versions to prevent accidental use.

Step 10: Monitor and Review

After implementation, monitor how the SOP works in practice through observation, audits, deviation trends, and feedback. Then review it periodically and revise when needed.

6. Standard SOP Structure and Content

A consistent template makes SOPs easier to write, read, and audit. A typical pharmaceutical SOP includes the following sections:

1. Header. Title, SOP number, version, effective date, department, and page numbering (for example, “Page 2 of 6”).
2. Purpose. The reason the SOP exists.
3. Scope. The areas, processes, equipment, or people covered.
4. Responsibilities. Roles and their duties, such as operator, supervisor, QA, and QC.
5. Definitions and abbreviations. Terms that may be unclear to readers.
6. Materials, equipment, and safety precautions. What is required and any hazards or protective equipment.
7. Procedure. The step-by-step instructions, the core of the document.
8. Documentation and records. The forms, logs, or records to be completed and retained.
9. References. Related SOPs, regulations, and guidelines.
10. Attachments and appendices. Forms, flowcharts, tables, or diagrams.
11. Revision history. What changed in each version and why.
12. Approval block. Author, reviewer, and approver signatures and dates.

The procedure section deserves the most attention. Steps should be numbered, sequential, and focused on one action each. Decision points should be explicit, for example, “If the result is outside the limit, stop and notify QA.”

7. Writing Style: Making SOPs Clear and Usable

Even technically correct SOPs fail when they are hard to read. The following writing practices improve usability.

Use Plain, Direct Language

Choose simple words over jargon, and explain technical terms where needed. Replace “the operator shall ensure the verification of the integrity of the filter” with “Check that the filter is intact.”

Use Active Voice and Imperative Verbs

Active instructions make it clear who does what. “Weigh 500 g of material” is clearer than “500 g of material should be weighed.”

Be Specific

Avoid vague words such as “appropriate,” “suitable,” “sufficient,” “periodically,” or “as necessary” unless they are defined. Give values, limits, and frequencies: “Clean the equipment within 4 hours of use” rather than “Clean promptly.”

One Action per Step

Combining multiple actions in one step increases the chance that one will be missed. Break complex steps into separate numbered lines.

Use Visual Aids

Flowcharts, photographs, diagrams, and tables can communicate more effectively than paragraphs of text, particularly for multi-step or decision-based processes such as gowning, line clearance, or equipment assembly.

Keep It Concise

Long SOPs discourage use. Move secondary detail to appendices, and avoid repeating content that belongs in another document. If an SOP exceeds a manageable length, consider whether it should be divided.

Write for the Reader

Consider the reading level, language, and working environment of the users. In some facilities, SOPs may need translation or bilingual versions. A procedure used in a cleanroom or on a production line needs to be scannable at a glance.

Highlight Critical Steps

Use warnings, cautions, and notes sparingly but consistently, reserving them for information that genuinely affects safety, quality, or data integrity. Overuse dilutes their impact.

8. Document Control and Lifecycle Management

A well-written SOP loses its value if it cannot be controlled. A strong document control system ensures that the right document is in the right place at the right time.

Numbering and Versioning

Use a logical numbering scheme that identifies document type, department, and sequence. Version numbers should change with every revision, and the system should prevent duplicates.

Approval and Effective Dates

Distinguish between the approval date and the effective date. Effective dates should follow training completion.

Controlled Distribution

Controlled copies should be issued, tracked, and retrieved when superseded. Uncontrolled photocopies and personal printouts are a frequent source of outdated procedures in use. Electronic systems reduce this risk by displaying only the current approved version.

Change Management

Revisions should go through a documented change control process, including justification, impact assessment, review, approval, training, and implementation. Emergency or temporary changes need particular care, with a defined process and time limits.

Periodic Review

SOPs should be reviewed at defined intervals, commonly every one to three years depending on risk, to confirm they remain accurate and aligned with practice and regulations. Reviews should also be triggered by events such as deviations, audit findings, equipment changes, process changes, or regulatory updates.

Archiving and Retention

Superseded and obsolete SOPs should be archived securely and remain retrievable for the period required by regulations and company policy. This allows investigators to determine which version was in effect on any given date.

9. Training and Effectiveness

SOPs only work if people understand and apply them. Training should be more than signing a read-and-understood sheet.

Effective SOP training includes:

• Role-based assignment. Staff are trained only on procedures relevant to their duties, but fully.
• Varied methods. Reading, instructor-led sessions, demonstrations, simulations, and on-the-job coaching suit different tasks.
• Assessment. Quizzes, practical demonstrations, and observed performance verify understanding.
• Timely updates. When an SOP changes, affected staff are trained on the changes before the effective date.
• Training records. Documentation shows who was trained, when, on which version, and by whom.

Training effectiveness can be evaluated by monitoring error rates, deviations linked to procedural failures, and audit observations. If the same SOP repeatedly appears in deviation reports, the cause may be the training, the SOP itself, or the process.

10. Linking SOPs to Deviations and CAPA

SOPs and quality events are closely connected. Deviations reveal where procedures are unclear, unrealistic, or not followed, and investigations should ask whether the SOP contributed to the event.

When a deviation occurs, consider these questions:

• Was the SOP clear and complete?
• Did it reflect actual practice?
• Was the person trained on the current version?
• Was the SOP difficult to follow or access?
• Would a change to the SOP prevent recurrence?

Corrective and preventive actions often include SOP revisions. However, revising an SOP should not be the default response to every incident. Adding more steps, warnings, and sign-offs each time something goes wrong can produce bloated procedures that are harder to follow. Root cause analysis should determine whether the real problem lies in the procedure, the training, the equipment, the workload, or the culture.

11. Data Integrity Considerations

SOPs play a central role in data integrity. They define how data is generated, recorded, reviewed, and retained. Well-designed procedures support the ALCOA+ principles by:

• Specifying that data be recorded at the time of the activity.
• Describing how corrections are made without obscuring original entries.
• Defining user access levels and password management for electronic systems.
• Requiring audit trail review where applicable.
• Clarifying how raw data is identified, stored, and backed up.
• Preventing practices such as unofficial testing, unrecorded repeat analysis, and backdating.

Regulators often compare SOPs with actual behavior. A procedure that promises secure electronic data but is undermined by shared logins reflects a gap between paper and practice.

12. Electronic Document Management Systems

Many organizations are moving from paper to electronic document management systems (EDMS). The benefits are significant:

• Automated workflows for authoring, review, and approval.
• Controlled access and version control.
• Automatic notifications for periodic review.
• Integration with training management, so staff are assigned training when a document is updated.
• Searchability and quick access at the point of use.
• Audit trails of document activity.

However, an EDMS must be validated for its intended use and must comply with electronic records and signature requirements. Digitization also does not fix poorly written SOPs. Clean up and simplify the library before migrating it, or the problems simply move to a new system.

13. Common SOP Problems and How to Avoid Them

Too long or too complex. Split by topic, use flowcharts, and move detail to work instructions or appendices.

Vague instructions. Replace subjective terms with specific, measurable criteria.

Gap between SOP and practice. Involve end users in drafting, observe real processes, and update documents when practice legitimately changes. Do not leave “the real way” unwritten.

Conflicting procedures. Cross-check related documents and use a central inventory to spot overlaps and contradictions.

Outdated content. Enforce periodic review and link SOP updates to change control.

Poor training. Train before effective dates and verify understanding.

Copy-paste writing. Borrowed text from other sites or templates may not match local equipment or processes. Adapt every document.

Over-reliance on SOPs for every issue. Not every problem requires a new procedure. Sometimes better equipment, clearer labeling, or additional staff is the right answer.

Lack of ownership. Every SOP should have a named owner responsible for its accuracy and maintenance.

Uncontrolled copies. Remove outdated printouts and use controlled distribution.

14. Building a Culture That Supports SOP Compliance

A strong SOP system depends on the attitudes of the people who use it. Several cultural factors make the difference.

• Leadership example. When managers follow procedures and support compliance even under time pressure, employees do the same.
• Ownership by users. People follow procedures they helped create. Encourage feedback and show that suggestions lead to improvements.
• No-blame reporting. Staff should feel safe reporting when an SOP is unclear or impossible to follow. Hiding problems or creating workarounds is a sign of a weak culture.
• Explaining the why. When people understand the reason behind a step, they are more likely to follow it and less likely to take shortcuts.
• Continuous improvement. Treat the SOP library as a living system that improves based on experience, data, and feedback.

15. Quick Checklist for SOP Quality

Before approving an SOP, ask:

1. Is the purpose and scope clear?
2. Are responsibilities defined?
3. Are steps in the correct sequence, numbered, and specific?
4. Is the language simple and unambiguous?
5. Does it match actual practice and validated processes?
6. Are critical parameters, limits, and frequencies stated?
7. Are required records and forms identified?
8. Are references accurate and up to date?
9. Has it been reviewed by the people who will use it?
10. Has it been tested or walked through?
11. Is the revision history complete?
12. Is training planned before the effective date?

Conclusion

SOPs are far more than regulatory paperwork. They are the practical tool that turns quality intentions into consistent action. A good SOP is clear, accurate, usable, and controlled. It is developed with input from the people who do the work, tested before release, supported by effective training, and kept current through disciplined document control and periodic review.

Pharma organizations that treat SOPs as living tools rather than static documents benefit in tangible ways: fewer deviations, smoother inspections, faster onboarding, and greater confidence that every batch is made and tested the same way. The effort invested in writing procedures that people can understand and follow is an investment in product quality and, ultimately, in patient safety.

Guideline References

1. US FDA, 21 CFR Part 211 – Current Good Manufacturing Practice for Finished Pharmaceuticals (notably Subpart J, Records and Reports, and requirements for written procedures).
2. US FDA, 21 CFR Part 210 – Current Good Manufacturing Practice in Manufacturing, Processing, Packing, or Holding of Drugs: General.
3. US FDA, 21 CFR Part 11 – Electronic Records; Electronic Signatures.
4. European Commission, EudraLex Volume 4, Part I, Chapter 4 – Documentation.
5. European Commission, EudraLex Volume 4, Annex 11 – Computerised Systems.
6. ICH Q7 – Good Manufacturing Practice Guide for Active Pharmaceutical Ingredients (Section 6, Documentation and Records).
7. ICH Q9 (R1) – Quality Risk Management.
8. ICH Q10 – Pharmaceutical Quality System.
9. WHO Technical Report Series No. 986, Annex 2 – WHO Good Manufacturing Practices for Pharmaceutical Products: Main Principles.
10. WHO Technical Report Series No. 996, Annex 5 – Guidance on Good Data and Record Management Practices.
11. PIC/S PE 009 – Guide to Good Manufacturing Practice for Medicinal Products.
12. PIC/S PI 041 – Good Practices for Data Management and Data Integrity in Regulated GMP/GDP Environments.
13. US FDA (2018) – Guidance for Industry: Data Integrity and Compliance With Drug CGMP: Questions and Answers.
14. MHRA (2018) – GXP Data Integrity Guidance and Definitions.
15. ISPE GAMP 5 (Second Edition) – A Risk-Based Approach to Compliant GxP Computerized Systems.