I have sat on evaluation committees where a technically superior bidder scored zero on a section because they answered the question they wished had been asked. I have also watched an average solution win comfortably because every claim was evidenced, every clause was addressed, and the evaluators could score it without arguing. Public tenders are not won by brilliance; they are won by making brilliance easy to score.
This post distils the process we run at Avednex for every technical bid we support — the same one we teach client bid teams.
The bid/no-bid decision is your highest-leverage hour
Before anyone writes a word, score the opportunity honestly: Do we meet every mandatory criterion with evidence we already possess? Do we know the buyer's actual problem, or only the tender text? Can we staff the delivery if we win? A disciplined no-bid on a 20% opportunity funds a proper bid on a 60% one. Most firms lose money on tenders they should never have entered.
Build the compliance matrix on day one
Take every requirement — technical, functional, eligibility, documentation — and put it in a matrix with four columns: the clause, our response location, the evidence, and an owner. This matrix, not the document, is the bid. It is reviewed daily, and nothing is 'green' without evidence attached.
Mandatory criteria first: one miss disqualifies the entire effort
Map each requirement to the section and page where you answer it
Attach proof for every claim — certificates, references, staff CVs
Track corrigenda as first-class changes; re-baseline the matrix each time
Write to the evaluation matrix, not to impress
Evaluators score against published criteria under time pressure. Mirror the tender's structure and language exactly. If the criterion says 'demonstrated experience in multi-district rollouts', your heading should contain those words, followed immediately by the two projects that prove it, with dates, scale and a referee. Make the evaluator's job effortless and the marks follow.
The best bid document is the one an evaluator can score correctly at 7 p.m. on the last day of evaluation week, without reading anything twice.
Red-team before you submit
Three days before the deadline, hand the full response to someone who did not write it, along with the evaluation criteria, and ask them to score it cold. Their score sheet will find the missing annexure, the unsupported claim and the section that assumes knowledge the evaluator does not have. Fix those, and only those — late-stage rewrites introduce more errors than they remove.
None of this is glamorous. That is exactly why it works: most of your competitors will not do it.
