📄 Lesson 4.1: Reports, Proposals & Business Documents
Emails move the day; documents move decisions. When you need to present findings, justify a budget, or win approval for a plan, you write a report or a proposal. This lesson gives you the structure, the executive summary, the formal register, and — most importantly — the language of recommendations that actually get approved.
📚 What You'll Learn
By the end of this lesson, you will be able to:
- Structure a business report and a proposal using standard, reader-friendly sections
- Write a clear, standalone executive summary that a busy decision-maker can act on
- Use appropriate formal, objective register and a bank of ready-made document phrases
- Present findings and make persuasive, actionable recommendations tied to your evidence
⏱️ Estimated Time: ~60 minutes
🎯 Task: Draft a short, structured report or proposal — with an executive summary and prioritized recommendations — on a work-relevant topic.
In This Lesson
Reports vs Proposals
These two documents look similar and share much of the same language, but they answer different questions. Knowing which you are writing keeps you focused — and tells the reader what to expect.
- A report presents information and findings — usually looking backward or analyzing the present: what happened, what the data shows, what we learned. It may end with recommendations.
- A proposal persuades toward a future action or plan: here is what we should do, why it is worth doing, and what it will take. It must sell.
| Report | Proposal | |
|---|---|---|
| Core question | What happened / what does the evidence show? | What should we do next, and why? |
| Orientation | Past / present — analysis | Future — action |
| Main job | Inform (and sometimes advise) | Persuade and win approval |
| Tone | Objective, evidence-led | Objective but persuasive |
| Typical trigger | "Give me the findings." | "Convince me to fund / approve this." |
💡 The overlap is real
The two blur together. A strong report often ends in recommendations (moving toward proposal territory), and a good proposal is grounded in findings (borrowing the report's evidence). The difference is one of emphasis: a report leads with what is; a proposal leads with what should be.
Report & Proposal Structure
Readers of business documents don't read start to finish — they scan, jump, and dip in. Standard structure with clear headings lets them find what they need. Never make a busy reader hunt.
Standard report structure
| Section | What goes in it |
|---|---|
| Title | Clear, specific subject + author + date |
| Executive Summary | Standalone recap of purpose, key findings, main recommendations (written last, read first) |
| Introduction | Purpose, scope (and limits), background, method |
| Findings / Body | The evidence, organized by theme, with sub-headings, data, and figures |
| Conclusions | What the findings mean — the interpretation, no new data |
| Recommendations | Specific, prioritized actions that follow from the conclusions |
| Appendices | Supporting detail: full data, tables, references (optional) |
Standard proposal structure
| Section | What goes in it |
|---|---|
| Background / Problem | The situation and the need — why this matters now |
| Objectives | What the plan aims to achieve, ideally measurable |
| Proposed Solution / Plan | What you propose to do, concretely |
| Benefits | The value and payoff — sell it (link to the reader's goals) |
| Costs / Resources / Timeline | What it takes: budget, people, schedule |
| Risks | What could go wrong and how you'll manage it (builds trust) |
| Recommendation / Call to action | The clear ask: approve, fund, decide by [date] |
🔁 Proposals must sell
A proposal is persuasion in document form — everything you learned in Lesson 3.3 about benefits over features applies here. Don't just describe the plan (features); spell out the benefits to this reader's priorities — cost saved, risk reduced, revenue gained, time freed. Facts inform; benefits convince.
The Executive Summary
If you learn one thing from this lesson, learn this: the executive summary is the most-read and most-important part of your document. Decision-makers are busy — many will read only the summary and act on it. Everything else is there to back it up.
⚠️ Written last, read first
You can only summarize a document you've finished, so write the executive summary last — but position it first. It must be standalone: a reader who sees nothing else should still understand the purpose, the key findings, and what you recommend. Don't tease ("this report will discuss…"); state the conclusions.
How to write one
- Keep it short — a few tight paragraphs, or roughly 5–10% of the document. One page at most.
- Cover three things: the purpose (why this document exists), the key findings (the headline results), and the main recommendations (what to do).
- Lead with the answer — put the bottom line up front, not at the end.
- Use plain language — no jargon a busy senior reader outside your team would stumble over.
- Make it self-sufficient — no "as discussed above"; it may be read alone.
MODEL — Executive Summary (from a report)
Purpose → This report assesses the causes of rising customer-support wait times in Q2 and recommends a response.
Key findings → Average wait time rose from 4 to 11 minutes, driven by a 38% increase in ticket volume and the loss of two agents. Notably, 60% of tickets concern a single, fixable billing issue.
Recommendations → We recommend three actions: (1) fix the billing error to remove the largest source of tickets; (2) add a self-service FAQ for the top five queries; and (3) hire two support agents by the end of Q3. Together these are projected to return wait times below five minutes within two months.
Notice: it stands alone, states results rather than teasing them, and ends with clear, numbered recommendations. A reader who stops here still knows exactly what to approve.
Formal, Objective Register
Documents sit higher on the formality spectrum than most emails (recall Lesson 1.1). The goal is an impersonal, objective, evidence-based voice — the facts should feel like they speak for themselves, not like your personal opinion.
| Email register (often) | Document register |
|---|---|
| I think we lost customers because… | The data indicates that customer loss was driven by… |
| We found out that… | It was found that… / The analysis reveals that… |
| I'm pretty sure this means… | This suggests that… / It appears that… |
| You should hire more people. | It is recommended that the team be expanded. |
| contractions, "I / you", chatty asides | full forms, impersonal phrasing, neutral tone |
💡 Four register habits for documents
1. Be objective — attribute claims to evidence ("The data indicates…", "It was found that…"), not to feelings.
2. Use the passive where it helps — "It was found that…", "The survey was conducted…" keeps the focus on findings, not on who did what.
3. Hedge honest conclusions — "This suggests…", "It appears that…", "The results imply…" are more credible than overclaiming.
4. Signpost and structure — clear headings, short paragraphs, and bullet points make dense content scannable.
⚠️ Clarity beats showing off
Formal does not mean dense, long-winded, or jargon-heavy. The classic document mistake is burying a simple point under complicated words to sound impressive — "utilize", "leverage synergies", "in order to facilitate the operationalization of…". Busy readers reward clarity. Write to be understood on the first read, not to look clever.
Document Phrase Banks
These are the workhorse phrases of professional documents, grouped by what they do. Keep them handy and adapt them.
Stating the purpose
Presenting findings
Referring to data & appendices
Drawing conclusions
Making recommendations
📖 A note on "It is recommended that…"
In formal recommendations the verb after "recommend that", "propose that", or "suggest that" often takes the subjunctive (the base form): "It is recommended that the team be expanded" / "We propose that the deadline be moved." Use should and could to distinguish a firm recommendation ("we should") from an option worth considering ("we could").
Recommendations That Get Approved
The recommendations section is where a document earns its keep. Vague advice ("improve communication", "consider our options") gets nodded at and ignored. Approvable recommendations share five traits:
💡 The five marks of an approvable recommendation
- Specific — names the actual action, not a vague aspiration. "Add a billing-FAQ page", not "improve support".
- Actionable — someone could start on Monday. Ideally: who does what, by when.
- Prioritized — order them, or label short-term vs long-term. Don't hand over an unranked wish-list.
- Cost/benefit-aware — acknowledge what it takes and what it returns. Decision-makers weigh both.
- Tied to the findings — every recommendation should trace back to evidence in the body. No surprises.
| Vague (ignored) | Approvable (specific & actionable) |
|---|---|
| We should improve customer support. | We recommend hiring two support agents by the end of Q3 to bring average wait times below five minutes. |
| Marketing needs more budget. | We propose increasing the digital ad budget by 15% for Q4, targeting the two channels that returned the highest ROI in Q3 (see Appendix B). |
| Something must be done about turnover. | As a priority, we recommend introducing quarterly stay-interviews for at-risk teams; longer term, the review of pay bands could follow in Q1. |
Here is the structure of a report and a proposal at a glance:
🧠 Mindset: Clear writing is clear thinking
Nobody is born writing polished reports — every confident business writer once stared at a blank page too. The struggle to make a document clear is really the work of making your thinking clear, and that is a skill you build by doing. Each report you draft, restructure, and tighten trains the muscle. Great communicators are made, not born: your tenth report will be far better than your first, precisely because you wrote the first. Start messy, then shape it.
🔊 Hear It & Repeat — Model Sentences
Listen to each model sentence, then say it back. Use the 🎧 Audio control (bottom-right) to choose a UK or US voice and slow the speed down. These formal, objective phrases give a report or proposal a clear, credible structure.
- The purpose of this report is to review last year's performance.
- The findings suggest a clear upward trend in customer demand.
- As shown in Appendix A, costs remained stable throughout the year.
- Based on these results, we recommend expanding the pilot program.
- In conclusion, the proposal offers a strong return on investment.
Practice & Task
🏋️ Exercise 1: Order the sections
Objective: Put these report sections into the correct standard order.
- Recommendations
- Executive Summary
- Findings / Body
- Introduction
- Conclusions
✅ Answer
Correct order: Executive Summary → Introduction → Findings/Body → Conclusions → Recommendations (then Appendices). Remember: the executive summary comes first in the document even though you write it last.
🏋️ Exercise 2: Match the phrase to its function
Objective: Label each phrase — Purpose, Findings, or Recommend.
- "It is recommended that the process be automated."
- "The aim of this report is to evaluate supplier performance."
- "The data indicates a 20% drop in returns."
- "The best course of action would be to renegotiate the contract."
- "Notably, satisfaction rose fastest among new customers."
✅ Answer
"It is recommended that…" = Recommend · "The aim of this report is…" = Purpose · "The data indicates…" = Findings · "The best course of action would be…" = Recommend · "Notably, satisfaction rose…" = Findings. Notice how the recommend-phrases point to a future action, the purpose-phrase states why the document exists, and the findings-phrases report evidence objectively.
🏋️ Exercise 3: Fix the vague recommendation & tighten the wordy line
Objective: (a) Turn this vague recommendation into a specific, actionable one; (b) tighten this wordy, jargon-heavy passage.
- Vague: "The company should try to reduce its costs where possible."
- Wordy: "In order to facilitate the operationalization of enhanced efficiencies going forward, it is our considered view that the utilization of the new system should perhaps be leveraged."
✅ Answer (models)
1. "We recommend cutting the two lowest-performing ad channels (see Appendix A), saving an estimated $40k in Q4." — specific, actionable, tied to evidence, cost-aware. (Many good versions exist; the test is: could someone act on it Monday?)
2. "We recommend adopting the new system to improve efficiency." — same meaning, a third of the words (27 → 9), no jargon. Clarity over showing off.
🎯 Your Task: Draft a Structured Report or Proposal
Choose a real, work-relevant topic — e.g. a recurring problem on your team, a tool or process you'd like approved, or findings from something you recently ran.
- (5 min) Decide: is this a report (present findings) or a proposal (persuade to act)? Write a clear title and pick the matching structure from this lesson.
- (20 min) Draft the body: for a report, write the Introduction, 2–3 themed Findings with at least one piece of evidence each, and Conclusions; for a proposal, write the Problem, Objectives, Plan, Benefits, and Costs/Risks.
- (10 min) Write 3 recommendations that pass the five-marks test — specific, actionable, prioritized, cost/benefit-aware, and tied to your findings. Use the recommendation phrase bank.
- (10 min) Now write the executive summary last (purpose + key findings + main recommendations), and place it first. Make it standalone.
- (5 min) Register pass: remove chatty phrasing and jargon, check headings and bullets, and confirm a busy reader could act on the summary alone.
Options: Do this solo (write and self-review), or swap drafts with a colleague and role-play the decision-maker — read only each other's executive summary and say whether you'd approve it and why.
✅ Task Completion Checklist
- ☐ I chose the right document type and matching structure, with a clear title
- ☐ My executive summary is standalone and covers purpose, findings, and recommendations
- ☐ Each finding/claim is backed by evidence or a reference
- ☐ My recommendations are specific, prioritized, and tied to the findings
- ☐ The register is formal, objective, and jargon-free — clarity over showing off
🎯 Quick Quiz
Question 1: Which best describes a good executive summary?
Question 2: Which recommendation is most likely to get approved?
Tips & Common Mistakes
✅ Do's
- Write the executive summary last and make it stand entirely on its own — assume it's all the reader sees.
- Structure for scanning — clear headings, short paragraphs, bullets, and one point per section.
- Tie every recommendation to a finding — no conclusion or recommendation should surprise a reader who read the body.
❌ Common Mistakes
⚠️ Watch Out
- Density and jargon: the classic document error — long words and complex sentences to sound impressive. Busy readers reward clarity, not effort.
- Vague recommendations: "improve", "consider", "look into" without an action, owner, or deadline get ignored. Be specific and actionable.
- A weak or missing executive summary: burying your conclusions on page 6 means the decision-maker never reaches them. Put the answer up front.
- No structure: a wall of text with no headings forces the reader to hunt. Signpost everything.
📓 Learning Journal
Keep a Business English journal throughout the course. After each lesson, note:
- Key phrases you want to start using at work
- Situations where you could apply the lesson this week
- Things that felt awkward or unclear to revisit
- A real document or decision you'll handle differently now
- Your confidence in professional communication over time
✍️ This lesson's prompt: Think of a report or proposal you've written or received that didn't land — a plan that wasn't approved, or findings that were ignored. Was the executive summary weak, the register too dense, or the recommendations too vague? Note one concrete change you'll make to your next document.
📝 Lesson Summary
🎓 Key Takeaways
- A report presents findings (past/present analysis); a proposal persuades toward a future action — and proposals must sell the benefits.
- Use standard structure with clear headings so busy readers can scan and jump: summary, intro, findings, conclusions, recommendations.
- The executive summary is the most-read part — standalone, purpose + findings + recommendations, written last and read first.
- Documents use a formal, objective, evidence-based register — but clarity beats jargon every time.
- Recommendations that get approved are specific, actionable, prioritized, cost/benefit-aware, and tied to the findings.
🎉 What You've Accomplished
You can now structure a professional report or proposal, write an executive summary a decision-maker can act on, hold an objective and formal register without drowning in jargon, and turn evidence into recommendations that actually get approved. These are the documents that shape budgets, projects, and strategy — and you now have the language to write them well. 🎉
❓ Common Questions at This Stage
How long should a business report or proposal be?
As short as it can be while doing its job — busy readers thank you for brevity. Many workplace documents are 1–4 pages plus appendices. Let the structure, not padding, carry it: if a section adds no decision-relevant information, cut it.
Isn't the passive voice supposed to be bad writing?
In documents it has a real job: "It was found that…" and "The survey was conducted…" keep the focus on findings and lend an objective tone. Use it where it helps objectivity — but don't let it make sentences vague or clumsy. Clarity still wins.
What if I'm not sure whether to include recommendations in a report?
Check what the reader asked for. If they want your judgment, include clear recommendations; if they only want the facts to decide themselves, stop at conclusions. When in doubt, ask — and if you do recommend, keep it a distinct, well-marked section.
🔭 Looking Ahead
You've mastered the documents that move decisions inside an organization. In Lesson 4.2, we turn to the documents that move your career: CVs, cover letters, and job interviews — how to present your experience persuasively, tailor your application, and speak with confidence about your value.
✅ Before the Next Lesson
- Finish drafting your report or proposal, including a standalone executive summary.
- Ask a colleague to read only your executive summary — could they act on it alone?
- Write your Learning Journal entry for this lesson.
🌟 Encouragement for the Journey
The ability to turn a messy situation into a clear, persuasive document is one of the most valued skills in any workplace — and it's entirely learnable. You just built the framework the best business writers use every day. Draft boldly, tighten ruthlessly, and lead with your best point. Your next report will be sharper than your last. See you in Lesson 4.2! 👋