Start from the record
Most technology disputes turn on what a requirement meant, what was delivered and whether it works. Read each contested requirement as written, then check the bid, the deliverables and the evaluation record against it.
When a project has stopped, secure every deliverable, document and access right the contract gives you. Then get a short independent reading of what was delivered, whether it is usable and what it would take to finish.
An opinion your lawyers can use
It states the question, the documents reviewed, the findings and the reasoning, in plain language a committee or a judge can follow. It keeps what the documents show apart from my judgment. If your position is weak on a point, it says so while you can still choose what to do.
Counsel can then size the dispute against the practical options: finish with the vendor under new terms, move the work to another firm, or stop. Settling without that picture can mean paying for work nobody can use.
Depending on your seat
If you head an agency facing a bid challenge, review each contested requirement for the need it served and how many bidders met it. A defensible record has that answer for every requirement. Have procurement counsel assess the challenge before any public response.
If you're on the board after a costly settlement, ask for the dispute's causes mapped to contract terms and decisions. Look for undefined acceptance, verbal changes, unclear ownership and weak remedies. Then require those terms, and an independent review before approval, for technology contracts above a threshold.
What to check before you decide
- Quote each disputed requirement word for word, and note where it can be read more than one way.
- Collect the evidence for each claim: bid text, deliverables, test results and minutes.
- Trace the drafting history of contested requirements, and who gave input.
- Secure all deliverables, documentation and access the contract entitles you to.
- Estimate the cost to finish with the vendor, to finish with another firm, and to stop.
- Give counsel the technical picture before the legal strategy or any public response is fixed.
- Afterwards, review your current major contracts for the same weak terms.
Questions people ask
A vendor dispute ended in a costly settlement, what should the board change in how the company contracts for technology?
Trace the dispute to the contract terms and the decisions that led to it: undefined acceptance, verbal changes, unclear ownership, weak remedies. Then set requirements for technology contracts above a threshold: acceptance, change control, ownership, exit, and an independent review before signature. It depends on what the settlement record shows and on the company's contract approval thresholds.
A losing bidder claims our tender requirements favored the winner, how do I check whether our process was sound?
Review each contested requirement for the need it served and whether more than one product could meet it, with the evidence from the evaluation record. A sound process has that answer per requirement; a weak one has a product sheet in its history. It depends on how the requirements were drafted and on what your procurement rules allow in the response.
Our project with the vendor stopped and lawyers are involved, how do I get a practical way out?
Get an independent technical picture of what was delivered, what works and what it would take to finish, because every settlement option depends on it. Then negotiate on that picture: finish with the vendor under new terms, take the work to another firm, or stop. It depends on what the contract gives you in the deliverables and on how much of the work is usable.
How I can help with this decision
- Ask or talk (Free)
- I give my view on how to get the technical picture quickly, how to read the requirements against the claims, and which settlement structures usually work.
- Review (Pay if it was worth it)
- I write an independent assessment of the contested requirements, the record and the delivered work, for counsel to use. I recommend the position to take and what to change in the next tender or contract.
- Retain (When it makes sense)
- I stay close through the response or settlement, and review the next requirements or major contracts before approval.