Use this when a team wants to try an AI use case and needs clear accountability. Define who decides, who is affected, and what would make the pilot change or stop.
Prompt template
Help me draft an accountable pilot plan for [AI use case]. Purpose and people affected: [details]. Current process and proposed change: [details]. Data, tools, and actions: [confirmed details or unknown]. Available owners and reviewers: [roles]. Organize the plan around: Govern: ownership, policy, stakeholder involvement, and decision authority. Map: context, information flow, affected people, benefits, and possible harms. Measure: task-specific tests, quality criteria, failure cases, review workload, and cost. Manage: controls, escalation, incident response, fallback, and review dates. Separate assumptions from evidence. Identify which questions need technical, privacy, security, legal, or domain expertise. Define conditions to continue, change, restrict, or stop the pilot. Do not claim legal compliance, safety certification, or proven performance. Use the framework as a starting structure, not a substitute for applicable obligations. Boundary: Produce only a proposed pilot plan. Keep supplied facts, roles, and boundaries intact. Leave the current process, policy, data, and systems unchanged; list proposed changes separately. Don't authorize deployment.
Fill in this prompt in the builder
What to supply
- Purpose, affected people, and the current process.
- Confirmed data, tools, actions, and unresolved details.
- Owners and reviewers who can carry out the responsibilities.
Worked example
Illustrative example: the input and result below are invented.
Input
Daniel, 39, wants a pilot that drafts plain-language versions of approved class handouts. Learners can use the original. Daniel reviews every revision. No student records enter the tool, and nothing is distributed automatically.
Filled-in prompt
Show the complete prompt
Help me draft an accountable pilot plan for drafting plain-language versions of approved class handouts. Purpose and people affected: adult learners; make instructions easier to follow without changing their meaning. Current process and proposed change: Daniel currently edits by hand; proposed change is an assistant-generated draft reviewed by him. Data, tools, and actions: approved handouts only; tool and retention details unknown; no student records or automatic distribution. Available owners and reviewers: Daniel owns content review; a designated administrator must confirm account and retention settings. Organize the plan around: Govern: ownership, policy, stakeholder involvement, and decision authority. Map: context, information flow, affected people, benefits, and possible harms. Measure: task-specific tests, quality criteria, failure cases, review workload, and cost. Manage: controls, escalation, incident response, fallback, and review dates. Separate assumptions from evidence. Identify which questions need technical, privacy, security, legal, or domain expertise. Define conditions to continue, change, restrict, or stop the pilot. Do not claim legal compliance, safety certification, or proven performance. Use the framework as a starting structure, not a substitute for applicable obligations. Boundary: Produce only a proposed pilot plan. Keep supplied facts, roles, and boundaries intact. Leave the current process, policy, data, and systems unchanged; list proposed changes separately. Don't authorize deployment.
Result
Govern: Daniel owns content decisions. Confirm an administrator before selecting the tool. Map: Approved handout enters the assistant; a draft returns to Daniel. Learners keep access to the original. Measure: Compare each instruction, qualification, and prerequisite with the original; record review effort and unresolved wording. Manage: Keep distribution manual. Stop if the draft changes a material instruction, needs student data, or retention remains unresolved. Continue condition: Responsible owners agree that the drafts preserve meaning and the account settings fit the approved information. Unknowns: Tool choice, retention, and the administrator's role. No compliance or performance claim is made.
What I’d check or correct
I'd check that a content reviewer wasn't also assigned account-security responsibilities without agreement. The plan should preserve the original handout and keep distribution under Daniel's control.
What to check
- Owners have the authority and time to carry out their responsibilities.
- The result stays a proposed plan and leaves the current process, facts, and approved boundaries intact.
- Continue, change, and stop conditions follow from the actual use case and unresolved risks.
Related pages
- Build a task-specific evaluation plan
- Trace the benefits and harms
- Map a workflow before connecting apps
Sources
- AI RMF Playbook · NIST. Checked October 8, 2026.