30 Claude Prompts That Build Business Reports

You are a project manager who writes clear, honest status reports. <context> I need a project status report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, for a stakeholder review. </context> <inputs> - Project name and reporting date: [PROJECT / DATE] - Overall status and why: [GREEN / AMBER / RED] - Milestones: [DONE, IN PROGRESS, UPCOMING WITH DATES] - Scope, schedule, budget health: [EACH RAG-RATED] - Risks and issues: [WITH OWNER AND MITIGATION] - Decisions or help needed: [ASKS] </inputs> <task> Build a report with: a header and a prominent overall RAG status with a one-line reason, a scope/schedule/budget health tri-panel each RAG-rated, a milestone tracker table (milestone, owner, due, status), a risks-and-issues register with severity and mitigation, an accomplishments-since-last-report list, a next-period plan, and a decisions-needed callout. Be straight about anything off track. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - RAG status shown by both color and text; a red status must include a recovery plan. - Milestone dates explicit; risks ranked by severity; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain what tipped your overall status rating and the fastest path back to green. </format>

You are a site-reliability lead who writes blameless post-mortems. <context> I need a blameless incident post-mortem built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, suitable for an engineering review and a customer-facing summary. </context> <inputs> - Incident title and severity: [NAME / SEV LEVEL] - Impact (who, what, how long): [USER/REVENUE IMPACT, DURATION] - Timeline of events: [DETECTION TO RESOLUTION, TIMESTAMPS] - Root cause: [WHAT ACTUALLY BROKE] - Contributing factors: [WHAT MADE IT WORSE] - Action items to prevent recurrence: [FIXES] </inputs> <task> Build a post-mortem with: a summary box (severity, duration, impact, status), an impact section quantifying who and how much, a detailed timeline table (time, event, who), a root-cause analysis using a 5-whys chain, a contributing-factors list, a "what went well / what went poorly" two-column block, and an action-items table with owner, due date, and type (prevent/detect/mitigate). Stay blameless: focus on systems, not people. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Timeline uses consistent timestamps; the 5-whys reaches a systemic root cause, not a person. - Action items are specific and assignable; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain the deepest 'why' you reached and the single action item that best prevents recurrence. </format>

You are an operations analyst who turns metrics into a readable dashboard report. <context> I need an operations KPI dashboard report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, that a weekly ops review can run on. </context> <inputs> - Operation and period: [TEAM / WEEK OR MONTH] - Core KPIs and targets: [METRIC: VALUE, TARGET, PRIOR] - Volume and throughput: [UNITS, TICKETS, ORDERS, ETC] - Quality and SLA metrics: [ERROR RATE, ON-TIME %, CSAT] - Trends to highlight: [WHAT'S MOVING] - Issues and bottlenecks: [PROBLEMS] </inputs> <task> Build a dashboard report with: a top KPI tile grid (value, target, delta, status), a throughput trend chart in inline SVG, a quality/SLA section with gauges or progress bars in CSS, a bottleneck callout ranking the top constraints, a commentary section interpreting the numbers, and a focus-for-next-period list. Make the page work as a recurring template. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; gauges/charts in CSS/SVG. - Each KPI tile shows status vs. target by color and text; trends signed. - Designed for reuse; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain which KPI you placed top-left and why it's the one to watch first. </format>

You are a risk manager who produces structured risk assessments. <context> I need a risk assessment report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, for a governance or leadership review. </context> <inputs> - Scope of assessment: [PROJECT / BUSINESS AREA] - Risks identified: [LIST WITH BRIEF DESCRIPTIONS] - Likelihood and impact estimates: [PER RISK] - Existing controls: [WHAT'S ALREADY IN PLACE] - Risk appetite / threshold: [HOW MUCH WE TOLERATE] - Mitigation owners and timelines: [WHO / WHEN] </inputs> <task> Build a report with: an executive summary of the overall risk posture, a risk register table (risk, likelihood, impact, score, control, owner, status), a likelihood-vs-impact heat-map matrix drawn in CSS, a top-risks deep-dive with mitigation plans, a residual-risk note after controls, and a recommendations section. Rank risks by score and call out anything above appetite. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; the heat map drawn in CSS/SVG. - Risk score = likelihood x impact, shown consistently; risks over appetite flagged. - Distinguish inherent vs. residual risk where possible; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then name the highest residual risk after controls and why it stays elevated. </format>

You are a strategy operations lead who reports on OKR progress. <context> I need a quarterly OKR progress report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, for a company-wide review. </context> <inputs> - Quarter and team(s): [Q AND YEAR / SCOPE] - Objectives and their key results: [O AND KRS] - Current progress per KR: [% OR ACTUAL VS TARGET] - KRs at risk or off track: [WHICH AND WHY] - Blockers and dependencies: [WHAT'S IN THE WAY] - Adjustments proposed: [RE-SCOPE / RE-PRIORITIZE] </inputs> <task> Build a report with: an overall confidence summary, an objective-by-objective section each showing its KRs with a progress bar, current vs. target, and an on-track/at-risk/off-track label, a roll-up scorecard of all KRs by status, a blockers-and-dependencies list, and a proposed-adjustments section. Be honest about graded progress; don't inflate. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; progress bars in CSS. - Each KR shows a 0-100% bar plus the underlying actual vs. target; status labeled in text. - A KR over 70% is not auto-green if the target is soft; note grading caveats; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then explain which objective you'd deprioritize and what evidence supports cutting it. </format>

You are a data analyst who writes findings reports that drive decisions. <context> I need a data analysis findings report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, that translates a dataset into action. </context> <inputs> - Analysis question: [WHAT WE WANTED TO LEARN] - Dataset and method: [SOURCE, SIZE, APPROACH] - Key findings: [3-6 FINDINGS WITH NUMBERS] - Supporting data for charts: [TABLES / SERIES] - Caveats and limitations: [WHAT NOT TO OVER-READ] - Recommended actions: [SO WHAT] </inputs> <task> Build a report with: an executive summary stating the answer up front, a methodology box, a findings section where each finding pairs a one-line claim with an inline SVG chart and a short interpretation, a key-numbers callout band, a limitations section, and a recommendations list ranked by confidence. Separate what the data shows from what you infer. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; all charts inline SVG/CSS, no libraries. - Only chart data I supply; never invent data points to fill a chart. - State confidence on each finding; correlation is not labeled causation; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then explain the strongest finding and the one most likely to be a false signal. </format>

You are a strategy analyst who writes balanced feasibility studies. <context> I need a feasibility study built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, that helps a committee decide go/no-go. </context> <inputs> - The proposed initiative: [WHAT WE'RE EVALUATING] - Objectives and success criteria: [WHAT GOOD LOOKS LIKE] - Market/technical/operational factors: [CONSIDERATIONS] - Cost and resource estimates: [BUDGET, PEOPLE, TIME] - Expected benefits / ROI: [UPSIDE] - Major risks and constraints: [DOWNSIDE] </inputs> <task> Build a study with: an executive summary with a clear go/no-go/conditional recommendation, a feasibility assessment across market, technical, operational, and financial dimensions each scored, a cost-benefit section with a simple ROI/payback table, an alternatives-considered comparison, a risk summary, and conditions that must hold for a 'go'. Be even-handed; don't rubber-stamp. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Each feasibility dimension gets a rating and a one-line rationale; the recommendation follows from the scores. - ROI/payback math shown, not asserted; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then state your recommendation in one sentence and the single factor that would flip it. </format>

You are a growth experimentation analyst who reports test results rigorously. <context> I need an A/B test results report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, that an experiment review can ship a decision from. </context> <inputs> - Test name and hypothesis: [WHAT AND WHY] - Variants: [CONTROL VS VARIANT(S) DESCRIPTION] - Primary metric and result: [METRIC, LIFT, P-VALUE/CONFIDENCE] - Sample sizes and duration: [N PER ARM, DAYS] - Secondary/guardrail metrics: [OTHER EFFECTS] - Decision context: [WHAT WE'LL DO WITH THE RESULT] </inputs> <task> Build a report with: a verdict banner (ship / don't ship / inconclusive), a hypothesis-and-setup box, a results table per metric (control, variant, lift, confidence/significance), a comparison bar chart in inline SVG, a guardrail-metrics check, a sample-and-power note, and a recommendation with caveats. Be honest about significance and don't over-claim small lifts. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; charts inline SVG/CSS. - Report confidence/significance for the primary metric; flag underpowered or peeking risks. - Distinguish statistical from practical significance; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then explain your ship/no-ship verdict and what would make you re-run the test. </format>

You are a deal analyst who writes tight due-diligence summaries. <context> I need a due-diligence summary report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, for an investment or acquisition committee. </context> <inputs> - Target and deal type: [COMPANY / INVESTMENT OR ACQUISITION] - Thesis and what we're testing: [WHY THIS DEAL] - Findings by area: [FINANCIAL, COMMERCIAL, OPERATIONAL, LEGAL, TEAM] - Red flags and open questions: [CONCERNS] - Valuation or terms context: [PRICE / STRUCTURE] - Recommendation leaning: [PROCEED / PASS / CONDITIONAL] </inputs> <task> Build a summary with: an executive recommendation up top (proceed/conditional/pass with confidence), a thesis box, a findings-by-workstream grid each rated (strong/neutral/concern) with key evidence, a red-flags-and-open-questions register, a valuation context note, and a conditions-to-proceed list. Be skeptical and specific; separate verified facts from claims to confirm. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Each workstream gets a rating and the evidence behind it; unconfirmed items marked clearly. - No invented financials; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain the single finding that most affects the recommendation and what would resolve it. </format>

You are a performance analyst who benchmarks an organization against peers. <context> I need a benchmarking report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, that shows where we stand against comparables. </context> <inputs> - What we're benchmarking: [METRICS / FUNCTION] - Our values: [OUR NUMBERS] - Benchmark set: [PEERS / INDUSTRY AVERAGE / BEST-IN-CLASS] - Comparison metrics: [THE METRICS TO COMPARE] - Where we lead and lag: [INITIAL VIEW] - The goal of the exercise: [WHY WE'RE COMPARING] </inputs> <task> Build a report with: a summary of overall standing (above/at/below benchmark), a comparison table (metric, us, benchmark, gap, percentile), a grouped-bar chart in inline SVG comparing us to the benchmark per metric, a gap-analysis section ranking the biggest under- and over-performances, a strengths-to-protect note, and prioritized closing actions for the largest gaps. Be precise about which benchmark each comparison uses. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; charts inline SVG/CSS. - Each metric states its benchmark source and gap direction; percentiles only where defensible. - Don't conflate different benchmark sets; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then name the largest closeable gap and the action with the best effort-to-impact ratio. </format>

You are an account manager who keeps clients informed and reassured. <context> I need a client-facing progress report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, polished enough to send directly to a client. </context> <inputs> - Client and engagement: [CLIENT / PROJECT OR RETAINER] - Period covered: [DATES] - Goals and the results delivered: [OUTCOMES VS OBJECTIVES] - Key metrics that matter to them: [THEIR KPIS] - Work completed and in progress: [DELIVERABLES] - Next steps and any asks: [WHAT'S NEXT] </inputs> <task> Build a report with: a branded-feeling header, a results-at-a-glance band tied to their goals, a metrics section in their language with deltas, a completed-work list with brief outcome notes, an in-progress and upcoming roadmap, a wins-and-value-delivered callout, and a clear next-steps block with any client actions needed. Write warm, confident, client-appropriate prose. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; placeholder for the client's logo and accent color. - Frame everything in terms of the client's outcomes, not your internal tasks; no jargon. - Specific value language, no fluff; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain how you reframed internal work as client outcomes and where to slot a renewal nudge. </format>

You are a nonprofit program lead who reports impact to funders. <context> I need a grant or program impact report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, suitable for funders and stakeholders. </context> <inputs> - Program and reporting period: [NAME / DATES] - Mission and goals for this period: [INTENDED OUTCOMES] - Outputs delivered: [NUMBERS SERVED, ACTIVITIES] - Outcomes and impact measures: [CHANGE ACHIEVED] - Budget used vs. granted: [SPEND] - Stories and challenges: [QUALITATIVE] </inputs> <task> Build an impact report with: a mission and period header, an impact-at-a-glance stat band, an outputs-vs-goals table, an outcomes section pairing each measure with an inline chart and plain-language meaning, a budget summary (granted, spent, remaining) with a simple breakdown, a beneficiary story callout, a challenges-and-learnings section, and a next-period plan. Distinguish outputs from real outcomes. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; charts inline SVG/CSS. - Outputs (counts) and outcomes (change) clearly separated; budget figures reconcile. - Honest about challenges; accessible contrast; print-friendly for grant submission. </constraints> <format> Return the full HTML as an artifact, then explain which outcome best demonstrates real impact versus mere activity. </format>

You are a people analytics lead who reports workforce metrics to leadership. <context> I need an HR people analytics report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, for a leadership people review. </context> <inputs> - Period and scope: [QUARTER / ORG OR TEAM] - Headcount and changes: [START, HIRES, EXITS, END] - Attrition and retention: [RATES, BY SEGMENT IF KNOWN] - Engagement and eNPS: [SCORES] - Diversity and pipeline metrics: [IF TRACKED] - Hot spots and actions: [WHERE TO FOCUS] </inputs> <task> Build a report with: a workforce summary band (headcount, net change, attrition, eNPS), a headcount-movement chart in inline SVG, an attrition section with rate, trend, and a regrettable-vs-non split if available, an engagement section with score distribution, a diversity/pipeline snapshot where data allows, a hot-spots callout, and recommended people actions. Handle small-group data carefully for privacy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; charts inline SVG/CSS. - Suppress or aggregate any segment too small to report safely; note where data is withheld. - Rates defined consistently (annualized vs. period); accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain which attrition signal most warrants action and how you protected small-group privacy. </format>

You are a sustainability lead who writes credible, non-greenwashed ESG reports. <context> I need a sustainability/ESG report built as one self-contained HTML file with inline CSS and charts, previewable instantly as an artifact, for stakeholders and reporting. </context> <inputs> - Organization and reporting year: [NAME / YEAR] - Environmental metrics: [EMISSIONS, ENERGY, WASTE, WATER] - Social metrics: [WORKFORCE, SAFETY, COMMUNITY] - Governance highlights: [POLICIES, BOARD, ETHICS] - Targets and progress: [COMMITMENTS VS ACTUAL] - Challenges and next-year goals: [HONEST GAPS] </inputs> <task> Build a report with: an executive summary, a materiality or focus framing, environmental, social, and governance sections each with key metrics, a trend chart in inline SVG, and progress against targets, a targets-scorecard table (commitment, baseline, current, target year, status), a challenges-and-honest-gaps section, and a forward commitments list. Avoid vague claims; tie every statement to a metric. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; charts inline SVG/CSS. - No greenwashing: every claim has a number or is omitted; baselines and scopes stated. - Progress shown against targets, including misses; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain which target you're most behind on and how you framed it without spin. </format>

You are a program lead who runs honest after-action reviews on completed efforts. <context> I need an after-action (campaign wrap) report built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, that captures lessons for the next time. </context> <inputs> - What concluded: [CAMPAIGN / PROJECT / EVENT] - Goals set vs. results achieved: [TARGET VS ACTUAL] - Key metrics and outcomes: [NUMBERS] - What went well: [SUCCESSES] - What went wrong or fell short: [SHORTFALLS] - Lessons and changes for next time: [TAKEAWAYS] </inputs> <task> Build a wrap report with: a results-vs-goals summary band, an objectives scorecard (goal, result, met/missed), a metrics recap with the headline outcomes, a "what worked / what didn't" two-column analysis, a root-cause note on the biggest miss, a lessons-learned list translated into specific changes, and a recommendations-for-next-time block. Be candid; the value is in the honest retrospective. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Every lesson maps to a concrete change, not a platitude; the biggest miss gets a real root cause. - Goals-vs-results stated plainly; accessible contrast; print-friendly. </constraints> <format> Return the full HTML as an artifact, then explain the single lesson most worth carrying into the next effort and why. </format>