For local government and district purchasing
Two honest statements, and the second one costs vendors more than the first. A cooperative contract is usable only where the lead agency’s competition actually covered the scope you are buying — and the risk of a mismatch lands on your file, not on the seller’s. What exists here is a small purchase, your own solicitation, or a partner subcontract described as exactly that.
The calendar is not negotiable. A purchase above a threshold goes to a board or a council that meets on a fixed schedule, with an agenda deadline before that, and a legal notice period before that. Miss the packet deadline and the answer is six weeks later regardless of urgency.
The ordinance adds constraints a state or federal buyer does not have: local preference, small and minority business participation, prevailing wage on some categories, and sometimes a residency requirement. Each is legitimate and each narrows the field before merit is considered.
Everything is public in a way that federal procurement is not, immediately and locally. The file will be read by a losing bidder, by a local reporter, and by a resident with a grievance and a records request form — often within days rather than years.
And the office is small. In many counties one person handles purchasing for every department, which means depth on any single category is impossible and reliance on cooperative contracts is not laziness, it is arithmetic.
Which is precisely why a co-op number gets waved. It looks like competition already done, it saves the calendar, and the question of whether the lead agency competed this scope is the one nobody has time to check — until somebody does.
Using a cooperative contract requires establishing that the lead agency’s competition covered this scope, and that verification is the step with no time budgeted for it — so it is the step most often skipped.
That is the actual exposure, and it is created by the vendor and carried by the buyer. A seller who shows a co-op number and does not volunteer its scope boundaries has transferred a risk without mentioning it.
So this page refuses that move twice. We hold no cooperative contract of our own — no lead agency has competed us. And where a partner holds one, we will not point at it as though it authorised our scope. If a partner’s cooperative contract genuinely covers what you are buying, that is a question about the lead agency’s solicitation, and the honest thing is to hand you the solicitation language and let your counsel read it rather than to assert coverage.
What exists instead is three routes with plain limits. A small purchase inside your own threshold, which fits a bounded first scope and does not touch the board calendar. Your own solicitation, on your own timeline, with us as one respondent. Or a subcontract under a partner’s contract with your entity, described as a subcontract in every document.
And the fourth answer, again: not a candidate. A scope that must be executed through a cooperative contract this quarter is not one we can serve, and saying so before an agenda deadline is more useful than after.
Scope coverage verified rather than assumed — measured by whether the lead solicitation language is in the file, rather than a vendor’s coverage claim.
Time to eliminate or shortlist this company — measured by whether the route answer was available before an agenda deadline rather than after.
Requirements shaped around an unavailable route — measured by count of scopes that had to be re-shaped once the purchasing route was established.
Board calendar surprises — measured by count of items that missed a packet deadline because a route question was unresolved.
Defensibility of the file to a records request — measured by whether every representation in the file can be checked without contacting the vendor.
any cooperative contract, any lead agency award, any statewide or interlocal agreement of our own, and any coverage assertion about a contract somebody else holds. We will hand over a lead agency’s solicitation language; we will not tell you it covers your scope, because that is your counsel’s determination and the consequence of it lands on your file.
Where a partner holds a cooperative contract and a route through it may exist, the honest structure is a subcontract: the partner holds the contract with your entity and carries its terms, and we are a subcontractor described that way in every document.
Whether the lead agency’s competition covered a given scope is a legal question about their solicitation, not a marketing question about our capability. We will provide the solicitation and the contract language; your counsel decides. A vendor who answers that question for you has answered a question they do not own.
For a small purchase the relationship is direct and bounded by your own threshold, which suits the bounded first scope this architecture recommends independently.
Local preference, participation and wage requirements are established before scoping rather than discovered during it, because a scope built without them is a scope that has to be rebuilt.
Because the person who pays for a wrong coverage assertion is the purchasing agent, not the seller. A vendor asserting that a co-op covers your scope has given you something that feels like assurance and carries none, and when a protest arrives the assertion is not in your file — the award is.
So the position is: we hold none, and we do not characterise anybody else’s. That costs us the fastest route in local government and it is the only version of this page that a purchasing agent could rely on.
Every representation we make is one you can check in a public record without contacting us, which is the standard a file read by a losing bidder actually needs.
And on assurance: an independent SOC 2 Type II attestation is in progress and no report exists yet. Where a state or local requirement attaches to a specific category, terms are agreed in writing during scoping.
The purchasing agent needs a route answer early enough to matter, which means before an agenda deadline rather than after a demonstration. That answer is on this page rather than in a meeting.
Counsel’s question, where a partner’s cooperative contract is in play, is whether the lead agency competed this scope. They should read the solicitation rather than a summary, and we provide the solicitation.
The clerk’s concern is the file and the records request. Everything we represent is checkable publicly, and the assurance position goes into the file in writing rather than as a claim on a slide.
And a board reading an agenda item wants one sentence about why this route and not another. That sentence should be true and short, and it is easier to write when the vendor has not overstated anything.
One bounded observation scope sized to your own small purchase threshold, with the deliverable and the measurement written before the purchase order, and no board action required.
Sizing under the threshold is not an avoidance of scrutiny — the file is still public and still built to be read. It is that a bounded observation scope which requires a board item has made the calendar the project, and the calendar will win.
The observation phase produces a measurement your entity keeps whatever happens next, which is the only thing worth buying at that size.
If your requirement is genuinely above the threshold and needs a competitive path, then your own solicitation is the route and we are one respondent on your timeline. That is slower and it is honest.
Possibly they can, and the question that decides it is whether the lead agency’s solicitation actually competed the scope you are buying — not whether the number exists. Ask them for the lead solicitation language rather than the contract number, and have your counsel read it against your scope. If they will not provide it, that is information. We hold no cooperative contract at all, so we cannot offer you that route, and we will not point at somebody else’s and let the scope question land on your file.
It may, and that is worth establishing first rather than last. Local preference, participation goals and prevailing wage requirements should shape a scope before it is written, because a scope built without them gets rebuilt. If the ordinance closes the route, that is the correct outcome and we would rather know before you spend an agenda cycle on it.
Which is exactly why the recommended first scope is sized under your small purchase threshold — no solicitation, no board item, no packet deadline. The observation phase produces a measurement your entity keeps whatever happens afterwards, and if the measurement is not worth a small purchase to you, the honest conclusion is not to proceed. Nothing about a cooperative contract would change that arithmetic; it would only change who carries the scope risk.
The file has to be defensible on its own, so the useful test is whether every representation in it can be checked by a reporter without calling us. Ours can: what we hold is nothing, and that is verifiable in the public contract record of any cooperative programme. A bounded small purchase with a written deliverable and a stated measurement is a defensible file. An award through a co-op whose scope coverage nobody verified is not, however well-known the vendor is.