Advanced English Tutorials | How to Write English Reports and Proposals Clearly

Advanced Report-and-Proposal Diagnostic Lab

Weak functional writing often fails because the student does not understand the document’s job. One report may contain recommendations but no findings; another proposal may describe a problem but never recommend action; another may have the right ideas but hide them inside essay-style paragraphs with no navigational structure.

Use one recent response and label each section aim, background, evidence, finding, problem, recommendation, drawback or conclusion. Missing functions reveal whether the problem is task interpretation, evidence or organisation.

Report, Proposal and Recommendation

A report organises what was observed, researched or found. A proposal moves from a defined situation toward action. A recommendation is the specific action suggested and can appear inside either form when the task requires it.

Students should decide which function dominates before drafting. Otherwise the document can drift between reporting and persuasion without a clear reader pathway.

Read the Role and Audience

Functional writing often gives the writer a role: student representative, committee member, project leader or researcher. That role determines authority, background knowledge and what recommendations are realistic.

Audience matters equally. A principal, class committee and external organisation need different context and levels of explanation.

State the Aim Precisely

The opening should explain what the report or proposal intends to do. “This report examines student use of the library and recommends changes to opening hours” gives the reader purpose and scope immediately.

A vague aim such as “This report is about the library” does not tell the reader what information or decision will follow.

Use Functional Headings

Headings should reflect the reader’s tasks: Findings, Current Problems, Proposed Changes, Drawbacks, Recommendations or Conclusion.

Avoid headings that are merely decorative. Each heading should divide the document into meaningful jobs and make scanning easier.

Background and Scope

Background provides only the context needed to understand the findings or recommendation. Scope defines what was and was not examined.

If a survey covered only Secondary students, the report should not quietly generalise to every student in the school. Scope protects accuracy.

Method or Information Basis

When relevant, state where the information comes from: survey, observation, interviews, source review or consultation.

This helps the reader judge how much confidence to place in the findings and prevents recommendations from appearing unsupported.

Findings Versus Interpretation

Findings state what the evidence shows; interpretation explains what those findings may mean. Keeping them conceptually separate improves clarity.

For example, “62 per cent preferred later opening” is a finding; “this suggests current hours may not match student schedules” is interpretation.

Evidence Selection

Include evidence that helps the intended reader make the decision. A report should not become a data dump simply because more information was collected.

Rank evidence by relevance to the aim. One directly relevant statistic plus a clear explanation may be more useful than five loosely related numbers.

Recommendations Must Trace Back

Every recommendation should be traceable to a problem or finding. If the report finds crowding at lunch, a recommendation about weekend advertising needs an explicit connection or should be removed.

Students can draw arrows from each recommendation back to the evidence. Missing arrows reveal proposals that are intuitive but unsupported.

Proposal Benefits

A proposal should explain what the recommended action is expected to improve: cost, access, learning, participation, efficiency or another criterion.

Benefits should be concrete enough to evaluate later, not vague claims that the proposal will simply “make things better”.

Proposal Drawbacks

British Council proposal guidance encourages writers to acknowledge issues or drawbacks rather than pretend the solution is perfect.

A drawback section can strengthen the proposal when it identifies a real concern and explains how the risk could be reduced or why the benefits still outweigh it.

Formal Tone Without Heavy Language

Reports and proposals often use professional, measured language, but formality should not turn simple ideas into dense nominalisations and passive constructions. “Students reported difficulty finding seats” is clearer than “Difficulty regarding seating availability was reported by students” unless the impersonal form serves a real purpose.

Teach students to prioritise precision and reader access. Formal means appropriate to the audience, not maximally complicated.

Impersonal Constructions

Phrases such as “It is recommended that…” or “The survey indicates…” can keep attention on the action or evidence rather than the writer.

Use these structures strategically. A document made entirely of impersonal passive sentences can feel distant and harder to read.

Reporting Verbs

Reports, indicates, suggests, finds, notes and reveals differ in strength and function. The verb should match the evidence.

If a small survey merely points toward a pattern, “suggests” may be safer than “proves”. Lexical choice is part of evidential accuracy.

Quantitative Findings

Numbers should include enough context to be meaningful: sample size, unit, time period or comparison when relevant.

Do not write “attendance increased by 20” when the reader needs to know whether that means students, percentage points or per cent.

Qualitative Findings

Interview comments, open responses and observations can reveal concerns or experiences that numbers do not show.

Summarise patterns rather than quoting every comment, and distinguish a repeated theme from one isolated opinion.

Tables and Charts in Reports

Visuals can compress data and make comparisons easier, but they should have titles, labels and a clear reason for inclusion.

The prose should interpret the key pattern rather than repeat every value already visible in the chart.

Recommendations by Priority

When several actions are possible, rank them by impact, feasibility, cost or urgency.

A proposal becomes more useful when the reader can see which recommendation should happen first and why.

Feasibility

A proposal should consider whether the recommended action can realistically be implemented with available time, staff, budget or rules.

Students should not recommend an ideal solution that ignores the practical constraints described in the same document.

Costs and Trade-Offs

Recommendations often produce benefits and costs. A longer opening hour may improve access but require staffing; a digital system may reduce printing while creating setup needs.

Naming the trade-off makes the proposal more credible and creates a basis for judgement.

Addressing Drawbacks

A drawback section should do more than list problems. Explain whether the drawback can be reduced, accepted or offset by a larger benefit.

This turns limitation into evaluation rather than a reason to abandon the proposal automatically.

Conclusions in Reports

A report conclusion should summarise the central findings and, when required, the most important implication.

Avoid converting the conclusion into an essay-style reflection unrelated to the stated aim.

Conclusions in Proposals

A proposal conclusion should make the recommended action unmistakable and show why it follows from the earlier evidence, benefits and drawbacks.

The strongest ending usually sounds decisive but proportionate, not exaggerated.

Recommendations Versus Orders

Students should distinguish persuasive recommendation from command. Could, should, it is recommended that and must carry different force.

Choose language that matches the writer’s role and authority. A student committee may recommend changes it cannot order.

Section Balance

Some reports spend most of their space on background and leave only a few lines for findings and recommendations.

Allocate space according to the task. If the reader needs a decision, evidence and evaluation deserve more space than scene-setting.

Worked Example: School Library Report

A school library report may begin with an aim: examine lunchtime use and identify barriers. The evidence could include observation counts and a short student survey. Findings might show that demand is highest on two days and that seating, rather than book access, is the main complaint.

The conclusion should summarise those findings. If a recommendation is required, it might propose extending overflow seating on peak days. The recommendation is credible because it traces directly to observed demand.

Worked Example: Proposal for a Digital Newsletter

A proposal can begin by stating the aim and current problem, then explain the proposed digital format, expected benefits, possible drawbacks and a final recommendation. This mirrors the functional structure used in British Council proposal materials.

A useful drawback might be access or data privacy. The proposal becomes stronger when it acknowledges the issue and explains mitigation instead of pretending the solution has no cost.

Worked Example: CCA Participation Report

Suppose a survey finds that students value CCAs but cite timing conflicts and transport as barriers. The report should distinguish the measured findings from possible explanations.

A recommendation to change dismissal arrangements should only appear if the evidence supports that connection. Otherwise, the document should state what additional information is needed before recommending action.

Worked Example: Proposal With Competing Options

A school may consider either extending library hours or adding an online booking system. A strong proposal can compare cost, expected impact and feasibility before recommending one option or a phased combination.

The writer should state the decision criterion. Without a criterion, “Option A is better” remains a preference rather than a justified proposal.

Report From Observation

Observation reports should distinguish what was directly seen from interpretation. “Ten students waited for computers” is observation; “the computer area is under-resourced” is an interpretation that may be reasonable but needs wider context.

This distinction connects report writing with fact/evidence reasoning and prevents observations from becoming unsupported conclusions.

Report From Survey Data

Survey reports should name who responded and what questions were asked when those details affect interpretation. A result from twenty volunteers should not be described as the view of the entire school without qualification.

Students should use phrases such as “among respondents” when scope matters. Formal writing becomes stronger when it accurately represents evidence limits.

Proposal Based on Consultation

A proposal may combine survey results, interviews and practical constraints. Different source types can support different parts of the recommendation.

For example, surveys may show demand while staff interviews reveal feasibility. The proposal should synthesise these sources rather than treat every item as identical evidence.

Proposal Language for Benefits

Useful phrases include “would allow”, “could reduce”, “is likely to improve” and “would provide”. The modal choice should match certainty.

Students should avoid promising guaranteed results when the proposal has not yet been tested. Recommendations can be strong without being absolute.

Proposal Language for Drawbacks

Phrases such as “one limitation is”, “a possible concern is” or “this would require” help present drawbacks neutrally.

The next sentence should explain whether the concern can be addressed and how it affects the final judgement.

Report and Proposal Revision

After drafting, read only the headings. They should reveal a logical document: aim, evidence or findings, evaluation, recommendation and conclusion as required.

Then check whether each section contains only material that belongs under that heading. Misplaced material is a common cause of repetition and unclear function.

Report and Proposal Editing

Once structure is stable, check names, numbers, dates, units, source references and recommendation wording before general grammar polishing.

Functional writing can fail because one factual detail is wrong even when the sentences are grammatically elegant.

Final Transfer Standard

A strong learner can receive an unfamiliar functional-writing task, identify whether the reader needs findings, recommendations or both, and select a structure accordingly.

The student can use evidence, acknowledge limitations, make a proportionate recommendation and close the document clearly without relying on one memorised template.

A Report-and-Proposal Planning Grid

Before drafting, divide the task into five boxes: reader, aim, evidence, required sections and decision. Under reader, note what the audience already knows and what authority the writer has. Under aim, state whether the document is reporting findings, recommending action or doing both. Under evidence, list the strongest source material. Under sections, choose the functional headings. Under decision, write the recommendation or conclusion the document may be able to support.

This grid prevents two common failures: essay-like reports with no navigational structure and proposals whose recommendation appears before the problem has been established. The planning language can remain brief; its purpose is to clarify function before sentences begin.

Report-and-Proposal Practice Under Time

Timed practice should begin with section planning. Give the learner a short source pack and five minutes to produce headings, one evidence item under each relevant heading and a provisional recommendation. Then draft. The structure should make it possible to write section by section without repeatedly rereading the entire source pack.

During checking, read only the headings and first sentence of each section. They should reveal the document’s logic. Then verify exact figures, dates and recommendation language. This functional check is more useful than treating a report like a continuous essay and proofreading it only sentence by sentence.

Parent Report-and-Proposal Checklist

• Is the aim explicit and appropriate to the task?
• Do the headings reflect real functions rather than decoration?
• Are findings distinguished from interpretation and recommendation?
• Can every recommendation be traced to evidence or a defined problem?
• Are drawbacks or constraints acknowledged where relevant?
• Does the conclusion make the required next action or finding clear?

Final Functional-Writing Standard

A strong student can receive an unfamiliar reporting or proposal task, identify what the reader needs, choose functional sections, use evidence accurately, distinguish findings from recommendations and close with a proportionate decision. The writing remains professional without becoming heavy, and the structure makes the information easy to act on.

Reports and Proposals in Real Tasks

Reports and proposals become easier when students see them as decision documents. A report helps a reader understand what was found; a proposal helps a reader decide what to do. Many school tasks combine the two: gather evidence, interpret it and recommend a response. The writer should still keep the stages visible so findings are not disguised as recommendations.

Consider a report on student use of a study area. Observation may show heavy use after school, while survey comments identify noise as the main concern. A clear report presents those findings before recommending quieter zones or adjusted supervision. If the recommendation appears first, the reader cannot judge whether it responds to the evidence.

A proposal about extending opening hours creates a different problem. The writer needs to explain the benefit, likely users, staffing implications and any drawback such as cost or security. A strong recommendation might propose a limited trial period rather than a permanent change if the evidence is promising but incomplete. That is a more proportionate use of evidence than claiming the extension will definitely succeed.

Students should also learn to distinguish a recommendation from an implementation plan. “Extend access on Tuesdays and Thursdays” is a recommendation. A detailed schedule assigning staff and rooms begins to move into implementation. Include only the level of operational detail the task and reader require.

Reports and proposals often reward navigability. Headings, short paragraphs, tables or bullet lists can help when they match the information. But formatting cannot repair weak reasoning. A beautifully structured proposal with no evidence-linked recommendation remains weak.

For final checking, trace every recommendation backward and every important finding forward. The recommendation should connect to evidence; the evidence should have a reason for being included. This two-direction audit exposes orphan facts and unsupported proposals quickly.

The transferable skill is functional judgement: identify what the reader needs to know, what the evidence permits the writer to conclude and what action can reasonably be recommended. When those decisions are clear, language and formatting become much easier to control.