Writing a Policy Brief for Policymakers

A policy brief is one of the few research outputs written for an audience that will not read the underlying paper. For researchers and the research-administration staff who support dissemination and impact reporting, writing one well is a distinct skill from academic writing — and increasingly one that funders and impact-assessment frameworks expect institutions to be able to produce evidence of. This guide covers the research-to-policy translation task specifically: what a policy brief is as a genre, how its structure differs from a journal article or a plain-language summary, and where it fits into funder dissemination requirements and institutional impact evidencing.

What a policy brief is, and what it isn’t

CASRAI’s dictionary defines a policy brief as a short document — typically 2–8 pages — that synthesizes research evidence for a policymaker audience, states explicit policy implications or recommendations, and is structured for accessibility rather than for academic readers. That last point is the operative distinction: a policy brief is not a shortened journal article. It assumes the reader has policy expertise but not subject-matter expertise, has limited time, and needs to know what the evidence implies for a decision they are responsible for — not how the study was designed or why the methodology is sound.

It is worth being precise about neighboring genres, because they get conflated in practice:

Policy brief vs. white paper: a white paper is typically longer, more comprehensive, and often argues for a position or approach across a broader problem space; a policy brief is short, action-oriented, and usually tied to a specific, near-term decision.
Policy brief vs. discussion paper: a discussion paper is exploratory and open-ended, often circulated to invite feedback before a position is settled; a policy brief presents a conclusion and a recommendation.
Policy brief vs. plain-language summary: both simplify academic language, but a plain-language summary is written for a general public or patient audience and typically doesn’t make a policy recommendation; a policy brief is written for someone with institutional authority to act, and the recommendation is the point. See CASRAI’s separate guide on writing plain-language summaries if that’s the output you actually need.

The concept most directly behind the skill of producing any of these is knowledge translation (KT) — the broader practice of moving research findings into a form usable by non-academic decision-makers. A policy brief is one KT output among several; a policy brief aimed at legislators reads differently from one aimed at a hospital administrator or a school district, even when it summarizes the same underlying study.

Why this belongs in research administration, not just communications

Policy-brief writing sits at the intersection of a researcher’s subject expertise and an institution’s dissemination and impact-evidencing obligations, which is why it’s increasingly a research-office concern rather than a purely researcher-driven or purely PR-driven task:

Funder dissemination plans. Major funders require a dissemination plan as a condition of award, and policy briefs are one of the output types those plans commonly name alongside plain-language summaries, conference presentations, and toolkits. CASRAI’s guide to funder dissemination requirements covers how SSHRC, Horizon Europe, and NIH frame this obligation in more depth — this page picks up where that one leaves off, on the specific craft of producing a policy-facing document.
REF impact case studies (UK). The Research Excellence Framework assesses non-academic impact on two dimensions — reach and significance — and impact case studies need concrete evidence that a change or benefit occurred as a result of the underlying research being disseminated, not just that dissemination happened. A policy brief that a government department cites, adopts language from, or that demonstrably informed a consultation response is a recognized, citable form of that evidence; the brief itself is rarely sufficient on its own; it typically needs to be paired with corroborating evidence of the policy’s actual influence (a citation in a white paper, a testimonial, a change in guidance).
Broader-impact and pathways-to-impact statements. Funders such as NSF ask applicants to describe how a project’s findings will reach the people positioned to act on them; a track record of, or credible plan for, policy briefs is one concrete way to make that section specific rather than aspirational. See CASRAI’s guide on NSF broader impacts review criteria.
Institutional knowledge-exchange and public-affairs offices. Many universities now have a dedicated knowledge-exchange, public-affairs, or research-impact office that reviews or co-drafts policy-facing outputs before they go to a minister’s office or a legislative committee — both to sharpen the framing and to make sure institutional and funder attribution requirements are met. Researchers writing a first policy brief should generally route it through that office rather than sending it externally unreviewed.

Structure: what a policy brief actually contains

There is no single universal template, but independent guidance from research-to-policy organizations — the Overseas Development Institute (ODI), Canada’s International Development Research Centre (IDRC), and WHO’s SUPPORT Tools for evidence-informed health Policymaking — converges on a consistent shape:

Title and one-line takeaway. A policymaker should be able to tell what the brief is about, and what it wants them to do, from the title and first line alone.
Executive summary / key messages. Usually the top of page one, in a box or bulleted format — often the only section a busy reader gets to. State the issue, the finding, and the recommendation in three or four sentences.
Context / the problem. Why this issue matters now, in terms the reader’s own priorities recognize — not why it’s academically interesting.
Evidence. What the research actually found, presented as findings rather than methods. Methodology belongs in a footnote or an appendix reference to the underlying paper, not the body.
Implications and recommendations. The section that distinguishes a policy brief from a research summary. Recommendations should be specific, feasible within the reader’s actual authority, and clearly flagged as recommendations rather than blended into the findings.
Sources / further reading. A short reference list or link to the full study, not a full academic bibliography.

Typical length is 2–4 pages for a legislative or agency audience, occasionally up to 8 for a more technical policy readership; length itself is a design choice signaling how much of the reader’s time you’re asking for, so shorter is usually the safer default for a first brief.

Translating findings: the actual craft

The skill gap between “can write a good paper” and “can write a good policy brief” is almost entirely about register and framing, not content:

Lead with the finding, not the study. Academic writing builds up to a conclusion; a policy brief states the conclusion first and uses the rest of the document to support it.
State certainty honestly, without hedging in academic register. Phrases calibrated for a peer-reviewer audience (“results suggest,” “may indicate”) read as noncommittal to a policymaker. State what the evidence supports plainly, and be explicit and specific about genuine limitations or open questions rather than relying on academic hedge-words to carry that nuance — a policymaker needs to know what to weigh, not decode a register they weren’t trained to read.
Separate evidence from recommendation, visibly. Use a heading or visual break between “what we found” and “what we recommend” so a reader (or a committee staffer skimming for talking points) can’t misattribute a normative claim as a data point, or vice versa.
Write for the decision, not the discipline. Cut anything that doesn’t bear on the reader’s actual choice — disciplinary debates, competing theoretical framings, and citation of adjacent literature belong in the paper, not the brief.
Use plain language without oversimplifying the finding itself. Removing jargon is not the same as removing precision; a number, a comparison, or a specific mechanism is usually more persuasive to a policy reader than a qualitative generalization.

Common mistakes

Submitting a condensed abstract instead of a brief. Cutting a paper down to two pages preserves academic structure and register; it doesn’t produce a policy brief.
Recommendations that aren’t actionable by the actual reader. “More research is needed” or a recommendation aimed at a different level of government than the intended reader wastes the one thing a policy brief has to offer.
No single point of contact. A brief that doesn’t name a person or office the reader can follow up with functions as a document, not as the start of an engagement.
Skipping institutional review. A brief that goes out under the institution’s name without knowledge-exchange or communications review can create attribution, framing, or lobbying-disclosure problems the individual researcher isn’t positioned to see.

Frequently asked questions

Do funders require policy briefs specifically, or just “dissemination”?

Most funder dissemination-plan requirements name policy briefs as one acceptable output among several (plain-language summaries, toolkits, conference presentations, stakeholder workshops), rather than mandating the format itself. See CASRAI’s guide to funder dissemination requirements for how specific funders phrase this.

Does a policy brief count as evidence in a REF impact case study?

It can contribute, but on its own it typically demonstrates only that dissemination occurred, not that a policy changed as a result. REF impact assessment weighs reach and significance, and case studies need corroborating evidence — a citation, a testimonial, a documented change in guidance — that the brief actually influenced a decision, not just that it was produced and sent.

How is a policy brief different from a lay summary or plain-language summary?

Both simplify academic language for a non-specialist reader, but a plain-language summary is typically written for the public or research participants and doesn’t make a policy recommendation. A policy brief is written for someone with institutional authority to act, and the recommendation is the core content, not an optional add-on.

Who should review a policy brief before it goes out?

Practice varies by institution, but a knowledge-exchange, public-affairs, or research-impact office — where one exists — is the typical review point before a brief goes to an external policy audience, both for framing and for institutional attribution/compliance reasons.

How long should a policy brief be?

Most guidance from research-to-policy organizations converges on roughly 2–4 pages for a general policy audience, with up to about 8 pages acceptable for a more technical or specialist policy readership. Longer than that starts to function as a report rather than a brief.

Related CASRAI resources: research impact, policy impact, NSF broader impacts statements, and the scholarly writing pillar for the full cluster of researcher-facing writing guides.