Opening and closing meetings that work

The two meetings that bracket an audit take perhaps forty minutes between them, and they decide much of what follows. A rushed opening meeting leaves the auditee unsure what the audit covers, so every request feels like an ambush. A poor closing meeting sends findings into the report that the process owner has never properly heard, and the first response to the report is a dispute. This guide gives agendas for both, with an example from an internal audit at Kestrel Metals, a fictional fabricator in Lagos and Ogun.

Why the two meetings matter

ISO 19011:2018 describes an opening meeting and a closing meeting as part of conducting an audit. ISO 9001:2015 does not name them, but clause 9.2.2 expects audit results to be reported to the relevant management, and the closing meeting is the first place that happens.

The opening meeting sets the terms: what the audit covers, how it will run and what happens with the findings. The closing meeting tests the findings: the auditee hears them, checks the facts and agrees what happens next. Both are as much about the relationship between auditor and auditee as about procedure. Internal auditors usually audit the same colleagues again next year.

Who attends

For a typical internal audit of one process:

Role	Opening	Closing	Why
Lead auditor or auditor	Yes	Yes	Runs both meetings
Other audit team members	Yes	Yes	Present their own findings
Process owner	Yes	Yes	Accountable for the process and the response
Guide or main contact	Yes	Optional	Arranges access and people during the day
Supervisors or key staff	Optional	Optional	Useful if they will answer for specific findings
Quality manager or audit programme manager	Optional	Optional	Attends if a serious finding is likely
Senior management	Rarely	Optional	Useful for high-risk findings or a cross-functional scope

Keep the closing meeting small enough for a frank conversation. If senior managers want the results, they will get the report.

A sample opening meeting agenda

For an internal audit the opening meeting usually takes ten to fifteen minutes. Tunde Bakare used this agenda for the purchasing audit at Kestrel Metals’ Ikeja plant:

1. Introductions. Who is on the audit team, who is the guide, who is available during the day.
2. Objective and scope. Why this audit, which process, site and period. “Purchasing at the Ikeja plant, purchase orders raised January to August 2026.”
3. Criteria. ISO 9001 clause 8.4, procedure QP-08, and the customer requirements flowed down on purchase orders.
4. The plan. Timings, interviews, areas to visit, records to be ready. Confirm any changes since the audit plan was sent.
5. Method. Samples will be chosen by the auditor from full lists; the audit looks at the process, not individuals.
6. Findings and grading. How findings will be recorded and graded, and that possible findings will be raised during the day, not saved for the end.
7. Logistics. Safety rules and PPE, confidentiality, a room to work in, access to systems.
8. Closing meeting. Confirm time, place and who will attend.
9. Questions.

Item 8 is the one people skip. Agreeing the closing time at the start is what gets the process owner back in the room at 4 p.m.

Point 5 is worth saying aloud. Staff who believe the audit is about catching them out answer narrowly and hand over prepared files. A sentence at the start that the audit is of the process, and that findings name records and roles rather than people, changes the tone of the day.

Keep a short attendance record for both meetings: date, time, names and roles. It takes a minute and answers the certification auditor’s question about whether findings were communicated to the auditee.

Where people join remotely, for example a process owner at the Ogun plant joining an audit at Lagos, send the agenda and the plan in advance and check that everyone can see the same document. Remote attendees drift quickly in a long meeting, so keep the opening even shorter and ask the remote participants directly whether they have questions.

During the day: no surprises

The closing meeting goes well when nothing in it is new. When you find something that may become a finding, say so then: “I’ve found three suppliers without a current evaluation. Is there anything I haven’t seen?” This gives the auditee a chance to produce a record you missed, which is far better on the day than after the report is issued.

If the scope needs to change, for example because a trail leads into stores or finance, agree it with the process owner at the time rather than announcing it at the end.

A short check-in with the process owner at lunch, or halfway through a longer audit, helps too. Five minutes to say what has been seen so far, what is still to come and any possible findings gives the owner time to find missing records and prepares them for the closing meeting.

A sample closing meeting agenda

Allow twenty to thirty minutes for a one-day audit, longer if there are several findings. Before the meeting, spend half an hour alone or with the audit team reviewing evidence, agreeing findings and grades, and writing each nonconformity in its final form.

1. Thanks and scope recap. One sentence each.
2. Overall conclusion. Whether the process conforms to the criteria and appears effective, in plain language.
3. Positives. What works well, with evidence. Be specific: “All 12 purchase orders sampled stated grade and certificate requirements.”
4. Nonconformities. Read each one out: requirement, evidence, statement, grade.
5. Observations and opportunities for improvement.
6. Confirm the facts. Ask the auditee to confirm the facts behind each finding.
7. Next steps. Who will respond to each finding, by when, and when the report will be issued.
8. Questions and close.

At Kestrel Metals, the closing meeting covered one nonconformity and one observation. J. Okafor, the purchasing manager, accepted both and agreed to respond with a root cause and action within three weeks. Tunde committed to issuing the report within five working days.

Present findings without arguments

How findings are presented matters as much as what they say.

• Lead with the requirement and the evidence, not the conclusion. “QP-08 requires annual re-evaluation. Of the eleven active suppliers, three had no evaluation since 2023.” The auditee reaches the conclusion before you say it.
• Use numbers and record IDs. “Three of eleven” leaves less room for argument than “several”.
• Avoid judgement words such as “poor”, “inadequate” or “careless”.
• Do not offer solutions. If asked, say that the action is for the process owner to decide after looking at the cause. The guide on writing audit findings explains why.
• Do not trade findings. Downgrading one finding in exchange for acceptance of another undermines the whole audit.

Handling disagreement on the day

Disagreement usually falls into one of three kinds.

Disagreement	What to do
The facts are wrong	Check the new evidence. If it meets the requirement, withdraw or amend the finding and say so.
The requirement is misread	Read the clause or procedure together. If it is genuinely ambiguous, consider an observation about the procedure.
The grade is too harsh	Point to the written grading definitions. If still disputed, record the auditee’s view and refer it to the audit programme manager.

Settle disagreements about facts before you leave. Disagreements about grade can wait, but agree who decides and by when, and note it on the finding. An auditor who corrects a factual error openly gains credibility; one who defends it loses the next audit too.

Agree next steps and dates

End with a short list of commitments, read back so everyone hears them:

• Who will respond to each finding, and the date.
• When the report will be issued.
• How and when the actions will be verified, for example at a follow-up audit or the next scheduled audit.

Be realistic about dates. A response date the process owner cannot meet produces an overdue action within a month and an argument at the next audit. Two to four weeks for a root cause and action plan is common for internal findings; a correction to contain an immediate risk, such as quarantining product accepted with an out-of-date gauge, should happen the same day. Where an action needs budget or a decision above the process owner, say so at the meeting and name who will take it to the right manager.

Record the dates against each finding. In Orisynx, the person responsible for an action accepts it or disputes it with a reason before work can start, so a disagreement left over from the closing meeting is recorded rather than lost. The guide on writing the internal audit report covers what happens next.

Sources

• ISO 19011:2018, Guidelines for auditing management systems: https://www.iso.org/standard/70017.html