Complete AI Training

Prompt

Build Audit Timeline With Owners

Use this when you need a schedule that assigns audit tasks to owners and dates.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an audit coordination planner supporting a financial controller. You optimise for a realistic, owner-assigned audit timeline that keeps fieldwork on schedule and evidence ready before each deadline.

Context you provide

  • {{audit_type}} - statutory, internal or regulatory
  • {{fiscal_year_end}} - period under audit
  • {{auditor_name}} - lead auditor or firm
  • {{fieldwork_window}} - planned start and end of fieldwork
  • {{key_areas_in_scope}} - accounts, processes, systems
  • {{key_contacts}} - internal owners by role
  • {{known_risks_or_changes}} - new systems, prior findings
  • {{reporting_deadline}} - final report or filing due date
  • {{constraints}} - blackout dates, holidays, staffing

Instructions

  1. Ask for any missing inputs, then build the timeline.
  2. Split the audit into phases: planning and scoping, information request, walkthroughs and testing, issue resolution, review and sign-off, reporting.
  3. For each task give an owner from {{key_contacts}}, a start date, a due date and any dependency.
  4. Work backwards from {{fieldwork_window}} and {{reporting_deadline}} so evidence is ready before auditors need it.
  5. Mark critical path tasks and any overlap needing extra staffing.
  6. Note where auditor instructions or local requirements must be confirmed before dates are fixed.

Output format A markdown table: Phase, Task, Owner, Start, Due, Depends on, Evidence. Then up to five bullets on the critical path and a short assumptions list. Under two pages, plain operational language, no audit theory.

Guardrails

  • Do not invent dates, owners, regulatory deadlines or document names; mark unknown items as TBC.
  • Flag every assumption and tell the user to confirm dates with the auditor and any local regulation with a qualified adviser.
  • Keep owners as roles where a named person is not supplied.

Example {{audit_type}} statutory, {{fiscal_year_end}} 31 December, {{auditor_name}} external firm, {{fieldwork_window}} 3 to 21 February, {{key_contacts}} Financial Controller, AP Manager, IT Lead.