Cooperative purchasing means public buyers pool their buying power through one solicitation, so each agency does not run its own bid. A lead public body runs the process and other eligible entities can then buy under the resulting contract. For a security tool vendor it can shorten the path to many buyers. This is not legal advice.
Terms to know
Solicitation is the formal request a public body issues to buy something.
Cooperative contract is a contract awarded from one solicitation that other eligible public entities may use.
Lead state model is the approach NASPO ValuePoint describes, where a state leads a solicitation with support from multistate sourcing teams.
The NASPO ValuePoint page says the aim is better prices and terms for public buyers, and less repeated bid preparation for contractors. It also says eligible users include all 50 states, the District of Columbia, U.S. territories, political subdivisions and other eligible entities, and points readers to its buyer pages for eligibility rules.
Why a buyer might choose one
- Less paperwork. The competitive step has already happened for the contract vehicle.
- Pre-set terms. The contract carries base terms that the buyer can adopt.
- Speed. A school IT lead may reach a signed order faster than with a fresh bid.
The buyer still has to check whether their own rules allow using the contract, and whether the product on it fits their need. NASPO's page does not describe the specifics of how an entity joins a contract, so read the buyer FAQ on their site.
What a vendor should know
| Question | Why it matters |
|---|---|
| Is the product category on the contract? | A contract only covers what it lists |
| Who may order? | Eligibility follows the contract and each entity's rules |
| Do base terms cover security terms the buyer needs? | Buyers may still add their own security exhibits |
| Who supports the account after award? | Buyers will ask who to call |
Cooperative contract versus a direct bid
A direct bid gives the buyer full control of requirements and evaluation. A cooperative contract trades some of that control for speed and shared effort. Neither removes the security review. A buyer using a cooperative vehicle often still sends a questionnaire, asks for evidence and may run a pilot.
Questions a buyer should ask procurement
- Is there an existing cooperative contract that lists our product category?
- Does our entity allow orders under it, and who approves that choice?
- Which terms come from the base contract, and which can we add, such as a data security exhibit?
- Who signs, and what is the order process?
- Does the contract name support contacts and response times we can hold the vendor to?
Write the answers into the purchase record. If the vendor is not on a contract your entity can use, ask whether a direct quote is possible.
What a security team can do with this
If you are the buyer, ask procurement early whether a cooperative vehicle exists for your category. Then list the security checks that still apply: data handling terms, access controls, breach notice, and exit. If you are the vendor, prepare your standard security packet so it goes out the same day a buyer asks.
See also the steps in a public sector security tool purchase.
Quick check
Does a cooperative contract skip security review?
No. It speeds the contracting step. Buyers usually still review security and data handling.
Who can use a NASPO ValuePoint contract?
NASPO says public entities including states, the District of Columbia, territories and political subdivisions. Check the buyer pages for exact eligibility.
Sources
Last reviewed: 19 October 2026.
