How to Write a Policy Brief That a Legislator Will Actually Read
Most guides on how to write a policy brief include an executive summary, a methodology section, and a conclusion. What you end up with is a document that checks every box, but never gets read.
This guide is different. It is about the policy brief as it actually works in a legislative office: a single page, handed across a table, that keeps working after you leave the room. Here is how to write one.
What a policy brief actually is (and what it is not)
A policy brief is a one-page argument for one specific action, written for one specific decision-maker, built around the place they represent.
It is not a research summary. It is not a white paper with the margins tightened. It is not your organization's annual priorities document. Those have their place, and their place is an email attachment nobody opens.
This matters because of how the document gets used. A legislative staffer sorts every piece of paper handed to their office into two piles: keep or recycle. A one-page brief with a clear ask gets kept and passed up to the legislative director. Anything longer gets a polite nod.
The one-page policy brief format
After enough meetings, every leave-behind that works ends up looking about the same. Here is the format that survives a real office:
1. The ask (top of the page, one sentence)
The most common mistake in policy brief writing is burying the ask. The first thing a staffer reads should be exactly what you want. “Support SB 482.” “Co-sponsor HR 1234.” “Fund the state loan repayment program at $4.5M in the FY28 budget.”
If the reader gets nothing else from your page, they should get this. Write it first, put it at the top, and make it impossible to miss.
2. The summary
Two paragraphs of context: what the bill or issue does, and why it matters in this district, in this state, to this member's own constituents. Not nationally.
This is where most briefs go generic and die. One rule will save you: if a sentence could appear in a brief handed to any legislator in the country, cut it. The summary earns its space by being a page no other office could receive.
3. Key points
Three bullets, a line or two each. Each one should name a real local institution: the hospital system, the community college, the base, the port, the big employer. Legislators think in terms of the things they represent. Your bullets should be a list of those things.
4. Impact numbers
Three numbers that show what is at stake for this district or state. Jobs, dollars, patients, students, acres. Every number needs a source. Which brings us to the part most guides skip.
5. Citations
Every claim on the page should trace back to a source the staffer can check: the bill text, committee analysis, census data, agency reports. The fastest way to lose an office's trust is a number they cannot verify. The fastest way to earn it is a page that says, “check everything, we did.”
A policy brief example
Say a nursing association is asking a Florida House member to support a scope-of-practice bill. A weak brief says nurse practitioners improve access to care nationwide. A strong brief says there are three areas in this district that the government officially lists as short on primary care doctors. It names the two hospital systems in the district and the community college that runs the nursing program. It uses state health department numbers to show how long patients are waiting.
Same issue. Same bill. The first brief is about healthcare policy. The second is about the member's district.
Now look at what the strong version took. Someone had to find those shortage listings. Someone had to know which hospital systems operate in the district and which college runs the nursing program. Someone had to pull the wait-time numbers and make sure they were current. That is two or three hours of research for one page, for one member.
The format is not the hard part. The research is the hard part. And that is the section most guides on this topic conveniently end before reaching.
The five mistakes that kill policy briefs
- Burying the ask. If your ask first shows up in paragraph four, you do not have a brief. You have an essay.
- National numbers. “Affects 40 million Americans” is wallpaper. “Affects 61,000 people in this district” is an argument.
- Going past one page. The second page does not get read. It gets your first page thrown away with it.
- Claims nobody can check. One stat the staffer cannot trace poisons the nine they could.
- Jargon. The staffer covering your issue also covers twelve others. Write for a smart generalist, not a colleague.
Avoiding these five gets you to average. What gets a brief kept instead of recycled is not avoiding mistakes. It is having district facts on the page that took real work to find.
How long should a policy brief be?
One page. People ask this enough that it deserves its own answer, and the answer does not change when the issue gets complicated. Complicated issues do not need longer briefs. They need better compression. The full analysis can live in a linked report. The page you hand over is the argument, not the archive.
Knowing the format is the easy part
Here is the honest math that this article cannot change. A brief that works takes the format above, plus:
- District research. Doctor shortage listings, who the big employers are, school enrollment, where the facilities sit. Two or three hours per member, scattered across census data, agency reports, and legislative records.
- Checking every number. Each stat verified against the original source, because one stale number in front of the wrong staffer costs more than the other nine earn.
- Doing it again and again. A fly-in with twenty offices means twenty different districts, which means twenty different research jobs. The page written for rural Georgia is wallpaper in suburban Phoenix.
That math is why most organizations quietly give up and print one generic one-pager for every office. It is also why most leave-behinds end up in the recycling bin.
And it is exactly why we built PolicyPage. Pick the member, describe your ask, and it does the research. It pulls the district data, writes the page to the standard described above, and cites every claim to a source you can click and check. About 30 seconds per brief. It is free. Every account gets five briefs a month, no credit card, so a full fly-in's worth of tailored leave-behinds costs you nothing but the minute it takes to generate them.
You now know what a great policy brief requires. The only question left is whether you want to spend three hours per member producing it.
Frequently asked questions
What is the format of a policy brief?
One page: the ask in one sentence at the top, a two-paragraph summary connecting the issue to the reader's district, three key points naming local institutions, three sourced statistics, one line saying who you are, and numbered citations at the bottom.
How long should a policy brief be?
One page. Legislative offices sort paper by length before they ever read it. A single page gets kept and passed along. Anything longer gets set aside. Link to the full report instead of attaching it.
What is the difference between a policy brief and a white paper?
A white paper is a long analysis written to inform. A policy brief is a one-page argument written to persuade one decision-maker to take one action. The white paper proves you did the work. The brief is what survives the meeting.
Do policy briefs need citations?
Yes. Every statistic and factual claim should have a source the reader can check, listed at the bottom of the page. Sourced numbers are what separate a credible brief from marketing, and legislative staff do check.
Who reads a policy brief in a legislative office?
Usually a staffer first, typically a legislative aide or the legislative director, who decides whether it reaches the member. Write for that staffer: a smart generalist juggling a dozen issue areas with about fifteen seconds for your page.
Ready to skip the three hours? Generate your first policy brief free at PolicyPage
New to the terms in this piece? Browse the advocacy glossary.