ChatGPT Prompts for Budget Analysts: Rewrite for Non-Finance Audiences and Reduce Back-and-Forth with Auditors

You are a senior financial communications specialist with 10 years of experience translating complex budget analysis into language that non-finance stakeholders understand and auditors accept without follow-up questions. Help me rewrite my client financial review outputs so I can reduce back-and-forth with auditors and stop missing early warning signals in my own analysis. My situation: - Type of client financial review: [MONTHLY MANAGEMENT ACCOUNTS / QUARTERLY REVIEW / ANNUAL AUDIT PREP / AD HOC] - Primary audience for the rewritten output: [AUDITORS / SENIOR MANAGEMENT / BOARD / NON-FINANCE CLIENT STAKEHOLDERS] - Current problem with my outputs: [e.g., "auditors always ask for clarification on variance explanations" / "clients say the reports are too technical"] - Technical level of my current writing: [HEAVILY TECHNICAL / MODERATELY TECHNICAL / INCONSISTENT] - Report sections I struggle with most: [EXECUTIVE SUMMARY / VARIANCE ANALYSIS / FORWARD OUTLOOK / OTHER] - Volume of reports to rewrite: [ONE KEY REPORT / RECURRING MONTHLY PACKAGE / FULL CLIENT PORTFOLIO] Deliver: 1. A plain-English rewrite of my most technical report section — using [PASTE YOUR TEXT HERE] as the input placeholder 2. A financial jargon-to-plain-English translation guide — 20 common terms with their non-finance equivalents for consistent use across all reports 3. A variance explanation formula — a 3-part structure (what happened / why it happened / what we are doing about it) that works for any budget line 4. An auditor FAQ anticipation list — the 8 questions auditors most commonly ask about budget variance reports and the pre-emptive language to include that answers them before they are raised 5. A structural rewrite checklist — 6 questions to ask about any financial report section before sending it to a non-finance audience 6. An executive summary template — a 5-sentence format that covers the key financial position without requiring the reader to understand the numbers 7. A before-and-after rewrite example for 2 sections of my report — showing the transformation from technical to audience-appropriate language 8. A style guide for consistent tone — rules for tense, number formatting, and hedging language that make financial reports read as professional and authoritative For every rewrite recommendation, show the before and after version — never describe what to change without demonstrating it.