A technology director works out in March that the network needs replacing before students return in August. The work is specialized, the district does not employ anyone who has done it at this scale, and the obvious answer is to bring in outside help. The less obvious problem is that finding that help competitively can take longer than the work itself.
Cooperative purchasing exists to solve that specific problem. It is not a discount scheme and it is not a way around procurement rules. It is an arrangement in which one public agency runs a competitive solicitation properly, once, and other eligible organizations are permitted to buy from the resulting contract instead of repeating the exercise themselves.
What a cooperative purchasing contract actually is
A lead public agency identifies a category of goods or services that many organizations need. It advertises, solicits, evaluates responses against published criteria, and awards contracts to the suppliers that meet them. That much is an ordinary competitive procurement.
The difference is who may use the result. A cooperative contract is written so that other eligible organizations, usually members of the cooperative, can purchase under the same terms. The lead agency has already done the competitive work. A member organization that is permitted to use cooperative contracts can rely on that work rather than running its own.
Two things follow from this, and both matter more than the convenience.
- The competition happened at the point the contract was awarded, not at the point you buy. If your own rules require competition at the point of purchase for the amount you are spending, a cooperative contract does not remove that requirement.
- The scope is fixed by the original solicitation. A contract awarded for one category of work does not stretch to cover something adjacent because both parties would find that convenient.
Why public organizations use the model
The usual reason given is speed, and speed is real. But the more durable reasons are about capacity and risk.
Most public organizations do not have procurement staff sitting idle. Every solicitation consumes specification writing, legal review, evaluation panels, and scoring, and those hours come out of the same finite pool that is also handling construction, transport, insurance, and everything else. A cooperative contract lets a small team direct its scarce procurement effort at the purchases where a bespoke solicitation genuinely adds value.
There is also a quality argument that gets overlooked. Writing a good technical specification for something you have never bought before is difficult, and a poor specification produces a poor field of responses. A cooperative solicitation for a technology category is usually written by people who buy that category repeatedly, and it is evaluated against a larger field than a single organization would attract on its own.
What TIPS is
The Interlocal Purchasing System, universally called TIPS, is a national purchasing cooperative. It is managed by the Region 8 Education Service Center, a Texas education service center based in Pittsburg, Texas, which acts as the lead public agency for the contracts TIPS awards. TIPS states that it has served public agencies since 2002.
Its origins in an education service center explain a good deal about its membership. School districts and other education organizations are heavily represented, but membership is not limited to them, and cities, counties, special districts, higher education institutions, and some nonprofits participate as well. Whether a particular organization is eligible is a question for TIPS and for the organization's own governing rules, not for a supplier. Membership, eligibility, and the current list of awarded contracts are published by TIPS itself at tips-usa.com.
TIPS awards contracts by category. A supplier holds a contract for the specific category it was awarded, and an organization buying technology consulting looks for a contract awarded for technology consulting rather than assuming a supplier's presence on one contract covers everything the supplier sells.
What "awarded vendor" means, and what it does not
A supplier described as an awarded vendor responded to a solicitation in a defined category and was evaluated and awarded a contract under it. That is a meaningful statement about a competitive process having taken place. It is not a certification of quality, it is not an endorsement by the cooperative, and it is not a statement that the supplier is the right choice for your particular requirement.
It is also not permanent. Cooperative contracts run for a term and are re-solicited. LABUSA's own history on the site shows the pattern plainly: the company was awarded contract 190701 in 2019 for web hosting, services and content management, was awarded contract 200302 in 2020 for data center hosting, sales and service, and in 2022 was awarded contract 220701, which the announcement describes as a renewal and replacement for 190701 after three years.
The practical consequence for a buyer is that contract numbers change. A reference in a purchase order should cite the contract that is current at the time of the purchase, not the one somebody remembered from a previous project.
Buying products is not the same as buying professional services
This is the distinction that causes the most trouble, and it is worth being explicit about.
When the purchase is a product, a cooperative contract is close to a catalog. The item is defined, the price is established, and the buying decision is mostly a matter of confirming the specification and the quantity. Little scoping is required because there is little to scope.
When the purchase is professional services, almost nothing is predetermined except the categories of work and the commercial framework. Two districts buying "network consulting" under the same contract can be buying entirely different engagements: one wants a two week assessment and a written recommendation, the other wants a named engineer for eight months. The contract makes the purchase permissible. It does not define what is being bought.
That means a services purchase under a cooperative contract still needs a scope of work, a deliverable, a duration, and an agreed way to tell whether it succeeded. Organizations that treat a services purchase as though it were a catalog purchase tend to discover the gap several months in, when the engagement has run out of money and nobody can agree what was promised. Our guide to what a buyer actually does to purchase IT services through a cooperative contract covers that process in detail.
What a cooperative contract does not do
Four things, all of which remain your organization's responsibility.
- It does not grant purchasing authority. Whether your organization may use cooperative contracts at all, and for what value, is set by your own policies, by statute, and by whatever approval thresholds apply. A supplier cannot answer that question for you.
- It does not remove internal approvals. Board approval, governing body approval, and internal sign-off thresholds apply exactly as they otherwise would.
- It does not guarantee the best price for your specific requirement. It establishes a competitively procured commercial framework. Whether the resulting quote is good value for what you are asking for is still a judgment you have to make.
- It does not define scope. See above. For services, this is the one that matters most.
Questions worth asking before you rely on one
A short list, aimed at the procurement officer rather than the technologist.
- Are we an eligible member of this cooperative, and is our membership current?
- Do our own rules permit cooperative purchasing for a purchase of this type and this value, and is that permission recorded somewhere we can point to?
- Is the contract we intend to cite awarded for the category of work we are actually buying?
- Is that contract current, and what is the correct number to reference today?
- For services, what exactly is the deliverable, over what period, and who accepts it?
- What documentation does our organization expect on file to evidence the decision?
None of these are difficult questions. They are simply easier to answer before a project starts than during an audit.
Where LABUSA fits
LABUSA is an awarded TIPS vendor and holds contracts in several categories, which are listed on the LABUSA contract vehicles page. Technology consulting and related professional services are purchasable under TIPS Contract 230601. Data center services and broader technology solutions sit under separate contracts, because they were separate solicitations.
What is bought under those contracts varies widely. At one end it is an ongoing managed service, such as the managed Drupal hosting that public bodies buy for their public-facing websites. At the other it is a single assessment lasting a few weeks. The contract is the same kind of instrument in both cases. The scoping conversation is not.
The short version
Cooperative purchasing moves the competitive step earlier, so that a public organization can buy specialized help without repeating a solicitation somebody else has already run properly. It saves time and scarce procurement capacity, and for technology categories it often produces a better specification than a single organization could write alone.
What it does not do is decide anything on your behalf. Eligibility, authority, approvals, and scope all stay where they were. Treat it as a well-built instrument that removes one step, rather than as a shortcut around the rest, and it does its job well.