Writing the AI Handoff Brief

Use an outcome-first structure. Give ChatGPT the role, goal, approved source notes, constraints, and exact output you want back.

I am using Build The System for L&D systems work.

Prompt: Writing the AI Handoff Brief

Goal: Create a reusable brief for an AI-supported workflow step with source, constraints, and review gate.

Audience: L&D practitioners moving from casual prompting to governed AI workflow support.

Source material I will provide:
- Workflow step
- Approved source material
- Output needed
- What AI must not do
- Human review gate

Inputs to use: [workflow step], [source material], [output needed], [constraints], [review owner]

Working notes:
- workflow step: [add workflow step]
- source material: [add source material]
- output needed: [add output needed]
- constraints: [add constraints]
- review owner: [add review owner]

Rules:
- Use only approved source material.
- Do not invent policy, compliance, learner, employee, customer, financial, or business facts.
- Do not paste sensitive, confidential, employee, learner, customer, or proprietary data into an AI tool unless your organization has approved that tool for that data.
- Treat AI output as a draft that needs human review.

Return:
1. AI handoff brief
2. Opening prompt
3. Human review gate
4. Risks or assumptions to check

Human review checklist:
- Does the output stay inside the source material?
- Are assumptions and missing information labeled?
- Is there a clear human owner for the final decision?
- Does the output need legal, compliance, privacy, accessibility, leader, requester, or SME review?

Use labeled sections so context, source material, task, constraints, and output format stay separate.

<context>
I am using Build The System for L&D systems work.
Prompt: Writing the AI Handoff Brief
Use case: Create a reusable brief for an AI-supported workflow step with source, constraints, and review gate.
Audience: L&D practitioners moving from casual prompting to governed AI workflow support.
</context>

<source_material_to_prepare>
- Workflow step
- Approved source material
- Output needed
- What AI must not do
- Human review gate
</source_material_to_prepare>

<inputs>
- workflow step: [add workflow step]
- source material: [add source material]
- output needed: [add output needed]
- constraints: [add constraints]
- review owner: [add review owner]
</inputs>

<task>
Use the source material and inputs to produce a practical, review-ready output for this L&D workflow. Stay inside the source material. If a detail is missing, mark it as "Needs confirmation" instead of inventing it.
</task>

<constraints>
- Use only approved source material.
- Do not invent policy, compliance, learner, employee, customer, financial, or business facts.
- Do not paste sensitive, confidential, employee, learner, customer, or proprietary data into an AI tool unless your organization has approved that tool for that data.
- Treat AI output as a draft that needs human review.
</constraints>

<output_format>
1. AI handoff brief
2. Opening prompt
3. Human review gate
4. Risks or assumptions to check
</output_format>

<human_review>
- Does the output stay inside the source material?
- Are assumptions and missing information labeled?
- Is there a clear human owner for the final decision?
- Does the output need legal, compliance, privacy, accessibility, leader, requester, or SME review?
</human_review>

Use goal, source, expectations, and output. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.

Goal: Help me complete Writing the AI Handoff Brief for an L&D workflow.

Source: Use only the selected Microsoft 365 document, meeting notes, email thread, spreadsheet, SharePoint file, or pasted notes I provide. Do not use unsupported assumptions.

Context:
- Use case: Create a reusable brief for an AI-supported workflow step with source, constraints, and review gate.
- Audience: L&D practitioners moving from casual prompting to governed AI workflow support.
- Source material to have ready:
- Workflow step
- Approved source material
- Output needed
- What AI must not do
- Human review gate

Inputs:
- workflow step: [add workflow step]
- source material: [add source material]
- output needed: [add output needed]
- constraints: [add constraints]
- review owner: [add review owner]

Expectations:
- Use only approved source material.
- Do not invent policy, compliance, learner, employee, customer, financial, or business facts.
- Do not paste sensitive, confidential, employee, learner, customer, or proprietary data into an AI tool unless your organization has approved that tool for that data.
- Treat AI output as a draft that needs human review.

Output:
1. AI handoff brief
2. Opening prompt
3. Human review gate
4. Risks or assumptions to check

Before finalizing, add a short "Needs human review" section covering:
- Does the output stay inside the source material?
- Are assumptions and missing information labeled?
- Is there a clear human owner for the final decision?
- Does the output need legal, compliance, privacy, accessibility, leader, requester, or SME review?

Use a task-first structure with clear input labels, one example pattern, rules, and a concise output format. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM source sets.

Task: Complete Writing the AI Handoff Brief for an L&D workflow.

Use case:
Create a reusable brief for an AI-supported workflow step with source, constraints, and review gate.

Audience:
L&D practitioners moving from casual prompting to governed AI workflow support.

Input labels to use:
- workflow step: [add workflow step]
- source material: [add source material]
- output needed: [add output needed]
- constraints: [add constraints]
- review owner: [add review owner]

Source material to prepare:
- Workflow step
- Approved source material
- Output needed
- What AI must not do
- Human review gate

Example pattern:
Field: Missing information
Good answer: Name the specific detail to confirm, who can confirm it, and why it affects the next decision.

Rules:
- Use only approved source material.
- Do not invent policy, compliance, learner, employee, customer, financial, or business facts.
- Do not paste sensitive, confidential, employee, learner, customer, or proprietary data into an AI tool unless your organization has approved that tool for that data.
- Treat AI output as a draft that needs human review.

Return:
1. AI handoff brief
2. Opening prompt
3. Human review gate
4. Risks or assumptions to check

Human review checklist:
- Does the output stay inside the source material?
- Are assumptions and missing information labeled?
- Is there a clear human owner for the final decision?
- Does the output need legal, compliance, privacy, accessibility, leader, requester, or SME review?