Your AI Action Plan

Summarize this compliance-sensitive document for human review. Return: key facts, deadlines, obligations, missing information, ambiguous language, and questions for the responsible reviewer. Do not give legal, tax, or employment advice.

Document:
[PASTE]

Turn this policy or form instruction into a checklist. Include required fields, approvals, deadlines, evidence needed, common errors, and escalation triggers. Mark anything that needs a qualified human decision.

Text:
[PASTE]

Prepare a reviewer packet for this document. Return: 1. plain-English summary, 2. evidence table with source excerpts, 3. missing information, 4. risk questions, 5. reviewer decision log template. Keep all final decisions blank.

Document:
[PASTE]

Create a reusable compliance-review prompt for [ROLE]. It must require AI to: summarize only, cite source text, flag uncertainty, list missing information, avoid final legal/tax/employment decisions, and produce questions for the qualified reviewer.

Write a [TYPE - cold outreach / follow-up / proposal / status update] email.
From: [YOUR ROLE] at [COMPANY]
To: [RECIPIENT ROLE] at [THEIR COMPANY]
Context: [1-2 sentences of background]
Goal: [what you want them to do]
Tone: [professional / friendly / direct]
Length: [short = 3 sentences / medium = 1 short paragraph / full = structured email]

Write a weekly marketing performance report.
Period: [DATE RANGE]
Metrics to include: [list your KPIs]
Highlights: [what went well]
Issues: [what underperformed and brief reason]
Next week priorities: [3 bullet points]
Audience: [manager / team / client]
Tone: factual, no fluff. Use bullet points for metrics, short paragraphs for narrative.

Turn these rough notes into a clear [EMAIL / STATUS UPDATE / REPORT].
Audience: [WHO WILL READ IT]
Purpose: [DECISION, UPDATE, REQUEST, OR ESCALATION]
Raw notes:
[PASTE NOTES]

Return:
1. Suggested subject line
2. Short summary
3. Main message in my tone: [DIRECT / WARM / EXECUTIVE]
4. Action items with owners and dates
5. Risks or open questions

I'll share 3 examples of emails I've written. After reading them, identify:
1. My typical sentence length and structure
2. Words or phrases I use often
3. My tone (formal / casual / direct / warm)
4. Things I never say

[PASTE EMAIL 1]
[PASTE EMAIL 2]
[PASTE EMAIL 3]

Now write a [TYPE] email using my style. Here's the context: [CONTEXT]

Turn these rough process notes into a simple SOP. Include: purpose, when to use it, required inputs, step-by-step workflow, owner, tools, quality checks, and common mistakes.

Notes:
[PASTE]

Create a reusable checklist for [PROCESS]. Include sections for intake, execution, quality check, handoff, escalation, and completion evidence. Format it so I can paste it into Notion.

Convert this process explanation into: 1. SOP, 2. quick checklist, 3. training note for a new person, 4. edge cases, 5. questions to confirm with the process owner.

Transcript or notes:
[PASTE]

Design a procedure-library template for [TEAM]. Include fields for owner, last reviewed, inputs, steps, tools, examples, risks, escalation path, related templates, and update log. Add rules for when a procedure must be reviewed.

Summarize this meeting.
Notes or transcript: [PASTE]
Return: 1. short summary, 2. decisions made, 3. action items with owner and due date, 4. risks, 5. follow-up message draft.

Review this meeting transcript and create a follow-up note. Separate exact decisions from discussion points. Flag anything unclear. Transcript: [PASTE TRANSCRIPT].

Convert this meeting transcript into project tasks. For each task include owner, due date, dependency, priority, and a follow-up email paragraph. Transcript: [PASTE].

Create a meeting memory template for [TEAM / CLIENT]. For each meeting, capture decisions, action items, repeated themes, unresolved questions, stakeholder commitments, and items to revisit next time.

Clean this data before I enter it into [SYSTEM]. Return a table with columns: [COLUMNS]. Standardize dates, names, categories, and phone/email formatting. Add a final column called Review needed for anything uncertain. Do not invent missing values.

Raw data:
[PASTE]

Map this incoming form to my database fields. Required destination fields: [FIELDS]. Validation rules: [RULES]. Return a field mapping, transformations needed, and exception cases that should stop for human review.

Extract records from this input and prepare them for [SYSTEM]. Return: 1. clean records table, 2. duplicate warnings, 3. missing required fields, 4. values that need human review, 5. a short change log.

Input:
[PASTE]

Create a data-entry QA playbook for [PROCESS]. Include: required fields, allowed formats, duplicate checks, sensitive-data warnings, examples of good records, examples of records to reject, and a final human review checklist.

Create a neutral employee-relations chronology.
Notes: [PASTE DE-IDENTIFIED NOTES]
Return: timeline, people involved, source evidence, missing facts, policy sections to verify, and questions for HR/legal review. Do not assign blame or recommend discipline.

Summarize this HR policy for case review. Return: obligations, required steps, deadlines, documentation requirements, escalation triggers, and areas that require HR/legal interpretation.

Policy:
[PASTE OR REFERENCE APPROVED POLICY]

Prepare an employee-relations reviewer packet.
Case notes: [PASTE DE-IDENTIFIED NOTES]
Policy summary: [PASTE]
Return: neutral timeline, evidence table, policy questions, missing information, confidentiality reminders, and reviewer decision log with conclusions left blank.

Create an employee-relations AI guardrail prompt for HR. It must require: de-identification, fact/opinion separation, source citations, missing evidence flags, no legal conclusions, no discipline recommendations, and HR/legal review before action.

Create a manager brief for this HR policy update.
Policy text: [PASTE]
Return: what changed, who is affected, manager actions, employee questions to expect, risks, and items requiring legal/HR confirmation.

Draft a policy update memo using these approved source files: [LIST FILES]. Include: summary, reason for change, manager actions, employee FAQ, effective date, and review reminders.

Create a policy rollout packet.
Policy change: [PASTE]
Audience: [MANAGERS / EMPLOYEES]
Return: manager memo, employee FAQ, talking points, risk questions, acknowledgement workflow, and review checklist.

Design a policy-change operating system for HR. Include: intake fields, owner, legal/compliance review, affected groups, communication plan, acknowledgement tracking, escalation rules, and next review date.

Create a 30-60-90 day onboarding plan for [ROLE]. Include: goals, meetings, required training, policy acknowledgements, manager check-ins, success measures, and questions to verify with HR.

Create an onboarding checklist from these materials: [LIST FILES OR PASTE SUMMARIES]. Include owner, due date, required system, completion evidence, and manager follow-up.

Create an onboarding packet for [ROLE / DEPARTMENT]. Return: orientation agenda, 30-60-90 plan, manager guide, employee FAQ, policy acknowledgement checklist, and handoff notes.

Design an onboarding content library by role family. Include: core company modules, role-specific modules, manager tasks, employee milestones, compliance checks, feedback surveys, and quarterly refresh rules.

Draft HR metrics commentary from this de-identified table.
Data: [PASTE]
Return: key changes, possible drivers, caveats, questions to verify, and leadership summary. Do not infer protected-class causes or individual performance.

Analyze this HR metrics table for trends and outliers. Flag changes in turnover, hiring funnel, training completion, case volume, and time-to-close. Return only de-identified insights and questions to verify.

Create an HR metrics review packet.
De-identified data: [PASTE]
Business context: [PASTE]
Return: metric summary, trend table, risks, caveats, follow-up questions, and 6-slide leadership outline.

Create an HR analytics governance checklist. Include: allowed data, prohibited data, de-identification rules, protected-class caution, review owners, reporting templates, and escalation triggers.

Draft a manager talk track for [SITUATION].
Context: [PASTE DE-IDENTIFIED CONTEXT]
Return: opening, questions to ask, phrases to avoid, documentation reminders, escalation triggers, and HR review notes. Do not recommend discipline or legal conclusions.

Create a manager prep checklist for this sensitive HR conversation.
Context: [PASTE]
Policy: [PASTE]
Return: facts to verify, questions to ask, language to avoid, documentation steps, follow-up plan, and when to involve HR/legal.

Create a sensitive-conversation support packet.
Policy summary: [PASTE]
Situation: [PASTE]
Return: manager talk track, employee questions to expect, follow-up note draft, documentation checklist, and HR review checklist.

Create a sensitive-conversation playbook library for managers. Include: conversation types, required HR review, talk-track patterns, documentation rules, prohibited language, escalation triggers, and training refresh cadence.