Service
Advocacy & Coalitions
Legislative outcomes track discipline, not passion: the calendar is published years ahead, and the bills that pass belong to the organizations that worked the interim.
The work
What the work actually is.
The legislative calendar worked as a pipeline: coalitions, testimony, and constituent voice under consent discipline.
Most advocacy is episodic: a rally when the bill drops, testimony drafted the week of the hearing, coalition partners assembled after the calendar is set. But legislative calendars are known years in advance, and the organizations that pass bills treat the session as a pipeline: bill concepts developed in the interim, sponsors cultivated before they are needed, committee paths mapped, testimony prepared and rehearsed, coalition commitments secured in writing while there is still time to negotiate them. The work is unglamorous, which is why few institutions do it — and why it compounds for the ones that do.
Constituent voice is the strongest asset in any hearing room, and precisely because it is powerful it must be governed by consent: informed, specific, revocable. A story belongs to the person who lived it: used for the stated purpose, with a consent trail the organization could produce on demand. The model is not theoretical. The platform Lotus built for OFYC enforces it in code: no story appears without its author’s signed yes. The same standard belongs in every testimony packet and every campaign; anything less is spending constituents rather than representing them.
Coalition work gets the same rigor: shared asks in writing, roles and credit agreed before the win, message discipline held across partners who agree in meetings and drift at the microphone, and the whole motion run inside the lines, lobbying tracked against a dollar limit rather than a vague standard: the 501(h) election is what turns lobbying anxiety into bookkeeping, and most organizations that should have made it have not. The evidence that this discipline produces outcomes is the record of the institution whose platform the firm built: five Oregon laws authored by OFYC’s members, from 2009 to a Sibling Bill of Rights that passed the House unanimously in 2017.
Deliverables
What you keep.
- Legislative pipeline
- Bill concepts, sponsors, committee paths, and the interim worked as stages with owners: the session as a managed campaign.
- Testimony preparation system
- Witnesses selected, prepared, and rehearsed, consent documented before any story is used.
- Coalition agreements
- Shared asks, roles, credit, and message discipline: in writing, before the win.
- Consent architecture
- Informed, specific, revocable: the standard OFYC’s platform enforces in code, applied to every use of a constituent’s story.
Getting started
The last session, reconstructed: every ask traced through its committee path, interim work counted against the calendar, consent trails checked for every story used, before the next session’s calendar hardens.
The practice
The rest of Nonprofit & Philanthropy Reform.
- Nonprofit & Philanthropy Reform overview
- Program & Policy Design Programs designed backwards from the measurable claim, with policy change as a deliverable, not a hope.
- Funding Architecture Development built as a system: donor pipeline, grant calendar, matching machinery, restricted-fund discipline.
- Board & Governance Decision rights, conflict handling, and a board packet that survives a skeptical donor’s reading.
Get started