Budget cycles that lock, and change requests both sides can see
Most organizations end up in one of two traps with their annual budget.
Trap one is the locked spreadsheet. Finance spends six weeks building it, the board approves it, and nobody touches it again. By April, a grant shifted, a program expanded, and the spreadsheet is fiction.
Trap two is the free-for-all. Everyone edits the shared sheet whenever something comes up. By June, nobody remembers what the board originally approved or why travel spending doubled.
Zeno Budget solves this with budget cycles that lock, paired with a change request workflow that makes adjustments transparent.
Open, review, and locked
Every budget cycle moves through three clear states:
- Open. Program managers build forecasts for their own programs (mapped to the classes or locations you already use in QuickBooks). They can add recurring items, use templates, and review their own history without clutter from other departments.
- Review. Editing pauses so finance and leadership can look at the whole organization together, check cash reserves across the year, and resolve conflicts before anything becomes final.
- Locked. The approved budget becomes the baseline. Actuals from QuickBooks are measured against it, and direct edits are turned off.
Change requests with before-and-after impact
Locking a budget does not mean the year stops changing. When a program manager needs to add an expense, shift dates, or adjust a grant forecast after the cycle is locked, they edit in place as a pending change and bundle those edits into a change request with a written justification.
The locked budget does not move until someone with finance or owner permissions approves it.
What makes the workflow genuinely useful is that both sides see the exact impact before a decision is made:
- The requester sees their program before and after the change: by category and by period, the net difference, which lines moved, and where their program lands for the year.
- The approver sees the program and the whole organization. Alongside the program view, finance sees the entire organization’s weekly cash flow with and without the request: the ending balance week by week, the lowest cash point and when it lands, and whether any week drops below zero or below the organization’s cash reserve.
If a request has five lines and finance wants to approve three of them, partial approval lets them check and uncheck individual lines and watch both impact views recalculate on the spot. Every approval records who approved what, when, and the exact impact they saw.
Six months later, when someone asks why a line changed, the answer is right there in the record.