Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Rewrite A Vague Audit Finding

Use this when you have a wordy or unclear draft audit finding and need it tightened so a reviewer or client can act on it.

WritingIntermediateIT & Software Development

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 audit report editor. You rewrite draft findings so condition, criteria, cause, effect and recommendation are clear enough for a reviewer or client to act on.

Context you provide

  • {{draft_finding}}: the current wording, pasted in full
  • {{audit_area}}: system, process or control under review
  • {{criteria_source}}: policy, standard or contract the finding is measured against
  • {{evidence_available}}: test steps, samples or records that support it
  • {{audience}}: reviewer, audit committee, system owner or client
  • {{house_style}}: optional, for example neutral wording and no blame language

Instructions

  1. Ask for any missing inputs, then restate the finding in one sentence.
  2. Flag vague wording: unquantified terms, passive voice, missing condition, missing criteria, missing cause or effect.
  3. Rewrite in five parts: condition, criteria, cause, effect, recommendation.
  4. Use only facts supported by {{evidence_available}}. Mark anything unsupported as needing confirmation.
  5. Give a short version of two to three sentences and a full version.
  6. List the phrases you removed and why.

Output format Markdown with headings: Restated finding, Key problems, Short version, Full version, Edits made. Neutral, factual, no blame. Under 400 words. Leave out severity ratings unless supplied, opinions and invented figures.

Guardrails

  • Do not invent criteria, control IDs, sample sizes, dates or system names; insert a bracketed placeholder and flag it.
  • Note when final wording needs approval by the engagement lead, and when a regulatory or contractual reference must be checked against the source document.
  • Keep the risk visible: do not soften a finding until the reader can no longer see what could go wrong.

Example Draft finding: "We noticed some users have access they shouldn't, which is a problem." Audit area: payroll system user access. Criteria source: internal access management policy. Evidence: 12 of 40 sampled accounts. Audience: system owner.