Cooperative Purchasing Agreements for Technology
A cooperative purchasing agreement is a contract that has already been competitively bid and publicly awarded by a lead agency. Other agencies buy from that contract without repeating the full solicitation process themselves. The legal logic is straightforward; the operational reality is not.
The lead agency's original solicitation satisfies the competitive bid requirement, and participating agencies step into that compliance rather than generating it independently. Every state has enacted laws authorizing the method. Most state, local, and education agencies can use cooperative contracts as an approved procurement pathway.
The distinction between lead agency and participating agency matters more than it looks on paper. The lead agency runs the solicitation, negotiates master contract terms, and owns the competitive process. Participating agencies access the contract after award, but they are not passive passengers. They execute participating addenda or amendments to the master contract, and that is precisely where local compliance requirements get layered in: state law provisions, jurisdiction-specific terms, locally required clauses. I have seen agencies treat that addendum review as a rubber stamp, and it almost always costs them later, usually surfacing in an audit at the least convenient possible moment.
Cooperative contracts now account for roughly 20% of spending for public agencies. That is mainstream institutional adoption, not a niche workaround. But permissibility varies by state. Some jurisdictions require an approved cooperative vehicle above certain dollar thresholds; others treat cooperative purchasing as discretionary regardless of purchase size. What works in Minnesota is not sanctioned in Georgia under identical circumstances. Local statute governs, and no amount of precedent from another jurisdiction changes that.
Delayed procurement costs agencies budget windows, compliance deadlines, and sometimes vendor availability. The cooperative model exists to break that cycle. When used correctly, it does.
The Two Structural Models: Joint Solicitation Versus Piggybacking
Piggybacking is more common, and its appeal is obvious. One agency uses another's already-awarded contract without having participated in the original solicitation. No upfront volume commitment required; agencies buy what they need when they need it.
That flexibility is genuine. The pricing it produces, however, is not maximal, and this distinction matters more than most procurement leaders initially appreciate. Because suppliers cannot predict purchase volume under an open-ended piggybacking arrangement, they price against uncertainty. The result is pricing that is competitive relative to running an independent solicitation, but not as aggressive as committed demand would generate. You cannot negotiate away that structural limitation. It is baked into how vendors assess risk, and no amount of relationship-building at the table changes the underlying math.
Joint solicitation works from the opposite direction. Two or more agencies combine their requirements into a single solicitation before any contract is awarded. Suppliers price against guaranteed minimums. The discounts improve. The tradeoff is that agencies must align requirements upfront, which demands coordination, time, and organizational compatibility that not every procurement relationship can support. Joint solicitation is harder to execute. It is also genuinely better for large, predictable technology deployments where agencies can commit requirements months in advance and actually know what they need.
NIGP identifies Multiple Award Schedules as a distinct structural model, in which federal or state governments award contracts across multiple suppliers for similar categories. Agencies using MAS contracts still need to verify that their usage meets applicable competition requirements and authorized procurement methods; the pre-existing award does not eliminate that responsibility.
The practical read: piggybacking suits time-sensitive or opportunistic technology purchases where flexibility outweighs pricing optimization. Joint solicitation suits planned, high-volume deployments where agencies can commit in advance and want to extract the most favorable terms the market will actually offer.
The Major Cooperative Vehicles Available for Technology Purchases
The cooperative technology marketplace is not monolithic, and treating it as such is the first mistake agencies make. The vehicles differ by eligibility, scope, geography, and structure. Choosing the right one requires knowing what each one actually offers.
GSA's Multiple Award Schedule allows eligible state and local governments to purchase commercial IT products and services from pre-vetted federal vendors. The IT Category covers hardware, software, mobile device management, and firmware, among other areas. Broad recognition, substantial supplier depth.
NASPO ValuePoint is the cooperative purchasing division of the National Association of State Procurement Officials, operating on a lead-state model that aggregates demand across all 50 states, DC, territories, and political subdivisions. Its Cloud and Software Solutions Master Agreements, awarded through Utah as lead state, include 58 suppliers covering SaaS, PaaS, IaaS, cloud migration, security, compliance, and managed services. Over 30 states, including California, have signed participating addenda for cloud solutions. That level of adoption is not accidental; it reflects something real about the vehicle's utility in this category.
OMNIA Partners positions itself as the nation's largest cooperative purchasing group, with purchasing power aggregated across more than 234,000 member entities and access to more than 300 publicly awarded contracts through its OPUS platform.
Sourcewell, established by the Minnesota legislature, charges no membership fee. More than 50,000 member agencies across the United States and Canada access contracts at no cost. Suppliers pay a percentage back to Sourcewell upon contract execution, which funds the cooperative itself.
Texas DIR serves state agencies, local governments, and educational institutions within Texas, distributing hundreds of millions of dollars in K-12 and local government technology purchases in recent reporting periods.
E&I Cooperative Services is nonprofit and member-owned, focused exclusively on education. Its terms and conditions are built specifically around education-sector procurement requirements, which meaningfully reduces the compliance friction that comes with adapting general-purpose contracts to an academic context.
None of these vehicles are interchangeable. Eligibility depends on entity type, geography, and the specific technology category at issue.
What Technology Categories Cooperative Contracts Actually Cover
The coverage has expanded considerably over the past decade. Hardware, networking equipment, audiovisual systems, software licenses, SaaS, PaaS, IaaS, managed services, cybersecurity, cloud migration, consulting, and IT services all fall within current cooperative contract scopes. That range is not incidental; it reflects deliberate effort by lead agencies and cooperative administrators to track where public-sector technology spending is actually moving.
The bundling capability matters in practice. A school district building out a smart classroom environment can procure hardware, software licenses, networking equipment, and audiovisual systems through a single contract rather than running parallel procurement processes for each category. That consolidation removes administrative burden that compounds significantly when multiplied across dozens of annual technology purchases.
AI tools fit the current cooperative contract model well, for a specific reason: off-the-shelf licenses for writing assistants, data analysis platforms, and automated document management are exactly the kind of commercial software products that MAS and cloud solution contracts are designed to deliver. These are catalog purchases, not bespoke procurements requiring custom scoping. The cooperative infrastructure handles catalog purchases efficiently.
Illinois higher education institutions used 20 different cooperative purchasing organizations with approximately $890 million in total cooperative spending in fiscal year 2024. The variety of organizations they drew from reflects the variety of technology needs. No single vehicle covered everything, which is itself instructive.
The important nuance is scope verification. Complex requirements, including custom software development and highly specialized consulting engagements, do not always map cleanly onto existing cooperative contract scopes. Procurement leaders who assume a contract covers their need without confirming scope alignment are creating legal and operational risk. Approximate fit is not legally defensible, and in my experience, the agencies most confident about fit are sometimes the ones most exposed.
Where the Real Cost and Time Savings Come From — and What Limits Them
Savings figures associated with cooperative purchasing cover a wide range depending on category, contract structure, and whether the participating agency can make any form of volume commitment. NIGP studies cite savings of up to 15% annually; other analyses show figures as high as 30%. The spread is itself informative. Actual results depend heavily on specifics, and agencies that treat cooperative purchasing as a guaranteed discount mechanism will occasionally be disappointed.
Time savings are the more consistent benefit. Removing bid preparation, vendor evaluation, and demonstration scheduling can cut the better part of a year from a technology acquisition. For an agency facing a compliance deadline or a budget window that closes on a specific date, that is not a minor administrative convenience; it can be the difference between delivering a project and watching it die in procurement.
The structural pricing limitation of piggybacking deserves more candor than it typically gets. When vendors cannot know the quantity or delivery schedule of future orders, they build uncertainty into their pricing. Agencies that can commit to definite quantities and delivery schedules will consistently secure better terms. The closer a cooperative purchase resembles a firm volume commitment, the better the pricing outcome. Open-ended access is valuable; it just does not produce the same result as committed demand, and conflating the two leads to budget projections that do not survive contact with vendor negotiations.
Administrative fees and rebates paid to lead states or cooperative administrators are real costs. NASPO ValuePoint describes these fees as needing to be "reasonable," which establishes a meaningful standard but not a guarantee of inconsequential impact on total cost.
Some critics argue that cooperative procurement serves convenience more than genuine fiscal savings, and that private-sector cooperative operators compensated on executed contract volume can cost taxpayers more than a direct competitive bid would under the right conditions. That counterargument has merit. As independent audits of cooperative purchasing become more common across jurisdictions, procurement leaders should be prepared to address it with actual data rather than habit and assumption.
Compliance Requirements That Procurement Leaders Must Verify Before Using a Cooperative Contract
The competitive bid requirement is satisfied by the lead agency's original solicitation. That is the foundation of the entire model. It does not, however, eliminate all compliance obligations for participating agencies, and agencies that treat the cooperative model as compliance-complete tend to discover otherwise in audit findings, sometimes years after the fact.
FEMA guidance makes clear that cooperative purchasing programs do not always include the contract provisions required by federal law. Agencies spending federal funds must verify that the cooperative's vendor agreements include required clauses before proceeding. The absence of required federal provisions can jeopardize reimbursement and generate findings that are expensive and time-consuming to resolve, and "we used an approved cooperative" is not a sufficient defense when the provisions were never there.
For federally funded purchases, participating agencies must also ensure their solicitation includes a clear, accurate description of actual scope — not the lead agency's original scope, which was written for different needs in a different jurisdiction. Affirmative steps to encourage small business, minority-owned business, and women-owned enterprise participation are federally required; agencies must confirm the cooperative's process meets that standard rather than assuming it does.
The participating addendum is where local law gets incorporated into the cooperative contract structure. Reviewing it is not a courtesy step. It is the document that makes the cooperative contract legally operative within a specific jurisdiction, and it is where the gap between master contract terms and local requirements either gets closed or quietly remains open until someone looks.
Complexity scales with participation. The more agencies on a cooperative and the more vendors in the pool, the harder it becomes to track which terms apply to which transaction. Larger cooperative vehicles offer more choice; they also demand more diligence to navigate.
Before using any cooperative contract for a technology acquisition, four verifications are non-negotiable: authorization under state law, scope alignment with the actual procurement need, inclusion of required federal provisions if federal funds are involved, and reasonableness of administrative fees relative to what an independent bid would yield. Each one represents a distinct failure mode.
How Small and Mid-Sized Agencies Benefit — and Where the Access Gaps Remain
Cooperative purchasing meaningfully levels the competitive field for smaller public entities. A rural school district or small county government can access pre-negotiated pricing and established vendor relationships that would otherwise require procurement staff capacity and budget they simply do not have. The model provides institutional leverage without requiring institutional scale, which is genuinely valuable and not something smaller agencies can easily replicate on their own.
The Michigan Municipal Services Authority illustrates this in practice. Created in 2012 as a virtual city, it provides small municipalities with cooperative procurement for managed IT, cybersecurity, and electronic payments. Vendors report streamlined access to more prospective clients and more consistent pricing outcomes. Small agencies that could not independently attract competitive bids gain access to a functioning market they would otherwise sit outside of entirely.
The access gap runs in a different direction when it comes to vendor opportunity. Cooperative contracts naturally favor larger suppliers who can deliver at scale. The broad, online structure of most cooperative solicitations systematically advantages national vendors over local or regional businesses. Solicitations are typically written around the lead agency's jurisdiction and its vendor market, which often bears little resemblance to the local vendor landscape of participating agencies hundreds of miles away. Local businesses can find themselves structurally excluded from opportunities in their own communities. That tension is worth naming honestly, even when it lacks an easy resolution.
The data on whether cooperative procurement expands or contracts opportunity for small, diverse, and local vendors remains limited and genuinely contested. This is an open question that procurement leaders and policymakers are still working through, and anyone who tells you the answer is settled is selling something.
For technology specifically, this tension is less acute than in construction or professional services. Software licenses, cloud platforms, and cybersecurity tools are rarely local-vendor markets to begin with. The vendor pool for these categories is already concentrated among national and global suppliers, which reduces the friction on the local vendor question in technology procurement, though it does not eliminate it entirely.
How to Decide Whether a Cooperative Contract Fits a Specific Technology Acquisition
Start with scope. Does the cooperative contract's stated scope match what the agency actually needs, not approximately, but specifically enough to be legally defensible? If the answer requires generous inference or creative interpretation, the scope alignment is not sufficient.
Check authorization. Is this cooperative vehicle explicitly authorized under the agency's state law? Does any dollar threshold apply that would require or prohibit its use? Cooperative purchasing is an approved procurement method in every state, but the specific vehicle must be authorized under applicable statute or regulation, and those specifics vary in ways that are easy to overlook when you are moving fast.
Assess timing and volume. If the purchase can be planned in advance and quantity can be committed, explore joint solicitation or contracts that accommodate volume commitments, because better pricing consistently follows from better demand visibility. If the need is immediate or volume is genuinely uncertain, piggybacking is the appropriate practical choice.
Evaluate the vendor pool. Are the awarded suppliers on the cooperative contract capable of serving the agency's geographic location, technical requirements, and operational scale? A nationally awarded contract with no suppliers who can actually deliver to the agency's location is not a functional option in any meaningful sense.
Calculate total cost including fees. Administrative fees and rebates paid to the cooperative are real costs. They belong in any honest comparison against what an independent solicitation would produce. Omitting them makes the cooperative option look better than it sometimes is.
Verify federal provisions if federal funds are involved. This step cannot be delegated to assumption or past practice.
National cooperative sales at the state and local level have grown to tens of billions of dollars annually. That growth reflects broad institutional validation of the model. But scale does not substitute for judgment. The right cooperative contract is not the fastest one to access. It is the one whose scope, vendor pool, compliance posture, and pricing terms align specifically with the acquisition at hand, and finding that alignment is what separates a procurement that holds up from one that unravels when it matters most.
