Study guide

5.3 Conducting the Opening Meeting

CQI/IRCA ISO/IEC 27001:2022 Lead Auditor ISMS

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Management Systems and ISO/IEC 27001

1.1 ISMS Concepts, Business Benefits, and the PDCA Cycle 1.2 ISO/IEC 27001:2022 Clauses 4 to 10 Requirements 1.3 Risk Assessment, Risk Treatment, and the Statement of Applicability (SoA)

2 Chapter 2: Annex A Information Security Controls

2.1 Organizational and People Controls (Annex A Themes 5 & 6) 2.2 Physical and Technological Controls (Annex A Themes 7 & 8) 2.3 Selecting, Implementing, and Auditing Annex A Controls

3 Chapter 3: ISO 19011 Auditing Principles and Auditor Conduct

3.1 ISO 19011 Auditing Concepts and Types of Audits 3.2 Auditor Roles, Responsibilities, and Competence Requirements 3.3 Legal, Ethical, and Professional Auditor Code of Conduct

4 Chapter 4: Planning and Scoping the ISMS Audit

4.1 Audit Objectives, Scope, and Criteria Establishment 4.2 Managing the Audit Program and Team Selection 4.3 Developing a Risk-Based Audit Plan and Checklist

5 Chapter 5: Pre-Audit Activities and the Opening Meeting

5.1 Stage 1 Audit and Documented Information Review 5.2 Preparing Audit Checklists and Working Documents 5.3 Conducting the Opening Meeting

6 Chapter 6: Conducting the Audit and Collecting Evidence

6.1 Audit Communication and Team Coordination 6.2 Interviewing Techniques and Open-Ended Querying 6.3 Gathering and Verifying Objective Evidence (Sampling and Tracing)

7 Chapter 7: Audit Findings, Reporting, and Closeout

7.1 Identifying, Grading, and Documenting Nonconformities 7.2 Conducting the Closing Meeting and Presenting Results 7.3 Audit Reporting, Corrective Actions, and Follow-Up

5.3 Conducting the Opening Meeting

Key Takeaways Explain This Topic AI

The opening meeting formally starts on-site or remote audit activity: confirm objectives, scope, criteria, and plan, and establish communication channels.

The Lead Auditor introduces the team, explains methods and sampling uncertainty, and defines how findings will be graded and reported.

Logistics, health and safety, information security rules for the visit, and confidentiality commitments must be addressed explicitly.

A clear, professional tone reduces defensiveness and supports timely access to people and evidence throughout the audit.

Last updated: July 2026

Exam relevance

Opening-meeting items appear within the Conducting the audit domain (14/40 online exam questions). Expect scenarios about what must be confirmed (scope, criteria, plan), what must be explained (sampling, finding categories, communication), and which administrative topics are mandatory (safety, security of the visit, confidentiality). ISO 19011 describes opening meetings as the point where audit arrangements are confirmed and questions are addressed. For certification audits, ISO/IEC 17021-1 expects audits to be conducted according to plan with clear communication—professional opening meetings are how that starts in practice.

Core rules: purpose and tone

The Lead Auditor chairs the opening meeting with management, the ISMS owner/representative, and key process owners. Goals:

  • Confirm audit objectives, scope, and criteria
  • Confirm or adjust the audit plan and logistics
  • Introduce the audit team and roles (auditors, technical experts, observers, guides)
  • Explain methods, sampling, and reporting of findings
  • Establish communication channels and meeting cadence
  • Address health, safety, security, and confidentiality
  • Invite questions and confirm closing-meeting arrangements

Tone should be authoritative and calm—neither aggressive interrogation nor casual chat. Audits are stressful; defensiveness blocks access to evidence. Clarity and respect keep the process objective.

Recommended opening-meeting agenda

  • Agenda item Lead Auditor actions Why it matters
  • Introductions Name audit team roles; invite client introductions Maps contacts to processes
  • Objectives, scope, criteria Restate boundaries, standards, and exclusions Prevents mid-audit scope disputes

Audit plan walk-through Confirm interviews, locations, remote links, times Surfaces availability conflicts early

Methods and sampling Explain interviews, observation, document review; sampling uncertainty Manages expectations on "no findings"

Finding categories Define major/minor nonconformity and OFI (as used by the CB) Reduces closing-meeting arguments

  • Logistics and H&S Escorts, rooms, badges, evacuation, PPE Protects people and schedule
  • Security & confidentiality Device rules, photo bans, secure evidence transfer Protects sensitive ISMS data
  • Communications Daily wrap-ups; named contacts Keeps management informed
  • Questions & closing time Confirm Q&A and closing meeting slot Formalizes next steps
  • Explaining methodology without over-promising

Evidence will be collected through:

  • Interviews with process owners and practitioners
  • Observation of activities and the work environment
  • Review of documented information and records

Because audits sample available information, absence of reported nonconformities does not prove absolute conformity everywhere. State this plainly. Also explain how findings will be classified and when they will be communicated (for example, as they arise and/or in daily briefings), so surprises at the closing meeting are minimized.

  • Logistics, safety, security, and confidentiality checklist
  • Confirm guides/escorts and access to agreed areas and systems
  • Confirm emergency procedures and any site-specific hazards
  • Confirm rules on cameras, phones, removable media, and printing
  • Confirm secure channels for sharing screenshots, logs, and tickets (especially for remote audits)

Reaffirm NDA/confidentiality: audit information used only for audit purposes and protected against unauthorized disclosure

Confirm language, interpreters, and any observers' status

Remote openings add identity checks for participants, stable screen-share for the plan, and explicit agreement on evidence transfer tools that meet confidentiality expectations.

Scenario: scope creep attempt in the opening meeting

At opening, a CIO asks the team to "also quickly look at the newly acquired subsidiary" that was excluded from the certified ISMS scope and the agreed Stage 2 plan. The Lead Auditor thanks them for the request, restates the confirmed scope and criteria, and explains that expanding boundaries mid-audit would invalidate timeboxing and sampling design. Options offered: keep the agreed scope now, or pause to renegotiate contract/scope with the certification body before continuing. The CIO accepts the planned scope. By handling this in the opening meeting—not after two days of informal "extra" sampling—the Lead Auditor protects audit integrity and avoids unplanned conclusions about entities outside criteria.

Confirming plan logistics without losing control of the audit

The opening meeting is also where last-minute availability problems surface: a key process owner is on leave, a data center escort is delayed, or VPN tokens for remote evidence review fail. The Lead Auditor should adjust sequence and timeboxes while protecting audit objectives. Acceptable flexibility includes swapping interview slots or shifting a low-risk process to later. Unacceptable "flexibility" includes casually adding out-of-scope entities, skipping high-risk processes because the owner is busy, or accepting client-chosen samples that avoid known weak areas. Guides and observers should be identified; guides facilitate access but must not answer for interviewees or filter evidence.

Remote/hybrid specifics to confirm aloud:

  • Participant identity and role for each dial-in attendee
  • Breakout rooms or separate calls for parallel audit streams
  • Screen-share and recording rules (usually no recording unless contractually agreed)
  • How offline sites or paper records will be covered if the audit is partly remote
  • Managing resistance and closing the meeting

If participants appear anxious or hostile, restate that the audit evaluates the management system against agreed criteria—it is not a personal performance review. Emphasize continual improvement and the need for timely access to people and records. If someone challenges auditor competence or confidentiality, respond factually: outline roles, accreditation/certification-body framework at a high level, and the binding confidentiality arrangements—without becoming defensive or argumentative.

Second scenario: safety and device rules ignored

An opening meeting rushes past H&S. Mid-morning, an auditor enters a restricted operations hall with an unmarked tripping hazard and begins photographing rack labels on a personal phone, violating the client's no-camera policy. The audit stops for an incident discussion; trust drops; IT restricts further access. A proper opening meeting would have covered evacuation routes, escorts, camera bans, and approved evidence-capture methods (for example, client-assisted screenshots via a secure share). Administrative topics are not bureaucracy—they protect people, the client's security posture, and the audit schedule.

Record attendance, confirm the closing-meeting time and place (or link), answer remaining questions, and then begin evidence gathering promptly. A disciplined opening meeting is short relative to Stage 2, but it prevents the costliest failures: wrong scope, missing interviewees, unclear finding language, unsafe or insecure site conduct, and confidentiality misunderstandings. Master it as a Lead Auditor skill, not a formality.