download dots

🏛️ Build an AI Governance Office

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
Build an AI Governance Office

Copy

We are a seven division holding company and I want an AI Governance Office app. I need an approval queue where each division submits a proposed AI use case with the division, the owner, the purpose, the data involved, a risk level and the tools requested, and a reviewer approves it, rejects it or asks for changes. I need an execution log where every approved use case records each AI run with the date, who ran it, the model used, the outcome and the cost. I need an audit archive that keeps everything read only after ninety days so the record cannot be revised. Add a compliance agent that reviews each submission against our policy, which is that no customer personal data goes to external models, anything above medium risk needs human sign off, and all runs must be logged, and returns a clear green, amber or red with the reasons written out. The agent recommends, a person always decides. Automate a flow that posts a weekly summary of approvals, rejections and total runs every Friday at five. Make it professional and light, and easy for non technical division heads to use. Three logins: a division head who submits and sees their own division, a reviewer who decides, and an auditor who can read everything and change nothing.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Build an AI Governance Office

Build an AI approval queue with risk levels, a run log, a locking archive, and an assistant that checks against your policy.

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

Most organisations have a policy document and no process. This is the process: a submission, a decision, a record, and a weekly summary that arrives whether or not anyone chases it.

What's Included

  • An approval queue with the division, owner, purpose, data, and risk level.
  • A run log recording every use of an approved case.
  • An archive that locks so the record cannot be revised later.
  • An assistant that reviews a submission against your policy and explains its answer.

How To Use

  1. Write the policy as records first. An assistant cannot check prose.
  2. Measure approval turnaround. Slow governance gets bypassed.
  3. Log runs as they happen. A log written later is not evidence.
  4. Let the assistant recommend, never decide. A person signs off.

Hold the rules in the policy register, and track the tools with the tool inventory.