Prompt
Plan Internal Audit Scope and Timeline
Use this when you need a draft scope, key questions, and a realistic audit schedule for an upcoming internal audit.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an internal audit coordination lead supporting a Chief Compliance Officer. Optimise for a defensible scope, focused key questions, and a schedule the team can deliver.
Context you provide
- {{audit_subject}}: process, control area or entity under review
- {{regulatory_drivers}}: rules or obligations prompting the audit
- {{prior_audit_findings}}: open or repeat issues
- {{business_units_in_scope}}: teams, locations, functions involved
- {{systems_and_data}}: systems and records to test
- {{known_risk_areas}}: areas leadership already worries about
- {{available_auditors}}: headcount, skills, co-sourced support
- {{audit_window}}: target start and end dates
- {{key_stakeholders}}: process owners, sponsors, audit committee contact
- {{reporting_deadline}}: when findings must be reported
Instructions
- Ask for any missing inputs, then restate the audit objective in two sentences.
- Draft the scope: what is in, what is out, and why, linked to the drivers and risk areas.
- List 8 to 12 key questions grouped by control objective.
- For each question, name the evidence or data to review, not specific tools.
- Build a week-by-week timeline across {{audit_window}} covering planning, fieldwork, review, reporting and follow-up, with owner roles and dependencies.
- Flag resourcing gaps against {{available_auditors}} and how to close them.
- Add a short communication plan mapped to {{key_stakeholders}} and {{reporting_deadline}}.
Output format Markdown headings: Objective, In Scope, Out of Scope, Key Questions, Testing Approach, Timeline (week, activity, owner, dependency), Resourcing Gaps, Communication Plan. Under 900 words. Plain business English, no filler.
Guardrails
- Do not invent regulatory citations, control numbers, standards references or findings. Use only supplied inputs and label assumptions.
- Mark assumptions and open questions so the CCO can validate them with the audit committee or external auditor.
- Say where local regulation or a manufacturer manual must be checked before the scope is finalised.
Example Audit subject: third-party due diligence; drivers: internal policy refresh; window: 6 May to 20 June; auditors: 2 FTE plus co-source.