Abnormally Low Tenders: How to Explain a Low Price Without Losing Trust

A low tender price can win attention for the wrong reason.

Every bid team wants to be competitive. Nobody wants to leave unnecessary margin on the table, especially when the buyer has made price a heavy part of the evaluation. But there is a line between sharp pricing and pricing that makes an evaluator nervous. Once a buyer starts to wonder whether your tender is abnormally low, the question is no longer whether you are cheap. The question is whether you can actually deliver.

That is a very different argument.

An abnormally low tender is not automatically a bad tender. A supplier may have a genuine advantage: better technology, local infrastructure, reusable assets, lower overheads, a stronger supply chain, a more efficient operating model or a deep understanding of the scope. In those cases, a lower price can be a sign of maturity rather than desperation.

The problem is that evaluators cannot simply take that on trust. Under the Procurement Act 2023 environment, public buyers are paying closer attention to delivery credibility, financial resilience, performance transparency and the risk of contracts failing after award. A bid that looks too cheap may trigger scrutiny because the buyer is worried about omissions, under-resourcing, poor quality, non-compliance, future variation claims or service failure.

Bid team reviewing a tender pricing clarification with cost build-up, method statement and evidence files

This guide explains how to prepare for that scrutiny. It is written for bid managers, commercial leads, finance teams and subject matter experts who need to defend a competitive price without sounding defensive. It covers why buyers challenge low tenders, what evidence they expect, how to align your written method with your pricing schedule, where AI can help, and how platforms such as mytender.io help bid teams check consistency before submission.

This is practical bid writing guidance, not legal advice. If you are dealing with a live rejection, procurement dispute or formal challenge, speak to a procurement lawyer. But if you are still shaping the bid, the best defence is simple: make the price explainable before anyone asks.

Why abnormally low tender scrutiny is increasing

Public sector procurement has moved away from the lazy assumption that the lowest price is always the best value. The language of Most Advantageous Tender is important because it reinforces a broader point: buyers are evaluating value, risk, quality, outcomes and deliverability, not just the number at the bottom of the pricing schedule.

That does not mean price has stopped mattering. It absolutely has not. Many tenders still allocate 30%, 40% or even more to price. In framework mini-competitions, facilities management contracts, construction packages, waste services, cleaning, security and technology implementation, commercial scoring can be brutally competitive. A supplier that overprices may lose before quality has a chance to rescue the bid.

But buyers have also learned the cost of accepting prices that do not survive contact with reality. A contract that starts cheaply and then collapses into disputes, vacancies, poor performance, safety issues or constant change requests is not good value. It creates work for the authority, damages service users and undermines confidence in procurement.

That is why low pricing is now judged through a risk lens. Evaluators may ask themselves:

• Has the supplier missed part of the specification?
• Are staffing levels realistic for the promised service model?
• Are wage rates compliant with current and forecast obligations?
• Has TUPE been properly costed?
• Are mobilisation, training, travel, equipment, systems and management time included?
• Is the supplier relying on optimistic productivity assumptions?
• Are social value and carbon commitments actually funded?
• Will the supplier recover losses through variations after award?
• Does the quality response promise more resource than the price pays for?

A strong bid anticipates those questions. A weak bid waits for a clarification request and then scrambles.

What the Procurement Act changes for suppliers

For procurements governed by the Procurement Act 2023, the Act allows a contracting authority to disregard a tender if it considers the price abnormally low for performance of the contract. Before doing that, the authority must notify the supplier and give a reasonable opportunity to demonstrate that it can perform the contract for the offered price. If the supplier satisfies the authority, the tender cannot be disregarded on that basis. If the supplier does not, the authority may disregard it.

For suppliers, the practical lesson is clear: the answer must prove deliverability. A vague reassurance that the price is correct is not enough. The buyer needs enough evidence to feel safe that the price is not the result of an error, omission, unlawful practice or unrealistic delivery assumption.

The Act also sits in a wider climate of transparency and performance accountability. Contracting authorities are more alert to supplier performance, key performance indicators, payment behaviour, social value delivery and whole-life value. This matters because a low price explanation is not only a commercial clarification. It is a credibility test.

The practical implication is that bid teams need to treat pricing evidence as part of the response, not as a finance appendix that only appears when something goes wrong. If your commercial advantage is genuine, it should be capable of being explained in plain English, backed by documents, and cross-checked against the solution narrative before the final upload. That discipline protects the supplier as much as the buyer. It reduces late panic, stops accidental over-promising, and helps the final submission feel commercially mature rather than merely inexpensive.

Your response should therefore do four things.

First, it should show that the price covers the full scope. Every major requirement should be visible somewhere in the cost build-up, even if it is included within an overhead, management fee or blended rate.

Second, it should show that the delivery model and the price say the same thing. If the method statement promises named roles, site visits, audits, reporting, training, governance meetings, technology configuration or mobilisation activity, the commercial model must fund those commitments.

Third, it should show that legal, social, environmental and labour obligations have been respected. A low price that appears to depend on non-compliance is not a competitive advantage. It is a red flag.

Fourth, it should show why your organisation can price differently from others. The buyer needs a positive explanation, not just a denial. That explanation might be automation, proven productivity, owned assets, local depots, framework rates, existing teams, better data, lower overheads or a repeatable delivery model.

Procurement Act tender pricing review showing the path from low price concern to evidence-led supplier explanation

The difference between low, lean and reckless

Not every low price is a problem. Good suppliers often win because they understand the work better than competitors.

A low price can be healthy when it comes from efficiency. For example, a cleaning provider may use route density, existing local supervision and proven productivity data to reduce management overhead. A construction supplier may already own specialist plant that a competitor needs to hire. A software provider may have a reusable implementation framework that reduces configuration time. A facilities management contractor may already operate in the same geography and can share helpdesk, supply chain and mobile engineer capacity.

That is lean pricing. It is specific, evidenced and operationally grounded.

Reckless pricing looks different. It usually depends on silence. The bid does not explain assumptions. The cost model leaves gaps. The quality response promises more than the price can sustain. The supplier relies on future variations, unrealistic productivity, unpaid management time or an assumption that the buyer will relax the specification after award.

Evaluators are trained to spot the difference. They may not know your internal cost base, but they can compare the price against their own estimate, other bids, market benchmarks and the resource model implied by your narrative. If the gap is big enough, they will ask questions.

The safest approach is to write the bid as if a commercial evaluator and a technical evaluator will sit together and compare every promise against the pricing workbook. Because increasingly, that is exactly what happens.

Build the explanation before submission

The worst time to build an abnormally low tender explanation is after the buyer has raised the concern. By then the clock is running, the tone is defensive and the team is trying to reconstruct assumptions from spreadsheets, emails and old pricing calls.

A better approach is to prepare a low-price evidence file during bid development. You may never need to send it, but the exercise improves the bid.

Start by asking the commercial lead to identify the lines where your offer is materially sharper than market expectation. That might be labour hours, management fee, mobilisation cost, overhead recovery, material rates, subcontractor rates, travel, technology costs or margin.

Then ask why. The answer should be evidence-based. If the price is lower because you have an existing depot, include the depot location, coverage map and current capacity. If it is lower because you have agreed supplier rates, keep the supplier quotes. If it is lower because of automation, show the workflow, productivity assumption and previous results. If it is lower because of a lower margin, confirm that all direct and indirect costs are still covered.

Finally, check whether the explanation appears in the written response. If the bid depends on a technology advantage but the method statement barely mentions it, the evaluator will not connect the dots. If the bid depends on local operational density but the mobilisation plan reads like a generic national model, the price will feel risky.

Strong commercial explanations are rarely isolated. They should be woven into the delivery story.

What evidence buyers expect

A buyer questioning a low tender price is not looking for a marketing paragraph. They are looking for proof.

The most useful evidence usually falls into seven groups.

The first is a cost build-up. This should show the main cost categories: labour, management, supervision, subcontractors, materials, plant, systems, mobilisation, training, travel, overhead, contingency and margin. The level of detail should match the buyer's request. Do not drown them in unnecessary internal data, but do not hide the logic either.

The second is labour evidence. Where the contract is people-heavy, show role numbers, hours, rates, productivity assumptions and cover arrangements. Confirm that pay assumptions comply with applicable wage obligations, working time rules, TUPE where relevant and any buyer-specific employment requirements.

The third is supplier and subcontractor evidence. Quotes, framework rates, letters of support and capacity confirmations can turn a low materials or specialist delivery cost from suspicious to credible.

The fourth is asset and infrastructure evidence. Owned vehicles, plant, equipment, software licences, local premises, existing helpdesk infrastructure and operational teams can all explain lower set-up costs.

The fifth is productivity evidence. If your model uses fewer hours than a buyer expects, show why. Evidence might include time-and-motion data, historic contract performance, automation, route optimisation, standard operating procedures, self-service portals, remote monitoring or reduced rework.

The sixth is comparable contract evidence. A short anonymised example can be powerful: similar scope, similar price logic, delivered to standard, with KPI performance and no hidden recovery through variations.

The seventh is governance evidence. Show how the price will be controlled after award: budget ownership, monthly reviews, risk reporting, cost-to-complete tracking, open-book reporting if required, and escalation if assumptions change.

Evidence pack for an abnormally low tender response with cost build-up, supplier quotes, payroll checks and case study proof

The goal is not to reveal every commercial secret. The goal is to give the buyer enough confidence that the number is deliberate, complete and deliverable.

Align the method statement with the price

Most low-price problems are really consistency problems.

A bid can be commercially sound and still look risky if the narrative and the pricing model do not match. This happens when different people write different parts of the bid under deadline pressure. The operations lead describes an ideal service model. The commercial lead prices a leaner model. The bid writer improves the answer with extra governance, reporting, training and quality assurance. Nobody checks whether those additions are funded.

The result is a bid that scores well until someone asks a simple question: where is this paid for?

Before submission, run a price-quality alignment review. Take the written method statement and highlight every resource commitment. Look for words such as weekly, monthly, dedicated, named, on-site, audit, review, training, workshop, dashboard, meeting, inspection, visit, report, manager, engineer, supervisor, analyst and support.

Then check the pricing workbook. Is the resource included? Is the frequency realistic? Is the role covered? Is travel included? Is preparation time included? Is management time included? Is the software or reporting tool included? Are subcontractor costs included? If something is absorbed in overhead, is that explanation clear enough?

This review often catches issues that a normal proofread misses. It also improves writing. Instead of making broad promises, the bid can explain the operating model precisely.

For example, do not write that the contract manager will attend regular meetings unless the price covers the contract manager's time. Write that the contract manager will attend monthly operational reviews and quarterly strategic reviews, with weekly mobilisation meetings during the first eight weeks, because that is what the cost model includes.

Specificity protects trust.

Explain efficiency without sounding cheap

There is a tone problem in many low-price explanations. Suppliers either sound apologetic or aggressive.

The apologetic version says the price is correct and asks the buyer to trust them. That is too thin.

The aggressive version says the buyer is wrong to question the price. That is worse. It makes a legitimate evaluation concern feel like a fight.

The right tone is calm, factual and evidence-led. A good explanation says: we understand why this price may appear low against a conventional delivery model; the price is sustainable because our model differs in the following evidence-backed ways.

That framing does two things. It respects the buyer's concern, and it turns the discussion towards your advantage.

Useful explanations include existing operational density, mature technology, standardised processes, lower mobilisation cost, reusable templates, local supply chains, owned assets, cross-trained staff, reduced rework, better data, existing buyer knowledge, or continuous improvement savings that are already proven rather than speculative.

Avoid weak phrases such as highly competitive rates, efficient working practices and economies of scale unless you explain what they mean. Every supplier says they are efficient. The evaluator needs to know how.

A stronger version would say that your existing regional team already covers 82% of the contract geography, allowing supervision and escalation to be absorbed into current management routes without reducing response coverage. Or that your document automation workflow reduces manual compliance checking time because source evidence is already structured, reviewed and tagged in a controlled content library.

The more concrete the explanation, the safer the price feels.

Do not hide margin, risk and contingency

Some suppliers try to make a low price more attractive by squeezing or hiding contingency. That can backfire.

Buyers know contracts carry risk. They expect a credible supplier to price risk intelligently. If the price includes no visible allowance for mobilisation uncertainty, inflation, TUPE change, supplier lead times, travel, sickness, defects, rework or change control, the buyer may assume the risk has either been missed or pushed onto the contract later.

This does not mean padding the bid. It means being transparent enough to show that the model is controlled.

If risk is included in line-item rates, say so. If contingency is held centrally, explain the trigger and governance. If you have reduced contingency because you have unusually strong data, explain the data. If you have accepted a lower margin for strategic reasons, be very careful: the buyer still needs to see that cost, compliance, quality and resilience are protected.

A low margin is not a delivery method. It is a commercial choice. It only reassures the buyer if the rest of the model is sound.

Common mistakes in low tender explanations

The most common mistake is answering too narrowly. The buyer asks about price, and the supplier only replies with numbers. Numbers matter, but the buyer is really asking about performance risk. A strong response links numbers to delivery.

The second mistake is providing a spreadsheet without a narrative. Evaluators need to understand the logic. A short explanatory note should walk them through the main assumptions, the evidence and the reason the price is sustainable.

The third mistake is ignoring the quality response. If the written tender promised a high-touch service, the explanation must show how that service is paid for. If it cannot, the team needs to acknowledge and clarify the model rather than pretending there is no gap.

The fourth mistake is relying on generic efficiency claims. Words such as streamlined, optimised and innovative do not prove anything by themselves. Tie them to data.

The fifth mistake is overlooking statutory and policy compliance. A buyer will not be reassured by a low price that creates doubt about wages, safety, environmental standards, modern slavery controls, prompt payment, data protection or social value delivery.

The sixth mistake is submitting too much irrelevant information. An evidence-led response is not a document dump. It should be structured around the buyer's concern.

The seventh mistake is letting the tone become defensive. The buyer is allowed to ask. Your job is to make the answer easy to accept.

A practical response structure

When a buyer asks you to explain a potentially abnormally low tender, structure the response so the evaluator can follow the argument quickly.

Open by acknowledging the request and confirming that the tender price is complete, deliberate and capable of supporting full contract performance. Keep the tone factual.

Then summarise the reason the price is competitive. Use three to five points, not twenty. For example: existing regional infrastructure, owned equipment, agreed supplier rates, proven productivity model and lower mobilisation cost due to reusable systems.

Next, provide the cost build-up. Use the buyer's categories if they have specified them. If not, group costs logically: labour, management, mobilisation, materials, subcontractors, systems, overhead, contingency and margin.

Then reconcile the cost model to the delivery method. This is where many suppliers win or lose the argument. Show that the resource model, governance, service levels, training, reporting and mobilisation activity promised in the tender are covered by the price.

After that, address compliance. Confirm that the pricing supports applicable wage, labour, environmental, health and safety, social value, data protection and contract-specific obligations. Attach evidence where helpful.

Then include supporting proof. This might be supplier quotes, payroll assumptions, case study data, asset lists, productivity analysis, current operating maps, licences, mobilisation plans or management accounts. Only include what strengthens the answer.

Finally, close with governance. Explain how the contract will be monitored after award so the buyer knows the price will not turn into a performance problem.

Structured abnormally low tender explanation mapped from price concern to commercial evidence, compliance and contract governance

That structure gives the buyer what they need: confidence, evidence and a route to justify keeping your bid in the competition.

Sector examples

In facilities management, a low price often raises concerns about staffing, subcontractor coverage, helpdesk resilience, planned preventive maintenance, statutory compliance and mobilisation. A strong explanation will show engineer ratios, call-out assumptions, asset data confidence, regional coverage, supplier capacity and management overhead. If the price depends on an existing local team, include the operating footprint.

In construction, the concern may be plant, preliminaries, site management, materials, labour rates, programme realism, inflation, defects, design coordination and health and safety. A strong explanation will show supplier quotes, programme logic, owned plant, risk allowances, design responsibility and how preliminaries match the programme.

In waste management, buyers may worry about route density, vehicle availability, depot access, fuel assumptions, crew hours, contamination, recycling targets and mobilisation. A strong explanation will link the price to route modelling, fleet evidence, transfer station arrangements, staffing plans and performance data.

In technology and professional services, the concern is often under-scoped effort. A strong explanation will show implementation phases, role days, reuse of proven accelerators, automation, support assumptions, licence costs, integration boundaries and change control.

In healthcare or regulated services, a low price must be especially careful. The explanation should show that quality, safeguarding, compliance, training, audit and continuity are not being compromised.

The pattern is the same across sectors: explain the operating advantage, prove the assumptions, and connect the price to the method.

How AI helps with abnormally low tender risk

AI will not decide whether your price is commercially right. That remains a human, financial and operational judgement. But AI can help bid teams spot the inconsistencies that make a low price look unsafe.

A good AI tender platform can compare the specification, pricing assumptions, method statements and evidence library. It can flag when a quality response promises a role, meeting, report, audit or activity that is not reflected in the commercial assumptions. It can help build a checklist of buyer concerns. It can extract requirements that carry cost implications. It can find previous evidence showing similar delivery at similar scale. It can also help draft a clearer explanation once the commercial team has approved the substance.

This is where generic AI tools are limited. A general chatbot may produce fluent text, but it will not know whether your bid library contains the supplier quote, whether the mobilisation plan aligns with the pricing workbook, or whether a previous contract actually proves the productivity claim. Bid teams need grounded AI: tools connected to the documents, decisions and evidence that make the explanation true.

AI-assisted bid pricing review comparing tender requirements, method statements, cost assumptions and evidence sources

Pre-submission checklist

Before submitting a sharply priced tender, run this checklist.

Does the price cover the full specification, including mobilisation, management, reporting, training, travel, systems, transition, quality assurance and contract close-down?

Do the labour rates and hours match the promised delivery model?

Are all wage, working time, TUPE, safety, environmental, modern slavery, data protection and buyer-specific obligations covered?

Do social value and carbon commitments have budget, ownership and measurement behind them?

Does the mobilisation plan match the mobilisation cost?

Do subcontractor and supplier costs have quotes or agreed rates behind them?

Are overhead, margin and contingency visible enough to be credible?

Can you explain why your price is lower than a conventional model?

Is that explanation supported by evidence rather than assertion?

Does the quality response make promises that the pricing workbook does not fund?

Can the contract manager deliver the governance model described in the bid?

If a buyer asked for an explanation tomorrow, could you respond within the deadline without rebuilding the whole commercial story?

If the answer to that final question is no, the bid is not ready.

The strategic lesson

An abnormally low tender challenge is stressful because it turns a potential advantage into a potential threat. But it is also revealing. It shows whether the bid team truly understands the relationship between price, method, evidence and risk.

The strongest suppliers do not treat low-price scrutiny as an afterthought. They build explainability into the bid from the start. They know which assumptions make the price competitive. They keep evidence close. They align the method statement with the cost model. They check compliance. They avoid grand promises that the commercial model cannot support. And when challenged, they respond calmly with proof.

That is the difference between being cheap and being trusted.

In modern public procurement, buyers are not just buying a number. They are buying confidence that the supplier can deliver the promised outcome at that number. If your price is genuinely strong, make it easy for them to believe it.

A low price may get you noticed. A well-evidenced low price can still get you awarded.