Report Writing and Formal Proposals

Report Writing and Formal Proposals

Introduction: The Purpose of a Report

A report is a structured document that presents information — findings, analysis, recommendations — to a specific audience for a specific purpose. Unlike an essay, which builds a single argument, a report serves multiple functions simultaneously: it informs, it analyses, it recommends, and it provides a permanent record.

The most important question before writing any report is: who is the audience and what do they need to do with this information? A technical report for engineers reads differently from a board-level executive summary, which reads differently from a customer-facing product review. The structure, vocabulary, level of detail, and tone all depend on this primary question.

Part One: Standard Report Structure

TITLE PAGE: Includes the report title, author name, organisation, date, and version number if applicable. Professional reports are versioned — "v1.0," "v1.1 (revised)" — so that all recipients know they are reading the same document.

EXECUTIVE SUMMARY: The single most important section of a long report. Senior readers often read only this. It must include: the purpose of the report, the key findings, and the main recommendations — in three to five sentences. The executive summary is written last but placed first.

TABLE OF CONTENTS: For any report exceeding five pages. Lists all section headings with page numbers.

INTRODUCTION: States the purpose of the report, the scope (what is covered and what is not), the methodology used, and the intended audience. The introduction does not contain findings.

FINDINGS / BODY: Presents the information gathered, organised logically. Each section should have a clear heading and focus on one topic. Use data, evidence, and examples. Avoid opinion in the findings section — save it for the analysis.

ANALYSIS: Interprets the findings. What patterns emerge? What do the data mean? What are the implications? This is where professional judgement is applied.

RECOMMENDATIONS: Concrete, specific, actionable. Each recommendation should be numbered and should specify: what should be done, by whom, and by when. — Weak recommendation: "Communication should be improved." — Strong recommendation: "1. The team leader should send a weekly project update to all stakeholders by Monday morning, beginning the first Monday of next month."

APPENDICES: Supporting material (data tables, interview transcripts, detailed calculations) that would interrupt the flow if placed in the body.

Part Two: Language of Reports

Reports use a formal, precise, and impersonal register. Key features:

1. Third person: "The survey found..." rather than "We found..."
2. Passive voice (where appropriate): "Data were collected over a period of three months."
3. Precise numerical references: "73% of respondents" rather than "most respondents."
4. Hedged language for uncertainty: "The data suggest..." rather than "The data prove..." (unless the evidence genuinely proves)
5. Avoiding emotive language: "The project experienced delays" rather than "The project suffered disastrous delays" — unless the severity warrants it.

Part Three: Formal Proposals

A proposal argues for a course of action. It is a document of persuasion, not just information. Every section should answer the reader's implied questions:

PROBLEM STATEMENT: What problem are we solving? Why does it matter? PROPOSED SOLUTION: What exactly do you recommend? Be specific. RATIONALE: Why is this the best solution? What alternatives were considered? RESOURCES REQUIRED: What will this cost in time, money, and personnel? TIMELINE: When will each phase be completed? EXPECTED OUTCOMES: What will success look like? How will you measure it? RISKS: What could go wrong, and how will you mitigate it?

The risks section is the most commonly omitted by inexperienced writers — and the most carefully read by experienced decision-makers. A proposal that acknowledges no risks looks naive. A proposal that identifies risks and addresses them looks professional.

Part Four: Common Report Writing Errors

1. Mixing findings and analysis: "Sales decreased by 12% in Q3, which shows that the marketing campaign was ineffective." The decrease is a finding; the attribution to marketing is analysis. Keep them in separate sections.

2. Vague recommendations: "Steps should be taken to address this issue." By whom? What steps? When? Every recommendation must be specific enough to act on.

3. Executive summary as introduction: The executive summary is a miniature version of the entire report — findings, analysis, and recommendations. The introduction only frames the report. They serve different purposes and must not be merged.

4. Passive evasion of accountability: "Errors were made in the data collection process" — by whom? The passive voice is appropriate for processes, but not for attributing (or avoiding attributing) responsibility.

5. Technical language for non-technical audiences: Every piece of jargon you use is a barrier between your reader and your message. If your audience is not technical, translate. If some readers are technical and some are not, put technical detail in appendices.