Written and maintained by CASRAI Editorial Board
Published · Last updated
On this page
A recommendation in a report is a specific action you advise a named reader to take, based on what your findings showed. This page gives a fillable template, a complete fictional example, weak-versus-strong rewrites and a checklist. The guidance draws on two published writing guides: the MSF Evaluation Unit’s “How to write recommendations” (2019) and the Hong Kong Polytechnic University English Language Centre’s “Report Writing: Recommendations” (last updated 23 September 2014). Where the two differ, the difference is stated rather than smoothed over.
What a recommendation is, and how it differs from a conclusion
A recommendation tells someone what to do; a conclusion says what you think the evidence shows. The MSF guide puts it this way: conclusions are “what you are surmising on the basis of your evaluation”; recommendations are “what you are advising others to do on the basis of the evaluation”. It advises against mixing the two, and says to make a recommendation only if there is something concrete to say, with general observations going in the conclusions. The Polytechnic University guide describes recommendations as suggestions for solving a problem or taking advantage of an opportunity, placed as the last main section, after the Conclusion and before any appendices.
If you are writing a research paper rather than a report, the closing section works differently; see how to write a conclusion for a research paper.
Template for a recommendation
Each recommendation can be built from the same five slots. Fill every slot, and delete any recommendation you cannot fill.
- Link to the finding. A short phrase pointing back to the problem: “In view of [finding],” or “Because [finding],”.
- Action. One verb-led instruction: “[Audience] should [do what]”.
- Owner. The person or group who would carry it out.
- Timing or measure. A date, a deadline or a result that shows it worked.
- Something new. A recommendation that the report’s earlier sections have not already made.
Opening the whole section with one sentence that links back to the Conclusion, then numbering or bulleting the items, is the pattern the Polytechnic University guide describes.
Filled example (fictional)
All names, figures and findings below are invented for illustration. They describe no real organisation or study.
Context: a fictional report on a “Northfield Community Library” evening study-room pilot.
Conclusion (not a recommendation): The pilot’s study rooms were used mostly by students, and users reported that the booking page was hard to find.
Recommendations
Given the booking problems reported in the user survey, the following actions are advised.
- Because most survey respondents could not find the booking page, the library’s web team should add a “Book a study room” button to the homepage before the next term begins.
- In view of the low weekday-evening use, the operations manager should trial a later opening time on two weekday evenings and review the usage counts after eight weeks.
- To check whether the changes work, the project lead should repeat the same survey at the end of the following term and report the results to the steering group.
Each item names an owner, an action and a way to tell whether it happened. None repeats a conclusion.
Weak versus strong wording
| Weak | Stronger | Why |
|---|---|---|
| All sectors need to work together in future emergencies. | Create a strategy for responding to an emergency that has input from every sector, and is produced collaboratively. | The MSF guide gives this pair: the first is wishful thinking, the second is an action. |
| The booking page should be improved. (fictional) | The web team should add a “Book a study room” button to the homepage before term starts. (fictional) | The stronger version names who, what and when. |
| Staffing is a problem and more research is needed. (fictional) | The operations manager should compare evening staffing against usage counts for eight weeks. (fictional) | A general observation belongs in the conclusions; a recommendation needs something concrete. |
The MSF guide also asks writers to be directive but not prescriptive, and not to sacrifice clarity for brevity.
Wording: should, could and the verb after recommend
The Polytechnic University guide suggests “should” for confident recommendations and “could” for less certain ones, and “would” or “will” when describing confident results. It also notes that business recommendations are typically less tentative than academic ones. On verbs, it prefers “I recommend changing” or “I recommend that we change” over “I recommend to change”. Recommend, suggest and propose are all acceptable verbs.
Checklist for recommendations
- Does each recommendation answer a finding that appears earlier in the report?
- Is each one an action, with a verb, rather than a general wish?
- Does each name who should act?
- Is there a date or a measure that shows it was done?
- Have conclusions been kept in the conclusions section?
- Does each say something new rather than repeating the findings?
- Are the recommendations realistic for the resources of the people who must act? The MSF guide calls them “not a shopping list but a practical guideline for action”.
- Could a reader who skipped the rest of the report still understand them?
The Polytechnic University guide also lists content checks: weigh cost against benefit and the opportunity cost, look for the root cause rather than the symptom (for example with “5 Whys”), and test whether a recommendation is SMART (specific, measurable, achievable, result-oriented, time-bound).
Where recommendations sit and how long they run
Both guides place recommendations after the conclusions. The Polytechnic University guide says the section is usually longer than the Conclusion and shorter than the Findings. The MSF guide, written for evaluation reports, advises no more than two pages. These are conventions of two named guides, not universal rules; check your own template, funder or instructor first. The same applies to formatting: the Polytechnic University guide says to number each recommendation, while the MSF guide prefers bullet points to numbers. Follow whichever your reader expects.
For related report sections, see limitations versus delimitations and the dictionary entries for a final report and a technical report.
Making recommendations for different audiences
If different readers must act, the MSF guide advises grouping recommendations by stakeholder or by theme, using as few subheadings as possible and avoiding abbreviations. It also says to address any systemic issue at the start of the section and not mention it again. This makes the examples above easy to scale: one subheading per owner, each with its own numbered list.
Frequently asked questions
What is an example of a recommendation in a report?
“Because most survey respondents could not find the booking page, the library’s web team should add a ‘Book a study room’ button to the homepage before the next term begins” (fictional). It links to a finding, names an owner, states an action and gives a deadline.
How do I write recommendations in a report?
Start from your conclusions, write one action per finding, name who should act and when, and cut any item that is only a general observation. Use the template and checklist above.
Where do recommendations go in a report?
After the conclusions and before the appendices, according to the Polytechnic University guide.
How long should the recommendations section be?
The MSF guide sets a limit of two pages for evaluation reports. The Polytechnic University guide says only that it is usually longer than the Conclusion and shorter than the Findings.
Sources
- MSF Evaluation Unit, “How to write recommendations” (Writing recommendations, 2019, PDF), checked 29 October 2026: https://evaluation.msf.org/sites/default/files/2021-12/VEU%20Writing%20recommendations%202019.pdf
- English Language Centre, Hong Kong Polytechnic University, “Report Writing: Recommendations”, last updated 23 September 2014, checked 29 October 2026: https://elc.polyu.edu.hk/CILL/eiw/report_recommendations.aspx







