policy-brief · git:20260619.8a1ecd4 · 2026-06-19 · sha256 eeb24defe65c7cc4
policy-brief git:20260619.8a1ecd4A
Immutable. This exact content never changes and is served at /api/v1/blob/eeb24defe65c7cc4.
--- name: Policy Brief description: Write a concise, evidence-based policy brief for decision-makers. --- # Policy Brief Write a brief that lets a busy decision-maker understand a problem and choose an action in a few minutes. Concise, evidence-based, and honest about trade-offs. ## 1. Know the audience and decision Identify who decides and what decision they face. A brief exists to inform a specific choice, not to be a literature review. Tailor depth and jargon accordingly. ## 2. Structure (standard format) 1. **Title + executive summary**: the problem and your recommendation in 3-4 sentences. Many readers read only this — make it stand alone. 2. **Problem statement**: what is wrong, who is affected, why it matters now, and the cost of inaction. Quantify where possible. 3. **Background/context**: the minimum needed to understand the problem. 4. **Evidence**: what the data and research show. Cite primary sources. Present evidence on all sides, not just the convenient findings. 5. **Policy options**: 2-4 realistic options including status quo. For each: how it works, expected impact, cost, feasibility, and key trade-offs. 6. **Recommendation**: the preferred option and the reasoning. State assumptions and conditions. 7. **Implementation**: concrete first steps, owners, and timeline. ## 3. Make evidence rigorous - Cite credible, primary sources; note the strength and limitations of each. - Distinguish strong causal evidence from correlation or expert opinion. - Acknowledge uncertainty and dissenting evidence — credibility depends on it. ## 4. Compare options fairly Use consistent criteria across options (effectiveness, cost, equity, feasibility, time-to-impact). A comparison table helps. Do not strawman the options you reject. ## 5. Write for clarity - Lead with the conclusion (BLUF: bottom line up front). - Short sentences, active voice, no unexplained jargon or acronyms. - One to four pages. If it is longer, it is a report, not a brief. - Use headings, bold key points, and visuals where they aid comprehension. ## Guardrails - Be transparent about evidence quality and uncertainty — do not overclaim. - Present trade-offs honestly; every option has costs. - Separate evidence (what is) from values (what should be) and label normative choices. - Disclose assumptions; a recommendation is only as good as what it rests on.