A business office reaches this question in a fairly specific way. Someone has scoped a piece of technology work, found that an awarded cooperative contract appears to cover it, and now has to decide whether to buy through that contract or run a solicitation of their own. The decision usually gets made on how much time is left before the work has to start, which is the one input that should not decide it.
It is a real choice with a real answer, and the answer is more definite than most procurement questions.
The short answer
Use the cooperative contract when the competition already conducted genuinely covers the work you are about to buy, and your own rules permit you to rely on it. Run your own solicitation when it does not, or when they do not.
What the choice is not is a choice between procuring and not procuring. A cooperative contract is not an exemption from your procurement obligations; it is one recognized way of satisfying them. Where federal award funds are involved, the federal standards say so directly. 2 CFR 200.318(e) states that an entity "is encouraged to enter into state and local intergovernmental agreements or inter-entity agreements where appropriate for procurement or use of common or shared goods and services", and that "competition requirements will be met with documented procurement actions using strategic sourcing, shared services, and other similar procurement arrangements."
Read that last clause carefully, because it carries the whole answer. Competition requirements are met with documented procurement actions. The arrangement supplies the competition. You still supply the documentation, the specification and the judgment that this contract fits this purchase. Nothing about buying cooperatively removes any of the three.
Where they differ
The two routes differ on three things, and price is not one of them.
What competition has already happened. Running your own solicitation puts your specific requirement in front of the market and produces responses to that requirement. Buying through a cooperative contract inherits a competition that was run earlier, for a category of work, by another public entity acting as the lead agency. That earlier competition is real, and it is also general. It was conducted for a scope, not for your project.
So the question that decides the route is not whether competition happened. It is whether the competition that happened covers what you are buying now. A contract awarded for technology consulting services covers technology consulting services. It does not stretch to cover work that a reasonable reader would say sits outside it, and the fact that an awarded supplier is willing to do that work does not extend the award.
Who writes the specification. Under your own solicitation you write a specification and the market answers it. Under a cooperative contract you still write the specification, but you write it in the order rather than in a public document, and nobody is required to tell you it is thin. This is the difference buyers most often miss, and it is the reason a cooperative purchase can go wrong while remaining entirely compliant. The route you choose changes who reviews your scope before the work starts. It does not change whether you need one.
What record you finish with. A solicitation leaves a file that explains itself: the requirement, who responded, how responses were evaluated, why one was selected. A cooperative purchase leaves a much thinner trail unless you deliberately create one, because the competitive record sits with the lead agency rather than with you. What you hold afterwards is your own note explaining why this contract covered this work. If nobody wrote that note, the file has a hole in it exactly where an auditor will look.
Underneath both routes sits a separate question that neither answers: which procurement method your purchase requires in the first place. 2 CFR 200.320, "Methods of procurement to be followed", sets out three. Informal methods cover micro-purchases and small purchases. Formal methods cover sealed bids and competitive proposals. Noncompetitive procurement is permitted only where one of several listed circumstances applies, among them a single available source or a public exigency. Which method your purchase falls under is decided by its value against thresholds the regulation defines elsewhere by cross-reference, and by your own policy where local rules are stricter. That question survives whichever route you pick.
When each is right
The cooperative contract is the better route when three things are true at once. The work sits plainly inside the awarded scope. Your governing rules permit you to rely on an interlocal or cooperative agreement for a purchase of this size. And what you need from the market is a supplier who can do a well understood piece of work, rather than a set of competing views on how it should be approached.
Most routine technology work meets all three. Refreshing infrastructure, extending a network to a new building, adding capacity to a team for a defined period, delivering an assessment against a standard framework: these are specified more precisely by you than by any competitive process, and putting them to the market rarely surfaces an approach you had not considered.
Your own solicitation is the better route when any one of those is false, and there are four common cases.
The requirement sits outside the awarded scope, or close enough to the edge that reasonable people would argue about it. The work is genuinely novel, so what you want from the market is competing approaches rather than a price for an approach you have already chosen. Your local policy sets a threshold above which a formal solicitation is required regardless of what contracts exist, which is common and which your policy manual will state plainly. Or you need contract terms the awarded contract does not carry, and the supplier will not accept them in a purchase order.
One route that is not on this list is noncompetitive procurement. Buying through a cooperative contract is sometimes described inside an organization as a sole source, and it is not one. Noncompetitive procurement is its own category with its own conditions, and describing a cooperative purchase that way in your own file mislabels it as something harder to defend than what it actually is.
How to choose
Answer four questions in writing before the decision is made, not after.
Does the awarded scope cover this work? Read the scope, not the vendor list. Write one or two sentences saying which part of it covers what you are buying. If those sentences are hard to write, that difficulty is the finding.
What authority permits us to use it? This is where the two funding worlds separate. If the purchase uses federal award funds, the federal procurement standards apply on top of everything else, and 200.318(e) is the provision that recognizes the arrangement. If it does not, federal standards are not your authority and citing them is a mistake. Your authority is state law and local policy, both of which vary and neither of which this page can state for you. Cite the one that actually applies to the money you are spending.
Which procurement method does the value require? Informal, formal, or one of the noncompetitive circumstances. Answer it against the thresholds your rules apply, and record the answer.
Who approved the choice, and on what date? A route decision with no name against it is the part of the file that ages worst.
Those four answers are the record. They fit on one page, they take an afternoon at most, and they are the difference between a purchase that explains itself in three years and one that does not. If you want the questions to put to a supplier once the route is settled, they are a separate exercise, and the supplier evaluation checklist covers them.
Where this leaves the order
If the answer is your own solicitation, this page has done its job and the rest is your procurement process. If the answer is the cooperative contract, the work now moves to writing a scope the supplier can price and taking it through approval, which is the purchasing sequence rather than a further comparison. The background on how these contracts are structured, and what they do not do, is in the guide to cooperative purchasing.
For the technology consulting work this cluster covers, the awarded vehicle is TIPS Contract 230601, and LABUSA is an awarded supplier under it. What that award does and does not settle, including the scope it was competed for, is set out on the contract that competition was already run for. If you have a purchase coming and want a second read on whether the awarded scope covers it, you are welcome to send us the requirement you are working from.