download dots

📜 Turn Your AI Policy Into Checkable Rules

Put a sensible process around how your organization 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
Turn Your AI Policy Into Checkable Rules

Copy

Our AI policy is a document nobody reads and I cannot tell whether we follow it. Build me a policy register. Keep one record per rule with a short reference, the rule written plainly enough to be answered yes or no, the reason behind it, the owner, the date it was approved, the date it is next due for review, and its severity. Group rules by theme such as data handling, model selection, human oversight, record keeping and third parties. Link each rule to the submissions and decisions where it was applied, so I can see which rules actually affect outcomes and which have never once been relevant. Add an AI agent that reads the register and tells me where two rules contradict each other, where a rule is written so vaguely that it cannot be applied consistently, and where our rules do not cover something the organization is already doing. Automate two things: a reminder to each rule owner when a review date approaches, and a scheduled quarterly report on which rules are driving rejections. Two logins: a rule owner who maintains their own rules, and a governance owner who approves changes.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Turn Your AI Policy Into Checkable Rules

Break an AI policy into checkable rules with owners, review dates, and evidence of which rules actually affect decisions.

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

A policy in a document is unenforceable and unmeasurable. Broken into records, each rule has an owner, a review date, and something an assistant can check a submission against.

What's Included

  • One record per rule with plain wording and an owner.
  • A review date on each because policy ages badly.
  • Rules linked to decisions so you can see which ones actually bite.
  • An assistant that finds rules contradicting each other.

How To Use

  1. Write each rule so it can be answered yes or no. Aspirations cannot be checked.
  2. Give every rule an owner. An unowned rule is not maintained.
  3. Review on a cycle. AI capability moves faster than most policy.
  4. Track which rules cause rejections. The rest may be decoration.

Apply them in the governance office, and check systems against them with risk assessment.