6.3 Opening Meeting

Key Takeaways

  • The opening meeting (II.B.3, Apply) confirms purpose, scope, criteria, schedule, methods, logistics, and communication channels before detailed fieldwork.
  • Attendance should include audit team members and auditee leadership/liaison with enough authority to commit resources; record attendees for the audit file.
  • Scoring or classification criteria (e.g., major/minor/OFI definitions) and reporting expectations are explained so findings language is not a surprise later.
  • The meeting covers itinerary, escorts, safety/PPE, confidentiality, working hours, and how status and potential findings will be communicated.
  • Apply-level skill means running or participating in a complete opening meeting agenda—not treating it as optional small talk.
Last updated: August 2026

6.3 Opening Meeting (CQA BoK II.B.3 — Apply)

Quick Answer: The opening meeting (opening conference) officially starts fieldwork: confirm purpose and scope, criteria, schedule/itinerary, methods, classification/scoring expectations, logistics and safety, roles, and hold Q&A. Attendance is recorded. II.B.3 is Apply—you must be able to run or contribute to a complete, professional opening, not merely name the meeting.

If planning is the blueprint, the opening meeting is the site kickoff. Skipping it or reducing it to “hi, where’s the coffee?” creates avoidable conflict when findings appear, when auditors enter restricted areas, or when managers claim they never agreed to the scope.


Purpose of the Opening Meeting

The opening meeting aligns the audit team and auditee on how the engagement will be performed and what success looks like for communication—not on pre-deciding conformity.

Opening-meeting goalOutcome if done well
Confirm purpose & scopeShared boundaries; fewer mid-audit arguments
Confirm criteriaCommon yardstick for findings
Agree logistics & safetyEfficient, safe access
Explain methods & samplingLess fear that “they’re only looking for dirt randomly”
Explain classification / scoringTransparent severity language
Introduce team & rolesClear who leads, who escorts, who escalates
Set communication cadenceDaily status; potential findings raised early
Q&AConstraints surface before samples start

Apply note: For short, routine internal audits, the opening may be brief but should still cover purpose, scope, schedule, and logistics. For certification, regulatory, multi-day, or high-stakes second-party audits, expect a fuller formal meeting.


Who Should Attend

Audit side

  • Lead auditor (chairs the meeting).
  • Audit team members and technical experts who will work the engagement.
  • Interpreters if used.
  • Client representative when the program requires or when second/third-party rules include them (varies).

Auditee side

  • Management with authority over the areas in scope (or a designated management representative).
  • Audit liaison and primary escorts.
  • Quality/regulatory leads as applicable.
  • Process owners for major scope areas when practical (or they join area-level kickoffs).
  • EHS representative when safety briefing is integrated.
Attendance problemRisk
Only junior staff, no authorityCannot commit SMEs or resolve access
Audit team incompleteEscorts do not know faces/roles
No liaison presentLogistics collapse after the meeting
Unrecorded attendeesWeak audit file; later disputes about who was informed

Always record attendance (name, function, signature or electronic equivalent) in the audit file.


Core Agenda (Apply Checklist)

Use this as a practical run-of-show. Times scale with audit size (15 minutes to over an hour).

1. Introductions and roles

  • Lead introduces audit team, credentials at high level, and roles (lead, members, SME, observer).
  • Auditee introduces leadership, liaison, escorts.
  • Clarify observers (who may watch but not audit) and any trainees.

2. Purpose (objectives)

State why the audit is performed in plain language tied to the plan: e.g., annual internal system audit of Plant 2, supplier qualification for sterile packaging, surveillance of ISO 9001 processes X–Z, CAPA effectiveness verification for NCR-1044.

3. Scope and boundaries

  • Sites, buildings, processes, products, shifts, time period of records.
  • Explicit exclusions (e.g., design control out of scope; Site B next quarter).
  • Remote vs. on-site modules if hybrid.

4. Criteria

List the yardsticks: standards, regulations, contracts/quality agreements, customer specs, internal QMS procedures (controlled revisions). Invite questions on applicability.

5. Schedule and itinerary

  • Daily start/end times, breaks, shift coverage.
  • Sequence of departments/processes.
  • Planned interviews and key process observations.
  • Closing/exit meeting time (tentative).
  • Flexibility statement: itinerary may adjust for access and emerging risk (ties to 6.1).

6. Methods and sampling (high level)

  • Interviews, observation, document/record review, demonstration as applicable.
  • Sampling is risk-based and auditor-selected; auditee does not pick only “golden” lots.
  • Working language; need for translators.
  • Photo/video policy if relevant (many sites restrict).

7. Classification / scoring criteria

Explain how issues will be categorized under this program, for example:

Category (example program)Meaning (illustrative)
Major nonconformityAbsence or total breakdown of a required system element; likely significant risk to product/process/customer
Minor nonconformityPartial lapse that does not indicate system breakdown
Observation / OFINot a nonconformity; improvement opportunity or concern short of criteria failure
Positive practiceStrength worth noting

Stress that final classification follows evidence + program definitions, not auditor mood. If the program uses numeric scoring, scorecards, or traffic-light dashboards, explain the scheme and what feeds the report. Do not invent a scoring model if the program is purely nonconformity-based—state that clearly.

8. Logistics, access, safety, confidentiality

  • Badges, escorts, restricted areas, cleanroom/PPE, hearing/eye protection.
  • Emergency assembly points and stop-work authority.
  • Workspace, Wi-Fi, printer, secure document handling.
  • Confidentiality expectations (trade secrets, personal data, patient info).
  • How to request additional documents and people during the day.

9. Communication protocol

  • Daily debriefs or end-of-day status with liaison.
  • Potential findings raised as they mature for clarification.
  • Escalation path for access denial or serious risk discoveries.
  • Who receives the draft/final report (preview of reporting chapter).

10. Q&A

Invite questions. Typical topics: which shifts, union rules for interviews, system downtime, concurrent production peaks, COVID/visitor rules, language support. Capture constraints that require immediate plan tweak and confirm them aloud.

11. Close the meeting

Thank hosts, confirm first process visit and escort assignment, start fieldwork.


Sample Opening Statement (Lead Auditor)

“Thank you for hosting us. I’m Alex Rivera, lead auditor, with team members Sam and Dr. Lee (sterilization SME). Our purpose is a second-party process audit of your ethylene oxide release pathway against the quality agreement Rev D, your SOP set, and applicable ISO 11135 requirements as specified in the plan dated 12 March 2026. Scope is Building 4 sterilization and QC micro support; design and sales are excluded. We’ll sample records from the last six months, observe a load configuration if available Thursday a.m., and hold a closing meeting Friday at 3 p.m. Findings will be classified as major, minor, or OFI per our supplier audit procedure SUP-AUD-02—definitions are in your pre-read pack. We’ll raise potential issues as we go so you can provide clarifying evidence. Please confirm safety briefing and escort assignments, then we’ll take questions.”

This single statement hits purpose, scope, criteria, schedule, classification, communication, and Q&A setup—exam-friendly completeness.


Scenario — Apply the Full Agenda

Context: Three-day internal audit of a medical-device manufacturer’s production and final inspection for annual program coverage.

Opening (35 minutes):
Lead presents purpose (internal system/process hybrid slice), scope (Lines A–C, final inspection, DHR control; warehouse cycle-count excluded this cycle), criteria (ISO 13485 clauses as mapped in checklist + QMS procedures), itinerary (Day 1 production, Day 2 inspection/DHR, Day 3 CAPA follow-up and closing), methods (observation + record sample + interviews), classification table from the internal audit SOP, PPE/cleanroom rules, liaison contacts, daily 4:30 p.m. debrief.
Q&A: Production manager notes Line B changeover demo only possible Day 2 night shift. Lead applies flexibility: moves one auditor to night coverage; updates itinerary on the shared plan; records the change. Attendance sheet signed by 11 people. Fieldwork starts with gowning and Line A.

What good application looked like: Complete agenda, recorded attendance, transparent classification, and immediate schedule adjustment from Q&A—not ignoring the night-shift constraint.


Common Opening-Meeting Failures

FailureConsequence
No purpose/scope confirmationBoundary fights mid-audit
Criteria never statedFindings challenged as “opinion”
Classification surprise at closingHost hostility; claims of unfairness
No safety/PPE briefInjury risk; site rule violations
Itinerary secretSME no-shows; wasted time
Monologue with zero Q&AHidden constraints explode later
Wrong audience (no authority)Access and attendance problems
Opening used to present findingsWrong meeting—that is exit/closing

Opening vs. closing (keep them distinct)

OpeningClosing / exit
Confirm plan and logisticsPresent results and findings
Before detailed samplingAfter evidence collection
Set communication rulesConfirm understanding of issues and next steps

Do not pre-announce conformity conclusions in the opening; evidence is not yet gathered.


Remote and Hybrid Openings

Apply the same agenda via video when the audit is remote or hybrid:

  • Test connectivity before the formal start.
  • Share the itinerary and classification slide deck on screen.
  • Confirm document portal access and camera-tour rules during logistics.
  • Record attendance via meeting roster plus verbal roll call for critical roles.
  • For hybrid, state which activities are remote vs. on-site and when the team arrives on premises.

Documentation Outputs from the Opening

Keep in the audit file:

  • Attendance list.
  • Final confirmed itinerary (with any changes from Q&A).
  • Notes on constraints, denials, or special access conditions stated by the auditee.
  • Confirmation that purpose, scope, and criteria were reviewed (checkbox on plan or meeting minutes).

These records support later disputes (“we were never told…”) and demonstrate professional process control.


Key Exam Anchors

  • II.B.3 Apply: conduct/participate in opening meeting covering purpose, scope, criteria, schedule, methods, classification/scoring, logistics/safety, roles, communication, Q&A.
  • Record attendance; include people with authority plus liaison/escorts.
  • Explain how findings will be categorized under the program before fieldwork deepens.
  • Use Q&A to surface constraints and adjust the plan consciously.
  • Opening aligns the engagement; it does not present audit conclusions.
Test Your Knowledge

Which item belongs in the opening meeting rather than the closing meeting?

A
B
C
D
Test Your Knowledge

Why explain major/minor/OFI (or other scoring) definitions during the opening meeting?

A
B
C
D
Test Your Knowledge

During opening-meeting Q&A, the production manager states the only chance to observe a critical changeover is the night shift. What is the best apply-level response?

A
B
C
D
Test Your Knowledge

Who should typically chair and drive the opening meeting agenda?

A
B
C
D