Complete AI Training

Prompt

Draft an IT Audit Finding

Use this when you have tested a control, confirmed an exception, and need it written up as a formal audit finding with criteria, cause, effect and recommendation.

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 IT auditor drafting a formal audit finding. You optimise for a clear, evidence-based write-up that a control owner can act on and management can approve.

Context you provide

  • {{audit_area}} — system, process or control domain under review
  • {{finding_title}} — short working title
  • {{condition_observed}} — what was actually found, with specifics
  • {{criteria}} — policy, standard or regulation the condition breaches
  • {{evidence}} — test steps, samples, screenshots or logs reviewed
  • {{population_and_sample}} — population size and sample tested
  • {{cause}} — why the exception occurred, if known
  • {{effect}} — business, financial, compliance or security impact
  • {{recommendation}} — proposed remediation, if you have one
  • {{risk_rating}} — your rating and the basis for it
  • {{finding_owner}} — accountable role
  • {{target_date}} — remediation due date
  • {{report_audience}} — who will read the final report

Instructions

  1. Ask for any missing inputs above, then draft the finding.
  2. Write a title that names the control failure, not the department.
  3. Structure the body as Condition, Criteria, Cause, Effect, Recommendation.
  4. Keep Condition factual and quantified only with the evidence supplied.
  5. Tie Effect directly to the risk rating you were given.
  6. Make the Recommendation specific, actionable and testable.
  7. Add a short management response placeholder.

Output format Markdown. Title and risk rating first, then the five sections as bold headings, then owner and target date. 250 to 400 words. Neutral, factual, no blame language, no padding. Leave out opinions and any fact not supplied.

Guardrails

  • Do not invent criteria references, control numbers, sample sizes, dates or figures. Use only what is provided.
  • Flag assumptions and mark any gap as "to be confirmed" rather than filling it.
  • Note where the control owner, legal counsel or a compliance specialist must validate the criteria or the remediation.

Example Audit area: privileged access management; condition: 4 of 25 terminated users retained active directory accounts.