Writing Your AI Policy
Use this worksheet to turn the four documents the first four steps produced into one section of the compliance manual the firm already keeps. It is the companion to Write the AI Policy, which explains why; this page is where you write it down.
What this measures
This worksheet gathers two things: the four documents you attach, and the five decisions the policy records. It produces no score — each decision has an answer and a document it points to.
The result is a policy section: a few dated pages inside the compliance program that say what the four documents mean for day-to-day conduct, and nothing the four documents do not support.
Before you start
Have the four documents in front of you, dated: the use-case list from Decide What AI Is For, the duty map from Map the Rules That Apply, the data matrix from Sort Your Data, and the tool approvals from Vet and Choose Tools. Build any you lack first.
Two ground rules:
- Point, do not retype. Every rule in the policy names where it comes from: one of the four documents, or the step page that already covers it. A rule that points nowhere comes out.
- Cover the assistant. If the use-case list names work an assistant does, the policy covers that person, and so does the acknowledgment below.
The documents you attach
Attach the four documents as dated appendices, in this order. Record the version you attached; each changes on its own trigger.
| Document | Which step produced it | What you record |
|---|---|---|
| Use-case list | Decide What AI Is For | The date, and which uses are approved |
| Duty map | Map the Rules That Apply | The date, and the duties per use |
| Data matrix | Sort Your Data | The date, and which cells say no |
| Approved tools | Vet and Choose Tools | Each tool, its use, any condition, the approver, the date, and its re-check trigger |
The fourth row is a list rather than one document: one line per approved tool, copied from the decision at the end of each Vetting a Vendor checklist. A tool approved on a condition is listed with its condition beside it. Its re-check trigger is the one the checklist set: a change in the tool’s terms, a new use proposed for it, or an interval the firm chose.
The decisions the policy records
Work through the five decisions in this order. Each names a document. Check each decision below against the duty map you attached: a provision that answers no duty the map names is one the four documents do not support.
- Where the policy lives. Name the section of the compliance manual it becomes, and who keeps that manual. Not a standalone AI policy.
- What the policy says. Four statements, each pointing back:
- Who may use which tools for which approved uses — by name, from the use-case list and the approved-tools list, not “AI” in general.
- What must never be entered into a general-purpose tool — from the data matrix.
- Who reviews AI-assisted output before it is used inside the firm or sent to anyone outside it — a named review point, with Handle Client-Facing Use linked rather than restated.
- Who can approve a new use or a new tool — the same person Vet and Choose Tools already named.
- When the policy is reviewed. Tie it to two dates the firm already has: the review in Review and Keep Records, and the re-check trigger set for each approved tool.
- How it is communicated and acknowledged. Everyone the policy covers, the assistant included, reads it and acknowledges that in writing, and the acknowledgments are kept with the policy.
- What happens when the policy is silent. The policy says, in its own words, that a use it does not address is not allowed until someone decides; it names who decides, and the approver in decision 2 is the reasonable default.
| Decision | Which document it points to | What a clear answer names |
|---|---|---|
| 1. Where it lives | The compliance manual itself | Section, and who keeps it |
| 2. What it says | Use-case list, data matrix, approved tools | A person or a document for each of the four statements |
| 3. When it is reviewed | Approved-tools list | Review and Keep Records, and each tool’s re-check trigger |
| 4. Acknowledgment | The policy itself | Each person, and the date they signed |
| 5. When it is silent | Approved-tools list | The person who decides |
Your policy section
The section is the five answers written as plain rules, followed by the four appendices. The example is a fictional two-person firm, Harbor Lane Advisory, adviser Sam Example and one assistant; its approved-tools list holds one tool, approved for summarizing meeting notes on the condition that the notes are de-identified first.
| Provision | What Harbor Lane wrote | Points to |
|---|---|---|
| Where it lives | Section 9 of the compliance manual, kept by Sam | The manual |
| Who may use what | Sam and the assistant, the one listed tool, for meeting summaries only and on its condition | Use-case list; approved tools |
| What never goes in | This tool’s two cells that say no: client-identifying only after de-identifying; restricted, never | Data matrix |
| Who reviews output | Sam, before a summary goes into a client file or to a client | Handle Client-Facing Use |
| Who approves new uses | Sam, by adding a line to the approved-tools list | Vet and Choose Tools |
| When it is reviewed | At the Review and Keep Records step, and whenever the tool’s re-check trigger fires | Approved tools |
| Acknowledgment | Both signed on the date the section was adopted | Signed acknowledgments |
| When it is silent | Not addressed means not allowed; Sam decides | Approved tools |
Each provision is one or two sentences. Date the section on the day it is adopted, and date each appendix separately.
What this worksheet does and does not tell you
It tells you whether every rule can be traced to something the firm decided. A provision with nothing in the “Points to” column is the finding.
It does not tell you whether the four documents are right; each has its own worksheet or step for that. It does not tell you whether the section satisfies your regulator, which turns on the rules the duty map already records for each use — your state’s requirements, or, for an SEC-registered adviser, the federal rules. And it says nothing about your fiduciary duty, which stays with the firm whatever the policy says.
What to do with it
Adopt the section into the manual, collect the acknowledgments, and keep the dated set together: the section, its four appendices, and the signatures. It is the kind of record a firm may be asked to show in an examination. Where the section or an acknowledgment is a record the firm has to keep, how long it keeps it is set by rule — see Records and Documentation in this year’s figures — and a state-registered adviser checks what its own state requires.
Update the section at the review in decision 3, and whenever one of its appendices changes: a new tool approved, a cell of the data matrix changed, or a use added to the list each mean a new dated version. Then carry the section into Build the Workflows, where each approved use gets its written procedure.
At a larger firm
At a larger firm the section already exists, written by compliance, and the adviser’s job is to find it and fit inside it. Use this worksheet to check that fit: for each of the five decisions, find where the firm’s manual answers it, and note where your own use-case list or data matrix is narrower than the firm’s rule. Do not draft provisions of your own; where the manual is silent on a use you want, that is a question for whoever approves tools at the firm.