download dots

🧾 Prepare for an External Audit or Review

Put a sensible process around how your organisation uses AI, without stopping anyone getting work done. These prompts build the approval queue, the register of what is running, the log of what each tool actually did, and the policy an assistant checks submissions against. Written for the person who has been asked to own this and given no software to do it with.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Prepare for an External Audit or Review

Copy

We have an external review coming and I do not know whether we can evidence what we claim. Build me an audit readiness app. Keep the requirements we are being assessed against as individual records, each with what it demands in plain language, and map each one to the specific evidence we hold, whether that is a policy record, an assessment, an approval, a run log or a training record, with the evidence attached rather than described. Show readiness per requirement as evidenced, partially evidenced or missing, with an owner and a due date on every gap. Add an AI agent that reviews each mapping and tells me not only what is missing but where the evidence we have attached does not actually demonstrate what the requirement asks for, which is the more common problem and the one that fails an audit. Track auditor findings afterwards with corrective actions through to closure. Automate two things: reminders on open gaps as the review date approaches, and a scheduled monthly readiness report. Three logins: an evidence owner who maintains their own area, a governance owner who sees everything, and a read only view for an auditor.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Prepare for an External Audit or Review

Map each requirement to actual evidence, surface gaps and weak evidence early, and track findings to closure.

// the spark catches · intelligence awakens · the answer unfolds

The worst time to discover a gap is when an auditor does. This maps each requirement to your evidence and shows what is missing while there is still time.

What's Included

  • Requirements mapped to evidence one line at a time.
  • Gaps identified early with an owner and a date.
  • Evidence gathered as you go rather than in a panic.
  • An assistant that finds weak evidence, not just missing evidence.

How To Use

  1. Map requirements to evidence continuously, not before an audit.
  2. Find your own gaps first. It is a much better conversation.
  3. Attach the actual evidence, not a description of where it might be.
  4. Record the auditor findings and close them properly.

Draw the evidence from the audit archive, and the rules from the policy register.