IMScollect
Template · ISO 27001

Statement of Applicability (SoA) for ISO 27001

The Statement of Applicability is the document an auditor reaches for at the start of almost every ISO 27001 audit. It shows for each Annex A control whether it applies to you, why, and how far it has been implemented.

Download the Excel templateExcel file · as of 13 November 2026 · no email address
statement-of-applicability-iso-27001.xlsx

Examples

Six completed rows for orientation, invented values; please take the titles from your own copy of the standard

4 sheets14 columns103 rows prepared
Examples: extract from the template with example rows
ControlApplicableImplementation status
A.5.1YesImplemented
A.5.23YesPlanned
A.6.7YesPartly
A.8.13YesImplemented
A.8.25No
+ 9

more columns in the file: Theme · Title (from your copy of the standard) · Reason: risk treatment · Reason: legal or contractual requirement · Reason: own decision · Justification for exclusion · Responsible · Last review · Flag

InstructionsStatement of ApplicabilitySummaryExamples

Extract from the Excel file with example rows · the workbook has 4 sheets, highlighted columns are calculated by the template. The example values are invented.

What the template is for

Once the risk assessment is done, you decide which controls you will use to treat your information security risks. The Statement of Applicability records that decision for all 93 controls in Annex A: included or excluded, with a justification, and for the included ones the status of implementation.

That makes it the link between the risk treatment plan and everyday practice. In the stage 1 audit the auditor reads it in full; in stage 2 they pick individual rows and ask to see how the control is implemented.

What is in the file

  • An “Instructions” sheet with the steps, the terms and what each column means.
  • A “Statement of Applicability” sheet with all 93 controls from A.5.1 to A.8.34, grouped into the four themes organizational, people, physical and technological, plus ten blank rows for additional controls from other sources.
  • Columns for applicability, the three usual reasons for inclusion (risk treatment, legal or contractual requirement, own decision), justification for exclusion, implementation status, implementation in your own words, responsible person, evidence and last review, with drop-down lists.
  • A “Summary” sheet that counts applicable, excluded and implemented controls per theme by itself.
  • The control titles are not in the file because they are part of the licensed standard. You copy them from your copy of the standard into the “Title” column.
Step by step

How to fill it in

  1. 1

    Finish the scope and the risk assessment first. The Statement of Applicability follows from risk treatment, not the other way round.

  2. 2

    Enter the control titles from your copy of the standard, so the list can be read without the standard next to it.

  3. 3

    Decide for each control: applicable, yes or no. For every included control, mark at least one reason.

  4. 4

    Write a justification for every exclusion that refers to your scope or your risks, for example “no in-house software development, software is only bought in”.

  5. 5

    For the applicable controls, enter the status and describe in one sentence how you implement the control, with a reference to the policy, process or evidence.

  6. 6

    Add controls you take from other sources (such as an industry standard) in the blank rows at the end.

  7. 7

    Give the statement a version and a date and have top management approve it; review it after every new risk assessment.

The same steps are in the file on the “Instructions” sheet, together with the rating scales and the completed examples.

Common mistakes when filling it in

What most often goes wrong when filling in this file, and how to avoid it.

An exclusion without a real justification
The “Justification for exclusion” column stays empty or just says “not relevant”. Write a sentence that refers to your scope or your risks. If the justification is missing altogether, the “Flag” column points it out in that row.
Applicable, but no reason marked
A control is set to “Yes”, but none of the three reason columns has an X. Then nobody can tell why it was included. Mark at least one reason for every applicable control; otherwise the “Flag” column shows “Reason missing”.
“Implemented” with an empty evidence column
If you choose “Implemented”, note next to it where the evidence is kept: policy with version, record, configuration. If the column stays empty, the template flags the row with “Evidence missing”.
Control titles not copied in
The file lists the controls by number only, because the titles belong to the licensed standard. Without the titles from your copy, nobody can read the list without the standard next to it, including top management when approving it.
Version and approval left blank in the subtitle
The subtitle row of the sheet asks for the version, the approval date and a name. If it stays blank, nobody can tell which version applies. Increase the version with every change and have it approved again.

What an auditor checks for this clause and which nonconformities they often find is explained on the clause page: ISO 27001, clause 6.1.3 d: Statement of Applicability (SoA).

ISO 27001 with IMScollect

In IMScollect you keep the Statement of Applicability with all 93 controls in the system, with justification, implementation status, owners and evidence, next to assets and risks.

Find out more

See it working in one system

In a free demo we show you how these lists work together in IMScollect, with your standards and your questions.

Start 14-day free trial

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →