Plain-language summary
What this guide covers
A playbook is a repeatable workflow. It includes the goal, audience, inputs, preparation, steps, human checkpoints, risks, success criteria, and conditions where AI should not be used. These playbooks are designed for low-to-moderate-risk learning and work tasks, not emergencies or high-stakes decisions.
Many AI mistakes happen when a user starts with a blank prompt and no review plan. A playbook slows the task just enough to protect privacy, improve quality, and keep human responsibility clear.
What you will learn
- Choose the right playbook for a low-to-moderate-risk task.
- Prepare safe inputs before prompting.
- Use human checkpoints and success criteria.
- Recognize when a playbook should not be used.
- Adapt templates without adding sensitive data.
Guide section
How to use these playbooks
Each playbook turns a common task into a safer sequence.
These playbooks are for tasks where AI can help draft, organize, summarize, or plan, while a person keeps responsibility. They do not replace expert review, official policy, school rules, workplace approval, or emergency channels. Use public, fictional, or approved information. When a task involves sensitive data, high stakes, rights, safety, health, money, legal duties, children, or confidential work, stop and escalate.
| Need | Use this playbook | Good fit | Avoid when |
|---|---|---|---|
| Understand a topic quickly | Research briefing | Public sources and a clear question. | You need legal, medical, tax, financial, or emergency advice. |
| Turn notes into next steps | Meeting follow-up | Low-risk notes and human approval. | The meeting includes confidential, personnel, legal, medical, or security matters. |
| Learn a skill | Learning plan | Public learning goals and safe practice tasks. | A credential, license, diagnosis, legal deadline, or expensive decision is involved. |
| Improve a small workflow | Small-business workflow review | A low-risk internal process. | The process affects safety, employment, credit, benefits, or regulated data. |
| Plan job-search evidence | Job-search skill inventory | Non-sensitive experience summaries and public postings. | The user wants fabricated experience or hidden keyword stuffing. |
Guide section
Playbook 1: Research briefing
Use this when you need a short, source-aware briefing on a public topic.
Playbook
Research briefing
Goal: Create a short briefing that separates facts, uncertainty, and next questions.
Audience: Students, workers, managers, lifelong learners, and small teams researching public topics.
Inputs: A public question, 2 to 5 trusted source links or excerpts, audience, desired length, and decision context. Do not include private records.
Preparation: Write the question in one sentence. Gather direct sources before asking AI to summarize. Decide what claims need verification.
Human checkpoints: Check all dates, names, numbers, legal or policy claims, quotes, and source relevance. A person decides what to use.
Risks: Fake citations, outdated facts, one-sided sources, missing caveats, and overconfident conclusions.
Success criteria: The briefing names what is known, what is uncertain, what sources support the summary, and what still needs checking.
Reusable template: Create a briefing on [question] for [audience]. Use only the source notes I provide. Separate summary, key facts, uncertainty, opposing evidence, and next questions. Do not invent sources. List claims I should verify.
Do not use when: The question needs professional legal, medical, tax, financial, safety, or emergency advice; the sources contain private data; or the decision is high stakes.
- State the research question and audience.
- Collect direct trusted sources before prompting.
- Remove private or sensitive information.
- Ask AI for a structured draft using only provided sources.
- Check every factual claim against the sources.
- Add caveats and unanswered questions.
- Decide whether the briefing is safe to share.
Guide section
Playbook 2: Meeting follow-up
Use this to turn low-risk notes into action items after human review.
Playbook
Meeting follow-up
Goal: Produce a clear follow-up note with decisions, action items, owners, dates, and open questions.
Audience: Team members, volunteers, students, project groups, or small-business staff.
Inputs: Low-risk notes, meeting purpose, attendee roles, known decisions, and deadlines. Use fictional notes for practice.
Preparation: Confirm the notes do not include confidential personnel, legal, financial, medical, security, or customer-sensitive information. Decide who approves the final follow-up.
Human checkpoints: Verify attendees, decisions, commitments, deadlines, sensitive details, and tone before sending.
Risks: Invented action items, wrong owners, false deadlines, exposure of private content, or a tone that sounds final before decisions are approved.
Success criteria: People can tell what was decided, who owns each task, when it is due, and what still needs discussion.
Reusable template: Turn these safe meeting notes into a draft follow-up. Include decisions, action items, owners, due dates, open questions, and items needing confirmation. Do not invent commitments. Mark anything uncertain.
Do not use when: The meeting involves HR, discipline, legal advice, medical details, confidential finance, security incidents, layoffs, children, investigations, or sensitive customer records.
- Confirm the notes are safe for the tool.
- State meeting purpose and audience.
- Ask for decisions, action items, owners, dates, and open questions.
- Review uncertain or missing items.
- Remove sensitive details not needed for the follow-up.
- Have the meeting owner approve the final version.
- Send only after a person confirms commitments.
Guide section
Playbook 3: Learning plan
Use this to create a safe, practical learning plan for a skill.
Playbook
Learning plan
Goal: Build a 30-day learning plan with practice, evidence, reflection, and safety checks.
Audience: Beginners, students, workers, retirees, job seekers, and lifelong learners.
Inputs: Skill goal, current level, weekly time range, preferred learning style, public resources, and safe practice topics.
Preparation: Keep the goal narrow. Use public or fictional information. Check school, workplace, or program rules if the plan affects assignments or employment.
Human checkpoints: Review whether the plan is realistic, accessible, and safe. Ask a teacher, mentor, peer, or supervisor for feedback when possible.
Risks: Overly broad goals, unsafe data use, unrealistic time demands, skipped practice, and relying on AI instead of learning.
Success criteria: The plan has weekly tasks, one artifact, reflection questions, and a review date.
Reusable template: Create a 30-day learning plan for [skill] for a [beginner/intermediate] learner with [hours per week]. Include weekly goals, practice tasks using public information, one evidence artifact, reflection questions, and safety checks. Do not promise outcomes.
Do not use when: The plan involves diagnosis, therapy, legal deadlines, professional licensing decisions, medical treatment, financial commitments, or urgent safety needs without qualified guidance.
- Define one skill and one reason for learning it.
- Set a realistic weekly time range.
- Choose public or fictional practice material.
- Ask AI to draft a plan with weekly practice and one artifact.
- Check the plan for safety, access, and realism.
- Complete the first practice task.
- Reflect and adjust after two weeks.
Guide section
Playbook 4: Small-business workflow review
Use this to review a low-risk workflow before adding AI.
Playbook
Small-business workflow review
Goal: Map a small workflow and find safe places where AI might assist, not blindly automate.
Audience: Small-business owners, managers, team leads, freelancers, and nonprofit staff.
Inputs: A low-risk workflow name, steps, roles, handoffs, public or fictional examples, and current pain points.
Preparation: Do not include customer lists, payment data, employee records, contracts, tax records, medical information, passwords, or private messages. Start with a workflow that can be improved without high-stakes decisions.
Human checkpoints: Review privacy, policy, customer promises, accessibility, bias, and the final decision owner.
Risks: Automating a broken process, exposing customer data, inventing policies, reducing service quality, or removing human escalation.
Success criteria: The output includes a workflow map, bottlenecks, risks, human checkpoints, success measures, and a clear decision about whether to test AI.
Reusable template: Review this low-risk workflow: [workflow]. Steps are [steps]. Pain points are [pain points]. Suggest where AI might assist, where human review is needed, what data must stay out, what risks to watch, and how to measure success. Do not recommend full automation unless risk is low and review is clear.
Do not use when: The workflow affects hiring, firing, credit, housing, health, safety, legal rights, taxes, regulated records, children, employee discipline, or confidential customer decisions.
- Name the workflow and outcome.
- List steps, owners, handoffs, and decisions.
- Mark sensitive data and high-stakes points.
- Ask AI to identify bottlenecks and possible assistive uses.
- Screen each suggestion for privacy, error, bias, and accountability.
- Choose one low-risk test or decide not to use AI.
- Measure quality, time, trust, and errors after any test.
Guide section
Playbook 5: Job-search skill inventory
Use this to organize real skills and evidence without fabricating experience.
Playbook
Job-search skill inventory
Goal: Turn real experience into a truthful skill inventory for resumes, interviews, or learning plans.
Audience: Job seekers, students, career changers, entry-level workers, and employed learners.
Inputs: Non-sensitive summary of experience, target role, public job posting language, and examples you can explain honestly.
Preparation: Remove private employer, customer, student, patient, coworker, salary, ID, and reference information. Use a role summary rather than a full personal history.
Human checkpoints: Check that every skill, tool, credential, result, and project is real and explainable. Remove unsupported metrics and hidden keywords.
Risks: Inflated expertise, fake projects, copied posting language, private data exposure, and AI-written bullets the applicant cannot defend.
Success criteria: The inventory lists real tasks, tools, review steps, outcomes, evidence artifacts, and gaps to learn next.
Reusable template: Using this safe summary of my experience and this target role, help me organize a truthful skill inventory. Separate proven skills, developing skills, examples I can explain, evidence artifacts, and gaps. Do not invent experience, metrics, tools, credentials, employers, or outcomes.
Do not use when: The user wants fake experience, hidden keyword stuffing, false credentials, misleading references, or unauthorized use of confidential work samples.
- Write a safe summary of your real experience.
- Add the target role or public posting summary.
- Ask AI to group skills, examples, evidence, and gaps.
- Check every item for truth and explainability.
- Remove unsupported claims and private details.
- Choose two skills to strengthen.
- Use the inventory to guide resume, interview, or learning-plan work.
Avoidable errors
Common mistakes and better approaches
Using a playbook with sensitive data.
Better approach: Practice with public, fictional, de-identified, or approved information.
Skipping human checkpoints.
Better approach: Check facts, privacy, fairness, and commitments before using output.
Treating a playbook as professional advice.
Better approach: Use playbooks for educational support and escalate high-stakes decisions.
Using the same workflow for every task.
Better approach: Choose the playbook that matches the risk and purpose.
Remember this
Key takeaways
- A playbook is a repeatable safety-aware workflow.
- Good inputs matter as much as good prompts.
- Human checkpoints should be named before prompting.
- Every playbook has conditions where it should not be used.
- Templates must be adapted without adding sensitive data.
- Success criteria help users decide whether the output is usable.
- Playbooks are for support, not emergencies or professional decisions.
Questions readers ask
Frequently asked questions
Can I use these playbooks at work?
Only if your workplace rules allow the tool and the type of information involved. Do not use confidential data in unapproved tools.
Can a playbook make AI output accurate?
No. A playbook improves process, but users still need source checking, human review, and escalation for risky cases.
What should I do if my task does not fit a playbook?
Use the safety framework first. If the task is sensitive, high-stakes, unclear, or urgent, do not force it into a playbook. Escalate to the proper human process.
Can students use the learning plan playbook?
Yes, if school rules allow it and the use supports learning rather than hidden completion of required work. Do not include private student data.
Sources and review notes
Sources were accessed on the dates shown. Links open the original organization’s page.
- SRC-01Artificial Intelligence Risk Management FrameworkNational Institute of Standards and Technology · Published 2023-01-26 · Accessed 2026-06-20
- SRC-02Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence ProfileNational Institute of Standards and Technology · Published 2024-07-26 · Accessed 2026-06-20
- SRC-04Artificial IntelligenceCybersecurity and Infrastructure Security Agency · Accessed 2026-06-20
- SRC-05Privacy and SecurityFederal Trade Commission · Accessed 2026-06-20
- SRC-08Artificial intelligence in educationUNESCO · Accessed 2026-06-20
- SRC-13Prompt engineering techniquesMicrosoft Learn · Published 2026-05-13 · Accessed 2026-06-20
- SRC-14Prompt engineeringOpenAI · Accessed 2026-06-20