A curator can love a proposal in October and still not be able to book it until January. That gap confuses a lot of vendors, who assume interest and approval move at the same speed. They don't, and the difference is a fiscal year that hasn't opened yet.
An institution's procurement cycle is the internal calendar that decides when money actually becomes available to pay a vendor, separate from when a project gets approved in spirit. A strong pitch can be fully endorsed and still wait months for a new fiscal year, a new budget line, or a purchase order to clear before booking can happen. Timing, not enthusiasm, is usually the real constraint.
What is an institution's procurement cycle, in plain terms?
A procurement cycle is the internal calendar an institution follows to plan, approve, and release its own spending, separate from any single project's timeline. It determines when a budget line actually exists to pay a vendor, not just when someone there wants to hire one.
Most institutions, whether a museum, a university gallery, a foundation, or a cultural nonprofit, set an annual budget tied to a fiscal year that may or may not match the calendar year. Spending against that budget usually needs to be planned, and in many cases approved, before the fiscal year begins, not decided on the fly once it's underway.
This is different from a single job's intake process, where a client and a vendor agree on scope and price for one project. A procurement cycle sits above that. It's the reason a department might already know exactly what it wants to book, and still not be able to issue a purchase order until a specific date arrives on the institution's own calendar.
Understanding this distinction changes how a vendor reads a slow institutional response. A quiet month isn't always indecision. It's often a budget that hasn't opened yet, moving on a schedule set well before the conversation with the vendor even started.
Knowing that timing exists is often more useful than knowing the exact rules behind it, since every institution runs its own version.
Why can something be approved and still not be bookable?
Approval and booking are different steps because approval is a decision and booking is a transaction, and an institution can complete the first without having access to the second yet. A proposal can be fully endorsed internally while the money to pay for it is still sitting in a future budget period.
A department head might sign off on a project in principle, agree on scope, and even confirm they want to move forward, all without controlling the exact date funds become available. That authority often sits somewhere else entirely, with a finance office or a board cycle that releases funds on its own schedule.
This split explains why a vendor can leave a meeting feeling like the deal is done, only to be told a few weeks later that booking has to wait. Nothing about the enthusiasm changed. What changed is that the excitement lives on one calendar and the money lives on another.
It helps to treat these as two separate milestones rather than one moment. A yes on the work is real progress, worth confirming and holding onto, but it isn't the same milestone as a purchase order or a signed engagement, and conflating them is where a lot of scheduling frustration starts.
Recognizing the gap early lets a vendor ask a more useful question than when do we start. The better question is when does the budget for this actually open.
How do fiscal years shape when a project can actually book?
A fiscal year sets the window an institution's budget covers, and spending outside that window usually isn't possible no matter how ready everyone feels. Many institutions run July to June or October to September rather than the calendar year, which changes when a given project becomes payable.
A project pitched in the fall might be conceptually approved right away, but if the fiscal year doesn't open until July, the actual purchase order may not exist until then. The work discussed in October and the money that pays for it in July are on two different timelines, even though they're connected to the same project.
This isn't unique to any one type of institution. Universities, museums, foundations, and government-adjacent cultural organizations all tend to run some version of a fixed fiscal year, and the exact start date varies enough that it's worth asking directly rather than assuming.
Knowing the fiscal year in advance changes how a vendor plans their own calendar. A project that can't book until a specific month isn't a lost opportunity, it's a project with a known start date, and that's a very different thing to plan around than an open-ended maybe.
The fiscal year is also often the point where new budget lines get created, which is why a project that felt stuck in one quarter can suddenly move the moment a new year opens.
What actually slows down a purchase order once a budget exists?
Even after a budget technically opens, a purchase order can still take time because it usually has to pass through several internal steps: a requisition, an approval chain, and sometimes a finance office review before a vendor sees a signed agreement or payment.
A requisition is the internal request that starts the process, often written by the department that wants the work done. That request then typically needs sign-off from someone with budget authority, which might be a director, a dean, or a finance committee, depending on the size of the institution and the size of the spend.
Larger purchases sometimes require additional review, competitive bidding, or a formal contract process that smaller projects skip entirely. None of this reflects doubt about the vendor. It's simply the internal machinery every purchase above a certain size has to move through before money changes hands.
This is why two projects that feel identical in scope can move at very different speeds. One might fall under a threshold that only needs a single approval, while the other crosses into territory that triggers a longer internal process, regardless of how ready both sides are to start, or how similar the two projects looked from the outside.
Asking early whether a project is expected to need that longer process is one of the more useful questions a vendor can ask, since it sets real expectations instead of assumed ones.
How is this different from the intake conversation for a single job?
A single job's intake conversation is about scope, deliverables, and price for one project. An institution's procurement cycle is about when that institution's own money becomes available at all, and the two conversations answer completely different questions even when they happen back to back.
Quoting a job accurately depends on knowing what's being delivered, where, and under what conditions. That conversation can be finished in a single call and doesn't require knowing anything about the institution's internal budget calendar. It produces a number and a scope, and both sides can agree on it quickly, sometimes within the same conversation.
Procurement timing depends on none of that. It depends on the institution's fiscal year, its internal approval chain, and whatever purchasing thresholds apply to the size of the project. A vendor can nail the intake conversation perfectly and still be told the earliest possible start date is months away, because the two processes were never actually connected in the first place.
Mixing them up is a common source of frustration. A vendor who assumes a finished quote means an imminent booking is applying single-job logic to an institutional-budget problem, and the two rarely move at the same pace, no matter how clean the quote turned out to be.
Separating them mentally makes both conversations easier. One is about the work. The other is about the calendar the money lives on, and neither one substitutes for the other.
What are the signs a project is still waiting on next year's budget?
A project is usually pre-budget when the enthusiasm is real but the language stays conditional: phrases like once the new year opens, pending board approval, or after we finalize allocations are common signals that the money isn't available yet, even though the interest clearly is.
Another sign is a contact who can describe the project in detail, including scope and rough dollar range, but can't give a firm start date. That combination, specific about the work and vague about timing, usually points to a budget that exists on paper but hasn't formally opened for spending yet.
References to a board meeting, a finance committee, or an annual planning cycle are also worth noting. Those are typically the moments when new spending actually gets released, and a project mentioned alongside one of those milestones is likely tied to its outcome more than to anything the vendor could control.
None of these signs mean the project isn't real. They usually mean it's real and simply early, sitting ahead of the point where it becomes payable. Recognizing the pattern helps a vendor plan around a likely window instead of guessing at an exact date that doesn't exist yet.
A polite, direct question about the fiscal year and approval process usually clears this up faster than reading between the lines, and most institutional contacts are glad to answer it plainly.
What can a vendor do while a project waits on its budget?
A vendor can keep the project moving without a booking by confirming scope, sending any required paperwork early, and asking directly when the fiscal year opens. None of that requires a signed agreement, and all of it removes friction from the moment the budget actually becomes available.
Scope can be settled well ahead of a purchase order. Agreeing on what the project includes, roughly when it would happen, and what it depends on gives both sides a clear starting point the moment funding clears, rather than restarting that conversation from scratch several months later, once everyone is trying to move quickly.
Paperwork is often the quiet bottleneck once a budget opens. A W-9, a certificate of insurance, or a vendor registration form can usually be submitted long before a purchase order exists, and getting it done early means it isn't the thing holding up a booking once the money is there and everyone is ready to move.
Asking plainly about the fiscal year and the approval chain is a reasonable question, not an awkward one. Institutional contacts are usually used to explaining their own budget calendar, and a vendor who asks clearly tends to get a clearer answer than one who waits and wonders.
None of this guarantees a faster booking. It just means nothing on the vendor's side is the reason for the delay.
Why doesn't a slow procurement timeline mean the project fell through?
A slow procurement timeline usually reflects an institution's internal calendar, not a change of heart about the project. The same budget cycle that delays a booking in one quarter is often the reason it becomes possible at all once the fiscal year opens, on its own predictable schedule.
It helps to remember that institutions run this process for every vendor, every year, not just for one particular project. A slow start isn't a signal specific to the work being discussed. It's simply how that institution moves money through its own system, regardless of who's on the other end of the conversation or how strong the proposal was.
A useful comparison is a seasonal calendar. Just as certain months are naturally quieter for approvals, certain points in a fiscal year are naturally quieter for new spending, and neither pattern reflects on the quality of a specific proposal or the relationship behind it.
Treating the wait as structural rather than personal changes how a vendor experiences it. A pending fiscal year isn't a maybe. It's a known, if sometimes distant, point in time, and projects tied to it tend to move forward reliably once that point arrives.
Patience here is less about hoping and more about understanding which calendar the project is actually running on, and planning around it accordingly rather than reading too much into a quiet month.
Frequently asked questions
Why would an institution approve a project but not book it right away?
Because approval and booking are two different steps. A department can genuinely endorse a project in principle while the money to pay for it still sits in a future budget period controlled by a finance office or board cycle. The enthusiasm is real, but the purchase order depends on a separate calendar, one tied to the institution's fiscal year rather than the conversation with the vendor.
What is a fiscal year, and why does it matter for booking timing?
A fiscal year is the window an institution's budget covers, and it often doesn't match the calendar year, sometimes running July to June or October to September instead. Spending usually can't happen outside that window, so a project discussed in one season may not become payable until a new fiscal year opens, regardless of how ready both sides are to start the work itself. Asking about it directly usually clears up the timing question fast.
How is procurement timing different from getting a quote for one job?
A single job's intake conversation covers scope, deliverables, and price, and can be finished quickly without touching the institution's internal budget calendar. Procurement timing is a separate question entirely: it depends on the fiscal year, the approval chain, and internal purchasing thresholds. A finished quote does not guarantee an imminent booking, since the two processes rarely move at the same pace or answer to the same calendar.
What can a vendor do while waiting on an institution's budget to open?
Plenty, without needing a signed agreement yet. Confirming scope, submitting a W-9 or certificate of insurance early, and asking directly when the fiscal year opens all move the project forward. None of it locks anything in, but it removes friction from the process once funding actually becomes available, so nothing on the vendor's side causes an avoidable delay once the budget clears and the purchase order is finally ready to move.
Does a slow procurement process mean the project probably won't happen?
Not usually. A slow timeline typically reflects an institution's own internal calendar rather than any doubt about the project. Every vendor that institution works with moves through the same budget cycle, so the delay isn't specific to one proposal. Projects tied to a known fiscal year tend to move forward reliably once that year actually opens, which makes the wait predictable rather than worrying, as long as the fiscal year itself is actually known.
Planning photo or video in NYC?
Tell us what the files need to do, where the work is happening, and what the day has to protect. We will help shape a practical production plan around it.
Start a project →