Nonprofit Policy Analysis

When to Use This Skill

Use this skill to produce the written research and analysis that underpins a nonprofit's advocacy positions:

• Drafting an issue brief, white paper, or policy position paper on a specific bill, regulation, or systemic issue
• Writing a one-page fact sheet or leave-behind summarizing a policy problem and the org's ask
• Analyzing a specific bill, amendment, or proposed agency rule section-by-section for impact on the org's constituents
• Comparing two or more policy options/proposals to recommend a stance
• Building the evidence base (data, precedent, case studies) that a board or ED needs before adopting a formal position
• Responding to a regulatory agency's request for public comment with substantive analysis (the comment letter itself; see also the comment/testimony boundary note below)

Boundary — hand off when the ask is: - Scheduling and running legislator meetings, lobby days, or delivering oral/written testimony at a hearing → nonprofit-legislative-advocacy - Negotiating a joint position across multiple organizations, MOUs, or shared campaign governance → nonprofit-coalition-building - Turning a position into an action alert, petition, or supporter call-to-action → nonprofit-grassroots-mobilization - Structuring 501(h) lobbying expenditure limits or (c)(3)/(c)(4) entity questions → nonprofit-c3-c4-structure

Core Framework: The Issue Brief Structure

A credible nonprofit policy brief follows a standard structure funders, legislative staff, and journalists all recognize. Deviating from it (e.g., leading with emotion instead of the ask) is the single most common reason briefs get set aside unread.

1. Header/title — Neutral, specific (e.g., "The Impact of SB 214 on Rural Behavioral Health Access" not "SB 214 is Dangerous")
2. Executive summary / "the ask" (3-5 sentences, always first) — What you want the reader to do, stated before the evidence. Legislative staff often read only this paragraph.
3. Background/context — The problem in plain terms, scoped to why it matters to this audience (district, committee jurisdiction, budget cycle)
4. Evidence/data — Statistics, studies, fiscal notes, constituent impact data; every figure cited to a source with a date (stale data is the #2 credibility killer)
5. Section-by-section or provision-by-provision analysis (for bill/reg analysis specifically) — What each key section does, who it affects, effective date
6. Counterarguments addressed — Steelman the opposing view and rebut it; briefs that ignore opposition read as advocacy, not analysis, to skeptical staff
7. Recommendation/position — Support, oppose, support-with-amendments, or monitor — stated as a single unambiguous sentence
8. Call to action / next step — What the reader (legislator, funder, board) should do next
9. Sources/citations and contact — Named staff contact for follow-up questions

Keep the brief to 1-2 pages for a legislative audience; a 6-10 page version with full appendix data is appropriate for board adoption or a funder-facing white paper — produce both from the same research base rather than writing two separate documents from scratch.

Bill and Regulation Analysis Method

When asked to analyze a specific bill or proposed rule:

1. Pull the actual text, not a summary — use the legislature's/agency's official bill tracking site or the Federal Register for proposed rules. Note the version (as introduced, as amended, as engrossed) since amendments change the analysis mid-session.
2. Identify the bill's practical mechanics: what it requires, prohibits, funds, or authorizes; effective date; sunset clause if any; delegated rulemaking authority it creates.
3. Run a stakeholder impact matrix: rows = affected groups (the org's clients, staff, partner orgs, funders), columns = impact type (financial, operational, access, rights) — this is the fastest way to surface unintended consequences before a board takes a position.
4. Check the fiscal note or agency cost estimate if one exists; flag when your organization's own data contradicts the official estimate — this is often the most persuasive content in a brief.
5. Trace committee/procedural status: committee of jurisdiction, companion bill in the other chamber, comment period deadline for regulations — this determines urgency and the brief's shelf life.
6. Draft the position recommendation using the four standard postures: support, oppose, support-if-amended (specify exact amendment language), or monitor/no position — avoid "concerned about" as a final posture; boards need one of the four.

Standard Deliverables

• Issue brief (1-2 pages, legislative/funder audience)
• One-pager / fact sheet (single page, leave-behind for meetings — coordinate format with nonprofit-legislative-advocacy since it is used there, but this skill authors the content)
• Position paper / white paper (5-15 pages, board-adoption or public-facing)
• Regulatory comment letter (formal submission to an agency docket, following that agency's required format and citing the specific rule section/docket number)
• Talking points sheet (bulleted, 5-8 points, for spokespeople — distinct from full testimony script, which belongs to nonprofit-legislative-advocacy)
• Bill comparison table (when tracking multiple competing bills on the same issue in a session)

Common Failure Modes

• Leading with the story instead of the ask. Legislative and funder audiences want the recommendation up front; save narrative/anecdote for the second section or an appendix.
• Undated or unsourced statistics. Every number needs a source and a year; a single stale or uncited figure can get an entire brief dismissed by opposing staff.
• No counterargument section. Briefs that only make the favorable case read as one-sided advocacy rather than analysis, reducing credibility with neutral legislative staff.
• Conflating "position" with "priority." A brief can recommend "oppose" without implying the org will spend lobbying capacity on it this session — separate the analytical position from the advocacy resource-allocation decision (the latter belongs with legislative strategy).
• Skipping the fiscal/operational impact check. Emotional or rights-based arguments alone often fail with fiscally-focused committees; pair values-based framing with a cost/benefit or cost-of-inaction data point whenever possible.
• Writing one brief for two audiences. A board-facing white paper and a legislator-facing one-pager need different lengths and openings; don't hand a legislative staffer the board version.

Practitioner vs. Advisor Application

• As the practitioner (policy/advocacy staff): Draft the brief yourself using the structure above, pull primary-source bill text, build the stakeholder matrix, and route the recommendation through your ED/board for formal position adoption before it's used publicly.
• As an advisor/consultant: Frame the brief-writing process as a facilitated decision tool for the board — position papers should surface the four-posture decision (support/oppose/amend/monitor) explicitly so the board is voting on a clear recommendation, not absorbing raw research. Flag for the client when a "position" question is actually a 501(h)/lobbying-classification question that needs nonprofit-c3-c4-structure input before publication.

Example

Input: "We need a one-pager on the proposed change to SNAP eligibility verification requirements for our state legislative visits next month."

Output approach: Pull the actual bill/rule text and effective date; build a stakeholder matrix (clients losing benefits, caseworker admin burden, state cost of new verification system); check for an official fiscal note and compare to the org's caseload data; draft using the 9-part structure above at one page; state the position as one of the four postures with a specific ask (e.g., "oppose Section 3; support Sections 1-2 if amended to delay implementation 12 months"); hand the finished one-pager to nonprofit-legislative-advocacy for use in the actual meeting prep.