Nonprofit operating budget planner

What it does

Bring prior costs, grant plans and staff needs. Build the budget by program, show how shared costs split and draft the board memo.

What goes in and out

You give it

• Your prior-year actual income and costs
• Your expected grants, gifts and other income, with any renewal notes
• Your program list and staffing plan with salaries and FTEs (full-time equivalents)
• Your shared costs and how you split them, such as headcount or square footage
• Your fiscal year end and board meeting dates (optional)

You get

• A budget assumptions memo you can hand to the finance committee
• Income and expense budgets tied to named sources and programs
• A split of costs into program, management and fundraising, with the method stated
• A one-page board summary showing net result and reserve impact
• A budget calendar and a variance report template

How the task works

• Set assumptions and method. Choose incremental, zero-based or priority-based budgeting to fit the organization’s situation and document the basis.
• Build and reconcile. Tie funding to named sources, budget expenses by program and allocate shared costs using reproducible assumptions.
• Prepare approval and monitoring. Show net result and reserve impact, schedule committee and board review, and set variance explanations and amendment controls.

Full instructions

• Gather your prior-year actuals, grant award letters, staffing plan and shared-cost figures first.
• Open Claude, ChatGPT or Gemini and paste in the skill instructions. No code, files or paid tools are needed.
• Paste your numbers and say which fiscal year you are budgeting. Name any big changes, such as a lost grant or new program.
• Check the budgeting method and assumptions your AI picks. Correct any it got wrong before it builds the tables.
• Look for anything marked missing and fill it in. Check that every shared-cost split has a stated basis.
• Have your finance lead review the draft before it goes to the board. The board adopts this, so errors carry through the year.

Full instruction file

Nonprofit Budgeting

Before you start

Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

What you need (use your own material or the linked skill):

• A business profile (yours): a sourced business profile with buyer, offer, activation, growth goal, stage and limits; missing private metrics remain unknown.
• Your results (yours): an export of your numbers for set dates, from the tool that holds them: an ad account, your store, analytics or your product.
• A plan (yours): the goals, steps, constraints and dates for this work.

How to start:

1. Look first. Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. Check what's missing. Look for a business profile, your results, a plan. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. Do the job. Follow the skill below with the facts and tools you have. Mark each gap with MISSING: where it belongs and never invent a fact to fill it.

When to Use This Skill

Use this skill to build or revise a nonprofit's annual operating budget, decide between budgeting methodologies, allocate projected costs across program/management-general/fundraising, or run the budget through board approval. Trigger tasks include: "build our FY27 operating budget," "help me figure out what percent of our budget should be program vs. overhead," "we need a zero-based budget this year instead of just adding 3%," "draft a budget narrative for the finance committee," "set up a budget calendar," or "our board wants a multi-year budget projection tied to the strategic plan."

Boundary: this skill produces the plan. Turning actuals into GAAP-format financial statements is nonprofit-financial-statements. Setting reserve targets or forecasting cash timing within the budget year is nonprofit-reserves-cash-flow. Calculating a formal indirect cost rate for a federal or foundation grant is nonprofit-cost-allocation. Designing who approves what dollar threshold is nonprofit-financial-controls.

Core Framework

A nonprofit operating budget is a board-approved financial plan of revenue and expense for one fiscal year, built at the account/program level and rolled up to functional categories for external reporting. Treat it as three linked documents, not one:

1. Revenue budget — grants, contracts, individual giving, events, earned income, investment income, in-kind — each line tied to a named source or a documented assumption (e.g., "renewal probability 80% based on 3-year history").
2. Expense budget — built by natural category (salaries, benefits, occupancy, professional fees, travel, supplies) and tagged by program/department, so it can be re-sliced into functional categories.
3. Functional allocation — the same expense dollars re-cut into Program Services, Management & General, and Fundraising, per FASB ASC 958-720. This is what a board and outside reviewers (Charity Navigator, GuideStar/Candid, grantors) will judge.

Budgeting Methodologies — Choosing and Naming the Approach

• Incremental budgeting: prior year actuals ± a percentage adjustment. Fast, low-conflict, but perpetuates existing allocation and hides sunk-cost programs. Default for stable organizations.
• Zero-based budgeting (ZBB): every line must be justified from zero each cycle, program by program. Surfaces programs that no longer earn their keep; expensive in staff time. Recommend for organizations that haven't reassessed program mix in 3+ years, post-merger, or after a major revenue shock.
• Priority-based (a.k.a. Budgeting for Outcomes): rank programs against mission/strategic priorities first, then fund top-ranked programs fully before funding lower-ranked ones — useful when revenue is flat or declining and across-the-board cuts would hurt high-performing programs as much as weak ones.
• Program/activity-based budgeting: build the budget by program (each with its own mini P&L) rather than only by natural expense category — needed once an org has 3+ distinct programs with different funding mixes, since it exposes which programs are subsidized by unrestricted revenue.
• Rolling/multi-year forecast: 12-month budget plus a 2-3 year projection updated quarterly — pair with nonprofit-strategic-planning outputs when the board wants the budget to visibly fund strategic priorities.

State which method is being used and why; do not silently default to incremental when the organization's situation (declining revenue, program pruning, post-merger) calls for ZBB or priority-based.

Program-vs-Admin-vs-Fundraising Allocation

• Every cost is either direct (traceable to one program, e.g., a case manager's salary) or shared/indirect (benefits multiple functions, e.g., the ED's salary, rent, IT, the finance director).
• Allocate shared costs using a documented, defensible basis — headcount %, square footage, time studies/timesheets by function, or a negotiated indirect cost rate (see nonprofit-cost-allocation for the formal rate-negotiation version of this). Time studies are the most audit-defensible basis for personnel costs that split across functions.
• Common failure mode: dumping all occupancy, IT, and admin salaries into "Management & General" without allocation, which inflates the reported overhead ratio and triggers funder/watchdog scrutiny (Charity Navigator and BBB Wise Giving Alliance both flag high M&G ratios). Fix by allocating a reasonable share of shared costs to programs based on actual usage.
• Common failure mode #2: over-allocating to programs to make the overhead ratio look artificially low — this fails an audit or a funder cost review when the allocation basis isn't documented and reproducible. Every allocation percentage must be traceable to a stated method (see nonprofit-cost-allocation).
• There is no single "correct" overhead ratio; benchmark against organizations of similar size/sector rather than a flat 15%/85% rule of thumb, and be ready to explain the ratio's composition rather than just the number.

Step-by-Step: Building the Annual Budget

1. Set the calendar. Work backward from the fiscal year start and the board's final vote date. Typical timeline for a June 30 fiscal year end: kickoff/assumptions in February, department/program drafts in March, finance committee review in April, board first read in May, board approval in June. Adjust similarly for a December 31 fiscal year end.
2. Set budget assumptions first, in writing — salary increase %, benefits inflation, known grant renewals/losses, new program launches, inflation on occupancy/insurance. Circulate assumptions to department heads before they draft numbers so everyone budgets against the same baseline.
3. Build revenue first, conservatively. Use a probability-weighted approach for uncommitted revenue (committed/contracted = 100%, highly likely = 75-90%, prospective/unconfirmed = 25-50%). Never budget to a fundraising goal that has no plan behind it — cross-check every revenue line against the development plan/pipeline (see nonprofit-donor-pipeline for the underlying pipeline).
4. Build expenses program-by-program and department-by-department, tagging each line with the program/department it belongs to so the functional roll-up is mechanical, not a re-derivation.
5. Reconcile to net. Decide upfront whether the board requires a balanced budget, allows a planned deficit funded from reserves (state the dollar amount and reserve impact explicitly — see nonprofit-reserves-cash-flow), or requires a modest surplus to build reserves.
6. Run the functional allocation and check the resulting Program / M&G / Fundraising percentages against the prior year and peer benchmarks before it goes to committee — large swings need a one-line explanation ready for the board.
7. Finance committee review. Expect questions on: variance vs. prior year actuals, any new FTEs, assumptions behind the largest revenue lines, and the M&G ratio. Bring a one-page assumptions memo, not just the spreadsheet.
8. Board approval. Most bylaws require full board vote on the annual budget (check nonprofit-bylaws-policy if unclear); present a summary page (revenue by source, expense by function, net, reserve impact) plus the detail as an appendix — do not hand the board the full general-ledger-level workbook as the primary document.
9. Set up budget-to-actual monitoring — monthly or quarterly variance reports against this approved budget, with a defined threshold (e.g., >10% or >$5,000 variance) that triggers a written explanation to the finance committee.
10. Amend formally when needed. A material shift (new large grant, lost major funder, unplanned hire) should go back to the board or finance committee as a budget amendment, not be silently absorbed — keep an amendment log for audit trail.

Standard Deliverables

• Budget assumptions memo (1 page)
• Revenue detail by source with probability weighting
• Expense detail by natural category, tagged by program/department
• Functional expense summary (Program / M&G / Fundraising %)
• Board-facing budget summary (1 page) + full detail appendix
• Budget calendar with named owners and dates
• Budget-to-actual variance report template (monthly/quarterly)

Common Failure Modes

• Budgeting revenue to a fundraising goal rather than a pipeline — creates a mid-year crisis when the gap surfaces in month 8.
• No written assumptions, so a board member's "why did salaries jump 12%?" has no ready answer.
• Treating the functional allocation as an afterthought done only for the 990, instead of building it into the budget structure from day one — this causes a scramble every year and inconsistent methodology year to year.
• No variance monitoring cadence set at approval time, so the board only learns of a problem at year-end.
• Approving a deficit budget without an explicit reserve drawdown plan and reserve-policy check.

Practitioner vs. Advisor Framing

• As the ED/finance staff, build the budget bottom-up from program and department input, own the assumptions memo, and drive the calendar so finance committee/board deadlines aren't missed.
• As an advisor/consultant, frame budget review as a governance and strategy conversation for the board: is the functional allocation defensible to funders and watchdogs, does the revenue mix match the strategic plan's priorities, and is the board being shown a decision-ready summary rather than a raw spreadsheet. Push back diplomatically on incremental "add 3% to everything" budgets when the underlying situation (revenue decline, program underperformance) calls for zero-based or priority-based budgeting instead.

After this

When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:

• The Project completion funding checker. It takes the document and spreadsheet.
• The Construction funding schedule planner. It takes the document and spreadsheet.
• The Construction completion funding reviewer. It takes the spreadsheet and document. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.