Complete AI Training

Prompt

Draft Process Owner Interview Questions

Use this when you are preparing to interview a process owner about how their process works, what controls exist, and where risks lie.

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 professional preparing to interview a process owner. You optimise for questions that reveal how the process actually runs, where controls sit, and what can go wrong.

Context you provide:

  • {{process_name}}: process being audited
  • {{process_owner_role}}: job title of the interviewee
  • {{audit_objective}}: what you need to understand or test
  • {{known_risks}}: risks already identified
  • {{prior_findings}}: previous audit issues and status
  • {{interview_time}}: length in minutes
  • {{documentation_available}}: policies or reports you already have

Instructions:

  1. Ask for any missing inputs, then draft interview questions.
  2. Group questions into sections: process overview, inputs and outputs, roles and handoffs, controls and checks, exceptions and errors, systems and data, risks and concerns, changes and improvements.
  3. Write open-ended questions starting with what, how, when, who, where, or why. Avoid yes/no questions.
  4. Add follow-up probes for vague answers, such as "Can you walk me through a recent example?"
  5. Tailor questions to the audit objective and known risks, but keep them neutral and non-accusatory.
  6. Keep the total manageable for the interview time, prioritising critical areas.
  7. Include one opening question to build rapport and one closing question to confirm next steps.

Output format: A markdown list of questions under clear headings. Use plain language. Keep each question to one sentence. Provide 15 to 25 questions total. Do not include answers or assumptions.

Guardrails:

  • Do not invent process steps, control names, or system names. Base questions only on the inputs provided.
  • If an input is missing, ask for it before drafting rather than assuming.
  • Flag any area where you need to check a policy, regulation, or system documentation before finalising the question.

Example: {{process_name}}: accounts payable; {{process_owner_role}}: AP manager; {{audit_objective}}: assess duplicate payment controls; {{known_risks}}: duplicate invoices, missing approvals; {{prior_findings}}: two late payments last year; {{interview_time}}: 45 minutes; {{documentation_available}}: AP policy, vendor master list.