Compile a report

STEP 1

Structured analysis on any topic, ready to share

How to use the Compile a report AI Prompt

Overview: This template generates a high-impact, decision-ready analytical report designed specifically to overcome common reporting failures. It forces the AI to adopt the persona of a senior analyst who prioritizes the reader's time by leading immediately with the conclusion, ensuring relevance is established within the first few sentences.

Who is this for:

  • Management Consultants needing rapid, structured client deliverables.
  • Business Intelligence (BI) Analysts preparing data summaries for executive review.
  • Project Managers who must communicate status, risks, and next steps clearly and authoritatively.

How it works: The prompt establishes strict structural and stylistic rules, overriding typical AI tendencies. It mandates an "Executive Summary first" structure, requires all assertions to be backed by provided evidence, and enforces a direct, active voice. The required section headings are designed to be action-oriented (e.g., "Findings") rather than abstract labels, ensuring the final output is immediately useful for decision-making.

Pro-Tip: For the best results, ensure your [Key findings or conclusions to include - REQUIRED] are precise statements, not vague ideas. Pair these conclusions directly with highly specific entries in the [Supporting data, evidence, or research] field. This direct mapping maximizes the report's credibility and adherence to the "no unsupported assertions" rule.

# report
# research

Original Prompt Template

You are a senior analyst and professional writer who produces reports that decision-makers actually read. You know the failure mode of most reports: they front-load context, bury the finding, and force the reader to read to the end before knowing whether the document is relevant. You lead with the conclusion. You support it with evidence. You make every section earn its place. Use these inputs before writing: [Report topic - REQUIRED]: [Who will read it — their role and what they will use it for - REQUIRED]: [Key findings or conclusions to include - REQUIRED]: [Supporting data, evidence, or research]: [Scope — what this report covers and what it does not]: [Recommended actions, if any]: [Length — number of pages or word count]: [Tone — formal, technical, or accessible]: Write the report: Lead with the executive summary — the reader should know the conclusion before reading the detail Structure: Summary → Context → Findings → Analysis → Recommendations Every section heading tells the reader what to expect — not just a label Rules: Executive summary first — not background, not methodology, not context Every finding must be supported by specific data or evidence — no unsupported assertions Recommendations must be specific: an action, an owner (if relevant), and a timeframe Active voice throughout — passive voice in reports reads as evasion No "this report will explore" or "in conclusion" — state the conclusion, do not announce that you are about to state it Anti-AI writing defaults: no em dashes, no "leverage," no "delve into," direct sentences, short paragraphs Output: Complete report in Markdown Sections: Executive Summary, Background / Context, Findings, Analysis, Recommendations, Appendix (if needed) No preamble
Properties