Policy Brief

A policy brief is a short document that frames a policy issue, lays out the realistic options, and recommends one of them to a specific decision-maker. Its job is to be read fast and acted on, not to demonstrate the full depth of research behind it — that belongs in a separate report the brief can point to, not repeat.

Key components

• The issue, framed in one paragraph — what the problem is, why it matters now, and who it affects, stated plainly enough that a reader with no prior context understands the stakes immediately.
• The specific options considered — a short, realistic set (often two to four), not every option in the abstract; each stated with its actual tradeoffs, not just its appeal.
• A clear recommendation with its rationale — which option is being proposed and why it beats the alternatives on the criteria that matter to this decision-maker (cost, political feasibility, timeline, risk).
• An executive summary that alone conveys the recommendation — a reader who reads nothing else should still walk away knowing what's being proposed and why; this is usually the first thing written and the last thing trimmed.
• Supporting evidence, kept brief — the key facts and figures that justify the recommendation, with fuller evidence and citations left to an appendix or a linked report rather than crowding the brief itself.

Why writing for a specific, named decision-maker changes the brief

The same underlying issue reads very differently depending on who has to act on it. A minister needs the political and public framing, the headline cost, and a decision they can defend in five minutes; a technical committee needs the methodology, the assumptions behind the numbers, and enough detail to interrogate the recommendation. A brief written for a generic "policymaker" audience tends to satisfy neither reader well — it's too shallow for the technical reviewer and too dense for the time-pressed decision-maker. Naming the actual audience before writing determines what to include, what to cut, and what tone to use throughout.

Common pitfalls

• Buried recommendation — the reader has to reach the last page to find out what's actually being proposed, when the whole point of a brief is that the recommendation is findable in the first paragraph.
• Written for a generic audience instead of the specific decision-maker who will actually read it — a brief that tries to serve everyone ends up serving no one especially well.
• Options presented with no real tradeoff analysis — listing alternatives without weighing their costs, risks, or feasibility makes the final recommendation read as arbitrary rather than reasoned.
• Evidence dump instead of a brief — restating the full research report inside the brief defeats its purpose; a decision-maker who wanted the full evidence base would have read the report.
• No stated timeline or next step — a recommendation with no clear "do this, by when" leaves the decision-maker unsure what action is actually being asked of them.

Learn more

• Freedom of Information Request for one way policy-relevant records get surfaced before a brief is written about them.
• Environmental Impact Assessment and Sustainability Report for two of the underlying evidence sources a policy brief on environmental issues would draw from and summarize, not reproduce.