This planner is deterministic, not a mock. It builds a plan and a low/base/high cost estimate from the inputs you type and a versioned public model catalog — not measured from your systems. It does not run, rank, or supervise agents, and it is not a quality or compliance verdict.

Measure your delivery setup
3 min · no signup · nothing stored

AI Governance Policy Generator

Fill in your approved tools, data rules, oversight, and review cadence and get a vendor-neutral AI governance / acceptable-use policy in Markdown — structured around the sections ISO/IEC 42001 and the NIST AI RMF assume. Copy or download it; nothing leaves your browser.

The generator

Your details

Policy preview

# Your organization — AI Governance & Acceptable-Use Policy

> Draft generated from the ShipReady Metrics AI governance policy template. Adapt each
> section to how your teams actually work; a policy that does not match reality is ignored.
> This is a starting outline, not legal advice.

## 1. Purpose & scope

This policy sets out how Your organization adopts and uses artificial intelligence: which tools are
approved, what data may be used with them, who is accountable, and how AI-assisted work is
overseen. It applies to all employees, contractors, and systems that use AI on behalf of Your organization.

## 2. Roles & accountability

AI risk is owned by **_TODO: name the role accountable for AI risk and tool approval_**,
who approves new tools, maintains the AI inventory, and is accountable for AI-related risk across
the organization. Each AI system has a named owner responsible for its appropriate use.

## 3. Approved tools & intake

The following AI tools are approved for use:

- _TODO: list the AI tools approved for use_

To request a new tool, submit it to the policy owner for review before use. Using an unapproved
AI tool for Your organization work is not permitted until it has been through intake.

## 4. Data handling

The following data classes must **never** be entered into AI tools without documented controls
and the policy owner's approval:

- _TODO: list the data classes that must not be entered into AI tools (e.g. PII, secrets, regulated data)_

When in doubt, treat data as restricted and ask before using it with an AI tool.

## 5. Human oversight

A human must review and take responsibility for AI output before it is relied on in the following
cases: _TODO: describe where human review of AI output is required_.
AI assists people; it does not replace accountable human judgment.

## 6. AI inventory (AI-BOM)

Your organization maintains an inventory of AI systems in use — the tool, its purpose, the data it processes,
the model(s) and relevant configuration, and the system owner. New AI systems are recorded before
they go into use. You cannot govern the lifecycle of a system you have not recorded.

## 7. Provenance & records

Enough information is logged to reconstruct an AI-assisted decision after the fact: the system
used, the inputs provided, and the human who reviewed and relied on the output. Records are
retained per Your organization's data-retention schedule.

## 8. Third-party & procurement

Vendors whose products embed AI are subject to diligence proportionate to the risk and the data
involved, including how they use inputs for training and their security posture.

## 9. Prohibited uses

The following uses are never permitted:

- _TODO: list uses that are never permitted (e.g. fully automated high-stakes decisions)_

## 10. Review & exceptions

This policy is reviewed **at least annually** and whenever AI capability or Your organization's usage changes
materially. Exceptions must be requested from the policy owner and are recorded with a rationale
and an expiry.

---

*Aligned to the structure of ISO/IEC 42001 and the NIST AI Risk Management Framework, both of
which assume you can enumerate and manage your AI systems. Sections 6 and 7 (inventory and
provenance) are what make those requirements achievable.*

Nothing is stored or sent anywhere — the policy is generated in your browser. Blank fields become TODO prompts so the draft never invents your rules for you.

How to use this

The point of an AI governance policy is to make the sanctioned path clear and fast, so people do not route sensitive data through ungoverned tools. Keep it concrete — name the approved tools and the specific data rules. Adapt each section rather than adopting it verbatim; a policy that does not match how your teams work gets ignored. See the AI governance policy template for the reasoning behind each section.

Frequently asked questions

What should an AI governance policy include?
Purpose and scope, roles and accountability, an approved-tools catalog with an intake process, data-handling rules, human-oversight requirements, an AI inventory (AI-BOM), provenance and record-keeping, third-party diligence, prohibited uses, and a review-and-exceptions process. This generator produces all ten sections.
Is the generated policy legal advice?
No. It is a vendor-neutral starting outline to adapt to how your organization actually works. Have it reviewed by the people accountable for risk and, where needed, by counsel. Blank fields are left as explicit TODO prompts rather than invented for you.
How does it relate to ISO 42001 and the NIST AI RMF?
Both frameworks assume you can enumerate and manage your AI systems. The policy's inventory and provenance sections are what make those requirements achievable — you cannot govern a system you have not recorded. The outline is structured around that.
Is my input stored anywhere?
No. The policy is generated entirely in your browser as you type. Nothing is sent to a server; you copy or download the Markdown yourself.