CORAA
CORAA University / Free kickoff pack

Internal audit kickoff pack generator

Build the entrance-meeting pack auditors actually need before fieldwork starts: agenda, scope confirmation, stakeholder RACI, first PBC commitments, escalation protocol and minutes tracker.

Kickoff profile
Readiness
94/100
Stakeholders
4
Scope items
4
PBC requests
6
Suggested agenda
1. Confirm appointment basis, reporting line, scope owner and governance expectations.Named sponsor, reporting route and approval expectations.
2. Walk through audit universe, risk ranking, cycle coverage, locations and review cadence.Confirmed cycles, locations, period and cadence.
3. Agree the first PBC list, evidence channel, ERP extracts and access support.Owner-wise request list, due dates and access method.
4. Confirm observation discussion route, management-response timeline and ATR ownership.Documented decision, owner and due date.
Stakeholder map and RACI
FunctionOwnerRoleResponsibility
Scope confirmation
AreaIn scopeOut of scopeDependency
First PBC commitments
AreaRequestOwnerDue
Minutes and action log
TopicDecision / actionOwnerDue date
Connect the file

Kickoff decisions should not stay in meeting notes.

Move approved scope into the programme, convert PBC commitments into a request tracker, and escalate unavailable evidence before fieldwork slips. Build the programme or open the evidence tracker.

How it works

An internal audit kickoff pack documents agreement before fieldwork begins. It should capture the review objective, approved scope, reporting route, stakeholder responsibilities, data access route, first PBC commitments and escalation triggers.

The pack is most useful when it is treated as a workpaper: scope decisions feed the audit programme, evidence commitments feed the PBC tracker, and unresolved blockers feed the evidence escalation log.

Worked example

A company begins its first quarterly internal audit covering P2P, O2C, R2R, payroll and ITGC.

Inputs
ModeFirst-year internal audit
CadenceQuarterly
Stakeholders4
Output
ExportExcel/PDF kickoff pack
Next filePBC tracker, programme and evidence escalation log

Common mistakes

Starting fieldwork without access owners
ERP extracts and source documents stall when no one is accountable for report access, extraction filters and completeness tie-out.
Unclear out-of-scope items
Document exclusions during kickoff. Otherwise rejected procedures later look like audit delay instead of agreed scope.
No escalation route
Evidence delays should have defined triggers, owners and timelines before the first request becomes overdue.

Frequently asked questions

What should an internal audit kickoff meeting cover?+
It should cover the objective, scope, period, locations, process owners, reporting route, evidence access, PBC timelines, observation discussion process and escalation protocol.
Is a kickoff pack required by law?+
The Companies Act and Rules do not prescribe a specific kickoff-pack format. It is a practical documentation aid that supports clear methodology, periodicity, scope and evidence planning.
How does the kickoff pack connect to the audit programme?+
Confirmed scope and dependencies should feed the internal audit programme. Data commitments should feed the PBC tracker, and unresolved evidence issues should feed the escalation tracker.

Authoritative sources

ICAI
ICAI IASB - Compendium of Standards on Internal AuditUse SIA planning, communication, evidence, documentation, reporting and follow-up principles when tailoring the kickoff pack.
ICAI
ICAI IASB - PublicationsLists current Standards on Internal Audit, generic guides, industry guides and knowledge booklets.
MCA
Companies (Accounts) Rules, 2014 - Rule 13Rule 13(2) refers to scope, functioning, periodicity and methodology for internal audit.
Always confirm against the latest version of the source. Regulations evolve and amendments are common.
Related calculators
Internal audit SOW generatorInternal audit data request listInternal audit programme generatorInternal audit resource hub
Share this tool
Last reviewed: 2026-08-30 · For informational purposes only — not professional advice.