ISO 27001 Audit Checklist: Stage 1 and Stage 2

By Brian Crocker · Published 15 November 2026 · Last reviewed 15 November 2026

Initial ISO 27001 certification is two visits, not one. Stage 1 asks whether your ISMS is designed and documented; Stage 2 asks whether you actually run it. Stage 1 findings are usually about missing or inconsistent documents; Stage 2 findings are almost always about a gap between what a document says and what people do. The practical consequence is that the work you do between the two visits is operating your system and generating records, not writing more policy. This checklist sets out what each stage looks for and what to have ready.

The two stages, and why they are separate

Stage 1 Stage 2
Question Is the ISMS designed, documented and ready to be audited? Is it implemented and effective?
Main evidence Documented information Records of the system operating
Typical output Areas of concern to close before Stage 2 Nonconformities, major or minor
Common failure Documents missing, or inconsistent with each other Documents that do not describe what people actually do
What fixes it Writing Time

ISO 27001 certification bodies operating in the UK are accredited by UKAS against ISO/IEC 17021-1, the umbrella standard for bodies that audit and certify management systems, with ISO/IEC 27006-1:2024 as the ISMS-specific supplement to it. UKAS's certification body accreditation page lists them that way: under the heading "ISO/IEC 17021-1: Certification of Management Systems" it pairs each scope with its own part or supplement — QMS with ISO/IEC 17021-3:2017, EMS with ISO/IEC 17021-2:2016, and the entry headed "Information Security Management Systems Certification (ISMS) to ISO/IEC 27001" with ISO/IEC 27006-1:2024. Each scope is a single entry there, naming the applicable part or supplement on the line beneath the scope heading. A supplement of that kind sits under the umbrella rather than replacing it; the mandatory QMS audit-time document under ISO/IEC 17021-1 states the principle directly — "All clauses of ISO/IEC 17021-1 continue to apply, and this document does not supersede any of the requirements in that standard." The two-stage structure comes from ISO/IEC 17021-1. ⚠️ Its text is not publicly available, so what follows describes how UK bodies run the stages rather than quoting the requirement — check the specifics with your own certification body, because the allocation of time and topics between the two visits varies.

UKAS's technical bulletin on ISO/IEC 27006-1:2024 records that the 2024 revision "refined the requirements for remote audits; updated the audit time calculation requirements" and removed "the quantitative requirement for the work experience and training experience of ISMS auditors". If your body quotes you a remote Stage 1, that is where the rules for it live.

⛔ Do not use an ISO 9001 audit-day table for an ISO 27001 quote. The QMS audit-duration document — formerly IAF MD 5, now Global ACI-TECH-3-004 (M) — covers quality, environmental and occupational health and safety management systems only. ISMS audit time sits under 27006-1. ISO 9001 software and audit costs explains the QMS basis and says the same thing in the other direction.

Stage 1 checklist: documents the auditor expects to exist

Stage 1 is a document review. The auditor is checking that a coherent ISMS exists on paper and that its parts agree with each other. Have each of these available, current, and consistent:

  1. ISMS scope — what is in, what is out, and the interfaces between them. The most common Stage 1 finding is a scope that does not match the rest of the documentation.
  2. Information security policy — approved, dated, and communicated.
  3. Risk assessment methodology — how you identify, analyse and evaluate risk, written down before the results. See our ISO 27001 risk assessment template.
  4. Risk assessment results — the register itself, with owners.
  5. Risk treatment plan — what you are doing about each risk, who owns it, by when. This is a separate document from the risk assessment and auditors check that it is.
  6. Statement of Applicability — every Annex A control, applicable or not, with justification either way. Our Statement of Applicability guide covers the format.
  7. The mandatory documented information — the full list is in ISO 27001 mandatory documents.
  8. Internal audit programme — planned, even if not yet executed.
  9. Management review plan — same.
  10. Objectives — information security objectives with something measurable attached.

The consistency test the auditor is actually applying: pick a risk from the register, trace it to a treatment decision, trace that to a control in the Statement of Applicability, and trace that to a policy or procedure. If the chain breaks anywhere, it is a Stage 1 finding. Run that trace yourself on three risks before the visit.

Check which edition your reference material uses

A real and easily missed problem. ISO/IEC 27001:2022 reorganised Annex A, and a large share of the ISO 27001 guidance still in circulation online uses the 2013 control numbering.

UKAS's technical bulletin on the ISO/IEC 27001:2022 transition records what changed: "Annex A has been aligned with the controls defined in ISO/IEC 27002:2022, which contains 93 controls (11 of which are new) organised in 4 themes. In addition to the 11 new controls, 24 have been merged and 58 have been updated."

(UKAS states the 11 / 24 / 58 figures of the ISO/IEC 27002:2022 control set, not of Annex A entries.)

So if a checklist you are working from cites a control like "A.9.2.2", it predates 2022. The 2013 edition used a different structure with different control numbers; the current Annex A has 93 controls in 4 themes. A Statement of Applicability built on the older numbering will not reconcile against the current Annex A, and that is a Stage 1 finding waiting to happen. Our list of Annex A controls uses the current structure.

Stage 2 checklist: records that prove the system runs

Stage 2 is about evidence of operation. The auditor will sample, interview staff, and look for the gap between the documented system and the real one. What they ask for, broadly:

Records that only time can produce

  • Internal audit reports covering the ISMS, with findings and their closure. Not a plan — completed audits. A separate guide on writing the ISO 27001 internal audit report follows this one.
  • Management review minutes with the required inputs actually discussed and decisions recorded.
  • Corrective actions raised, investigated to root cause, and closed with evidence.
  • Risk register reviewed and updated at least once since it was created.

Evidence that controls operate

  • Access reviews: who has access to what, reviewed and signed off, with joiners and leavers traceable.
  • Supplier arrangements: security requirements in contracts, and some evidence you assess suppliers.
  • Incident records — including the case where nothing serious happened, which is a legitimate record.
  • Backup and restore: evidence of a restore having been tested, not just configured.
  • Awareness and training records for the people in scope.
  • Logging and monitoring: evidence someone reviews what is logged.

Interviews

Auditors talk to staff who are not the person running the ISMS. Expect straightforward questions: what would you do if you received a suspicious email, who do you report an incident to, how do you get access to a new system. If the answers do not match your procedures, the procedures are the problem. Brief people honestly beforehand — not with scripted answers, which auditors recognise immediately, but by making sure they know the two or three things they genuinely need to know.

Nonconformities: major, minor, and what happens next

  • Major — a systemic failure, or a requirement not implemented at all. Certification is not recommended until it is corrected and the correction verified. This usually means a follow-up visit, which usually costs money.
  • Minor — an isolated lapse in an otherwise working system. Normally closed with a corrective action plan rather than another visit.
  • Observation / opportunity for improvement — not a finding; do not spend Stage 2 arguing about these.

For each finding, the response the auditor wants is a root cause and a corrective action that addresses it — not a patch on the single instance they happened to sample. The expensive mistakes UK SMBs make covers the same pattern on the quality side, and the ISO 9001 non conformance report template is a usable structure for recording either.

Before you book: check the body is accredited

An unaccredited ISO 27001 certificate is cheaper and, for most UK buyers, does not do the job — supplier approval processes and public-sector frameworks commonly require accreditation. UKAS states that "Only UKAS accredited certificates include the UKAS accreditation symbol".

Two checks, both free:

  • Confirm the body's accreditation and its scope in the UKAS directory of accredited organisations. Accredited for ISO 9001 does not mean accredited for ISO 27001.
  • Once certified, your certificate is verifiable in UKAS CertCheck, which UKAS describes as "a free-to-use and publicly accessible tool, allowing users to quickly search and verify the validity of claims of UKAS accredited certification." Your customers can and do use it — UKAS notes that "A key feature of CertCheck is the ability to track the accredited status of the certifications your supply chain hinges on."

How long to leave between the stages

Long enough to generate records, which in practice means running the ISMS for a period rather than closing document findings quickly. A system that was documented last month cannot show a reviewed risk register, a completed internal audit and a management review, because those things take elapsed time rather than effort.

If Stage 1 surfaces a scope or Statement of Applicability problem, fix that before anything else — both are upstream of everything Stage 2 samples. Our ISO 27001 gap analysis template is the right instrument for finding out where you are, and the ISO 27001 list of controls gives you the 93 current Annex A controls to baseline against.

Practical takeaway checklist

  1. Treat Stage 1 as a documents audit and Stage 2 as an evidence audit
  2. Trace three risks end to end — register, treatment, Statement of Applicability, procedure — before Stage 1
  3. Make sure your scope statement agrees with every other document
  4. Check your reference material uses 2022 Annex A numbering, not 2013 — the current Annex A has 93 controls in 4 themes
  5. Keep the risk treatment plan as a document distinct from the risk assessment
  6. Complete at least one internal audit and one management review before Stage 2
  7. Have a tested restore, not just a configured backup
  8. Brief staff on what they genuinely need to know; do not script them
  9. Answer every finding with a root cause, not a patch
  10. Confirm the body's UKAS accreditation covers ISO 27001 specifically, then verify your certificate in CertCheck
  11. Never price an ISO 27001 audit off a QMS audit-day table

This article is for general informational purposes only and does not constitute legal, regulatory, or professional compliance advice. The text of ISO/IEC 27001, ISO/IEC 27002 and ISO/IEC 17021-1 is not publicly available; nothing here is a quotation from any of them, and the stage descriptions reflect how UK certification bodies commonly run the audit rather than a requirement quoted from the accreditation standard. The 93-control, 4-theme figure is UKAS's, stated of ISO/IEC 27002:2022, with which UKAS says the current Annex A has been aligned; no control count is stated for the withdrawn 2013 edition, because none is available from a free primary source. Audit scope, duration and the split of topics between stages vary by certification body — confirm yours with your UKAS-accredited body.

ClauseWise is coming soon

Generate your ISO 9001 and ISO 27001 documentation without consultant fees.

We'll email you once when ClauseWise launches. Ask to be removed any time. Privacy policy