How to Write a Policy Brief

A policy brief is a short, focused document that presents a specific problem, reviews the available evidence, and recommends a course of action to a defined audience — usually policymakers, administrators, or advocacy organizations.

It is not an essay. It is not a research report. The purpose is practical: to inform a decision or prompt an action. Everything in a policy brief — the structure, the tone, the length — is shaped by that purpose.

The defining feature of a strong policy brief is that it respects the reader’s time while giving them exactly what they need to act.

Whether you are writing one for a class assignment, an internship, or a professional role, the fundamentals are the same.

What Is a Policy Brief?

A policy brief is a concise document — usually two to eight pages — that:

• Identifies a specific, current problem
• Summarizes the evidence around that problem
• Presents one or more policy options for addressing it
• Recommends a specific course of action

It differs from a position paper in that it is written for practitioners, not an academic audience. The reader is not grading your argument — they are deciding whether to act on it. That shift in audience changes almost everything about how you write.

Know Your Audience Before You Write

Before you write a single section, identify exactly who will read the brief. A brief written for a state legislator reads very differently from one written for a hospital administrator or a nonprofit board.

Ask:

• What does this audience already know about the issue?
• What decisions do they have the power to make?
• What would convince them — data, cost savings, public opinion, legal risk?
• How much time will they realistically spend reading this?

Policymakers are time-constrained. They often read the executive summary only and skim the rest. Write accordingly: the most important information belongs at the top, not buried in the middle.

Define the Problem with Precision

The problem statement is the foundation of the brief. If it is vague, the rest of the document falls apart.

A precise problem statement:

• Is specific — not “healthcare is expensive” but “uninsured adults in rural counties face emergency room costs averaging three times higher than those in urban areas”
• Is current — uses recent data, ideally from the past two to three years
• Shows scope — how many people are affected, in what way, and over what timeframe
• Is framed in terms the audience cares about — cost, safety, equity, efficiency

Avoid the temptation to describe the history of the issue in depth. One to two sentences of context is usually enough. The reader needs to understand the problem, not study it.

Present the Evidence Without Overloading the Reader

Policy briefs use evidence to establish that the problem is real, that it can be addressed, and that the recommended approach has worked elsewhere or is grounded in reliable research.

Rules for evidence in a policy brief:

• Prioritize clarity over comprehensiveness — a few strong data points beat a wall of statistics
• Name sources in plain text within the document rather than as footnotes the reader will skip
• Use visuals sparingly — one clear chart or table can do what three paragraphs cannot
• Avoid jargon specific to your academic field unless you are certain the audience shares it

The goal is not to show how much you know. The goal is to give the reader confidence that the problem is real and that the solution is based on solid ground.

Lay Out Policy Options

Most strong policy briefs present two to three options for addressing the problem before recommending one. This signals intellectual honesty and helps the reader understand the landscape before they see your recommendation.

For each option, briefly describe:

• What the policy would do
• Its likely benefits
• Its limitations or trade-offs

Keep this section balanced. If every option except your recommendation looks obviously terrible, the reader will sense the framing is manipulated and trust will drop.

Make a Clear Recommendation

This is the core of the document. State your recommendation directly and specifically.

Vague: “Policymakers should consider investing in early childhood education.”

Specific: “The state legislature should expand the existing pre-K subsidy program to include households earning up to 200 percent of the federal poverty level, beginning in the next fiscal year.”

Your recommendation should include what, who, when, and how where possible. A recommendation that is too general gives the reader no path to action.

End the recommendation section with a brief call to action — one or two sentences that tell the reader exactly what you are asking them to do next.

Format, Length, and Presentation

Policy briefs are typically structured as follows:

Section	Typical Length
Title and executive summary	100–200 words
Problem statement	1–2 paragraphs
Evidence review	2–4 paragraphs
Policy options	1 paragraph per option
Recommendation	1–2 paragraphs
References or sources	As needed

Total length depends on context, but two to four pages is the most common target for student assignments and many professional settings.

Use short paragraphs, bullet points where appropriate, and clear section headers. Dense academic prose works in a journal article. It does not work in a policy brief.

Common Mistakes That Weaken Policy Briefs

Starting with background instead of the problem. Readers lose interest before the core issue is stated. Lead with the problem.

Being vague about the recommendation. “More funding” or “increased awareness” are not recommendations. Specificity is what makes a brief actionable.

Ignoring the audience’s constraints. A recommendation that requires a budget the agency does not have, or authority the reader does not possess, is not useful.

Relying on one type of evidence. A brief built entirely on one study or one data source is fragile. Use multiple sources where available.

Forgetting the executive summary. Many readers will only read this section. Write it last, once you know exactly what you are recommending, and make it complete enough to stand alone.

---

A policy brief is only useful if it is read and acted on. Every decision about structure, length, and language should serve that goal. The best brief is not the most thorough one — it is the one that gets a decision-maker from problem to action in the least amount of friction.