Operations Prompts to Communicate More Effectively

You are a controller drafting the end-of-day close status update. Status data: [PASTE: Current date | Day of close | Tasks completed today | Tasks remaining | Any blockers | Preliminary revenue and expense figures if available] Write a close status email covering: 1) Where we are vs. plan (on track / 1 day behind / at risk) 2) What got completed today 3) What's remaining and who owns it 4) Any blockers requiring CFO decision or escalation 5) Key financial highlights (preliminary figures) — flag as unaudited/preliminary Tone: Concise, factual, no fluff. CFO should be able to read this in 60 seconds. Format: Short email, max 15 lines. Bold key numbers and action items.

You are an AR manager preparing the monthly AR aging review. AR aging data: [PASTE: Customer | Total outstanding | Current | 1-30 days | 31-60 days | 61-90 days | 90+ days | Credit limit] Produce: 1) Aging summary — total AR by bucket, % of total, change vs. prior month 2) Top 10 customers by outstanding balance — flag any over credit limit or 60+ days overdue 3) DSO calculation — days sales outstanding vs. prior month and prior year 4) High-risk accounts — customers with balances 90+ days with no recent payment activity 5) Recommended write-offs — accounts where collection is unlikely; include estimated bad debt reserve impact Output: AR aging report for CFO/credit committee. End with 3 recommended collection actions this week.

You are an AR specialist drafting customer collection communications. Account data: [PASTE: Customer name | Outstanding amount | Invoice numbers | Due dates | Days past due | Previous contact attempts (dates and outcomes)] Write a collection email for each stage: - Stage 1 (1–15 days past due): Friendly reminder, assume oversight - Stage 2 (16–30 days past due): Follow-up, request confirmation of payment date - Stage 3 (31–60 days past due): Formal notice, reference specific invoices, request immediate payment or payment plan - Stage 4 (60+ days past due): Final notice before escalation to collections or legal For each email: keep it professional, specific to the invoice amounts and dates, leave a clear next step. Tone: Firm but professional. Preserve the customer relationship through Stage 2.

You are an AR manager preparing for a customer account review meeting. Customer data: [PASTE: Customer name | Credit limit | Current outstanding | Aging detail | Payment history (last 12 months avg days to pay) | Open orders | Any disputes | Account manager name] Summarize: 1) Account health overview — balance, utilization of credit limit, payment performance 2) Risk flags — anything that has changed in the last 90 days (slower payment, higher balance, disputes) 3) Trend — better, worse, or stable vs. 6 months ago 4) Open orders — what's in the pipeline and the credit exposure it creates 5) Recommended action: maintain current terms / reduce limit / require prepayment on new orders / release hold Output: One-page account review brief. Suitable for account manager + credit manager meeting.

You are an FP&A analyst drafting the monthly variance commentary for the board report. Variance data: [PASTE: KPI or P&L line | Budget | Actual | Variance $ | Variance %] Business context: [DESCRIBE: 2–3 key things that happened operationally this period that explain the numbers] For each material variance: - Write a 2–3 sentence explanation: what drove it, whether it's expected to continue, and what (if anything) should be done about it - Use cautious language where cause is not confirmed: "appears driven by," "may reflect" - Do NOT invent explanations — if a variance has no clear driver, say so Output: Variance commentary table ready to paste into the board pack. Each line gets 2–3 sentences maximum.

You are an FP&A analyst preparing the monthly KPI narrative for the executive team. KPI data: [PASTE: KPI name | This period actual | Last period actual | Budget | Prior year | Trend (improving/stable/declining)] For each KPI: - Write a 1–2 sentence plain-English explanation of what the number means and what drove the change - Flag: KPIs more than 10% below target — explain root cause - Note: KPIs moving in the wrong direction for 3+ consecutive months — signal a trend, not a blip - Highlight: 1–2 KPIs that deserve particular management attention this month Output: KPI dashboard narrative — suitable for pasting into a board/exec update. Each KPI gets 2–3 lines max. End with: the most important management action this data suggests.

You are a CFO preparing the monthly board financial summary. Financial data: [PASTE: Revenue (actual vs. budget vs. prior year) | EBITDA | Net income | Cash balance | Key operating metrics for your business] Narrative context: [DESCRIBE: 2–3 key things that happened this month operationally that explain the numbers] Write a board financial summary covering: 1) Headline numbers: revenue, EBITDA, cash — actual vs. budget, actual vs. prior year 2) What drove performance this month — 2–3 specific factors (not generic) 3) Items requiring board awareness or decision 4) Outlook: are we on track for the full year? What are the top risks? 5) One key metric or trend worth watching closely next month Output: Executive summary, max 1 page. Format for non-finance board members. Use plain English — no accounting jargon. Bold headline numbers.

You are a supply chain planner preparing the monthly S&OP meeting. Data inputs: [PASTE: Demand forecast (next 3 months by product family) | Supply plan / production capacity | Current inventory levels | Open customer orders | Any supply constraints or disruptions known] Build the S&OP prep brief covering: 1) Demand vs. supply balance — where are the gaps by product family? 2) Inventory position — over/under vs. target days on hand by family 3) Capacity constraints — any weeks where demand exceeds available production or supply capacity 4) Open issues requiring a decision — items where S&OP team alignment is needed 5) Recommended decisions — specific choices for the team to make at the meeting Output: One-page S&OP pre-read. Each section max 5 bullet points. Suitable for distributing to cross-functional team 48 hours before the meeting.

You are a production supervisor preparing the end-of-shift report. Shift data: [PASTE: Date/shift | Line or machine | Product produced | Target quantity | Actual quantity | Scrap quantity | Downtime (minutes + reason) | Headcount | Any quality holds or customer issues] Produce: 1) Output summary — actual vs. target, efficiency %, cumulative vs. daily plan 2) Downtime log — total downtime by reason category (mechanical / changeover / material / quality / operator) 3) Quality summary — scrap rate, any holds placed and reason 4) Shift highlights — notable events (near miss, equipment issue, quality escape, strong performance) 5) Handover notes — what does the next shift need to know? Any ongoing issues? Output: Shift report ready to hand to incoming supervisor and send to production manager. Tone: Factual, specific. No vague language.

You are an HR business partner drafting communications for an organizational change. Change details: [DESCRIBE: What is changing (restructure / role elimination / new team / reporting change), who is affected, effective date, business reason, what support is available for affected employees] Draft three communications: 1) Manager talking points — what managers should say to their teams; anticipate the top 5 questions employees will ask and provide answers 2) All-staff email — announces the change at the appropriate level of detail; professional, empathetic tone 3) FAQ document — detailed Q&A covering: why this change, what it means for job security, timeline, next steps, who to contact with questions Tone: Honest and direct. Don't minimize the impact if it's significant. Employees will trust communication more if it acknowledges difficulty.

You are a finance director preparing the monthly management operating review (MOR) pack. Data available: [PASTE: Key P&L metrics (revenue, gross margin, EBITDA) | Cash position | Key operational metrics | Headcount | Top 3 business events this month] Build the MOR pack structure: 1) Financial scorecard — revenue, margin, EBITDA vs. budget and prior year; traffic-light status (green/amber/red) 2) Cash and liquidity — current position, trend, any concerns 3) Operational metrics — 3–5 metrics most relevant to the business (fill rate, customer count, utilization, etc.) 4) Business narrative — what happened this month; don't just repeat the numbers 5) Issues requiring leadership decision — specific items, clear recommendation, decision needed by when Output: MOR pack outline. Each section max 1 slide equivalent. Designed for a 30-minute leadership meeting.

You are a CFO writing the financial narrative section of the board pack. Financial data: [PASTE: Revenue | Gross margin | EBITDA | Net income | Cash | Debt — actual vs. budget vs. prior year for the period] Business context: [DESCRIBE: 2–3 key things that happened operationally this period that explain the numbers] Write a board financial narrative that: 1) Opens with the headline: what the numbers say in one sentence 2) Explains performance vs. budget — what drove the variance? Be specific. 3) Explains performance vs. prior year — growth story or decline? 4) Notes anything the board should be watching closely 5) States whether we're on track for the annual plan and why Format: 400 words maximum. Plain English. Board members are not accountants — avoid jargon. Bold headline numbers.

You are a senior analyst preparing a cross-functional KPI summary for the executive team. KPI data: [PASTE: KPI name | Function | This period | Last period | Same period last year | Target | Trend (improving/declining/stable)] For each KPI: - Write a 1-sentence plain-English explanation of what drove the result - Flag: KPIs more than 10% below target or declining for 3+ consecutive periods - Highlight: KPIs where we're exceeding target — note whether it's sustainable or a one-off Group KPIs by theme: Revenue & Growth / Profitability / Operations / Customer / People. Output: Executive KPI summary — each KPI gets maximum 3 lines. End with: the 2 metrics that most need management attention this period and why.

You are an FP&A analyst preparing the weekly executive flash report. Data: [PASTE: Week ending date | Revenue this week | Revenue MTD | Revenue vs. plan MTD | Cash balance | Top 3 operational highlights | Any issues or risks] Write an executive flash report covering: 1) Revenue performance — this week, MTD, vs. plan. One sentence on what drove it. 2) Cash position — current balance, trend vs. last week 3) Operational highlights — what happened this week worth noting 4) Open issues — anything requiring an executive decision or awareness 5) Next week outlook — any known material events Format: Short email. Max 15 lines. Bold key numbers. CFO should be able to read this in 60 seconds. No filler.

You are a senior analyst writing the monthly business performance narrative for distribution to all managers. Financial and operational data: [PASTE: Revenue, costs, and key operational metrics for the period vs. budget and prior year] Business events: [DESCRIBE: What happened this period — new customers, lost customers, operational issues, market events, team changes] Write a business performance narrative that: 1) States clearly: were results good, mixed, or below expectations — and why 2) Explains the top 3 drivers of performance in plain English 3) Acknowledges what didn't go well without softening it 4) Notes what the team did well 5) Previews the focus for next month Tone: Direct and honest. Managers trust narratives that don't spin the numbers. If results were poor, say so and explain why. Format: 300–400 words. No tables — this is narrative.

You are a project manager preparing for an ERP go-live. Go-live details: [DESCRIBE: System going live, date, modules/departments affected, planned downtime window, cutover approach (big bang / phased), key contacts for issues] Draft the communication plan including: 1) Pre-go-live email (1 week before) — what's changing, what users need to do to prepare, training resources 2) Countdown email (1 day before) — final reminder, downtime window, who to contact with questions 3) Go-live announcement (day of) — system is live, where to log issues, support resources available 4) Post-go-live check-in (1 week after) — how is it going, where to report ongoing issues, FAQ based on common early questions 5) Issue escalation matrix — who to contact for different types of issues (system access / data errors / training / process questions) Output: Four email drafts + escalation matrix. Tone: Clear, reassuring, practical. Users should feel supported, not anxious.

You are an ERP administrator creating end-user training documentation for a new module. Module context: [DESCRIBE: Module name (e.g., AP invoice processing / inventory receiving / expense reports), user role who will use it, key transactions they need to perform, system name] Draft training documentation including: 1) Overview — what this module does and why it matters to this user's job (2 sentences) 2) Step-by-step process guide — numbered steps for each key transaction; one action per step; include what screen to navigate to and what to click/enter 3) Common errors and how to fix them — top 5 mistakes new users make 4) Key fields explained — any field that isn't self-explanatory gets a one-line explanation 5) Who to contact for help — by issue type Output: Training guide formatted for a new employee on their first day. Plain language. No IT jargon. Assume zero prior ERP experience.

You are a business analyst documenting an ERP system change request. Change details: [DESCRIBE: What needs to change in the system, why (business reason), who requested it, which module/process is affected, any workaround currently in place] Write a system change request covering: 1) Business case — why this change is needed and what problem it solves 2) Current state — how the process works today and what the specific pain point is 3) Proposed solution — what the system needs to do differently (in business terms, not technical) 4) Impact assessment — which other processes, reports, or users could be affected by this change 5) Testing requirements — how will we confirm the change works correctly before go-live? 6) Priority — urgent (business impact today) / high (workaround exists but costly) / medium / low Output: Change request document ready for IT review. Written in business language so both business users and technical teams can understand the requirement.