1. Why the scope drives the whole project
The scope describes what the management system covers: which sites, processes, information systems, data and people. All the later work is built on this choice. The risk analysis covers what lies within the scope, the controls apply there and the audit verifies there. A badly defined scope means redoing documents, revising risks and repeating checks.
The scope must also be understandable to anyone reading the certificate. A customer who reads 'certified for service X at site Y' expects that service to be genuinely managed under the system. If the certificate appears to cover more than what actually happens, the contractual and reputational risk is real. For this reason it must be written precisely, without generic formulas.
2. What you need before you start
Before writing a single line, gather the basic information. You need an up-to-date list of sites, a simple organisation chart, the main processes and a map of the systems with the supplier of each. You also need the contracts with your most important customers, because they often impose security requirements that must be met. Keep them together with the contracts, so you do not forget clauses that affect how data is handled.
If these lists do not exist, building them is the first task. They do not have to be perfect; they only need to be sufficient to make decisions. Involve people who really know the processes, not only those with the title, because the most useful information often sits with the people who do the work every day. Bring concrete questions with you, so the conversation stays on facts and not on intentions.
- List of the sites and premises where work is carried out or data is stored
- Organisation chart with the managers of the main processes
- List of the processes that handle data or deliver important services
- Inventory of systems, applications and cloud services
- List of suppliers that manage data or systems on your behalf
- Security requirements imposed by customers or by law
3. The steps to define the scope
Follow these steps in order. Each step produces a written result that goes into the final document, and whoever approves the scope must be able to retrace the logic. Update the draft as you go, so that each decision stays linked to the information that generated it. The step on suppliers is the one most often forgotten. If you do not know who handles a piece of data, this is where you will discover it.
- List the information that has value for the business, such as customer data, projects, administrative data or technical documents.
- For each piece of information, identify the process that creates, uses or stores it.
- For each process, identify the sites where it takes place and the systems that support it.
- Decide which sites, processes and systems to include and, for each exclusion, write down the reason.
- Verify that suppliers handling parts of the scope are covered by clear requirements in their contracts.
- Draft a scope statement with the description, the justified exclusions and the approval of top management.
4. Broad or narrow scope: how to choose
There is no single right scope. It depends on what the business needs, who is requesting the certification and how manageable the system is. A scope covering the whole company is simple to explain but heavier to maintain. One limited to a single site or service is easier to govern, provided the boundaries are clear.
The table summarises the three most common approaches. Use it to discuss with management and with the certification body before deciding, and remember that every choice must be justified in writing. If management prefers an intermediate solution, describe that too, because the body assesses the consistency of the choice more than its breadth. You do not need a perfect choice; you need one that you can explain.
| Approach | When it works | Point of attention |
|---|---|---|
| Whole organisation | Small organisations or those whose processes are all shared | The workload grows with every department included |
| One site or division | Separate activities with their own systems | Shared services used by the rest must be clear |
| One service or product | A customer or offer that requires certification | Common data and systems must be treated as a boundary |
5. Common mistakes in defining the scope
The recurring mistakes are predictable. The first is excluding systems that the certified part uses every day, such as email, backups, access management or cloud. The second is including a service but not the people who run it. The third is defining the scope by department rather than by process, which leaves the boundaries blurred as soon as people change roles. A process, by contrast, remains recognisable even when the people and departments change.
Another mistake concerns suppliers. If a supplier hosts data or runs a system within the scope, responsibility does not stop at your boundary. You do not need to include them in the system, but you must establish with them requirements, responsibilities and ways of verifying them. Finally, many scopes are frozen in the document and never updated when sites, services or systems change. A periodic check of the list, even a quick one, prevents discovering the differences only during the audit.
6. How to check that the scope holds up
A good scope passes some practical tests. Ask a person working in a process where the data lives and which systems they use: if the answer does not appear in the scope, there is a gap. Then follow a piece of information from the moment it enters until it is archived or deleted. Every step that leaves the scope must be justified. If the explanation takes more than one sentence, the boundary probably is not yet clear.
Have someone outside the project read the document. The judgement of someone who does not know the project is the most useful test you can run. If they understand what is included and what is not without asking for explanations, the scope is clear. If a long verbal explanation is needed, it should be rewritten. Reopen the scope every time you change a site, open a new service or replace a major supplier. Each change must be recorded in the document version, with date and owner.
7. How to start
This week, prepare the list of sites and main processes, and set a short meeting with the people running the company and those who know the systems. The aim is to obtain a first draft of the scope with exclusions to discuss. Do not seek perfection on the first pass. A draft discussed today is better than a perfect scope postponed for months. Involve at least one person from operations, because they see every day what the document must describe.
After the draft, the next step is the risk analysis, which uses the scope as its basis. For a practical method you can apply straight away, read the dedicated guide on risk analysis under the standard. Remember that the scope can still be adjusted after the first assessment, if systems or processes not previously considered emerge. Ask management to confirm the scope in writing before you launch it.
Frequently Asked Questions
Can the scope change after certification?
Yes, but every change must be documented, assessed and communicated to the certification body, which may need to verify its impact. Adding a site or service requires reviewing risks, controls and the statement of applicability. Reducing the scope is more delicate, because it changes what the certificate covers. Before acting, speak with the certification body and with the customers who have relied on the certificate.
Must the scope include cloud and hosted services?
If a cloud or hosted service supports processes within the scope and stores relevant data, it falls within the assessment. You do not need to list every technical component, but do include the systems that matter for the business and for the data processed. For third-party services, ask the supplier which controls they offer and what evidence they can provide, and record their responsibilities in the contract.
Can I exclude part of the personal data from the scope?
It depends on what you process and how the company is organised. An exclusion is acceptable only if it is justified, documented and does not create gaps in the processes that remain inside. It is not a loophole for leaving out the most sensitive data. Check with your data protection consultant or a lawyer how the exclusions interact with GDPR obligations.
Who should approve the scope?
Top management must approve it, because the scope represents a business and risk decision. The project lead prepares it and keeps it up to date. Record in the document who approved it and on what date, so the decision remains traceable and later checks are simpler.
How do I write an effective scope statement?
A good statement describes what is included in concrete terms: the service, the sites, the main processes and systems. Avoid vague phrases such as all activities or all company systems, which cannot be verified. Add exclusions with their reasons. Reread it asking yourself whether someone who does not know the company would understand what is covered.