What it is about
The scope defines what the management system covers: which sites, which organisational units, which activities, products and services. It draws a boundary, and everything inside that boundary must actually be covered by the system. It is based on the issues from 4.1 and the requirements of the interested parties from 4.2.
For the company, the scope is more than a formality. It becomes the text on the certificate that customers, tenders and partners read. A scope drawn too narrowly is of little use in sales; one drawn too widely promises something the system does not deliver. The certification body therefore checks whether the described scope matches what it sees in the audit.
The scope also covers the question of what is not applicable. ISO 9001 allows individual requirements to be declared not applicable if they genuinely do not occur in the company, such as design and development at a pure contract manufacturer; this has to be justified and must not affect the ability to provide conforming products and services. ISO 14001 and ISO/IEC 27001 offer no such route for clauses 4 to 10. What is excluded there are controls from Annex A of ISO 27001, justified in the statement of applicability, and that is a matter of risk treatment.
In all three standards, the scope has to be maintained as documented information. With several standards it may differ per standard: quality management often covers the whole company, while the information security management system covers only the head office and IT operations. What matters is that each version is complete and unambiguous in its own right.
What the auditor checks
“What exactly is certified at your company, and what is not?”
Whether the answer matches the documented scope and the certificate. If top management names a site or line of business that is missing from the text, or leaves out one that is in it, the auditor follows up.
“Why is this site, this activity not included?”
Whether the boundary is justified. A boundary is allowed, but it must follow from the facts, such as a separate legal entity with its own management, not from the wish to keep a difficult area out of the audit.
“You declared this requirement not applicable. Why is that?”
For ISO 9001, the justification and whether it is correct. Anyone who excludes design and development but offers customers solutions that first have to be engineered has a justification that does not hold up on the walk-through.
“Which activities do others carry out for you, and how are they integrated?”
Outsourced processes such as IT operations, contract work, warehousing or maintenance do not disappear from the scope just because someone else carries them out. For ISO/IEC 27001, the auditor explicitly asks about interfaces and dependencies with other organisations, such as the data centre, cloud provider or parent company.
“When did you last review the scope?”
Whether new sites, new products, a move or a change of company name have been reflected. A scope that has not changed for years although the company has will be noticed at the latest when compared with the audit planning.
“Where do your employees and customers find the scope?”
Whether it is available. ISO 14001 explicitly requires interested parties to be able to see it. For the other standards too, it should not sit only in the management representative's folder, but where employees and customers look.
Which evidence convinces
A documented scope per standard
Sites and organisational units, products and services, boundaries and, for ISO 27001, the interfaces and dependencies. The clearer the sentences, the more easily the certification body takes the text onto the certificate unchanged.
Justifications for requirements that are not applicable (ISO 9001)
One or two sentences per requirement explaining from the business why it does not occur. They only hold up in the audit if the walk-through confirms them.
The comparison with the certificate
Certificate text and documented scope side by side, with the same sites and activities. If they differ, clarify it with the certification body before the next audit.
An organisation chart or site plan showing the areas included
It shows at a glance where the boundary runs, including for shared buildings, networks or services.
Date and result of the last review
Whether the scope stayed the same or was adjusted, and why, shows that it is looked at again after changes in the company.
Typical nonconformities
Certificate and the system in practice do not match
A site, product line or service appears on the certificate but is not covered by the system, or the other way round. If the system does not cover a certified area at all, it does not work at that point, and that is a major nonconformity. If only individual activities are missing, it is usually a minor nonconformity, because the requirement is only partly not met.
Exclusion without a sound justification
Design and development are excluded although the company designs products to customer specifications; or monitoring and measuring resources, although inspection takes place in production. An exclusion that does not hold up on the walk-through is a nonconformity, and the requirement is audited as if there were no exclusion.
Clauses excluded from ISO 14001 or ISO 27001
In these standards, requirements of clauses 4 to 10 cannot be excluded. Declaring emergency preparedness “not applicable” under ISO 14001, for example, confuses this with the ISO 9001 route.
Boundaries too vague
“All activities at the site” for a building the company shares with a sister company, or a network both use: without a clear boundary and without the interfaces, it remains open what the system is responsible for. For ISO 27001 this is particularly delicate, because risks arise precisely at these interfaces.
Not updated
A new site has been occupied, a line of business added or dropped, but the scope reads as it did at the initial certification. At the latest, the certification body's audit planning, which is calculated by sites and employees, brings it to light.
Differences by standard
ISO 9001ISO 9001
ISO 9001 requires the products and services to be considered when determining the scope, and the text names them. Every requirement applies if it is applicable within the determined scope. If one is declared not applicable, a justification is needed, and conformity may only be claimed if this does not affect the conformity of products and services or customer satisfaction. Typical candidates are design and development (8.3), monitoring and measuring resources (7.1.5) and property belonging to customers (8.5.3).
ISO 14001ISO 14001
ISO 14001 explicitly names what to consider when drawing the boundary: organisational units, functions and physical boundaries, the activities, products and services, and the authority and ability to exercise control and influence. Everything within the scope belongs fully to the environmental management system; taking out individual environmentally relevant activities is not intended. The scope has to be made available to interested parties.
ISO 27001ISO/IEC 27001
ISO/IEC 27001 additionally requires the interfaces and dependencies between your own activities and those of other organisations to be considered: data centres, cloud services, IT service providers, group functions or customers with access to your systems. The requirements of clauses 4 to 10 cannot be excluded; what is not applicable only concerns controls from Annex A and is justified in the statement of applicability.
How IMScollect covers it
In IMScollect, clause 4.3 has its own page, with one tab per standard. Each standard carries its complete scope in four entries: sites and organisational units, products and services, boundaries, and interfaces and dependencies. That way quality management can cover the whole company and information security only part of it, without a shared text claiming otherwise.
You enter exclusions per standard with their own justification; only requirements that can be excluded at all are offered. The justification also appears on the page of the excluded clause, where an auditor asks about it. You plan the review with a responsible person and a date, which becomes a task, and the history shows what has changed since the last review. You keep your certificates in the same system with their scope by company and site. On request, the AI advisor Conni helps you describe the scope of a standard.
Frequently asked questions
What belongs in the scope under ISO 9001?▾
The sites and organisational units and the products and services that the quality management system covers, and the boundaries around them. Added to this are the justifications for each requirement declared not applicable. The scope has to be maintained as documented information.
Which ISO 9001 requirements may be excluded?▾
There is no fixed list. A requirement can only be not applicable if it genuinely does not occur within the determined scope and its absence does not affect the conformity of products and services or customer satisfaction. Most often this concerns design and development, monitoring and measuring resources or property belonging to customers. Every exclusion needs a justification.
Can ISO 27001 cover only part of the company?▾
Yes. The scope of an information security management system may be narrower than the company, such as one site, one data centre or one product. The interfaces with the areas outside then have to be defined, and it must be clear to customers what the certificate covers. Within the scope, clauses 4 to 10 apply in full.
May the scope differ per standard?▾
Yes. In an integrated management system this is common: quality management covers the whole firm, environmental management the production sites, information security the IT operations. Each standard then needs its own complete text, and each certificate states its scope.
What is the difference between the scope and the statement of applicability?▾
The scope defines what the management system covers. The statement of applicability exists only in ISO 27001: it states which controls from Annex A are implemented, which are not, and why. It is produced during risk treatment and presupposes the scope.
