State term schedules, explained

What a term schedule actually is

A state term schedule is a catalog contract. The state competes or evaluates it once, awards to many vendors, publishes approved items and prices, and then lets its agencies order against it without running a new solicitation every time. Nothing in that arrangement promises anyone a dollar. Ohio's standard schedule cover page says so in the plainest language a procurement office has ever used: "The State makes no representation or guarantee that agencies will purchase the supplies and/or services approved in the State Term Schedule." That sentence is the entire decision compressed into one line. A term schedule buys a firm the right to be bought from. It does not buy demand.

What a firm actually acquires on award day is a price list on file, an administrative fee obligation, a quarterly reporting calendar, and a set of contract terms it accepted without negotiating. Whether that is a good trade depends on facts that are public and checkable before anyone fills out an application. This piece walks the mechanics that decide it, using state procurement codes, published schedule documents, and the master agreement terms the cooperative programs post in full.

The names differ, and so do the mechanics

Ohio calls it a State Term Schedule. Florida calls it a state term contract. Texas runs term contracts through its Statewide Procurement Division and layers a schedule program on top. California groups its master agreements under the heading of Leveraged Procurement Agreements, of which the California Multiple Award Schedules are one branch. New York calls them OGS centralized contracts. NASPO ValuePoint runs multi-state master agreements that look like schedules and behave differently.

These are not five words for one thing. They differ on the question that matters most, which is what the buyer is obligated to do once the vehicle exists.

Vehicle	How a vendor gets on it	What it obligates the buyer to do
Ohio State Term Schedule Dept. of Administrative Services	Submit an offer; DAS evaluates the pricing and approves specific items onto published price pages.	Nothing. The schedule states the state "is not obligated to procure any products or services from this STS," and existing mandatory-use contracts take precedence over it.
Florida state term contract Dept. of Management Services	Win a competed statewide solicitation run by the department.	The strongest obligation of the group: agencies "shall," and eligible users "may," purchase from state term contracts under s. 287.056(1), F.S.
Texas TXMAS Comptroller, Statewide Procurement Division	Adapt an existing competitively awarded government contract; apply in a quarterly window.	State agencies and Texas SmartBuy members may buy; the purchaser still makes its own best value determination.
California CMAS Dept. of General Services	Apply at any time. DGS states no bids are required; pricing is set against a base schedule.	Use is optional and open to state and local agencies. CMAS operates as a pool of suppliers an agency solicits offers from.
New York OGS centralized contract	Win the OGS solicitation; services contracts are structured as backdrops.	Authorized users order against it. On the hourly IT services contract, work is released through an expedited competitive Mini-Bid.
NASPO ValuePoint master agreement	Win a single procurement run by one lead state on behalf of the group.	Nothing, until a state signs. A contractor "may not deliver Products under this Master Agreement until a Participating Addendum acceptable to the Participating Entity and Contractor is executed."

Mandatory use is the question that decides everything else

Florida's statute is the clean case. Section 287.056(1), Florida Statutes, reads: "Agencies shall, and eligible users may, purchase commodities and contractual services from purchasing agreements established and state term contracts procured by the department." The verb is shall for state agencies. A Florida state term contract in a live category is a real channel because the buyer has been told to use it.

Ohio sits at the other end. The standard State Term Schedule cover page carries two sentences that a vendor should read before spending a week on an application. The first: all General Distribution Contracts, Limited Distribution Contracts, Multiple Award Contracts and RFP-based contracts "take precedence over this State Term Schedule (STS). This STS is only for governmental entities without a mandatory use contract." The second: the state and its agencies, boards, commissions, universities and colleges are "not obligated to procure any products or services from this STS." An Ohio schedule in a category already covered by a mandatory-use contract reaches almost no state agency spending. Its value is elsewhere, in the political subdivisions registered as members of the DAS Cooperative Purchasing Program, who are the actual audience for many of these schedules.

California states the position outright on the program page: use of CMAS "is optional and is available to state and local government agencies." That is not a defect. It is a design choice that shifts the vendor's job from winning the schedule to marketing against it. Three questions settle this before an application goes in. Does the state's code make the vehicle mandatory for executive agencies? Does a competing mandatory-use contract already cover the category? Does the vehicle reach counties, cities, school districts and universities, or only the executive branch?

The schedules that ride on a federal contract

Two of the largest state schedule programs do not run their own price competition. They import one.

California Multiple Award Schedules. DGS establishes an independent California agreement for products and services already priced under a base schedule, most often a federal GSA Schedule contract, and offers them at equal or lower prices. Suppliers may apply at any time and DGS states no bids are required. That is unusually open compared with a competed statewide solicitation, and the openness has a matching consequence: the field is large, and being listed does not distinguish anyone. DGS also publishes a separate requirement set for non-IT services orders over $50,000 placed against CMAS, which is a useful signal that services orders above that size carry more process than a catalog purchase.

Texas Multiple Award Schedule. The Statewide Procurement Division "establishes TXMAS contracts to supplement SPD Term Contracts" by adapting existing governmental contracts for use by Texas buyers. Pricing rides on most favored customer terms, and buyers may negotiate below the schedule price. Applications are accepted in quarterly windows in September, December, March and June, submitted as an offer packet with a catalog and sample terms. The program's current posture matters for anyone planning a fiscal year around it: TXMAS is closed to new applications until September 1, 2026. That is a planning date, not a closed door, and it is exactly the kind of fact that belongs in a capture calendar rather than a surprise in month three.

The third door, which many firms already hold. A federal Multiple Award Schedule can serve state and local buyers directly through GSA's Cooperative Purchasing Program. Section 211 of the E-Government Act of 2002 opened federal supply schedules to state and local purchase of information technology; security and law enforcement categories followed later. Two limits shape how useful it is. The eligible scope is category-bound rather than open across the whole schedule, and participation is not automatic on either side: GSA states that MAS contractors "can accept or decline Cooperative Purchasing, Disaster Purchasing, PHE, and 1122 orders by state or local governments." A firm holding a federal schedule in the IT category, selling to a state buyer who already knows how to place a cooperative order, may not need a state schedule at all.

Getting on the schedule usually moves the competition rather than ending it

This is the misunderstanding that costs the most money. A firm treats schedule award as the win, staffs up against it, and then discovers that every order still runs through a second competition among the vendors already on the list.

Florida writes the second competition into statute. Section 287.056(2) allows agencies and eligible users to issue a request for quote "to obtain written pricing or services information from a state term contract vendor," for the purpose of finding a price, term or condition more favorable than the schedule already provides. On contractual services contracts with 25 or fewer approved vendors, the agency issues the request to all of them; with more than 25 approved vendors, to at least 25. The same subsection then adds the line every vendor should commit to memory: "Use of a request for quote does not constitute a decision or intended decision that is subject to protest." A firm that loses at the quote stage has no protest forum.

New York does the same thing under a different name. On the hourly IT services centralized contract, services required by an authorized user are obtained through an expedited competitive Mini-Bid. California's program describes CMAS as creating a pool of suppliers an agency can solicit offers from, which is the same structure stated as a design intent.

Read together, these three tell a firm what to build for. The schedule is the qualification round. The revenue event is the second competition, and the second competition is fast, lightly documented, decided among vendors who are all already qualified, and frequently decided on price and availability. A differentiator that needs forty pages to explain does not survive a quote round. A differentiator that shows up as a named engineer available in nine days, a fixed price, and a written acceptance test does.

What a schedule costs to hold

The application is the cheap part. The carrying costs run for the life of the contract and they are almost never modeled before someone signs.

The administrative fee, which comes out of your price. The published NASPO ValuePoint master agreement terms set it precisely: a contractor pays "a NASPO ValuePoint Administrative Fee of one-quarter of one percent (0.25% or 0.0025) no later than sixty (60) days following the end of each calendar quarter," based on all sales under the master agreement less taxes and shipping. The same clause states the fee "is not negotiable" and is "to be included as part of the pricing submitted with a vendor's response." A separate clause covers state-imposed fees, where a participating state requires an additional amount paid directly to that state on purchases in its jurisdiction. New York's hourly IT services contract sets its administrative fee at three-quarters of one percent (0.75%) of sales, with travel and other authorized expenses excluded. Florida assesses a transaction fee on payments to vendors through MyFloridaMarketPlace under Rule 60A-1.031, Florida Administrative Code, with rulemaking authority in sections 287.032, 287.042 and 287.057, Florida Statutes; the rule was last amended effective July 22, 2024, so read the current text for the rate rather than an older summary of it.

Reporting that continues when nothing sells. The NASPO terms require a quarterly sales report through the program's reporting tool, submitted within thirty days of the end of each calendar quarter, "including quarters during which a Contractor has no sales." A dormant vehicle is not a free vehicle. It is a recurring administrative obligation with a compliance consequence attached.

Catalog maintenance on the state's process, not yours. Ohio puts the burden in writing: the contractor's contact is responsible for keeping the schedule current, and every update — telephone numbers, contact names, email addresses, tax identification number, prices, catalogs — must be "processed through the formal amendment authorization process which is initiated by way of a written request from the contractor's contact." There is no self-service portal for a price change. Plan for weeks, not minutes, and plan for it every time a rate card moves.

Price exposure. Schedules built on most favored customer terms tie your government price to your commercial discounting behavior. That is manageable, and it is a real constraint on how a firm prices a strategic commercial deal for the life of the contract.

Registration overhead. Foreign qualification with the Secretary of State, a registered agent, certificates of insurance naming the state, electronic payment enrollment, and in several states a separate vendor registration renewal. Each is small. Across five states they become an annual line item and a calendar.

The schedules were built for catalogs, and services fit awkwardly

Look at the shape of an Ohio schedule and the origin is obvious. Purchase orders placed against it use UNSPSC codes on the requisition. The contract carries basic order limitations with a stated minimum and maximum, and agencies are told to contact Procurement Services when they expect to exceed the maximum order limitation. State agencies may buy up to $2,500 on the state payment card and use a formal purchase order above that. This is a product catalog with a mechanism for buying a specific listed thing at a listed price.

Services are pushed into the same frame as a labor-category rate card: named categories, ceiling hourly rates, and a term during which those ceilings hold. Three consequences follow, and none of them are hypothetical.

Rate compression. A ceiling rate set in year one is still the ceiling in year four. If the schedule allows an economic price adjustment, find the clause and the index before you price. If it does not, price the term, not the quarter.

Shape distortion. A rate card invites hourly staff augmentation, which is the least attractive structure for a firm whose advantage is finishing faster. Efficiency under an hourly ceiling reduces your own revenue. Where a schedule permits deliverable-based fixed price, that is the better instrument and it is worth asking for explicitly during the offer.

Scope drift at the order level. Only approved items may be sold. Ohio states it flatly: anything not on the approved price sheets "are outside the scope of this schedule." A services engagement that grows past the listed categories needs an amendment, and the amendment runs on the state's process. Build the categories wide at offer time, because widening them later is slow.

NASPO ValuePoint is national in scope and local in access

Multi-state cooperative agreements deserve a separate frame because they look like the biggest prize on the board and behave like fifty separate business development problems.

One lead state runs the procurement on behalf of the group and executes the master agreement with the winning suppliers. The published terms set an initial term of two years, extendable "for three (3) additional years at the Lead State's discretion and by mutual agreement" after review of participating entity requirements, market conditions and contractor performance. That is the ceiling to model, not an assumption of indefinite renewal.

Then comes the part that surprises people. A master agreement award does not open a single state. The terms are explicit: a contractor "may not deliver Products under this Master Agreement until a Participating Addendum acceptable to the Participating Entity and Contractor is executed." States decide individually whether to sign, and the terms note that states permitted to participate "may use an informal competitive process to determine which Master Agreements to participate in." Eligible non-state entities can sometimes sign their own addendum, subject to the consent of the chief procurement official of the state where they sit, and the terms add a caution worth quoting: permission to participate "is not a determination that procurement authority exists." Winning the master agreement is the start of the campaign, not the end of it.

The ordering above is a judgement, not a measurement, and it is worth saying why the top two sit where they do. Mandatory-use language is the only factor on the list that changes the buyer's behavior rather than the vendor's odds. Published spend is the only one that can be verified from outside before a dollar is committed. Everything below them affects how hard the work is; those two decide whether the work has a floor.

How to size a schedule before you apply

• Read the current holder list and the published price pages. States post them. If forty firms already sell your category at rates you cannot beat, the schedule is not the constraint on your growth.
• Check the transparency portal for real spend. Most states publish vendor payment data, and some summarize it by commodity class. An afternoon of reading actual payments beats any market estimate.
• Find out whether a mandatory-use contract already covers the category. In Ohio that single fact can move a schedule from a channel to a formality for state agencies.
• Read the second-competition rule before the offer, not after award. Whether it is a request for quote, a mini-bid or a pool solicitation, that process is where the money is decided.
• Price the administrative fee into the rate. On cooperative agreements the fee is often stated as non-negotiable and required to be inside the submitted price.
• Confirm the application window. Some programs accept offers continuously, some accept them quarterly, and some are closed for a period with a published reopen date.
• Model the exit. Term length, renewal discretion, and what happens to in-flight orders when the vehicle lapses.

When a term schedule is the wrong instrument

Four situations come up often enough to name.

The category has no mandatory-use force and thin schedule spend. Holding the vehicle costs fees, reporting and maintenance, and returns a listing nobody browses. The same effort spent on a named buyer with delegated purchasing authority produces work sooner.

Your advantage cannot survive a quote-only round. If the value of what you do only becomes visible in a technical evaluation, a vehicle whose orders are decided by three-line quotes will systematically undervalue it. Qualification-based pools and competed RFPs are the better fit.

The buyer you actually serve is a county or a district. Local governments often have their own cooperative memberships and their own thresholds, and a local direct purchase can close in weeks. Check whether the state vehicle even reaches them before assuming it is the path.

You already hold a federal schedule in an eligible category. If the state or local buyer can use cooperative purchasing to reach your existing federal contract, adding a state schedule adds fees and reporting for access you already have. Confirm the category eligibility and confirm you are willing to accept those orders, since acceptance is at the contractor's discretion.

Bottom line

A state term schedule is infrastructure, not a customer. It removes friction from a purchase somebody has already decided to make, and it does nothing at all to make them decide. The states that make it worth holding are the ones whose statutes point their agencies at the vehicle, whose transparency portals show money moving through it, and whose second competition is a race you are built to win. The rest are a listing, an annual fee, and a quarterly report filed on quarters with no sales. All of it is knowable in advance, from documents the states publish, before a single hour goes into the application.

Frequently asked questions