Standard Operating Procedure: Defining and Maintaining Quality System Scope

This Standard Operating Procedure (SOP) establishes the formal framework for defining, documenting, and reviewing the scope of an organization’s Quality Management System (QMS). Establishing a clear scope is a foundational requirement for international standards (such as ISO 9001:2015), ensuring that all relevant internal and external issues, stakeholder requirements, and operational boundaries are clearly identified. This document ensures that the scope remains accurate, aligned with strategic direction, and effectively communicated across all departments.

1. Initial Assessment and Boundary Definition

• Identify Organizational Context: Conduct a review of the organization’s strategic objectives and the core "reason for being" (the mission statement).
• Determine Operational Boundaries: Define the physical locations, remote sites, and specific business units included in the QMS.
• Map Product and Service Portfolio: List all products, services, and associated processes intended for inclusion within the system.
• Identify Exclusions: Document any requirements of the relevant standard (e.g., ISO 9001 Clause 8.3 Design and Development) that are deemed non-applicable, and provide a documented justification for each.

2. Stakeholder and External Factors Analysis

• Conduct Stakeholder Analysis: Document interested parties (customers, regulators, suppliers, employees) and their specific quality-related requirements.
• Evaluate External Factors: Review political, economic, social, technological, legal, and environmental (PESTLE) factors that impact the QMS scope.
• Align with Strategic Direction: Ensure the scope statement reflects the high-level business strategy and resource allocation capabilities.

3. Documentation and Formalization

• Draft the Scope Statement: Write a concise, unambiguous statement describing the activities, products, and services covered.
• Executive Review: Present the draft to top management for formal sign-off to ensure alignment with business goals.
• Update the Quality Manual: Integrate the formal scope statement into the Quality Manual or the primary QMS documentation repository.
• Communicate the Scope: Distribute the finalized scope to all department heads and ensure it is accessible to all employees via the company intranet or document management system.

4. Periodic Review and Maintenance

• Annual Scope Audit: Review the scope during the annual Management Review meeting to ensure it remains current regarding organizational changes.
• Trigger-Based Review: Re-evaluate the scope following major changes, such as facility expansions, mergers and acquisitions, or the introduction of new core product lines.
• Version Control: Ensure the scope document reflects current versioning and approval dates in accordance with the Document Control SOP.

---

Pro Tips & Pitfalls

• Pro Tip (The "Just-Right" Balance): Avoid being overly granular. If your scope is too specific (e.g., listing every model number), you will have to update your QMS documentation every time you launch a product. Keep it high-level (e.g., "The manufacturing and distribution of medical-grade filtration components").
• Pitfall (Ignoring Outsourced Processes): Many managers fail to realize that even if a process is outsourced (e.g., outsourced logistics or contract manufacturing), it often still falls within the scope of the QMS. You must account for how you manage these external providers within your quality system.
• Pitfall (The "Copy-Paste" Error): Never copy an organization’s scope statement from another company. Your scope must be unique to your specific operational risks, locations, and regulatory environment.

---

Frequently Asked Questions (FAQ)

Q: Can we exclude a specific facility from our QMS scope? A: Yes, provided that the exclusion is clearly documented, justified, and does not compromise the ability of the organization to meet customer or regulatory requirements. However, you must explicitly state what is included and what is excluded in your official documentation.

Q: Does our scope need to change if we start a new project? A: Not necessarily. If the project falls within the existing high-level description of your products or services, your scope remains valid. If you are entering an entirely new business sector or moving into a new country with different regulatory requirements, you likely need a scope revision.

Q: Where should the scope be formally published? A: The scope must be available to interested parties. It is typically found in the introductory section of the Quality Manual, the company’s website, or provided upon request to customers and auditors during certification audits.