Your AI Action Plan

Draft a billing message using these account notes. Include: what happened, amount/date if provided, what the customer should do next, and what I must verify before sending. Do not invent charges or promise refunds.

Notes:
[PASTE]

Review this billing or payment list and create an exception summary. Flag duplicates, missing amounts, mismatched dates, unclear customer names, and items that need approval. Do not approve or process payments.

Data:
[PASTE]

Create a billing review packet from this data. Return: summary, items ready for approval, items blocked, customer-facing explanation draft, and audit notes. Keep the final action field blank for a human approver.

Data:
[PASTE]

Create billing automation guardrails for [ROLE/TEAM]. Include: AI-allowed tasks, human-only decisions, approval thresholds, customer communication rules, exception examples, and audit-log requirements.

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.

Write a scheduling email for [MEETING PURPOSE].
Participants: [WHO]
Time options: [OPTIONS]
Duration: [LENGTH]
Prep needed: [PREP]
Tone: [FRIENDLY / DIRECT / FORMAL]
Include a 3-bullet agenda and a clear reply request.

Write a short message that shares my booking link and explains the purpose of the meeting.
Booking link: [LINK]
Purpose: [PURPOSE]
Who should attend: [ROLES]
What to prepare: [PREP]
Keep it under 120 words.

Create intake questions for a [MEETING TYPE] booking page. Then write a prep brief template that summarizes the answers into: context, goal, risks, decisions needed, and agenda.

Build a meeting routing playbook for [TEAM / ROLE]. Include: meeting types, when to book vs handle async, required attendees, intake questions, agenda templates, prep checklist, and follow-up owner.

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]

Write a weekly [TEAM / CLIENT / PROJECT] report.
Period: [DATE RANGE]
Metrics: [PASTE METRICS]
Highlights: [WHAT WENT WELL]
Risks or blockers: [WHAT NEEDS ATTENTION]
Next actions: [3-5 BULLETS]
Audience: [MANAGER / CLIENT / TEAM]. Keep it factual, concise, and easy to scan.

Analyze this report data before drafting the summary.
Data: [PASTE TABLE OR METRICS]
Return: 1. Top 5 changes, 2. likely explanations, 3. questions to verify, 4. what should be highlighted, 5. what should not be overclaimed.

Turn this exported data into a decision memo.
Audience: [WHO WILL READ IT]
Data: [PASTE CSV OR TABLE]
Return: executive summary, key changes, likely causes, recommended action, risks, and a short appendix explaining assumptions.

Create a reusable monthly review template for [ROLE / TEAM]. It should include: required inputs, KPI table, variance analysis, stakeholder narrative, recommended actions, risks, and a quality checklist before sending.

Review this flagged invoice or expense report.
Item: [PASTE INVOICE / EXPENSE]
Office policy excerpts: [PASTE POLICY]
Return: plain-language summary, which rule is in question, what I still need to verify, who should approve (me / finance / owner), and a suggested reply to the submitter.

Triage this week of invoices and expense reports.
Data: [PASTE EXPORT]
Return: clean-to-approve list, needs-review list with reason per item (duplicate, over policy, missing receipt, unusual vendor, timing mismatch), and any item that must go to finance or the owner before I approve.

Build an invoice and expense exception queue.
Data: [PASTE EXPORT]
Return: exception reason, recommended action (approve / request clarification / deny / escalate), who to route to, customer or vendor message draft, and an approval-log line I can paste into our tracker. Leave the final decision field blank for me.

Build an expense-and-invoice approval playbook for [COMPANY]. Include: policy categories, approval thresholds by role, required evidence (receipts, POs, sign-offs), exception handling, vendor-specific rules, monthly audit checklist, and a communication template for declined items.

Update this SOP to reflect a small change.
Old SOP: [PASTE]
What changed: [DESCRIBE]
Return: updated SOP with tracked changes, a one-line changelog entry, a list of who I should notify, and any step that got more complex and may need manager review.

Audit this SOP pack against recent operational notes.
SOPs: [PASTE]
Recent notes or tickets: [PASTE]
Return: SOPs that match reality, SOPs that drift from reality (with evidence), missing SOPs I should add, and a priority order for updates.

A change has landed. Produce the full documentation update.
Change: [DESCRIBE]
Affected SOPs: [PASTE]
Return: updated SOP(s), changelog line with date and owner, staff announcement email, FAQ with 5 likely questions, and a rollout checklist with dates.

Design a quarterly SOP refresh system for [COMPANY]. Include: SOP inventory, owner per SOP, freshness criteria, input sources (tickets, Slack, interviews), review checklist, retirement rules, and a manager sign-off log.

Summarize this vendor contract for renewal review.
Contract: [PASTE]
Return: vendor, product, pricing, term length, auto-renewal clause with notice period, termination rights, service levels, and the 3 clauses I should re-read before signing. Do not invent terms that are not in the text.

Here is our vendor list with current spend and renewal dates.
Data: [PASTE]
Return: 12-month renewal calendar sorted by date, leverage per vendor (usage, alternatives, renewal clock), 3 negotiation asks per vendor, and any vendor I should replace rather than renew.

Prepare a renegotiation memo.
Usage data: [PASTE]
Current contract: [PASTE]
Return: what we actually use vs. what we pay for, realistic target pricing, 3 asks with justification, walk-away terms, a draft email to the vendor rep, and what I must confirm with finance before sending.

Design a vendor management playbook for [COMPANY]. Include: vendor inventory schema, renewal-prep triggers by contract value, negotiation checklist per tier, legal review triggers, approval thresholds, and a quarterly vendor-health review.

Narrate this KPI snapshot.
Data: [PASTE METRICS]
Return: 3-sentence summary, what changed vs last period, likely drivers, and one open question for leadership. Keep numbers exactly as given — do not estimate.

Here are the last 8 weeks of office KPIs.
Data: [PASTE]
Return: top 5 variances (by absolute change), likely internal vs external causes, evidence from the data, follow-up questions I should ask the team, and a flag if any variance looks like a data issue rather than a real change.

Build this week's KPI pack for leadership.
Data: [PASTE EXPORT]
Return: headline numbers, week-over-week and 4-week trend, variance explanations, risks to flag, 1 decision needed from leadership, and a short one-line summary I can paste into a group chat. Keep all numbers exactly as given.

Design an office KPI scorecard for [COMPANY]. Include: 6-10 KPIs with definitions, data sources, target + threshold bands, escalation rules per band, reporting cadence, owner per metric, and a quarterly review checklist.

Draft a Day-1 onboarding checklist for a new [ROLE].
Tools they need: [LIST]
People they should meet: [LIST]
Required forms: [LIST]
Return: timed schedule for Day 1, materials to send the night before, access requests I need to file, and a short welcome message I can send personally.

Build a 30/60/90 plan from this job description.
JD: [PASTE]
Team context: [PASTE]
Return: 30-day goals, 60-day goals, 90-day goals, weekly check-in questions, risks to watch, and a list of what the new hire needs from the manager in each phase.

Build an onboarding queue from this upcoming-hires list.
Data: [PASTE]
Return: per new hire — start date, access list, forms, buddy assignment, training modules with deadlines, Day-1 agenda, 30-day checkpoint, and who owns each step. Keep names exactly as given.

Create a living onboarding playbook for [COMPANY]. Include: role-agnostic core modules, role-specific add-ons, pre-boarding, Day-1, Week-1, 30/60/90, buddy-program rules, a 30-day feedback survey, and a quarterly review cadence that edits the playbook based on feedback themes.