Procurement Tenders: The Complete Buyer's Guide

Tenders are one of several routes a procurement team can take to market, and the skill lies as much in choosing the route as in running it. This guide is written from the buying side: how to judge when a tender is warranted, what your thresholds and policy triggers really mean, how to build a plan and timetable the business will accept, how to assemble and steer an evaluation panel, and how to carry the award through moderation, records, debriefs and onboarding without losing the thread.

When a tender is the right route

Every request that lands with a procurement team is a routing decision before it is anything else. A tender is only one option, and it is the most expensive one to run. Before you write a single line of specification, work out whether the requirement genuinely needs a full competition or whether a lighter route will produce the same outcome with less cost to you and to the market.

Three routes cover most spend. A request for quotes suits low value, well defined, repeat purchases where the market is understood and price is the main variable. A framework call off suits requirements that fall inside an arrangement someone has already competed, whether that is a national framework, a collaborative agreement or your own approved supplier list. A full tender suits everything else: high value, complex, novel or long term requirements, and anything where the award will be examined closely. The wider discipline of procurement is largely about matching effort to risk, and tenders sit at the heavy end of that scale.

The honest test is whether a documented competition would change the result. If you already know the market has three credible suppliers and the specification is a commodity, a tender adds weeks and rarely moves the price. If the requirement will shape how a department works for years, or if the spend will appear in an audit report, the rigour earns its keep. Our general tendering guide covers the mechanics of the competition itself; this article stays with the decisions the buying team owns around it.

Thresholds and policy triggers

Most organisations codify the routing decision in a set of financial thresholds. Below a small figure a budget holder can buy directly. Above that, a number of written quotes are required. Above a higher figure, a formal tender is mandatory. Public bodies overlay statutory thresholds on top of their internal ones, and in government procurement crossing the regulated threshold brings in advertising duties, minimum timescales and challenge rights. The exact figures vary by country and change periodically, so treat the numbers in your own policy as the authority rather than anything you remember from a previous employer.

Thresholds are only half the picture. Several non financial triggers should push a requirement towards a tender regardless of value:

• Contract duration. A modest annual value becomes significant once you aggregate it over a multi year term.
• Aggregation. Repeated small purchases of the same thing across departments count as one requirement, not many.
• Incumbent dependency. If one supplier has held the work for years without test, competition is overdue.
• Novelty or risk. New categories, safety critical work and anything touching personal data deserve formal scrutiny.
• External scrutiny. Grant funded, regulated or politically visible spend attracts questions you will want records for.

The trigger most teams get wrong is aggregation. Splitting a requirement into slices that each sit below the tender threshold is one of the few procurement errors that is treated as a breach rather than a mistake, and auditors look for it specifically. If three departments each buy the same service from the same supplier, that is one contract with a combined value, and the threshold applies to the total.

Building the tender plan and timetable

Once you have committed to a tender, the plan is what keeps it honest. It should name the requirement owner, the evaluation panel, the approval route for the award, the evaluation criteria and their weightings, and the dates for every stage. Criteria and weightings belong in the plan because they must be fixed before the tender is issued; deciding what matters after you have seen the bids is the single most common cause of a successful challenge.

Timetables slip in predictable places, so build the slack in deliberately. The table below shows a workable shape for a mid sized tender, which you can stretch or compress according to complexity and any statutory minimum periods that apply to you.

Two dates deserve particular care. The clarification cut off should sit far enough before the deadline that you can answer questions and circulate the responses to every bidder without forcing an extension. And the individual scoring window has to be booked in panel members' diaries at the planning stage, not when bids arrive, because compressed evaluation is where consistency collapses.

Assembling the evaluation panel and avoiding bias

A good panel is small, mixed and briefed. Three to five people is usually enough: the technical lead or budget holder who understands the requirement in detail, an end user who will work with whatever is bought, and a procurement professional who owns the method and keeps scoring consistent across assessors. Larger panels feel inclusive but slow moderation down and dilute accountability for the marks.

Bias is best handled structurally rather than by asking people to be objective. Take declarations of interest in writing before bids are released, and act on them: a panel member who worked for a bidder, or whose department has a strong preference for the incumbent, should step aside rather than be trusted to compensate. Anonymise the commercial envelope until the quality scores are locked, so nobody adjusts a technical mark to reach a preferred total. Give each assessor the same evidence pack, the same scoring scale with written descriptors for each level, and an instruction to score only what the bid says rather than what they know about the supplier from elsewhere.

Brief the panel on the mechanics too. Assessors should score independently before seeing each other's marks and note the evidence behind each score as they go. Scales collapse towards the middle when people are uncomfortable justifying extremes, which leaves the award decided by a rounding difference. Written descriptors for each point on the scale are the practical fix.

Moderation and consensus scoring

Moderation is the meeting where independent scores become a single agreed mark. It is not an averaging exercise. Each assessor explains the evidence behind their score, the panel discusses divergences, and a consensus mark is recorded with a short written rationale referencing the part of the bid it rests on. Where the panel genuinely cannot agree, record the range and the reason rather than papering over it.

Chair the meeting so the most senior voice does not set the tone. Ask the assessor with the lowest mark to speak first on each criterion, work through criteria in order rather than bid by bid, and keep the commercial scores sealed until the quality consensus is signed off. Wide divergence on a criterion, say one assessor at three and another at eight, is usually a sign that the question or the descriptor was ambiguous rather than that someone misread the bid, and it is worth noting for the next tender.

The output of moderation is the evaluation report: consensus scores, weighted totals, the rationale for each mark and a recommendation. That document does most of the work later. It is what the approver signs, what the debrief is drawn from, and what you produce if the award is questioned. Handling scoring inside an e-tendering platform helps here because it timestamps individual submissions before moderation opens, which is exactly the evidence a challenge tests. Our e-procurement tender guide goes into how the electronic route handles sealed bids and scoring trails.

Record keeping for audit

Assume from the start that someone will read the file. The complete record for a tender includes the route decision note, the approved plan with criteria and weightings, the issued documents, every clarification and its published answer, the bids as received with their submission timestamps, individual scores, moderation notes, the evaluation report, the award approval, the notification letters and any debrief notes. Retention periods depend on your policy and any funding conditions, and commonly run to several years after the contract ends.

The practical failure is not missing documents so much as scattered ones: bids in a mailbox, scores in personal spreadsheets, the approval in a chat thread. Keeping the competition in one system solves that without anyone having to remember to file. ProcureWave holds the documents, the clarification log, the scores and the award trail against a single tender record, so the audit file assembles itself as the process runs. You can see how that fits the wider buying cycle on our solution overview, or read our procurement process guide for how tendering sits among the other stages.

Debriefing unsuccessful bidders

Debriefs are treated as a chore and they are actually an investment. Suppliers who understand why they lost bid again; suppliers who receive a two line rejection quietly stop responding, and your competition narrows one tender at a time. In regulated procurement a standstill period and a reasoned decision are mandatory, but the commercial case for a good debrief holds in the private sector too.

Keep the content tight and factual. Give the bidder their own scores against each criterion with the rationale from moderation, and explain the characteristics and relative advantages of the winning bid at a level that does not disclose the winner's confidential pricing or intellectual property. Do not compare the bidder to named competitors, do not offer views on what they should have charged, and do not improvise: work from the evaluation report so what you say matches what you recorded. If a request for proposal style competition produced a close result, saying so honestly is better than implying a gap that the scores do not show.

Turning the award into a contract

The award decision is not the contract. Between them sit the standstill period where one applies, final verification of anything the bid asserted, agreement of the contract documents, and signature by someone with the authority to bind the organisation. Resist any pressure to let work start on the strength of an award letter, because the leverage you have to close open points disappears the moment delivery begins.

Carry the tender content into the contract deliberately. The specification, the winning bid's commitments, the pricing schedule and the service levels should all be incorporated by reference or annexed, so that what was promised in the competition is what the supplier is held to. Note anything the panel scored well that depends on a named individual or a proposed method, and make it a contractual obligation rather than an assumption.

Supplier onboarding and handover

Onboarding closes the loop. Set the supplier up in your systems with the agreed pricing, purchase order routing and payment terms, complete the compliance checks that were conditional at bid stage, confirm insurance and any certifications are current, and register the contract with its value, term, renewal date and notice period so it does not roll over unnoticed in three years.

Then hand over properly. The panel understood what was bought and why; the people who manage the contract day to day often were not in the room. A short handover covering the scope, the commitments that won the bid, the agreed service levels and the review cadence prevents the slow drift where a contract is managed against a purchase order rather than against the tender it came from. Note the date to begin planning the next competition well before the term expires, so you never renew by default for want of time.

Running tenders well is mostly a question of doing ordinary things in the right order and writing them down as you go. If you would like to see how ProcureWave keeps the plan, the bids, the scoring and the audit trail in one place, get in touch and we will walk you through a tender end to end.

Frequently asked questions

When should a procurement team run a tender rather than ask for quotes?

Run a tender when the value is high enough to cross your policy threshold, when the requirement is complex or long term, or when the award is likely to be scrutinised. Quotes suit low value, well understood, repeat purchases where three comparable prices tell you everything you need. The test is whether a documented competition would change the outcome or protect the decision.

Who should sit on a tender evaluation panel?

A panel of three to five people usually works best: the budget holder or technical lead who understands the requirement, an end user who will live with the result, and a procurement professional who owns the process and keeps scoring consistent. Finance or legal may join for high value awards. Anyone with a personal or commercial connection to a bidder should declare it and step aside.

What is moderation in tender evaluation?

Moderation is the meeting where panel members compare their independent scores and agree a single consensus mark for each criterion. It is not averaging. Assessors explain the evidence behind their marks, discuss where they diverge, and record the agreed score with a short justification. That written rationale is what you rely on later in a debrief or a challenge.

How long should tender records be kept?

Keep the full file for as long as your retention policy and any funding conditions require, which is commonly six years after the contract ends in the public sector and often similar in regulated private organisations. The file should include the tender documents, clarifications, bids, individual and moderated scores, the award decision and the debrief notes. Running the competition in an e-tendering system keeps that record complete by default.

Can we award a contract without a tender if we already have a framework?

Usually yes. A compliant framework or dynamic purchasing arrangement has already tested the market, so you can call off against it through a direct award or a mini competition among the appointed suppliers. Check that your requirement genuinely falls within the framework scope and that you follow its call off rules, because a call off outside scope is treated as an uncompeted award.