Why the distinction matters
A research finding answers a question about the material you examined. A recommendation proposes an action. Both may belong in a report, but they do different jobs. Readers need to know whether a sentence describes evidence, interprets its meaning, or asks someone to make a decision.
Imagine a team reviewing feedback about a training guide. “Several participants could not locate the practice exercises” is a finding if the feedback supports it. “Move the exercises to the start of each chapter” is a recommendation. The first statement reports an observed problem; the second selects one possible response. Putting them in the same sentence without a clear transition can make the proposed fix sound as though it was tested, even when it was not.
Build a visible path from evidence to action
A useful structure has four parts: the question, the finding, the interpretation, and the recommendation. The question defines what you investigated. The finding states what you observed and where the evidence came from. The interpretation explains why the finding may matter. The recommendation names an action worth considering. Keeping those parts visible lets readers agree with the evidence while still questioning the proposed action.
For example: “We asked where readers had trouble using the guide. In feedback from the people who reviewed this draft, locating the exercises was a recurring difficulty. This suggests the current placement may interrupt practice. Consider moving the exercises closer to the relevant instructions, then check whether readers can find them more easily.” The recommendation follows from the finding, but its wording does not pretend that the suggested change has already worked.
Write findings without slipping into advice
In a findings section, state the scope before stating the result. Identify what was examined, whose responses were included, or which documents were compared, as appropriate. Then describe the pattern in terms the evidence supports. “Interviewees described the instructions as difficult to follow” is narrower than “The instructions are unusable for everyone.” If people disagreed or the material was limited, say so rather than smoothing the disagreement away.
Watch for action verbs hidden inside apparent findings. “The team needs a shorter form” sounds like a result, but “needs” introduces a judgment about the solution. A more careful finding would be: “Participants reported skipping questions near the end of the form.” You can then explain possible interpretations before suggesting a shorter form. This separation is especially helpful when the same finding could support several responses, such as shortening the form, changing its order, or clarifying why each question is asked.
Make recommendations conditional and specific
A recommendation should identify who could act, what they could change, and what problem the change is meant to address. “Improve communication” gives a reader little to evaluate. “Ask the project team to add a short explanation of each required document to the application checklist” is more concrete. Specificity also exposes assumptions: the proposed change helps only if unclear document requirements are a meaningful source of difficulty.
Match the strength of the recommendation to the strength of the evidence. When evidence is limited, propose a reversible step or a test rather than a sweeping change. For instance, if a small set of reviewers struggled with the checklist, you might recommend trying revised wording with another group before adopting it broadly. This does not make the recommendation weak; it makes the decision proportional to what is known.
Use the report layout to prevent confusion
Separate headings for “Findings” and “Recommendations” provide a simple safeguard, but labels alone are not enough. Give each recommendation a clear link to the finding it addresses. A brief table or paired list can work when there are many items, provided each entry states the evidence plainly and avoids presenting an untested benefit as a result.
Before sharing the report, read each claim as a skeptical reader would. Can you tell what was observed, what was inferred, and what is being proposed? Could someone accept the finding but choose a different action? Have you named an important limitation or an alternative explanation? If the answers are clear, your report gives readers more than a conclusion: it gives them a way to judge the decision for themselves.
