Formatted Report Writer

Formatted Report Writer

A business report has two audiences: the executive who reads only the summary, and the analyst who reads everything. The costly failure this skill prevents is the report that serves neither - findings buried in chronology, a summary that teases instead of concludes, and a busy reader who gives up before reaching the recommendation they were supposed to approve.

Operating procedure

Step 1: Gather inputs - do not draft until these are settled

Answer in one sentence each; if the requester cannot, propose an answer and label it a guess:

1. What decision or action does this report enable?
2. Who is the primary reader, and what do they already know?
3. What must the reader believe by the end?
4. Register: formal (board, regulatory) or plain (internal ops)? Default: plain.
5. Source material: the findings, data, and analysis to be structured.

If these are unclear, the structure will be unclear - settle them first.

Step 2: Build the skeleton

Default structure for a business or consulting report:

1. Title block - title, author, date, version.
2. Executive summary - 150 to 250 words; stands alone; includes the recommendation. A reader who stops here must still know what to do.
3. Background / context - shared facts and scope boundaries.
4. Findings - the substance, organized by theme, never chronology.
5. Analysis - what the findings mean and why it matters.
6. Recommendations - numbered, prioritized, actionable: each names an action, an owner type, and what happens if ignored.
7. Appendix - supporting data, methodology, raw research.

Each section opens with a one-sentence statement of what it covers, so fast-navigating readers can skip with confidence.

Step 3: Write the executive summary last, place it first

Draft sections 3-6, then compress. The summary states the situation, the key findings (3-5 max), and the recommendation - no suspense, no "this report will explore."

Step 4: Apply the heading hierarchy

Three levels maximum, used consistently: H1 for major sections (numbered in formal reports), H2 for subsections, H3 only when a subsection has meaningful internal structure. Never use heading levels for visual emphasis - bold a sentence or use a callout instead.

Step 5: Enforce skimmability

• No paragraph longer than 6 lines in the findings and analysis sections.
• Every section's topic sentence lands in the first or second line.
• Numbered lists for sequences and ranked items; bullets for parallel non-sequential items.
• Tables beat prose for any comparison of 3+ items across 2+ attributes.
• Bold the key term or finding once per paragraph - not every important word.

Step 6: Set tone and purge passive voice

Default to plain register - clear sentences over impressive vocabulary; a report that requires a second read has failed. Passive voice is a red flag: "Revenue declined 18%" beats "An 18% decline in revenue was observed."

Step 7: Run the two-minute test

Read only the executive summary, the section-opening sentences, and the bolded findings. If that pass does not convey the situation, the evidence, and the recommendation, restructure before polishing prose.

Worked contrast: executive summary opening

Bad: "This report examines various aspects of the company's customer retention performance over the review period. A number of trends were identified and are discussed in the sections that follow, along with several considerations for management." Why it fails: no finding, no number, no recommendation; passive and self-referential; the executive learns nothing and must read on - which is exactly what they will not do.

Good: "Customer churn rose from 3.1% to 5.4% monthly over the last two quarters, concentrated in accounts onboarded without a kickoff call - those accounts churn at 2.4x the rate of accounts with one. We recommend making kickoff calls mandatory for all new accounts above the starter tier, which we estimate would retain roughly $840K in annual recurring revenue at a cost of one additional CS hire." Why it works: situation, quantified finding, causal pattern, and a recommendation with cost and payoff - a reader who stops here can still act.

Deliverable

Produce the full report in the seven-part skeleton: title block, standalone 150-250-word executive summary containing the recommendation, background, theme-organized findings, analysis, numbered prioritized recommendations, and appendix - with section-opening topic sentences and all skimmability rules applied.

Do NOT

• Do not organize findings chronologically ("first we looked at..."); readers need themes, not a diary of the work.
• Do not write a teaser summary ("this report explores..."); the summary is the report for most readers.
• Do not exceed three heading levels or use headings as emphasis; hierarchy collapses into noise.
• Do not let recommendations float without priority or ownership; an unranked list of ten is a decision deferred.
• Do not pad with passive constructions and hedges; they hide who did what and blur the finding.

Quality bar

• The executive summary stands alone, fits 150-250 words, and contains the recommendation.
• Findings are grouped by theme; every comparison of 3+ items sits in a table.
• No paragraph in findings/analysis exceeds 6 lines; topic sentences lead every section.
• Recommendations are numbered, prioritized, and actionable.
• The report passes the two-minute skim test end to end.