Your research is sound. The evidence is thorough. The recommendations are well-reasoned. And the policy brief sits unread in someone's inbox.
This is not unusual. It is, in fact, the default outcome for most policy briefs produced by research organizations, think tanks, and NGOs. The problem is almost never the quality of the research. The problem is almost always structural — the document is built to satisfy the researcher rather than serve the reader.
Policy audiences are not passive. A minister's adviser, a parliamentary researcher, or a senior official at a multilateral institution encounters dozens of documents each week. They make decisions about what to read within the first thirty seconds. If your brief does not answer their question in that window — what is this about, why does it matter to me, and what are you asking me to do — it will not get past the first page.
Below are the five most common structural problems we encounter when editing policy briefs, along with practical guidance on how to address each one.
1. The executive summary is an introduction, not a summary
The most common structural error in policy briefs is treating the executive summary as a preamble — a place to introduce the topic, explain the context, and set up the argument that follows. This is the wrong approach.
An executive summary should function as a standalone document. Many of your readers will read it and nothing else. A minister preparing for a committee hearing does not have twenty minutes for your full brief. An adviser writing a background note needs the core argument and the key recommendations immediately.
A well-written executive summary does four things: it states the problem clearly, presents the key finding or position, gives the two or three most important recommendations, and indicates who those recommendations are directed at. It does not summarize your methodology. It does not introduce the organization that produced it. It does not begin with background that the reader already knows.
Test: Give your executive summary to someone unfamiliar with the topic. Ask them: what does this organization want the government to do, and why? If they cannot answer in under a minute, the summary is not working.
2. The recommendation is buried
Research briefs are typically written in the order the research was conducted: context first, evidence second, analysis third, conclusion last. This is logical from a research perspective and almost always wrong for a policy audience.
Policy readers want to know your conclusion first. They will read your evidence and analysis in order to evaluate whether they agree with it — but only if they already know what you are arguing. A brief that makes the reader wait until page eight for the central recommendation will, in most cases, not be read past page three.
The fix is structural inversion. State your position at the start. Then present the evidence that supports it. This is the structure of every effective policy document from government white papers to IMF working notes. It feels uncomfortable to researchers trained in academic writing, where conclusions come last. But policy writing is not academic writing, and applying academic structure to a policy brief is one of the most reliable ways to ensure it goes unread.
3. The document has no identifiable audience
A policy brief aimed at everyone reaches no one. The specificity of your audience should determine the specificity of your language, the level of assumed knowledge, the tone of your recommendations, and the degree of diplomatic hedging in your conclusions.
A brief intended for a parliamentary committee operates differently from one intended for a ministry official, which operates differently from one aimed at a multilateral negotiating team. These differences are not cosmetic. They affect which arguments to lead with, which evidence to emphasize, how technical the language should be, and how directly the recommendations should be phrased.
Before editing or revising a policy brief, the first question to answer is: who is the specific person or group that this document is trying to reach, and what decision are they being asked to make? If the answer is vague — policymakers generally, or the development community — the brief will reflect that vagueness in every section.
4. The language is passive where it should be direct
Policy writing in research institutions tends toward the passive voice. Findings "were identified." Recommendations "are proposed." Action "should be considered." This construction is common in academic writing, where it signals objectivity and appropriate epistemic caution. In a policy brief, it is a liability.
Passive constructions place distance between your evidence and your conclusions. They make your recommendations sound tentative and make the document harder to act on. A policymaker reading "consideration should be given to revising the subsidy structure" faces a different decision than one reading "the government should revise the subsidy structure." The first construction requires interpretation; the second does not.
This does not mean abandoning precision or overstating certainty. It means reserving passive and hedged language for situations where genuine uncertainty exists, and using direct, active constructions everywhere else. The evidence either supports the recommendation or it does not. If it does, say so plainly.
5. The brief is too long
Most policy briefs we edit are too long. Not slightly too long — structurally too long, in a way that reflects the difficulty of cutting rather than the necessity of the content.
A policy brief is not a place to demonstrate the depth of your research. That is what the full report is for. A brief should present the argument and recommendations with enough evidence to be credible and enough concision to be read. For most topics, this means two to four pages for the brief itself, with a one-page executive summary at the front and references or supporting data in an annex.
The most reliable test for whether a section belongs in the brief is to ask: if a reader skips this, do they lose something essential to understanding the recommendation? If the answer is no, the section belongs in an annex or not at all.
Length is a structural problem, not a writing problem. You cannot fix it at the sentence level. Cutting a ten-page brief to four pages requires decisions about what the brief is fundamentally trying to do — which is why this kind of revision often benefits from an editor who can read the document as the intended audience would, rather than as the researcher who produced it.
A practical note
The five problems above are structural. They cannot be resolved by proofreading or sentence-level editing. Fixing them requires either a structural revision — working through the document's architecture before addressing the prose — or a rewrite in which the source material is retained but the document is rebuilt around the argument rather than the evidence trail.
If you are unsure whether your brief has structural problems, the fastest diagnostic is a free sample edit. We return a marked-up sample with a service recommendation within two business days, at no charge. No commitment required.