How to Create Accessible Research Findings Summaries for Policymakers

Accessible research findings summaries for policymakers: what actually gets read

I have watched a senior civil servant pick up a 40-page research report, flip to the executive summary, read four lines, and put the whole thing in the recycling bin. Twenty minutes later she quoted a two-page brief from a different team, chapter and verse, in a meeting with her minister. Same evidence quality. Completely different outcome.

That moment reshaped how I think about accessible research findings summaries for policymakers. The research was never the problem. The container was.

Here is the thing most academics and analysts miss: a policymaker is not a slow reader. She is a reader with roughly eleven minutes and four competing briefings on her desk. Your job is not to simplify your findings until they are harmless. Your job is to make them usable under time pressure.

What makes a research summary genuinely accessible (and what doesn't)

Most teams interpret "accessible" as "shorter and friendlier." That is half right and dangerously incomplete.

Accessibility for a decision-maker has three layers, and they stack. First, structural accessibility: can I find the recommendation in under ten seconds? Second, cognitive accessibility: can I follow your reasoning without holding four caveats in my head at once? Third, political accessibility: can I defend this position in a hostile room without you standing next to me?

Layer three is the one researchers forget. I once wrote a brief recommending a phased rollout of a licensing change. The evidence was solid. What I had not done was anticipate that a stakeholder group would read the phasing as an admission the policy was unworkable. The recommendation got quoted back at the minister as evidence of weakness. Painful lesson. Now I always ask: who will attack this, and with what?

The eleven-minute test

Print your draft. Hand it to someone who knows nothing about your project and give them eleven minutes. Then take it away and ask what you recommended and why. If they cannot answer both, restructure.

Cutting without losing rigour

You can drop almost all of your methodology from the main brief. Not because it does not matter, but because it belongs in an annex. What you cannot drop is the boundary of your claim. Remember: a policymaker who over-applies your finding because you overstated it will blame you, not herself.

• Keep: sample size, the single biggest limitation, the direction of the effect
• Move to annex: instrument design, robustness checks, literature positioning
• Never cut: the sentence that says what your evidence cannot tell them

The anatomy of a brief that gets used

There is no universal template, and anyone selling you one is selling you something. But effective briefs share a skeleton.

Section	Length	What it must answer
Title and one-line bottom line	1 line	What should change?
Why this, why now	3-4 sentences	What decision is pending?
What the evidence shows	Half a page	What do we actually know?
Options	Half a page	What are the plausible choices?
Recommendation	2-3 sentences	Which one, and why
Limits and risks	3-5 lines	Where could this go wrong?

Notice what is missing: no literature review. No abstract. No "introduction." Every section earns its space by answering a question the reader already has.

The bottom line up front

The single highest-return edit I make to any draft is moving the recommendation to the top. Not because readers are lazy, but because a reader who knows your conclusion reads your evidence differently. She is checking, not discovering. That is a faster mode of reading, and it is the mode you want.

Why options matter more than answers

Policymakers rarely want a single answer delivered with confidence. They want a defensible set of choices with the trade-offs named. If you present one option, you have written advocacy, not analysis. If you present five, you have written a menu nobody ordered.

Two or three real options. Each with a cost, a beneficiary, and a loser.

Who actually writes these things?

Short answer: not one profession. In my experience the authorship splits roughly into four groups, and each writes a recognisably different document.

• In-house analysts in ministries and agencies, often the strongest on political feasibility and weakest on evidence presentation
• Academic researchers funded to demonstrate impact, usually excellent on rigour and shaky on brevity
• Think tank staff, who write the most polished briefs and sometimes the most agenda-driven ones
• Consultants and evaluation firms, whose briefs are technically competent and frequently too long because the client paid by the page

The best brief I have read in the past two years came from a junior analyst in a regional authority. Six hundred words. Three options. One caveat. It changed a procurement rule.

Email, PDF, or one-pager: the distribution question nobody asks early enough

You can write the finest brief in your organisation and still lose, because you sent it as a PDF attachment at 6pm on a Friday.

Distribution is not an afterthought. It is half the work. What I have learned, mostly by getting it wrong:

• The body of an email outperforms an attachment for the first contact. Paste the bottom line directly into the message.
• PDFs get printed. If your brief is designed for screen only, it will look broken on paper, and paper is still where committee preparation happens.
• A one-page version is not a dumbing-down. It is the version that gets forwarded.
• If your organisation has a legislative calendar, work backwards from it. Two weeks before a hearing is worth more than two months before one.

I once delivered a brief three days after the relevant committee had met. The analysis was better than the alternative that was tabled. It did not matter. The window had closed.

Policy brief versus plain-language summary: getting the genre right

These get conflated constantly, and the confusion produces documents that serve neither audience.

A plain-language summary explains what your research found, for anyone curious. It is descriptive. Its reader wants to understand.

A policy brief argues what should be done, for someone who can decide. It is prescriptive. Its reader wants to act.

You can write both from the same evidence base, and often you should. But if you hand a decision-maker a plain-language summary and call it a brief, you will get a polite question about what you are actually recommending. If you hand a curious member of the public a prescriptive brief, you will get a complaint that you are telling people what to think.

One more distinction worth holding onto: a brief is not a report with the margins narrowed.

Quick self-check before you hit send

• Can a reader state your recommendation after reading only the first paragraph?
• Is every figure either from your own analysis or framed as a general order of magnitude?
• Have you named the strongest counter-argument yourself?
• Does the document work if it is printed in black and white?
• Would you be comfortable if it were leaked?

The three failure modes I see most often

Hedging to the point of uselessness. Every claim qualified until nothing is claimed. Academic training rewards this. Decision-making punishes it. State your finding, then state its limits in one place.

Recommendations that are actually wishes. "Greater coordination between agencies would be beneficial." That is not a recommendation. A recommendation names an actor, an action, and a timeframe.

Burying the counter-evidence. If your brief is challenged on a point you knew about and omitted, you lose not just the argument but your credibility for the next five briefs. Name the weakness first. It costs you three lines and buys you years.

None of this is complicated. It is just not what most researchers were trained to do, so it feels harder than it is.

What I would tell you if you asked me tomorrow

The distance between research that sits in a repository and research that changes a rule is almost never about quality. It is about whether someone, at 8:40 in the morning, with a meeting at nine, could find your recommendation and feel confident enough to repeat it out loud.

Write for that person. Not the version of her you wish existed, who has an afternoon free and a taste for regressions. The real one, with the recycling bin within arm's reach.

And when you next draft a brief, ask yourself the question that has saved me more times than any template: if the only sentence that survives is the first one, is it the sentence I would choose?