An award tells you that a procurement happened. It does not tell you that the supplier who holds it is right for your project. Contract 230601 covers a broad range of work, several awarded vendors can quote the same requirement, and the contract does not rank them. That judgment is yours.
This is a guide to making it: what to ask, what to compare, what should worry you, and how to reach a decision you can defend to whoever signs the purchase order. It does not tell you which supplier to choose, and it deliberately includes the questions you should put to LABUSA.
One thing is settled before you start, and it changes what the comparison is about.
Under this contract the hourly ceilings are published as part of the award. The rate is fixed before anyone speaks to you, so what you are really choosing between is everything a rate does not describe: who does the work, how much of it they believe there is, what you hold at the end, and what happens after that.
If you are still deciding whether a cooperative contract is the right vehicle, start with what an awarded vendor actually is. If you want the figures, they are published in full in our guide to what this contract costs. This page assumes both and moves on to the supplier.
Test the capability claim, not the contract category
A contract category is a boundary, not a qualification. A supplier can be legitimately awarded for consulting services and still have never done the specific thing you need. The useful question is not whether the work falls inside the scope. It is whether this supplier has done it, recently, at something like your size.
Ask a claimed capability to become specific. A supplier who has genuinely done the work can name things without preparation:
- the platform and the version, not the category. "Content management" is a category. A named platform at a named major version is a capability.
- where they last did it at roughly your scale, and roughly when.
- who did it, and whether those people are available for your work.
- what went wrong on that engagement, and what they changed afterwards.
Vagueness on the first three is a capability that lives in a proposal rather than in the organization. Vagueness on the fourth usually means nobody senior was close to the work. If you are not yet sure which kind of engagement you are buying, our guide to consulting engagement models sets out the four you are likely to be offered.
Look for experience in an environment shaped like yours
Public-sector work has constraints that break schedules: approval steps that cannot be compressed, fiscal years that end whether or not the project does, systems of record that predate everyone in the room, and staff whose day job continues throughout. A supplier who has only worked commercially will often be genuinely good and still surprised by all of it.
A logo list does not establish this. A reference call does, if you ask it to. Ask for a counterpart in an organization like yours, in a role like yours, and ask what they had to do themselves that they had not expected, and what the handover was actually like. Those two answers tell you more than an hour of presentation.
If you are buying for a school district, the constraints are specific enough to be worth reading separately: what makes a district different as a technology buyer.
Ask who does the work, and how your sites get covered
Organizations are awarded contracts. People deliver projects. The gap between those two sentences is where a good many disappointing engagements live, and closing it is mostly a matter of asking.
- Which named individuals will do this work, and what share of their time do you have?
- What happens if one of them leaves partway through, and who decides the replacement is acceptable?
- Is any part of the work subcontracted, and to whom? A supplier should tell you without being pressed.
- If you have several sites, how is each one covered? Remote for most of it and onsite for some is a normal and sensible answer. What matters is that somebody has actually thought about it before you asked.
Multi-site coverage is worth settling in writing rather than in conversation, because it is the assumption most likely to differ between what you pictured and what was quoted. Where the work is staffing rather than a defined project, the questions change shape, and bringing in technology professionals covers those separately.
Ask what the supplier needs from you
This is the question buyers most often skip, and it is the most diagnostic one on this page. Every engagement depends on the customer for something: access to systems, decisions made by a particular date, an environment to work in, time from your own staff, data in a usable form.
A supplier who has done the work before can list those dependencies without hesitating, because they have been burned by each of them. A supplier who cannot is telling you something important. Their list is also your first honest estimate of what the project will cost you internally, a real cost that rarely appears in any quote. When you are ready to turn all this into a purchase, our guide to the purchasing sequence itself covers what happens inside your organization.
Ask what is covered after acceptance
Implementation ends. The system does not. The period after acceptance is where expectations diverge most sharply, usually because nobody wrote them down while everyone was focused on delivery.
- Is there a defect period, how long is it, and what counts as a defect rather than a new request?
- Is ongoing support included, sold separately, or simply not offered?
- What documentation do you receive, in what format, and who signs to accept it?
- If your own staff are to run this afterwards, what does the handover consist of, and when does it happen? Handover scheduled for the final week is handover that will not happen.
Settle these at quote time, when you still have a choice of supplier, rather than after acceptance when you do not. LABUSA publishes its own support and response commitments in its service level agreement, which is the kind of document you should expect any supplier to be able to produce.
Insurance, data handling and certifications you can verify
This is due diligence on the supplier, a different exercise from your own security program. If you are building that, where a security roadmap starts is the place to look. Here the question is narrower: what will this organization be able to reach, and what happens if something goes wrong.
- A certificate naming coverage and limits, not an assurance that they are insured.
- Which of their people will have access to which of your systems, at what privilege, and how that access ends when the engagement does.
- What screening applies to staff who will be onsite or handling sensitive records, and whether your own rules require more.
- Where your data will be stored and processed, and what happens to it at the end of the contract.
Certifications deserve one discipline: verify them at the issuing authority, not on the supplier's website. Federal registration and exclusion status is published at SAM.gov, and Texas state vendor programs run through the Comptroller's vendor resources. Check on the day you rely on it, because programs are renamed and restructured more often than supplier websites are updated. Then read the certificate for its scope: a registration covering one part of a business tells you little about another.
What separates two responses under the same contract
When the ceilings are identical, the responses still are not. This is roughly what the difference looks like in practice.
| What you are evaluating | A weak answer | A strong answer |
|---|---|---|
| Capability | "Yes, we do that" | The platform, the version, and the nearest comparable engagement |
| Effort | A single total | The work broken out, with the assumption behind each part stated |
| People | "Our team" | Named individuals, their availability, and what happens if one leaves |
| Dependencies | Silence | A written list of what you provide, and by when |
| Handover | "Documentation will be provided" | The artefact, its format, and who signs to accept it |
| After acceptance | "We support our work" | A stated period, what it covers, and what it does not |
Warning signs
None of these is disqualifying on its own. Two or three together usually mean the engagement will be harder than the proposal suggests.
- Every question is answered yes. A supplier who has never once said "that is outside what we do well" is selling, not scoping.
- The estimate arrives with no assumptions attached. An estimate without assumptions is a number without a basis, and it will move.
- Nobody who will do the work has been in any conversation.
- Your questions about handover keep being answered with reassurance rather than with an artefact and a date.
- The supplier cannot say what it needs from you.
The questions to put to a supplier
Take these into the conversation. Every one should be comfortable for a supplier to answer.
- Where have you done this specific work, at roughly our scale, and when?
- Which named people will deliver it, and what share of their time do we have?
- Is the requested work within your awarded scope under this contract?
- What are you assuming, and what happens to the estimate if an assumption is wrong?
- What will we hold at the end, in what format, and who accepts it?
- What do you need from us, and by when?
- What support applies after acceptance, and what is excluded?
- How are changes to scope or effort handled once work has started?
Applying this to LABUSA
It would be a poor checklist that exempted its author. What LABUSA can evidence from published material: awarded TIPS contracts held since 2019, hourly ceilings published as part of the award rather than quoted per customer, and ISO 9001:2015 and ISO/IEC 27001:2022 registrations. LABUSA's contract response also identifies service capability across all fifty states, and the honest thing to say is what this page says about any such statement: it is a claim in a document, and the way to test it is to ask how coverage would be staffed for your specific locations.
What you should still ask us for, rather than assume: the named people for your work, the scope statement on those certificates, a reference in an organization shaped like yours, and the support terms written into the ordering document. A full description of what Contract 230601 covers is on the contract page, and you are welcome to start a scoping conversation whenever the requirement is clear enough to describe.
Frequently asked questions about evaluating a TIPS 230601 supplier
Does holding a TIPS contract mean a supplier has been evaluated for our project?
No. An award establishes that a competitive process took place for a category of work. It says nothing about whether a particular supplier suits a particular project, which is the evaluation this page is about and which remains yours to carry out.
What evidence can we reasonably ask a supplier to provide?
References in a comparable organization, the names and availability of the people who will do the work, a certificate of insurance showing coverage and limits, a sample of the documentation you would receive, and the scope statements on any certification claimed. All of that is ordinary to ask for.
How do we compare two quotes when the published ceilings are the same?
By comparing everything the rate does not describe: the effort each supplier believes the work needs and why, who would do it, what you would hold at the end, and what happens after acceptance. The figures are in our guide to what this contract costs.
What are the warning signs that a supplier is not the right fit?
Unqualified agreement to every requirement, an estimate with no stated assumptions, no contact with the people who would actually deliver, and an inability to say what the supplier needs from you. Any one may be innocent. Several together rarely are.
Can we ask more than one awarded vendor to quote?
Eligible members generally may, subject to their own procurement policies. If you do, give each supplier the same written requirement: responses to differently worded requests cannot be compared meaningfully however carefully you read them.
Do we still have to run our own solicitation if we use Contract 230601?
That depends on your organization and is not a question a supplier can answer for you. A cooperative contract may help eligible organizations streamline procurement by using a competitively solicited agreement, subject to applicable state and local law and to your own procurement policies. Whether it satisfies your requirements in a given case is a determination your organization must make. Our guide to the purchasing sequence sets out where that determination fits.
Can we define our own scope, deliverables and acceptance criteria?
Yes, and you should. The contract is the vehicle; the project is still yours to specify. A supplier's willingness to work to your definitions is itself worth evaluating, and one that resists writing acceptance criteria down is telling you something.