When to use this log
Use it for any prompt that more than one person uses, any prompt that touches customers, or any workflow where a worse draft could create support, privacy, pricing, legal, or trust risk. This is not software version control; it is a copy/paste operating log for owners and managers.
Copy/paste prompt version log
| Field | What to write |
|---|---|
| Prompt name | Example: Review response draft prompt, Estimate follow-up prompt, Intake summary prompt. |
| Current version | Use a simple number: v1.0, v1.1, v2.0. |
| Owner | One person responsible for edits and rollback decisions. |
| Approved use | What the prompt may draft. Be specific. |
| Forbidden use | Customer promises, prices, diagnosis, legal/HR/financial advice, private data, or anything requiring owner approval. |
| Change made | Describe exactly what changed in the wording, variables, source facts, tone rules, or stop rules. |
| Why changed | Customer confusion, stale policy, lower quality drafts, new service, compliance review, speed improvement, or repeated edit pattern. |
| Test sample | Paste the test input used to compare old vs new prompt. |
| Old output issue | What was wrong, risky, too vague, or too slow to edit. |
| New output check | What improved and what still needs human review. |
| Approved by | Owner/manager initials and date. |
| Rollback note | Where the prior version is stored and what would trigger a rollback. |
Three-minute change review
- Compare one real input. Run the old and new prompt against the same safe sample.
- Check fact control. Does the new version ask the AI to use supplied facts only?
- Check tone drift. Does it still sound like your business, not a generic AI assistant?
- Check stop rules. Does it refuse to invent pricing, promises, diagnosis, policy, legal terms, or unavailable scheduling windows?
- Check editing effort. Does the new draft require less cleanup than the old version?
- Write the rollback trigger. Example: rollback if two reviewed outputs invent facts or miss required disclaimers.
Copy/paste AI prompt for reviewing a prompt change
You are helping me review a changed AI prompt for a small business workflow.
Do not invent policies, prices, legal terms, guarantees, availability, or customer promises.
Prompt name: [NAME]
Approved use: [WHAT THIS PROMPT MAY DRAFT]
Forbidden use: [WHAT IT MUST NOT DO]
Old prompt: [PASTE OLD PROMPT]
New prompt: [PASTE NEW PROMPT]
Test input: [PASTE SAFE SAMPLE INPUT]
Compare the old and new prompt. Return:
1. What changed in plain English.
2. Whether the new prompt has stronger fact-control rules.
3. Whether the new prompt still needs a human-review step before customer use.
4. Any missing stop rules.
5. A rollback trigger if the new prompt performs worse.
6. A one-paragraph owner approval note.Human-review rule
Human-review rule: no prompt change is approved just because the AI says it is better. A real owner or manager must compare at least one realistic sample, confirm forbidden uses, and store the prior version before the new prompt is shared with the team.
Do not let AI invent the change history
Do not invent: If you do not know why a prompt changed, who approved it, or whether the output was tested, write “unknown” and review before use. Do not let AI reconstruct missing approvals, policies, compliance claims, customer promises, or old prompt versions from memory.
Where this fits
Pair this version log with the free AI prompt governance checklist. For a fuller owner-friendly system of prompts, worksheets, rollout steps, and review rules, see The Small Business AI Profit Kit.