Voting no on a CEO's budget is not a disciplinary act — it is a governance act. Your board's job is to ensure that the organization's resources are deployed in service of the outcomes you've committed to producing for the people you serve. When a budget fails that test, voting no is not just permitted — it's required.
The clearest reason to vote no is misalignment: the budget prioritizes programs, staff structures, or administrative costs in ways that don't match the board's adopted Goals. If your board has established that the organization exists to improve health outcomes in underserved communities, and the proposed budget grows central operations while cutting community-facing services, that's a misalignment the board must name and reject. A yes vote would be an abdication of your fiduciary responsibility, not a show of confidence in leadership.
A second legitimate reason is fiscal instability. If the budget relies on revenue projections that are speculative, draws down reserves below your policy threshold, or structurally spends more than it takes in without a credible plan for correction, your board should send it back. This isn't second-guessing the CEO's judgment — it's holding the financial guardrails that protect the organization's ability to serve beneficiaries next year and the year after.
What "no" should look like in practice
Voting no should never be a surprise. If the budget has problems, your board should raise them during the development process — not wait for the approval meeting. Good boards build in at least one substantive touchpoint during budget development: a preliminary review where trustees can flag concerns before the document is finalized. A vote no at final approval means the process broke down somewhere earlier.
When the board does vote no, it should be specific. "We can't approve this budget" is not enough. The board should identify the specific concerns — whether misalignment with goals, inadequate reserves, unsupported revenue assumptions, or something else — and give the CEO clear direction for revision. Vague rejection wastes everyone's time and damages the CEO's ability to bring back something approvable.
Instead of: "The board declines to approve the FY2027 budget and requests revisions."
Try: "The board declines to approve the FY2027 budget. Two concerns must be addressed: (1) the budget does not reflect the board's adopted Goal to increase direct service reach by 15% this fiscal year, and (2) the projected revenue from new grants lacks signed commitments. Please return with a revised budget that reflects the direct service commitment and marks speculative revenue separately from secured revenue."
What is not a reason to vote no
Your board should not vote no because individual trustees disagree with specific line items, dislike the CEO's management philosophy, or want to signal dissatisfaction about something unrelated to the budget. Those are not governance reasons. If you find your board voting no on budgets frequently, the problem isn't usually the budgets — it's that the board hasn't done the work to establish clear Goals and financial Guardrails up front, so the CEO has no reliable target to hit. Fix the front end of the process, and you'll rarely need to use the vote no option at the back end.
- Before budget season opens, share your adopted Goals and financial Guardrails with the CEO in writing — these are the targets the budget must reflect, and the CEO should know them before drafting begins.
- Build in at least one substantive board touchpoint during budget development — not at final approval — where trustees can flag misalignment while the CEO can still respond to it.
- When reviewing the proposed budget, ask one primary question for each adopted Goal: does the resource allocation in this budget make achieving this Goal plausible? If not, that's a misalignment worth naming.
- If you vote no, be specific in writing: identify the exact concerns, reference the Goals or Guardrails the budget fails to meet, and give the CEO clear direction for what a revised budget must address.
- Never amend specific line items from the dais. If the budget is wrong, send it back — the CEO drafts, the board adopts. Trustees who move line-item amendments are doing management, not governance.