How to use tender feedback after a win or loss

Preserve the record before discussing the result

Keep the exact submitted response, attachments, pricing schedule, clarifications, scoring method, feedback and award information together. Add the original bid/no-bid decision and an honest estimate of the time your team spent.

Use the submitted version when discussing comments. A strong paragraph in an earlier draft is irrelevant if it did not make it into the final file. If the buyer assessed a presentation or demonstration, include the approved material and the notes your team made at the time.

Check which feedback process applies

Under the Procurement Act, suppliers that submitted an assessed tender in a competitive tendering procedure receive an assessment summary before the contract award notice. An unsuccessful supplier’s summary also includes the required assessment information about the successful tender, subject to permitted redactions.

These requirements do not apply in the same way to framework call-offs or suppliers eliminated before the relevant assessment stage. Older procurements remain subject to their earlier rules. Read what the buyer has actually sent and the procedure that applies, and ask for feedback through the route the buyer has set out.

Separate what the buyer said from the cause

Suppose the feedback says the answer did not explain how service failures would be escalated. First find the question, scoring descriptor and passage the buyer assessed. Then ask whether the escalation process was missing, poorly evidenced or present but hard to find.

Each cause needs a different fix. Operations may need to define a process that works; the team may need a relevant example; or the writer may need to spell out the process that already exists. Do not treat all three as a writing problem.

Ask focused questions where the explanation is unclear

Refer to the criterion, score and relevant passage. Ask which part of the requirement you did not demonstrate, or how the score follows from the scoring descriptor. Keep the request factual and do not ask the buyer to redesign your offer.

If you think the process or assessment involved a material error, get qualified procurement advice promptly. The procedure and notice dates matter, and you should not assume an informal feedback request pauses any challenge period.

Give each lesson an owner and a task

Replace “provide more detail” with a task that someone can complete. For example: the operations manager will approve an escalation flow, identify the responsible roles and supply a recent incident example before the next service-management bid.

Keep a short action list with the evidence, owner, due date and a way to check the work is done. Deal first with weaknesses that keep recurring or matter most, rather than trying to redesign the whole process after one result.

• •Qualification: would the same information change the original bid decision?
• •Offer: was the proposed service credible and competitive?
• •Evidence and response: was the required proof present and understandable?
• •Process: did timing or coordination prevent a stronger submission?

Use the next bid to test the improvement

Before answering a similar question, go back to the action and look at the new evidence. Ask the reviewer to check for the specific weakness that appeared last time. Over several comparable bids, look for repeat comments and whether the relevant scores improve.

Be careful when comparing results: different buyers, questions and weightings can produce different scores. After a win, also hand the commitments to delivery colleagues and look for effort or risk you could have avoided. Winning does not mean every part of the process worked.