The Budget Cycle and Why Timing Can Beat Price
Why this matters
Two identical proposals, same scope, same price, same signature block, submitted to the same facilities director eleven weeks apart, do not have the same chance of being approved. One gets signed in nine days. The other gets a sincere "we love it, resubmit next year," and next year the line it needed has been reduced. Shops read that as a customer being flaky and respond by sharpening the price, which is the one lever that moves neither of the two forces that actually decided it. The fiscal calendar is not a soft factor around the edge of a sale on institutional work. It is frequently the deciding factor, and it is completely knowable in advance.
The two forces, and why they move in opposite directions
Fund availability is how much room is left in the line that would pay for your work. It starts full at the beginning of the fiscal year and drains as the year runs. Late in the year it is often at its most generous in practice, because the committed program has been paid and whatever is left is genuinely spendable, and in many institutions operating funds do not carry over into the next year. Money not encumbered by year end is swept.
Calendar availability is how many working days remain before the institution's internal cutoff for issuing purchase orders against the closing year. It starts effectively unlimited and shrinks to zero. That cutoff is normally weeks earlier than the last day of the fiscal year, because accounts payable needs runway to close the books.
Those two lines cross. Early in the year there is plenty of calendar and little slack in a freshly committed budget. Late in the year there is real slack and almost no calendar. The best moment to arrive with an unplanned request is where they cross, not at either end, and a shop that has only ever heard "spend it before June" is optimizing one force and ignoring the other.
Check the direction at both ends before you trust it. If late-year submissions were simply better, the shops that fax everything in during the last month would win, and they do not; their proposals die on the cutoff. If early-year submissions were simply better, no vendor would ever hear "we found some money." Both patterns exist, which is what tells you two forces are in play rather than one.
The four windows and the shape of request each accepts
| Window | What it has | What it accepts | What it rejects |
|---|---|---|---|
| Budget development, several months before the fiscal year starts | No money yet, maximum calendar | Condition assessments, multi-year plans, anything that needs to become a line item | Anything needing a purchase order now |
| Early in the fiscal year | Fresh funds, all committed | Work already in the plan, standing agreement releases | Unplanned discretionary requests |
| After the mid-year review | Known variances, reallocation happens here | Well-documented unplanned work, especially anything that reduces a line already running over | Vague proposals with no cost basis |
| Late year, before the encumbrance cutoff | Real slack, almost no calendar | Ready-to-encumber requests already priced and quoted | Anything needing a step you have not already completed |
The gate
Is there room in a fund that can pay for this, and is there enough calendar left to complete every procurement step before that fund closes?
Both halves, every time. Run it against two cases below. Same district, same proposal: replacing failed variable frequency drives on four air handlers, an amount that sits in the district's middle band, which requires written quotes from several sources. The district's encumbrance cutoff is 3 weeks before fiscal year end.
Case one: submitted 9 weeks before year end
Fund side: the HVAC repair line has run under, and the director knows it because the mid-year review told them. Room exists.
Calendar side: 9 weeks to year end, minus the 3-week encumbrance cutoff, leaves 6 weeks of usable calendar. The middle band's quote-gathering step took 7 working days, about 1.5 weeks, the last time this district ran it. Technical sign-off, business office review and purchase order issue took another 2 weeks on the last comparable request. That is roughly 3.5 weeks of process against 6 weeks available.
Both halves pass. Approved, purchase order in hand with about 2.5 weeks of slack, and the work itself scheduled into the summer break window.
Case two: identical proposal, submitted 4 weeks before year end
Fund side: unchanged. Same line, same room, arguably more visible now because the director is actively looking for legitimate work to encumber.
Calendar side: 4 weeks to year end minus the 3-week cutoff leaves 1 week of usable calendar against a process that has historically needed about 3.5. It fails by a factor of roughly three and a half, and no amount of goodwill compresses a quote-gathering step that depends on two other shops answering their phones.
The gate fails on the calendar half alone. The proposal is not rejected on merit and the director may genuinely intend to bring it back. What happens next is the part shops do not see: the line closes under budget, and a line that closes under gets reduced in the next budget build, so when the same proposal returns in the new year the fund half now fails too.
The lesson is not "submit earlier." It is that a calendar failure in one year converts into a fund failure in the next, which is why the same proposal can get harder rather than easier over time.
Why a price concession does not fix either half
Reducing your price does not create calendar and does not create a fund with room. In case two, a 10 percent reduction changes nothing at all, because the binding constraint was working days.
There is exactly one honest exception and it is worth knowing precisely. If a genuine scope reduction moves the request from the middle band into the lowest band, the quote-gathering step disappears and roughly 1.5 weeks of calendar is created. That is a real effect and it can rescue a late request. It only counts when the reduced scope is a complete and useful deliverable on its own, for instance two drives now and two in the next fiscal year, each fully functional. It is not the same as dividing one project into pieces to duck a competition requirement, which is a procurement violation your buyer will pay for. See related: How an Institution Decides to Spend Money.
The submission that is already ready to encumber
Late-window requests fail on process steps, so the counter is to arrive with the steps already done. What "ready to encumber" means concretely:
- A written scope specific enough that a competing shop could quote against it without another site visit.
- Your certificate of insurance, with the additional-insured wording their risk manager requires, already on file and unexpired. See related: The Certificate of Insurance a Customer or GC Asks For.
- Your vendor registration active in their system, with any portal onboarding complete.
- Equipment lead times stated in weeks, in writing, because a purchase order issued for material that cannot arrive before year end may still be a problem in some accounting treatments and the buyer needs to know.
- The band named. Say in the proposal which threshold band you believe this falls into and what that band requires. Buyers respond well to a vendor who already knows their own rules.
That package is not a sales tactic. It removes days from their process, and days are what the late window is short of.
The window shops forget entirely
Budget development is the highest-leverage window and almost nobody uses it, because there is no purchase order at the end of it and it happens months before anyone is thinking about next year.
This is where a condition assessment becomes a line item. A written record of a system's age, failure history and expected remaining service, delivered while budgets are being built, is how a replacement gets funded on a plan instead of on an emergency. It also protects you from the worst version of institutional work, which is being asked to keep something alive that should have been replaced two years ago, with the failures counted against your name.
Ask one question in the autumn or whenever their build starts: "When do you assemble next year's budget request, and would a written condition summary on the units we service be useful to you then?" The answer is almost always yes, and it costs a few hours of writing.
The year-end trap on the delivery side
Winning three or four late-window approvals in the same week feels like a great year and is a staffing problem. Every one of them will want to be executed in the same break week, because that is the only outage window the institution has, and you have just committed your entire crew to one two-week period in one building type.
Count it before you say yes. If four approvals each need 2 technicians for 3 days, that is 24 technician-days inside a 10-working-day window, which needs about 2.5 technicians running the full window with nothing left for a service call. Either stage the work across two windows or tell the director now, while they still have alternatives, rather than in June.
And the work itself changes character at night and during breaks. A partially occupied building with skeleton staffing means confirming before the shift who else is in the building and where, that egress lighting and the exit route are functional and unobstructed under 29 CFR 1910.37, and how the fire alarm reports at night when there is no one at the front desk. A hot work permit's fire watch and its post-work watch period do not shorten because the building is emptier, which is the exact inversion people reach for. NFPA 51B sets that watch, and an emptier building is a reason for a longer watch, not a shorter one, because there is nobody else to notice smoke.
How to check where you are in the cycle
Three facts, written on the customer record, that make every future proposal to that institution better:
- The fiscal year start and end dates. Not "July," the actual dates.
- The internal encumbrance cutoff, in working days before year end. Ask purchasing, not the director; purchasing knows it exactly.
- The elapsed working days from technical sign-off to purchase order on your last two jobs there. That is your real process time for that customer, in their bands, and it is the number the gate needs.
If you have those three for your top institutional accounts, you can look at a calendar in March and know which proposals are still live for the current year and which ones should be written as next-year line items instead. That single distinction, made honestly and early, does more for a close rate than any discount.
References
- 2 CFR 200.320, procurement methods under the Uniform Guidance, where federal award funds are involved and a band determines the competition requirement
- 29 CFR 1910.37, exit route maintenance in a partially occupied building during off-hours work
- NFPA 51B, fire prevention during welding, cutting and other hot work, including fire watch duration
- See related: How an Institution Decides to Spend Money; Capital Money and Operating Money Are Not the Same Money; The Facilities Director and What They Are Actually Judged On