Markdown Editor

Certification Cycle Plan Template (ISO/IEC 27001 3-year cycle)

3-year certificate cycle, timing rules, Gantt timeline, audit coverage, change notifications, suspension and withdrawal, recertification, transfers, budget

SMKI & ISO/IEC 27001LengkapISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024 certification cycle for ISO/IEC 27001:2022 + Amd 1:2024 (cited only)certificationcycleplandiagram

Cara menggunakan: Use it once the certification body is chosen and keep it for the life of the certificate. Fill the certificate facts and the CB's audit programme dates first, then the coverage plan. The main pitfall is treating surveillance as a light check-in and missing a window or leaving a major unresolved.

Pratinjau

Certification Cycle Plan: [Organization name]

Plan for the three-year ISO/IEC 27001:2022 + Amd 1:2024 certification cycle: initial certification (Stage 1 and Stage 2), surveillance audits in the following years, and recertification before the certificate expires. It follows the audit programme rules that certification bodies (CBs) apply under ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024, and supports clauses 9.2 (internal audit), 9.3 (management review) and 10 (improvement) by putting the internal cycle and the external cycle on one timeline. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document IDDOC-ISMS-094
Version[1.0]
Status[Draft / Approved / Superseded]
Owner[@isms-manager]
Approvers/reviewers[@ceo or top management sponsor], [@ciso], [@finance-lead]
Last updatedYYYY-MM-DD
Classification[Internal]
Standard and editionISO/IEC 27001:2022 + Amd 1:2024; CB rules per ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024
Certification body[CB name], accredited by [accreditation body] (signatory of the Global ACI MRA, formerly the IAF MLA), accreditation number [n]
Certificate number[n]
Certification decision dateYYYY-MM-DD
Certificate expiry dateYYYY-MM-DD
Certified scope (as printed)[scope wording], DOC-ISMS-002 [version]
SoA version on certificateDOC-ISMS-011 [version]
Sites on certificate[list or "single site plus remote workers"]
Next scheduled review[After each CB audit and at least once a year]

Approvals

RoleNameDecisionDate
ISMS manager[@isms-manager][Prepared]YYYY-MM-DD
Finance[@finance-lead][Budget confirmed for the cycle]YYYY-MM-DD
Top management[@ceo][Approved]YYYY-MM-DD

Revision history

VersionDateAuthorChange
1.0 (Example)2027-06-20[@isms-manager]First plan after the initial certification decision on 2027-06-15
1.1 (Example)2028-06-01[@isms-manager]Surveillance 1 result added; surveillance 2 dates confirmed by the CB
[x.y]YYYY-MM-DD[@author][Change]

Contents

  1. Purpose and scope
  2. The cycle at a glance and timing rules
  3. Cycle timeline
  4. What each audit covers
  5. Preparing each audit
  6. Changes to notify to the certification body
  7. Keeping the certificate valid
  8. Suspension, withdrawal, reduction and expiry
  9. Recertification
  10. Changing certification body
  11. Budget and resources across the cycle
  12. Size tiers
  13. Records and evidence
  14. References

1. Purpose and scope

This plan keeps the ISO/IEC 27001 certificate of [Organization name] valid for its three-year cycle and makes sure the ISMS is ready for each CB audit. It aligns the external audit dates with the internal ISMS activities that the CB will check: internal audits, management review, risk assessment updates, corrective actions and measurement.

The certificate is a commitment to customers and partners. In the Example, Quillmere Analytics Ltd has 12 customer contracts that require a valid ISO/IEC 27001 certificate, so a lapse would put those contracts in breach. List your own dependencies here:

DependencyWhat it requiresContactImpact if the certificate lapses
Customer contracts (Example)Valid certificate covering the SaaS platformAccount managementContract breach notice, renewal at risk
Public tenders (Example)Certificate number and scope in bidsSales operationsBids rejected
Cyber insurance (Example)Declared certification statusFinancePremium review
[dependency][requirement][@contact][impact]

2. The cycle at a glance and timing rules

PhasePurposeWhen
Stage 1CB reviews ISMS documentation, scope, readiness and plans Stage 2Before Stage 2; the gap is agreed with the CB
Stage 2CB evaluates implementation and effectiveness of the ISMSAfter Stage 1 concerns are resolved
Certification decisionCB decides after reviewing the audit report and accepted responses to findingsAfter all nonconformity responses are accepted and majors verified
Surveillance 1Confirms the ISMS still conforms and operates effectivelyNo later than 12 months after the certification decision date
Surveillance 2Same purpose, covering further parts of the ISMSIn the next calendar year
RecertificationConfirms continued conformity and effectiveness over the whole cyclePlanned and completed, with the decision made, before the certificate expires

Timing rules to plan around:

  1. The certificate cycle is three years from the certification decision.
  2. Surveillance audits take place at least once each calendar year, except in recertification years.
  3. The first surveillance after initial certification takes place no later than 12 months from the certification decision date.
  4. The recertification audit is planned and carried out in time for the CB to make its decision before the expiry date. Plan for the audit several months before expiry so that findings can be closed.
  5. Audit time for each audit is set by the CB under ISO/IEC 27006-1:2024 from the number of persons doing work under the organization's control and complexity factors. Days in this plan are Example values.
  6. Multi-site sampling, where it applies, follows ISO/IEC 27006-1:2024 and the multi-site requirements of the accreditation system (IAF MD 1:2023, now re-issued by Global ACI as Global ACI-TECH-3-001; check the current issue).

3. Cycle timeline

Example for Quillmere Analytics Ltd: internal audit IA-2027-01 from 2027-03-15 to 2027-03-17, management review on 2027-04-06, Stage 1 on 2027-04-12 and 2027-04-13 (1.5 audit days), Stage 2 from 2027-05-10 to 2027-05-12 (3.5 audit days), certification decision on 2027-06-15, certificate expiry on 2030-06-14.

EventPlanned date (Example)Rule check
Internal audit IA-2027-012027-03-15 to 2027-03-17Before the management review and Stage 1
Management review2027-04-06After the internal audit report (2027-03-29), before Stage 1
Stage 12027-04-12 to 2027-04-131.5 audit days
Stage 22027-05-10 to 2027-05-123.5 audit days; findings CBF-2027-01 and CBF-2027-02 among those raised
Certification decision2027-06-15Start of cycle
Surveillance 12028-05-15 to 2028-05-16Before 2028-06-15 (12 months from decision): meets rule 3
Surveillance 22029-05-14 to 2029-05-15Calendar year 2029: meets rule 2
Recertification audit2030-03-11 to 2030-03-13About 3 months before expiry, time to close findings
Recertification decision target2030-04-30Before expiry on 2030-06-14: meets rule 4
New certificate expiry[as set by the CB, often 2033-06-14 when recertification is completed on time]Confirm with the CB

Gantt bars show calendar days on site; the audit days that drive fees (section 11) can differ, for example 1.5 audit days spread over two calendar days, or 3.5 audit days over three calendar days when a second auditor joins for half a day.

4. What each audit covers

4.1 Items reviewed at every surveillance

CBs check a standing set of topics at each surveillance (ISO/IEC 17021-1:2015 sets these for all management system audits; this is a paraphrase, not the standard's text):

Standing topicWhat to have readyTemplate
Internal audit and management review since the last auditAudit reports, management review minutes and decisionsisms/isms-internal-audit-report, compliance/management-review
Actions on findings from the previous auditStatus and evidence for each nonconformityisms/certification-findings-action-plan
Handling of complaintsComplaint log and responses relating to information securityisms/audit-findings-register
Effectiveness against objectivesObjectives status and measurement resultscompliance/objectives-register, isms/isms-performance-report
Progress of continual improvementImprovement register entries and outcomesisms/continual-improvement-register
Continuing operational controlRecords showing controls operateisms/control-evidence-matrix
Changes since the last auditChange log for scope, organization, systems, risksisms/isms-change-plan
Use of the certificate and marksExamples of how the certification is referencedisms/certification-mark-usage

4.2 Coverage across the cycle

Example coverage plan for Quillmere Analytics Ltd. Each X means the area is planned for detailed audit; standing topics in 4.1 are covered every time.

AreaStage 2 (2027)Surveillance 1 (2028)Surveillance 2 (2029)Recertification (2030)
Clause 4 context and scopeXX
Clause 5 leadership and policyXXX
Clause 6 risk assessment, treatment, SoA, objectivesXXXX
Clause 7 support (competence, awareness, documented information)XXX
Clause 8 operationXXXX
Clause 9 performance evaluationXXXX
Clause 10 improvementXXXX
A.5 organizational controlsSampleAccess, suppliers, incidentsCloud, continuity, legalSample across theme
A.6 people controlsSampleScreening, awarenessRemote working, reportingSample across theme
A.7 physical controlsOfficeEquipment, disposalOfficeSample across theme
A.8 technological controlsSampleEndpoint, vulnerabilities, loggingDevelopment, backup, networkSample across theme

Clause 6, 8, 9 and 10 appear in every audit because risk, operation, evaluation and improvement are where the CB sees whether the ISMS is alive. Over the cycle, every applicable control in the SoA should have been sampled at least once; ask the CB for its audit programme to confirm.

4.3 Audit-type comparison

AspectStage 1Stage 2SurveillanceRecertification
Main questionIs the ISMS ready to be audited?Does it conform and work?Does it still conform and work?Has it worked over three years and will it continue?
Evidence periodDocuments and plansRecords since the ISMS started operatingRecords since the last auditRecords over the whole cycle
Typical locationOn site or remote, per CBOn site, with remote parts where allowedOn site or remote, per CBOn site, with remote parts where allowed
Example duration (Example)1.5 days3.5 days1.5 days2.5 days
OutputStage 1 report and concernsReport, findings, recommendationReport, findings, continuationReport, findings, recertification recommendation

5. Preparing each audit

Weeks before auditActivityOwnerOutput
16Confirm audit dates and auditor with the CB; report any changes (section 6)ISMS managerCB confirmation
12Run the surveillance readiness health checkISMS managerisms/surveillance-readiness-health-check report
10Complete internal audit cycle for the periodInternal audit leadInternal audit reports
8Hold management review with all required inputsTop managementMinutes and decisions
6Close or progress open corrective actions; update risk register and SoAProcess ownersUpdated records
4Receive the CB audit plan; book interviewees and rooms or remote sessionsISMS managerInterview schedule
2Refresh the evidence index and test remote access for the auditorISMS managerEvidence index
0Opening meeting, audit, closing meetingAllAudit report
+1 to +4Respond to findings by the CB deadlineISMS managerisms/certification-findings-action-plan

For remote audit parts, agree in advance the tools, screen sharing rules, what may be recorded, and how confidential evidence is shown without handing over copies. IAF MD 4 (now re-issued by Global ACI as Global ACI-TECH-3-003) covers the use of information and communication technology in audits; check the current issue.

6. Changes to notify to the certification body

ChangeExampleNotify within (Example)Who
Legal entity, ownership or nameAcquisition, merger, renameAs set in the certification agreement (Example: 30 days)Top management
Scope (services, products, processes)New product line in scope, a service removedBefore the change takes effectISMS manager
SitesNew office, closed site, new data centre or cloud regionBefore the change takes effectISMS manager
Number of persons in scopeHeadcount up or down significantly, affecting audit timeAt the next audit planning, or sooner if largeHR and ISMS manager
Key personnelNew ISMS manager or CISO, top management changePromptlyISMS manager
Major incident or legal actionSignificant breach, regulator investigationAs set by the CB (Example: promptly after containment)CISO
Major change to the ISMS or controlsOutsourcing of operations, new cloud providerBefore the change takes effectISMS manager

A scope extension or new site may need a special audit. Plan these in isms/scope-extension-multisite-plan (DOC-ISMS-095).

7. Keeping the certificate valid

ObligationHow it is metOwnerEvidence
Allow audits at the required frequencyDates in section 3 confirmed with the CB each yearISMS managerCB audit programme
Pay fees on timeFees in the annual budget (section 11)FinanceInvoices paid
Keep the ISMS conforming between auditsInternal audits, management review, corrective actionsISMS managerRecords in section 13
Use certificate and marks only as permittedApproval workflow in isms/certification-mark-usageMarketing and ISMS managerApproval log
Keep records of complaints and actionsComplaint log linked to the findings registerISMS managerComplaint log
Notify changesTriggers in section 6ISMS managerNotification log
Accept short-notice audits when the CB needs themContact list kept currentISMS managerCB contact record
Make claims only within scopeScope wording checked before publicationISMS managerApproval log

8. Suspension, withdrawal, reduction and expiry

RiskCommon triggerPrevention
SuspensionSurveillance not held in time; a major nonconformity not resolved by the CB deadline; serious misuse of the certificate or marks; client asks for a temporary suspensionDates confirmed 16 weeks ahead, findings plan with owners, mark approval workflow
WithdrawalSuspension not resolved within the period the CB sets (Example: 6 months, per CB rules); repeated serious breaches of the agreementEscalate any suspension to top management at once
Scope reductionPart of the scope persistently fails to meet requirementsTreat site or process weaknesses before they reach the CB
ExpiryRecertification audit or decision not completed before the expiry dateRecertification audit about 3 months before expiry

During suspension the certificate is temporarily invalid: stop all claims of certification and use of marks, and inform the customers whose contracts require it if the contracts say so. ISO/IEC 17021-1:2015 allows a CB to restore a certificate that expired because recertification was not finished in time: within six months of expiry, provided the outstanding recertification activities are completed; after that, at least a Stage 2 audit is needed. The certificate is not valid in the gap between expiry and the new decision; the CB sets the dates on the restored certificate, commonly an effective date on or after the recertification decision and an expiry date that follows the previous cycle (as explained in European co-operation for Accreditation guidance on the standard; confirm the period and conditions with your CB). Do not plan to rely on this.

9. Recertification

Before the recertification audit:

  1. Review context, interested parties and scope (DOC-ISMS-003, DOC-ISMS-002): has the business changed enough to change the scope?
  2. Refresh the risk assessment in full and update the SoA (DOC-ISMS-017, DOC-ISMS-011).
  3. Complete a full-scope internal audit cycle covering all clauses and all applicable controls.
  4. Hold a management review that looks at performance over the whole cycle: objectives trend, incidents, audit results, improvement.
  5. Check that every nonconformity from the cycle is closed and its effectiveness reviewed.
  6. Confirm with the CB the audit plan, duration (Example: 2.5 days) and any sites to visit.

The CB reviews the performance of the ISMS over the cycle, including previous surveillance reports, before it decides. Nonconformities found at recertification must be resolved in the time the CB sets and before expiry. If they cannot be, the certificate lapses at expiry.

10. Changing certification body

A valid, accredited certificate (issued under accreditation by a signatory of the Global ACI MRA, formerly the IAF MLA) can usually be transferred to another accredited CB without restarting the cycle. The receiving CB carries out a pre-transfer review of the current certificate, the last audit reports, open nonconformities, complaints and the reason for the change, under IAF MD 2 on transfer of accredited certification (now re-issued by Global ACI as Global ACI-TECH-3-002; check the current issue). Open major nonconformities usually block a transfer until closed. Plan transfers away from audit dates and keep copies of all reports from the previous CB. Use isms/certification-body-selection to choose the new CB.

11. Budget and resources across the cycle

Example CB fees for Quillmere Analytics Ltd at a day rate of USD 1,500 (an Example rate; ask your CB for its quote) and an annual certificate and administration fee of USD 600:

YearAuditsAudit days (Example)Day fees (USD)Admin fee (USD)Total (USD)
2027Stage 1, Stage 25.07,5006008,100
2028Surveillance 11.52,2506002,850
2029Surveillance 21.52,2506002,850
2030Recertification2.53,7506004,350
Total10.515,7502,40018,150

Add internal effort: the ISMS manager's time for preparation and response, interviewees' time on audit days, internal audit time, and travel for auditors if the CB charges it. Record the full plan in isms/isms-budget-resource-plan (DOC-ISMS-031).

12. Size tiers

AspectSmall: Quillmere Analytics LtdMedium: Quillmere Health SystemsLarge or multi-site: Quillmere Group
Profile46 staff, 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
Cycle plan ownerPart-time ISMS manager (0.5 FTE)Full-time ISMS managerCISO office with site coordinators
Audit timeSet by the CB from 46 persons in scope and complexity (Example total 10.5 days over the cycle)Set by the CB from 320 persons, two offices and the colocation suiteSet by the CB per site and phase, with sampling under ISO/IEC 27006-1 and IAF MD 1 (Global ACI-TECH-3-001)
Surveillance focusSame small team interviewed each time; rotate controlsRotate offices and the colocation suite across surveillancesRotate sampled sites; central functions every audit
IntegrationStand-alone ISMS cycle27001 cycle now; a PIMS certificate under ISO/IEC 27701:2025 planned the year after, possibly aligned datesIntegrated audits with ISO 9001 and ISO 22301 where the CB offers them (IAF MD 11, now Global ACI-TECH-3-008); phased site additions through scope extensions
Main riskOne person away at audit timeTwo cycles drifting apart if 27701 is added laterA site added late misses its sampled audit

13. Records and evidence

RecordOwnerLocationRetention (Example)
Certificate and certification decision letterISMS managerEvidence library, certification folderLife of certificate plus one cycle
CB audit programme and audit plansISMS managerCertification folderCurrent and previous cycle
CB audit reportsISMS managerCertification folderCurrent and previous cycle
Findings action plansISMS managerDOC-ISMS-093 per auditCurrent and previous cycle
Change notifications to the CBISMS managerNotification log in this planCurrent and previous cycle
Internal audit reports and management review minutesInternal audit lead, top managementDOC-ISMS-084, DOC-ISMS-085Per DOC-ISMS-028
Mark usage approvalsMarketingDOC-ISMS-097 approval logCurrent and previous cycle
Invoices and certification agreementFinanceFinance systemPer finance retention rules

Map these records in isms/control-evidence-matrix (DOC-ISMS-033) under clauses 9.2, 9.3 and 10.2. They also feed the ISMS annual calendar (isms/isms-annual-calendar, DOC-ISMS-032).

14. References

ReferenceEditionUse
ISO/IEC 27001:2022 + Amd 1:2024https://www.iso.org/standard/82875.html ; Amd 1: https://www.iso.org/standard/88435.htmlRequirements audited in every audit
ISO/IEC 17021-1:2015https://www.iso.org/standard/61651.htmlCertification cycle, surveillance, recertification, suspension, withdrawal
ISO/IEC 27006-1:2024https://www.iso.org/standard/82908.htmlISMS audit time, multi-site sampling, auditor competence
ISO/IEC 27007:2020https://www.iso.org/standard/77802.htmlISMS auditing guidance (under revision; check for a newer edition)
IAF MD 1, MD 2, MD 4, MD 11, re-issued as Global ACI-TECH-3-001, -002, -003 and -008Global ACI v1.0 issued 2026-07-10, in force 2026-08-28; check the current issueMulti-site, transfer, ICT in audits, integrated audits. IAF and ILAC ceased operations on 1 January 2026 and their work passed to Global Accreditation Cooperation Incorporated (Global ACI); the IAF MLA became the Global ACI MRA
Your CB's certification rules and agreementCurrent versionBinding dates, periods and obligations

Related templates: isms/certification-body-selection (DOC-ISMS-090), isms/stage-1-readiness-pack (DOC-ISMS-091), isms/stage-2-audit-evidence-index (DOC-ISMS-092), isms/certification-findings-action-plan (DOC-ISMS-093), isms/scope-extension-multisite-plan (DOC-ISMS-095), isms/surveillance-readiness-health-check (DOC-ISMS-096), isms/certification-mark-usage (DOC-ISMS-097), compliance/internal-audit-program (DOC-ISMS-082).

Standard and licence note

Structure aligned with the certification cycle described in ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024 for ISO/IEC 27001:2022 + Amd 1:2024 certification. The text, tables, timeline and examples are original. No ISO or IEC text is reproduced; read the official standards (purchase or licensed access from ISO, IEC or your national standards body) and your certification body's rules before relying on any period or rule stated here. Check the current edition of each standard and the current accreditation documents before use. Audit days and fees are Example values; audit time is set by the certification body, and certification decisions are made only by the accredited certification body. This is a documentation format, not certification or legal advice. Template licence: MIT.

Templat terkait