Understanding Bid Evaluation Criteria: How Governments Score Your Proposal

Every government tender document includes evaluation criteria — the rules that determine which bid wins. Yet most bidders treat this section as a formality, skimming it quickly before diving into writing. That’s a mistake. The evaluation criteria are the scoring rubric for your proposal. Understanding exactly how they work is the difference between writing a response that sounds good and writing one that actually scores well.

The three layers of evaluation

Government bid evaluation typically operates in three sequential stages. Failing at any stage eliminates you from consideration, regardless of how strong the rest of your submission might be.

Layer 1: Compliance check (pass/fail)

Before any scoring begins, procurement officers verify that your submission meets every mandatory requirement. This is binary — you either pass or you don’t. Common mandatory requirements include:

• Submission format: correct number of copies, right file format, within page limits, all required forms completed and signed
• Certifications and licences: ISO standards, security clearances, professional registrations, industry-specific accreditations
• Financial thresholds: minimum annual turnover, insurance coverage levels, financial guarantees or bonds
• Eligibility criteria: geographic restrictions, company size requirements (SME set-asides), sector classifications (NAICS, UNSPSC, CPV codes)

Layer 2: Technical evaluation (scored)

Submissions that pass the compliance check are assessed against the quality and technical criteria published in the tender. This is where the substantive scoring happens. Evaluators read your response against each criterion, assign a score, and multiply by the criterion’s weight.

Layer 3: Price evaluation (scored)

Your pricing is evaluated separately from your technical submission, usually by a different team. In most methodologies, the lowest-priced compliant bid receives the maximum price score, and other bids are scored relative to it.

Evaluation methodologies: how quality meets price

How governments combine technical scores and price scores determines the entire dynamic of the competition. There are three main approaches, and the one being used fundamentally changes how you should bid.

1. Lowest Price Technically Acceptable (LPTA)

Technical evaluation is pass/fail only — either your proposal meets the minimum standard or it doesn’t. Among all passing proposals, the lowest price wins. No comparative technical ranking occurs.

When it’s used: commodity purchases, well-defined services with clear specifications, repeat procurements where requirements are stable.

What it means for you: there is zero advantage in exceeding technical requirements. Meet every threshold cleanly and compete on price. Innovation, added value, and extra capability count for nothing in LPTA evaluations.

2. Best Value / Most Economically Advantageous Tender (MEAT)

Both technical merit and price are scored and weighted against each other. A higher-priced bid can win if its technical score is sufficiently better. This is the most common approach for complex procurements worldwide — it’s the default method across the EU, UK, Australia, and is increasingly used in US federal contracting.

Typical weightings range from 60:40 to 80:20 in favour of technical merit for complex services, and 40:60 to 50:50 where cost is the primary concern. The tender document will always state the ratio.

What it means for you: every point of technical score has a measurable dollar value. If technical merit is weighted 70% and price 30%, a bid that scores 10% higher on technical criteria can absorb a significantly higher price and still win.

3. Quality-Based Selection (QBS)

Only technical proposals are evaluated and ranked. Price is negotiated with the top-ranked bidder after selection. If negotiation fails, the buyer moves to the second-ranked bidder.

When it’s used: highly specialised professional services (architecture, engineering, consulting) where the quality of the team and approach matters far more than price. Common in US federal A/E procurement and World Bank-funded projects.

What it means for you: price is irrelevant during evaluation. Put everything into demonstrating the best team, methodology, and understanding of the problem.

How technical criteria are scored

Most government evaluations use a numerical scoring scale — typically 0 to 5 or 0 to 10 — applied to each criterion. Each criterion carries a weight, and your weighted scores are totalled. Here’s what a typical scoring scale looks like:

The critical point: the difference between a 3 and a 5 is evidence, not adjectives. Evaluators don’t award higher scores because you used more enthusiastic language. They award higher scores because you provided specific, relevant, verifiable evidence that you can do what you claim.

A response that says “we have extensive experience in this sector” scores a 3 at best. A response that says “we have completed 14 similar contracts totalling $47M over the past five years, with zero CPARS ratings below Very Good” scores a 5.

Common evaluation criteria and what evaluators look for

While every tender has its own criteria, five categories appear in the vast majority of government procurements. Here’s what evaluators are actually assessing in each one:

1. Technical approach and methodology

This is usually the most heavily weighted criterion. Evaluators want to see that you understand the problem, have a realistic plan to solve it, and have thought through the risks and contingencies.

What scores well: a step-by-step methodology tailored to this specific project, not a generic process description. Show awareness of the buyer’s particular context — their constraints, their stakeholders, their operating environment. Include a realistic timeline with milestones, identify potential risks and your mitigation strategies, and explain why your approach works better than the alternatives.

What scores poorly: generic methodology descriptions copied from your website. Vague references to “industry best practice” without explaining what that means in this context. Overpromising on timelines or outcomes.

2. Past performance and experience

Governments use your track record as the best predictor of future performance. They’re looking for evidence that you’ve done similar work, at similar scale, for similar clients — and done it well.

What scores well: case studies that are directly relevant to the tender requirements, with measurable outcomes. Include contract values, timelines, client names (where permitted), and results. If your work is reviewed through a formal system like CPARS (US) or contract performance reports, reference your ratings.

What scores poorly: a long list of unrelated projects. Testimonials without context. Past performance examples that are too old (most evaluators give reduced weight to work completed more than five years ago).

3. Key personnel and team

For services contracts especially, the quality of the people you’re offering matters enormously. Evaluators assess qualifications, certifications, direct experience, and availability.

What scores well: named individuals with CVs that directly address the experience requirements in the tender. Show their specific role in the project, their relevant qualifications, and examples of similar work they’ve personally delivered.

What scores poorly: generic role descriptions without named staff. CVs that list every qualification the person has ever earned rather than focusing on what’s relevant. Proposing people who won’t actually do the work — evaluators call this “bait and switch” and many contracts now include clauses penalising it.

4. Management and quality systems

Evaluators want confidence that you can manage the contract effectively: reporting, governance, quality assurance, risk management, and escalation procedures.

What scores well: a clear governance structure showing who is responsible for what, how you’ll report progress, and how you’ll handle problems. Reference your quality management certifications (ISO 9001, sector-specific standards) with evidence of how they apply to this contract, not just that you hold them.

5. Social value and sustainability

Increasingly, governments score social value as a standalone criterion — not just a nice-to-have. In the UK, the Procurement Act 2023 embeds social value into evaluation. Australia’s Commonwealth Procurement Rules include Indigenous Procurement Policy scoring. The EU’s directives encourage environmental and social criteria.

What scores well: specific, measurable social value commitments tied to the contract. How many local jobs will you create? What percentage of your supply chain is SME? What’s your carbon reduction plan for this project?

What scores poorly: corporate social responsibility statements lifted from your annual report. Generic commitments that aren’t tied to the specific contract or measurable outcomes.

How price scoring works

Price evaluation in government procurement is rarely as simple as “cheapest wins.” Even in LPTA evaluations, the price must be deemed reasonable. In best-value evaluations, price scoring usually follows one of two formulas:

Proportional price scoring

The lowest-priced compliant bid receives the maximum score (say 100 points). All other bids are scored proportionally:

Your price score = (Lowest price ÷ Your price) × Maximum points

So if the lowest bid is $800,000 and yours is $1,000,000, your price score is ($800,000 ÷ $1,000,000) × 100 = 80 points. You’ve given up 20 price points — your technical score needs to compensate by more than 20 points (adjusted for weighting) to win.

Price reasonableness and cost realism

Governments don’t just compare your price to competitors — they assess whether it’s realistic. A bid that’s significantly lower than others raises red flags: can you actually deliver at this price? Under US federal rules (FAR 15.404-1), agencies perform cost realism analysis to determine whether proposed costs are realistic for the work proposed.

Abnormally low bids can be rejected. In the EU, bids more than 20–30% below the average must be explained. If the explanation is unconvincing, the bid is excluded. Pricing too low is as risky as pricing too high.

Your technical approach and your price proposal must tell the same story. If your technical response describes a senior team of specialists, but your price reflects junior staff rates, evaluators will flag the disconnect. This inconsistency is one of the most common reasons for low scores.

The evaluation panel: who scores your bid

Understanding who reads your proposal helps you write it. Typical evaluation panels include:

• Subject-matter experts who assess the technical approach and methodology. These are the people who understand the work and can spot generic filler.
• Procurement professionals who manage the process, check compliance, and ensure consistency in scoring across evaluators.
• Financial analysts who evaluate pricing separately, checking for cost realism and value for money.
• End users or operational staff who will actually work with the winning contractor day to day.

Panel members typically evaluate independently first, then discuss scores in a moderation session where outlier scores are examined and consensus is reached. Your proposal needs to work for all of these readers — technically precise enough for specialists, clear enough for generalists, and structured so that every evaluator can find the information relevant to their criteria quickly.

Seven practical tips for scoring higher

1. Build a compliance matrix first

Before writing a single paragraph, create a spreadsheet mapping every evaluation criterion and sub-criterion to a specific section of your response. This ensures nothing is missed and your content is proportional to the criterion’s weight.

2. Mirror the evaluation structure in your response

Use the exact criterion headings from the tender as your section headings. If the tender says “Criterion 3.2: Proposed Methodology,” your response section should be headed “3.2 Proposed Methodology.” This makes it effortless for evaluators to find and score your content.

3. Allocate content proportional to weight

If technical methodology is worth 40% of the total score, roughly 40% of your response should address it. A criterion worth 5% should not get five pages while a criterion worth 30% gets two.

4. Lead with your answer, then provide evidence

Evaluators may be reading thirty responses. Don’t make them hunt for your key messages. Start each section with a clear statement of your approach, then follow with the evidence, examples, and detail that support it.

5. Use the buyer’s language

If the tender refers to “service delivery milestones,” use that exact phrase in your response — not “project checkpoints” or “key deliverables.” Evaluators are often scoring against a checklist. Using their terminology makes it obvious you’ve addressed their criteria.

6. Quantify everything you can

Replace vague claims with numbers. “We respond quickly to issues” becomes “our average incident response time is 2.3 hours, against a contractual SLA of 4 hours.” Numbers are harder to score low because they’re verifiable.

7. Get someone else to score your draft

Before submitting, have someone who wasn’t involved in writing score your proposal using the tender’s evaluation criteria. Where they can’t find evidence to justify a high score, you have a gap to fill. This red team review catches problems before evaluators do.

Common scoring mistakes to avoid

• Ignoring sub-criteria. If a criterion has three sub-criteria, each one needs a substantive response. Addressing two out of three leaves points on the table.
• Boilerplate responses. Evaluators can tell when content has been copied from another bid. Generic descriptions of your company’s capabilities without tailoring to this specific tender score poorly every time.
• Technical-price disconnect. Describing a team of senior specialists in your technical response while pricing junior staff rates creates a cost-realism problem that can disqualify your bid entirely.
• Exceeding page limits. If the tender sets page limits, evaluators are instructed to stop reading at the limit. Everything after it is ignored — no exceptions.
• Late submission. There is no grace period. Systems close at the deadline. A submission received one minute late is excluded, regardless of quality.

Reading the evaluation criteria before you write

The most important thing you can do before starting any tender response is read the evaluation criteria three times. First, read them quickly to understand the overall approach. Second, read them carefully to identify every criterion, sub-criterion, and weighting. Third, read them with a highlighter to mark the specific words evaluators will be looking for in your response.

The evaluation criteria aren’t just a section of the tender document — they’re the blueprint for your entire proposal. Every decision you make about what to include, how much space to allocate, and what evidence to present should flow directly from how evaluators will score it. Write to the rubric, not to your own sense of what matters.