Audit Opening Meeting Agenda: Scope, Evidence, Access and Communication

An audit opening meeting agenda establishes the working rules before evidence collection begins. It gives auditors and the audited team a shared understanding of authority, scope, access, timing and communication without negotiating away the auditor’s independence or the approved criteria.

This is a general operational agenda. Audit mandates, professional standards, contractual terms and regulatory requirements differ. The appointed audit lead and qualified local reviewers control the actual process.

Prepare the meeting before sending invitations

Confirm the audit mandate, sponsor, objectives, scope, criteria and lead auditor before scheduling. Identify the accountable management contact and process owners who can arrange access. Do not invite a large audience when only a few roles need to make decisions.

Send a short pre-read containing:

• authority and purpose;
• proposed scope and exclusions;
• applicable criteria or framework;
• fieldwork dates and locations;
• initial evidence request;
• access, security and accessibility needs;
• attendee roles;
• proposed agenda and correction route.

Use meeting governance to clarify who owns decisions, evidence provision and follow-through.

Copy this audit opening meeting agenda

AUDIT OPENING MEETING

Audit title / reference:
Date, location and format:
Chair / audit lead:
Minutes owner:

1. Introductions and roles
2. Audit authority, objectives and intended outputs
3. Scope, boundaries, sites, systems and exclusions
4. Criteria and reference documents
5. Method, sampling and evidence expectations
6. Timetable, interviews and site access
7. Evidence request and secure transfer route
8. Confidentiality, privacy, safety and accessibility
9. Daily communication and issue clarification
10. Escalation, scope-change and disagreement routes
11. Closing meeting and draft-report process
12. Actions, owners and next checkpoint

Timebox each item, but allow enough space to resolve material scope or access issues. Defer detailed evidence testing to fieldwork.

Confirm authority, objectives and independence

State who commissioned the audit, the authority under which it operates and the intended audience for outputs. Explain whether the work is internal assurance, supplier review, grant monitoring, certification support or another form of audit without implying credentials the team does not hold.

Clarify independence, conflicts and reporting lines. Participants should know who can approve scope changes and who receives escalated constraints. If management requests a change, record the request and route it through governance rather than agreeing informally in the room.

The grant monitoring visit report provides a related evidence workflow, but grant monitoring and formal audit should not be treated as interchangeable.

Walk through scope and boundaries

Define organizational units, processes, sites, systems, period under review and interfaces included. State explicit exclusions and dependencies. A clear boundary reduces both accidental overreach and later claims that a relevant area was never considered.

Use a scope table:

Distinguish an exclusion from a limitation discovered during fieldwork. Limitations should be documented and assessed by the audit lead, not quietly converted into exclusions.

Align on criteria without pre-judging results

List the policies, contractual requirements, procedures, control descriptions or other approved criteria against which evidence will be evaluated. Confirm version and effective date. The opening meeting should clarify interpretation routes, not determine compliance before testing.

If criteria conflict or remain ambiguous, assign a qualified owner to resolve the question and preserve the rationale. Do not let an AI-generated summary become the authoritative criterion. Original controlled documents and approved interpretations govern.

Explain method, sampling and evidence quality

Describe the planned evidence methods: document review, observation, interviews, walkthroughs, reperformance or sampling. Explain that the plan may evolve when evidence warrants, subject to the mandate.

Set expectations for evidence that is relevant, reliable, traceable and complete enough for its purpose. A screenshot without source context or an unsupported verbal assurance may help orientation but rarely proves a control operated.

Avoid promising that a particular sample size guarantees assurance. Qualified auditors select and adjust samples based on objectives, population, risk, method and applicable requirements.

Ask process owners to explain known data-quality constraints before testing begins. Missing fields, system migrations, manual workarounds and population-definition changes can alter the planned procedure. Recording them at opening does not excuse a control weakness or predetermine a finding; it helps the audit lead design an appropriate, reviewable response and request the right source evidence.

Agree evidence access and secure handling

Name the approved transfer channel, access owner, folder structure and request-tracking method. Define how restricted, personal, privileged, commercially sensitive or security-related information will be handled. Apply data minimization and access controls from the start.

An evidence request should include:

1. request identifier;
2. criterion or audit objective;
3. requested source and period;
4. owner and due date;
5. approved transfer route;
6. status, limitation and reviewer.

The meeting recording consent form covers general capture questions, but audit evidence may require stricter controls and qualified review.

Plan interviews, observation and site logistics

Confirm interview roles, expected duration, location, accessibility and whether a support person or interpreter is needed. Explain the interview purpose and how notes will be used. Do not imply that interviewees must speculate or answer outside their responsibilities.

For site work, cover induction, protective equipment, photography restrictions, escorts, system access and operational disruption. Safety and local access procedures control. Auditors should not bypass a control merely to test whether it can be bypassed unless the authorized method explicitly permits it.

Sequence interviews so the team first understands the process and then tests specific evidence. Give participants enough context to bring relevant records without coaching an expected answer. Confirm how cancellations, substitutions and unavailable staff will be handled. Where an interviewee performs several roles, record which role and period their evidence addresses.

Use the accessible meeting checklist to remove avoidable participation barriers.

Set communication and clarification routes

Agree a daily contact, request cadence and method for clarifying emerging evidence. This is not a promise to disclose tentative findings prematurely. It is a route to resolve factual misunderstandings and access blockers efficiently.

Define what should be raised immediately, such as a serious safety concern, suspected evidence loss or material scope restriction. Qualified people must apply the applicable escalation procedure; avoid automated severity or credibility scoring.

Define disagreement and scope-change handling

Participants may disagree about evidence, criteria or a preliminary interpretation. Explain how evidence can be supplemented, how factual corrections are submitted and who resolves unresolved points. Preserve dissent without turning the opening meeting into a negotiation over future findings.

Any material scope change should record trigger, rationale, authority, effect on timetable and notification. A decision log supports this governance trail.

Distinguish a disagreement from an obstruction. Good-faith questions about relevance, confidentiality or operational impact should be routed for timely resolution. Repeated inability to provide authorized evidence may become a limitation, but the audit lead should assess and document it using the applicable framework rather than assigning motive to the audited team.

Clarify outputs, review and closing steps

Describe expected outputs, classification language, factual review, management response and closing meeting. State which dates are provisional and which are governed by mandate. Factual review should correct evidence and context, not suppress supported findings.

Explain how open requests and late evidence will be handled. Assign a single owner for the master action list so instructions do not fragment across email, chat and meeting notes.

For an authorized opening meeting with visible, agreed capture, Kuno can help create draft notes and actions for human verification. It does not select audit evidence, apply criteria or decide findings. Explore Kuno

Close with confirmed actions

Read back scope clarifications, access commitments, evidence deadlines, interview arrangements and unresolved questions. Give each action one owner and a review date. Distribute reviewed minutes through the approved channel and invite corrections within a defined period.

Before fieldwork begins, confirm:

• Authority, objectives and reporting lines are understood.
• Scope, period, sites and exclusions are explicit.
• Criteria versions and interpretation routes are recorded.
• Evidence transfer and access controls are ready.
• Interviews and site requirements are workable.
• Escalation and disagreement routes are known.
• Output, factual review and closing steps are clear.
• Every opening action has an owner and date.

Start fieldwork from a shared, reviewable record. Kuno can support consented in-room capture and draft notes; qualified auditors remain responsible for evidence, judgment, assurance and the final record. See Kuno