What actually decides a technical proposal

Most losing bids are not beaten on price. They are beaten on the three pages the evaluation committee reads most carefully.

I have spent a fair amount of the last two years reading tender documents, writing technical and financial offers, and watching which ones go through. The pattern that surprised me is how rarely price is the deciding factor, and how often a bid loses on something the bidder had full control over.

The evaluation grid is published. Read it as a scoring sheet.

Almost every serious tender tells you how it will be scored — technical weight versus financial weight, and the sub-criteria underneath. People skim this and go straight to writing. That is backwards. If methodology carries thirty points and team CVs carry twenty-five, your proposal should visibly spend its energy there, in that order, with headings the evaluator can match to their own sheet without searching.

A committee scoring twelve proposals in a week is not reading for pleasure. Make their job mechanical. If the criterion is called "Understanding of the assignment", your section should be called "Understanding of the assignment".

Methodology is where bids are actually lost

The weakest section in most proposals is the one describing how the work will be done. It gets filled with generic phases — inception, implementation, reporting — that would fit any project in any sector. The evaluator has read that paragraph forty times.

What scores is specificity that could only have been written about this assignment: the actual constraints in the terms of reference, the sequence you would follow and why, what you would do in the first two weeks, which risks are real for this client and how you would handle them. A methodology that could be copied into another bid unchanged is a methodology that earns the minimum.

Experts are evidence, not decoration

A CV attached without a reason scores nothing. The link between the expert and the assignment has to be made explicitly — this person is proposed for this component because of this specific prior experience. If the terms of reference ask for someone with sector experience and a particular qualification, say plainly where in the CV both of those sit.

The financial offer tells a story too

A price that is far below the others is not read as good value. It is read as a bidder who has misunderstood the scope, and it invites questions you do not want. Build the number from the work — days, rates, travel, production, contingency — so that if you are asked to defend any line, you can. A defensible price beats a low one.

The administrative envelope kills more bids than anything else

Missing registration documents, an unstamped page, a tax certificate that expired last month, a bid bond with the wrong validity period, a signature in the wrong place. Technically excellent proposals get excluded before the technical committee ever sees them.

  • Build a checklist from the tender's own document list, not from memory
  • Sort out anything with an expiry date first — those have lead times you do not control
  • Have someone who did not write the bid check the envelope against the checklist
  • Submit a day early. The portal will be slow on the deadline, every time

After the result

Most agencies will give you a debrief if you ask for one professionally. Win or lose, ask. The scoring breakdown tells you more about how to write the next proposal than any amount of guessing — and it costs you one polite email.

Read next