Markdown Editor

Stage 1 Readiness Pack Template (ISO/IEC 27001 Certification)

Stage 1 audit prep: what Stage 1 reviews, document pack mapped to required documented information, records, go or no-go, logistics, typical findings

ISMS và ISO/IEC 27001Đầy đủISO/IEC 27001:2022 + Amd 1:2024 clauses 4 to 10 (cited only); ISO/IEC 17021-1:2015; ISO/IEC 27006-1:2024stagereadinesspack
Mở trong editorTải .md

Cách dùng: Use it eight to ten weeks before the Stage 1 audit. Fill the document pack checklist first, with approved documents and IDs. The main pitfall is treating Stage 1 as a formality and carrying unresolved areas of concern into Stage 2.

Xem trước

Stage 1 Readiness Pack: [Organization name]

Readiness pack and checklist for the Stage 1 certification audit of the information security management system (ISMS) of [Organization name] against ISO/IEC 27001:2022 + Amd 1:2024. It explains what Stage 1 reviews under ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024, lists the document pack mapped to the documented information the standard requires, sets go or no-go readiness criteria, covers logistics, and gives typical Stage 1 findings with the way to close them before Stage 2. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document IDDOC-ISMS-091
Version[1.0]
Status[Draft / In review / Approved / Superseded]
Owner[@isms-manager]
Approvers/reviewers[@ciso], [@ceo]
Last updatedYYYY-MM-DD
Classification[Internal / Confidential]
Standard and editionISO/IEC 27001:2022 + Amd 1:2024; CB rules ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024
Certification body[CB name] (selected in DOC-ISMS-090)
Stage 1 dates and mode[YYYY-MM-DD to YYYY-MM-DD, on site / remote / mixed]
Lead auditor[name as notified by the CB]
Pack sent to CB[YYYY-MM-DD, by secure channel]
Next scheduled review[After the Stage 1 report, YYYY-MM-DD]

Approvals

RoleNameDecisionDate
ISMS manager[@isms-manager][Pack complete]YYYY-MM-DD
Top management[@ceo][Go for Stage 1 / Postpone]YYYY-MM-DD

Revision history

VersionDateAuthorChange
0.1 (Example)2027-03-22[@isms-manager]Pack assembled, 3 documents still in review
1.0 (Example)2027-04-07[@isms-manager]All documents approved, go decision at the management review of 2027-04-06, pack sent to CB
1.1 (Example)2027-04-16[@isms-manager]Stage 1 areas of concern added in section 9

Contents

  1. Purpose and scope
  2. What Stage 1 reviews
  3. Timeline to Stage 1 and Stage 2
  4. Document pack checklist
  5. Records that show the ISMS operates
  6. Readiness criteria (go or no-go)
  7. Logistics
  8. Typical Stage 1 findings and how to close them
  9. Stage 1 report and closure tracker
  10. Size tiers
  11. Records and evidence
  12. References

1. Purpose and scope

This pack prepares [Organization name] for the Stage 1 audit of its ISMS. It gives the ISMS manager one checklist to confirm that the required documents exist and are approved, that the ISMS has produced records, that people and systems are available, and that known weak points are closed or planned before Stage 2.

ItemValue
Scope statement[Copy from DOC-ISMS-002, version n]
Sites and cloud regions in Stage 1[list]
Persons in scope (as declared to the CB)[n]
Statement of Applicability versionDOC-ISMS-011, version [n]
Planned Stage 2 window[YYYY-MM-DD to YYYY-MM-DD]

2. What Stage 1 reviews

Under ISO/IEC 17021-1:2015 the initial certification audit has two stages. Stage 1 is mainly about the documented system, its readiness and the planning of Stage 2. The list below is our own paraphrase of the Stage 1 objectives as commonly summarised from ISO/IEC 17021-1:2015; the standard and the CB's audit plan are the authority. In practice the auditor will typically:

  1. read your core documents (scope, policy, risk method, SoA, objectives and the records listed in section 4) and look for gaps against clauses 4 to 10 of ISO/IEC 27001:2022 + Amd 1:2024;
  2. test whether the scope on paper matches the real business: which entities, sites, teams and suppliers are in or out, and whether the headcount and site data behind the audit-day quote are still right;
  3. ask how you reached your risk decisions, which laws and contracts drive them, and what the business context looks like;
  4. look for proof that the improvement loop has started (an internal audit done, a management review held) and form a view on whether Stage 2 can go ahead;
  5. walk a site or a system demonstration and talk to the people who run the ISMS, to see whether they understand what the standard expects;
  6. settle the practical details of Stage 2 with you: who, where, which evidence and when.

ISO/IEC 27006-1:2024 adds ISMS-specific expectations for Stage 1, which in practice centre on the auditor understanding the ISMS design, the risk assessment and treatment, the SoA, and the information security policy and objectives before Stage 2 (check the standard for the exact requirements). The CB decides whether Stage 1 is on site, remote or mixed under its rules and IAF MD 4:2025, now re-issued by Global ACI as Global ACI-TECH-3-003 (check the current issue).

A note on CB practice: certification bodies usually expect one full internal audit of the ISMS and one management review before Stage 2 (CB practice, not a clause), and enough operating time for the ISMS to have produced records. This is CB practice and the auditor's judgement of readiness, not a clause in ISO/IEC 27001. Ask your CB what it expects and record the answer in section 6.

3. Timeline to Stage 1 and Stage 2

Example plan (Example: Quillmere Analytics Ltd, target certificate within 6 months of project start; audit days as quoted by the selected CB: Stage 1 1.5 days over two calendar days, Stage 2 3.5 days over three calendar days; certification decision 2027-06-15):

MilestoneDate (Example)Owner
Internal audit IA-2027-01 complete (fieldwork 2027-03-15 to 2027-03-17), report issued2027-03-29[@internal-auditor]
Management review held (go decision), minutes approved2027-04-06[@ceo]
Pack complete and approved2027-04-06[@isms-manager]
Pack sent to CB2027-04-07[@isms-manager]
Stage 12027-04-12 to 2027-04-13CB lead auditor
Stage 1 report received2027-04-16CB lead auditor
Areas of concern closed2027-05-07Action owners
Stage 22027-05-10 to 2027-05-12CB audit team

4. Document pack checklist

4.1 Documented information the standard explicitly requires

#ClauseRequired item (paraphrased)Our documentVersionStatusOwner
14.3ISMS scopeDOC-ISMS-002 ISMS scope[n][Ready / Not ready][@isms-manager]
25.2Information security policyDOC-ISMS-001 information security policy[n][Ready / Not ready][@ceo]
36.1.2Risk assessment processDOC-ISMS-010 risk assessment methodology (with DOC-ISMS-015 risk criteria)[n][Ready / Not ready][@isms-manager]
46.1.3Risk treatment processDOC-ISMS-010 and DOC-ISMS-013 risk treatment plan[n][Ready / Not ready][@isms-manager]
56.1.3 dStatement of ApplicabilityDOC-ISMS-011 SoA[n][Ready / Not ready][@isms-manager]
66.2Information security objectivesDOC-ISMS-024 objectives register[n][Ready / Not ready][@ciso]
77.2Evidence of competenceDOC-ISMS-026 competence and training matrix, training records[n][Ready / Not ready][@hr-lead]
87.5.1 bOther documented information the organization judged necessaryPolicies, procedures and standards in DOC-ISMS-005 policy index[n][Ready / Not ready]Policy owners
98.1Enough operational planning records to show that processes ran the way they were meant toDOC-ISMS-004 process map, DOC-ISMS-032 annual calendar, operating procedures (DOC-ISMS-049)[n][Ready / Not ready][@isms-manager]
108.2Risk assessment resultsDOC-ISMS-017 risk assessment report and DOC-ISMS-016 risk register[n][Ready / Not ready][@isms-manager]
118.3Risk treatment resultsDOC-ISMS-013 risk treatment plan status, DOC-ISMS-019 risk acceptance records[n][Ready / Not ready]Risk owners
129.1Monitoring and measurement resultsDOC-ISMS-080 measurement programme, DOC-ISMS-081 performance report[n][Ready / Not ready][@isms-manager]
139.2.2Audit programme and audit resultsDOC-ISMS-082 internal audit programme, DOC-ISMS-084 internal audit report[n][Ready / Not ready][@internal-auditor]
149.3.3Management review resultsDOC-ISMS-085 management review minutes[n][Ready / Not ready][@ceo]
1510.2Nonconformities and corrective actionsDOC-ISMS-087 nonconformity and corrective action records, DOC-ISMS-086 audit findings register[n][Ready / Not ready][@isms-manager]

Clause 6.3 (planning of changes, new in 2022) has no explicit documented information requirement, but auditors often ask how changes to the ISMS are planned. Include DOC-ISMS-025 (ISMS change plan) if you keep one. Amendment 1:2024 added climate change to the context analysis: decide whether it matters for your ISMS (4.1) and check whether any stakeholder has climate-related demands (4.2). Make sure DOC-ISMS-003 shows that decision.

4.2 Supporting documents auditors usually ask for

#DocumentIDWhy the auditor asksStatus
16Context and interested partiesDOC-ISMS-003Clauses 4.1 and 4.2, including the climate decision[Ready / Not ready]
17Roles, responsibilities and RACIDOC-ISMS-006Clause 5.3[Ready / Not ready]
18Legal, regulatory and contractual registerDOC-ISMS-014Clause 4.2 and A.5.31[Ready / Not ready]
19Asset inventoryDOC-ISMS-012Basis of the risk assessment, A.5.9[Ready / Not ready]
20Communication planDOC-ISMS-027Clause 7.4[Ready / Not ready]
21Documented information registerDOC-ISMS-028Clause 7.5, control of documents[Ready / Not ready]
22Incident response plan and incident registerDOC-ISMS-020, DOC-ISMS-021A.5.24 to A.5.27[Ready / Not ready]
23Supplier registerDOC-ISMS-066A.5.19 to A.5.22[Ready / Not ready]
24Business continuity and ICT readinessDOC-ISMS-121, DOC-ISMS-047A.5.29, A.5.30[Ready / Not ready]
25Control evidence matrixDOC-ISMS-033Shows where evidence for each applicable control sits[Ready / Not ready]
26Organisation chart and site list[ref]Scope and audit time[Ready / Not ready]

4.3 Pack rules

  • Send documents as read-only exports with the Document ID, version and approval date visible.
  • Send through the channel agreed with the CB, following DOC-ISMS-043 (information transfer policy). Do not send Restricted records (for example vulnerability details or personal data); offer them for viewing during the audit instead.
  • Keep an index of exactly what was sent and when (section 11).

5. Records that show the ISMS operates

ProcessRecordPeriod coveredCount (Example)Status
Internal auditAudit reports, findings[from to]1 full cycle, 4 findings (AF-2027-001 to 004)[Ready / Not ready]
Management reviewMinutes and actions[date]1 review, 9 actions[Ready / Not ready]
Risk managementRisk register updates, acceptance records[from to]62 risks, 1 accepted by top management (ACC-001)[Ready / Not ready]
Objectives and measurementMeasurement results per objective[from to]3 months of results for 6 metrics[Ready / Not ready]
Corrective actionNonconformity records[from to]7 opened, 4 closed[Ready / Not ready]
AwarenessTraining completion[from to]44 of 46 persons complete[Ready / Not ready]
Access reviewsReview records[from to]1 quarterly review of production access[Ready / Not ready]
Incidents and eventsIncident register entries[from to]11 events, 2 incidents[Ready / Not ready]
Supplier reviewsSupplier assessments[from to]9 critical suppliers assessed[Ready / Not ready]

The counts are Example values for Quillmere Analytics Ltd. The 46 persons match the scope headcount (38 employees and 8 contractors); the 2 persons not yet trained must be trained before Stage 2 or the gap shown with a dated plan.

6. Readiness criteria (go or no-go)

#CriterionEvidenceResult
R1All 15 items in section 4.1 approved and currentDOC-ISMS-028 extract[Met / Not met]
R2Scope, SoA version and risk treatment plan are consistentCross-check by [@isms-manager][Met / Not met]
R3Risk assessment complete for the whole scope, with owners and treatment decisionsDOC-ISMS-017[Met / Not met]
R4At least one full internal audit cycle completed (CB practice)DOC-ISMS-084[Met / Not met]
R5At least one management review completed covering all 9.3.2 inputs (CB practice)DOC-ISMS-085[Met / Not met]
R6Internal audit findings have corrective action plans with owners and datesDOC-ISMS-086[Met / Not met]
R7Measurement results exist for each objectiveDOC-ISMS-081[Met / Not met]
R8No high or critical risk without an approved treatment or acceptanceDOC-ISMS-016, DOC-ISMS-019[Met / Not met]
R9Key people available on Stage 1 datesSection 7[Met / Not met]
R10CB expectations confirmed in writing: [record the CB's answer]CB e-mail of YYYY-MM-DD[Met / Not met]

Decision rule (Example): go if R1 to R5 and R8 are met and any other gap has an owner and a date before Stage 2.

7. Logistics

ItemArrangement
Audit plan received from CB[YYYY-MM-DD]
Mode[On site at (address) / remote via (platform) / mixed]
Audit guide (escort)[@isms-manager]
Note taker[@name]
Room or call link[room name / link sent by secure invitation]
Interviewees and time slotsTop management [@ceo] [time]; risk owner [@coo] [time]; IT and cloud [@head-of-engineering-ops] [time]; HR [@hr-lead] [time]
Evidence displayScreen share from the document store; no uploads of Restricted records
Site visit route[office areas, secure areas, colocation suite if in scope]
Visitor rulesSign-in, badge, escort, confidentiality agreement if the CB contract does not cover it
Opening meeting attendees[@ceo], [@isms-manager], [@ciso]
Closing meeting attendeesSame as opening, plus process owners with findings
Fallback if the call fails[phone number, rescheduling rule from the CB contract]

8. Typical Stage 1 findings and how to close them

#Typical area of concernWhy it mattersHow to close it before Stage 2
T1Scope statement vague or does not match the sites and services quotedScope drives audit time and the certificate wordingRewrite DOC-ISMS-002 with services, sites, entities and exclusions; tell the CB if headcount or sites changed
T2Interfaces and dependencies with out-of-scope parties not describedAuditor cannot see where responsibility changesAdd an interfaces table to the scope and link supplier controls
T3Climate change decision missing in context (Amd 1:2024)Clauses 4.1 and 4.2 changed in 2024Add the decision and rationale to DOC-ISMS-003
T4Risk criteria not defined or not applied consistentlyClause 6.1.2 needs repeatable, comparable resultsApprove DOC-ISMS-015 and re-score inconsistent risks
T5SoA justifications generic, or exclusions without a reasonClause 6.1.3 dRewrite rows with risk, legal, contractual or business basis (see compliance/statement-of-applicability)
T6Risk treatment plan without owners, dates or risk owner approvalClause 6.1.3Complete DOC-ISMS-013 and record risk owner approval of residual risk
T7Objectives not measurable or without plansClause 6.2Add metric, target, owner, resources and due date per objective
T8Internal audit did not cover all clauses or all Annex A areas plannedClause 9.2Complete the remaining audit scope before Stage 2
T9Management review minutes miss required inputsClause 9.3.2Hold a supplementary review or add the missing inputs with decisions
T10Competence evidence missing for key rolesClause 7.2Complete DOC-ISMS-026 and attach certificates or training records
T11Documents not controlled (no version, owner or approval)Clause 7.5Bring documents under DOC-ISMS-028 control
T12Measurement results missing or started very recentlyClause 9.1Collect results for every metric and report them in DOC-ISMS-081

9. Stage 1 report and closure tracker

IDCB refArea of concernClause or controlActionOwnerDueEvidence of closureStatus
STG1-001 (Example)AOC-01Climate change decision not recorded (logged as AF-2027-005 in DOC-ISMS-086)4.1Add decision to DOC-ISMS-003, approve at steering committee[@isms-manager]2027-04-30DOC-ISMS-003 v1.2, minute of 2027-04-29Closed
STG1-002 (Example)AOC-02Management review did not cover feedback from interested parties9.3.2Supplementary review item at the steering meeting of 2027-05-04[@ceo]2027-05-05Minutes DOC-ISMS-085 of 2027-05-04Closed
STG1-003 (Example)AOC-03Two persons in scope without awareness training7.3Complete training, add a check to onboarding[@hr-lead]2027-05-07Training records dated 2027-05-03, updated onboarding checklistClosed
[STG1-NNN][ref][concern][clause][action][@owner]YYYY-MM-DD[record][status]

Summary (Example): 3 areas of concern, all 3 closed by 2027-05-07, before the Stage 2 start date of 2027-05-10.

10. Size tiers

AspectSmall: Quillmere Analytics Ltd (Example)Medium: Quillmere Health Systems (Example)Large: Quillmere Group (Example)
Profile46 persons, one office plus remote staff, one cloud provider in two regions320 staff, two offices, one colocation suite2,400 staff, 6 sites in 4 countries, OT and IT, ISO 9001 and ISO 22301 certified
Pack ownerPart-time ISMS manager (0.5 FTE, Head of Engineering Operations)Full-time ISMS manager with a 3-person security teamCISO's 14-person security office with site coordinators
Stage 1 modeRemote, with a short office visitMixed: remote document review, visit to one office and the colocation suitePhase 1 sites only (for example HQ and data centre), on site, under the phased plan in isms/scope-extension-multisite-plan
Pack size15 required items plus about 10 supporting documentsSame plus colocation contract and 27701 readiness notes for next yearSame per phase, plus integrated management system documents shared with ISO 9001 and ISO 22301
Main riskToo few records because the ISMS started recentlyHealth-sector legal register incompleteDifferent practices per site and country, weak central control
Readiness checkISMS manager and CEOSteering committeeGroup steering committee and site leads, site-by-site go or no-go

11. Records and evidence

RecordOwnerLocationRetention
Index of documents sent to the CB, with versions and date[@isms-manager][ISMS document store]Certification cycle + 3 years (Example)
Go or no-go decision (section 6)[@ceo][Steering committee minutes]Certification cycle + 3 years
CB audit plan and Stage 1 report[@isms-manager][ISMS document store]Certification cycle + 3 years
Closure tracker (section 9) with evidence[@isms-manager][ISMS document store]Certification cycle + 3 years
Attendance at opening and closing meetings[@isms-manager][ISMS document store]Certification cycle + 3 years

Register these in DOC-ISMS-028 and link the evidence locations in isms/control-evidence-matrix.

12. References

ReferenceEditionUse
ISO/IEC 27001:2022 (https://www.iso.org/standard/82875.html)2022Clauses 4 to 10 and Annex A
ISO/IEC 27001:2022/Amd 1:2024 (https://www.iso.org/standard/88435.html)2024-02-23Climate change in 4.1 and 4.2
ISO/IEC 17021-1:2015 (https://www.iso.org/standard/61651.html)2015Two-stage initial certification audit
ISO/IEC 27006-1:2024 (https://www.iso.org/standard/82908.html)2024ISMS-specific audit requirements
ISO/IEC 27007:2020 (https://www.iso.org/standard/77802.html)2020, under revisionISMS auditing guidance
IAF MD 4:2025, ICT for conformity assessment, re-issued as Global ACI-TECH-3-003Issue 3, application 30 Jan 2026; Global ACI v1.0 in force 28 Aug 2026 (check the current issue)Remote Stage 1

Related templates: isms/certification-body-selection, isms/stage-2-audit-evidence-index, isms/certification-findings-action-plan, isms/isms-documented-information-register, isms/control-evidence-matrix, compliance/ms-scope, compliance/statement-of-applicability, compliance/internal-audit-program, compliance/management-review, isms/certification-audit-explained.

Standard and licence note

Structure aligned with ISO/IEC 27001:2022 + Amd 1:2024 (clauses 4 to 10 and the documented information they require) and with the Stage 1 requirements for certification bodies in ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024. The checklists, readiness criteria, typical findings and examples are original; no ISO/IEC text is reproduced, and the required items are paraphrased by clause number. ISO and IEC standards are copyrighted: obtain the official text from ISO (https://www.iso.org/standard/82875.html) or your national standards body. Check the current editions and your certification body's audit plan and rules before use. Completing this pack does not guarantee certification; the certification decision belongs to the certification body. Template licence: MIT.

Template liên quan