How to Respond When You Disagree With a Tender Specification (2026)
Sooner or later, every experienced bidder encounters an occasion where they disagree with a tender specification. This could be an approach that is outdated, a staffing ratio that does not reflect current best practice, or a technical requirement that appears to misunderstand how the service actually works. A frequency or volume assumption that does not match the reality of the site.
This is one of the most uncomfortable situations in tendering — and one of the least discussed. The instinct is often to write the response you believe is right rather than the response the specification asks for. This is almost always the wrong instinct. This guide covers how to handle disagreement with a specification professionally — and how to decide when disagreement is a signal to walk away entirely.
Why This Happens
Specifications are written by people — procurement officers, commissioners, technical leads — working from the information available to them at the time. That information is sometimes outdated. A specification may be substantially copied from a previous procurement, carrying forward requirements that reflected conditions years ago. It may be written by a generalist procurement team without deep technical knowledge of the specific service, producing requirements that a specialist would immediately recognise as impractical or misaligned with current standards. Or it may reflect genuine current priorities that you simply disagree with on professional grounds — a staffing model you believe is unsafe, a methodology you believe is ineffective, a specification that appears to prioritise cost over the outcomes it claims to value.
Understanding why a specification might be flawed helps you respond appropriately — because the right response depends substantially on which of these situations you are in.
The Fundamental Rule: The Specification Is What You Are Evaluated Against
Before considering any of the responses below, internalise this: the evaluation panel will mark your response against the specification as written — not against what you believe the specification should say. A response that substitutes your preferred approach for the specified approach, however well-reasoned, will typically score poorly on compliance and specification-alignment criteria. Evaluators are not usually empowered to award marks for “a better idea than what we asked for.” Their job is to assess whether your response demonstrates that you will deliver what was specified.
This means that simply writing the response you believe is correct — ignoring the specification’s stated requirement — is rarely the right approach, even when you are professionally confident that you are right and the specification is wrong. There are better options.
Option 1: Raise It Through Clarification
If you believe a specification requirement is based on an error, an outdated assumption, or a misunderstanding of the service, the clarification period is the right channel to raise it — before you commit to a final response approach.
Frame the clarification factually and professionally. Do not frame it as “we think this requirement is wrong.” Frame it as a request for confirmation: “Section X specifies [requirement]. Current best practice in [relevant context] typically reflects [different approach] for the reasons of [brief, factual justification]. Please confirm whether the specification requirement as stated reflects the buyer’s intended approach, or whether bidders may propose alternative methodologies that achieve the specified outcomes by different means.”
This framing achieves several things. It demonstrates your professional expertise — you understand the subject well enough to identify a potential issue. It gives the buyer the opportunity to correct an error if one exists, without you having to assert that they made one. And it gives you a definitive answer about whether alternative approaches are acceptable — removing the guesswork from your response strategy. Our guide to the tender clarification period covers how to phrase clarification questions effectively.
The outcome of this clarification determines your next step. If the buyer confirms the requirement as stated and indicates no flexibility, proceed to Option 2. If the buyer confirms that alternative approaches are acceptable provided specified outcomes are achieved, you now have explicit permission to propose your preferred approach — and should do so with confidence, referencing the clarification.
Option 2: Comply With the Specification — and Add Your Perspective as Added Value
If the specification requirement stands and no alternative is permitted, the safest approach for the majority of your response is compliance. Describe how you will deliver the requirement as specified. This is what will be evaluated, and a response that does not address the stated requirement scores poorly on compliance grounds regardless of the merits of an alternative approach.
Within that compliant response, you can still add your professional perspective — framed as added value rather than as a substitute for compliance. “In addition to meeting the specified [requirement], we would propose [additional measure] to further enhance [outcome]” presents your professional view as an enhancement to the specified approach rather than a rejection of it. This allows you to demonstrate the depth of your expertise — including your awareness of approaches beyond the specification — without creating a compliance risk.
This approach also has a strategic benefit beyond this specific submission. If you are subsequently awarded the contract, the relationship you build during mobilisation and early delivery is the appropriate context for raising operational improvements to the specified approach — with the buyer’s engagement and consent, informed by your delivery experience. Raising it as added value in your tender response plants the seed for that conversation later, in a way that a confrontational tender response would not.
Option 3: Recognise When Disagreement Is a Bid No-Bid Signal
Sometimes disagreement with a specification is not a minor methodological difference that can be addressed through clarification or added value framing. Sometimes it reflects a fundamental misalignment between what the buyer is asking for and what you believe is professionally appropriate to deliver.
If the specification asks for a staffing ratio, a service model, or an approach that you genuinely believe would compromise safety, quality, or regulatory compliance if delivered as specified — this is not a tender to pursue, regardless of the contract value. Submitting a compliant response that commits you to delivering something you believe is unsafe or substandard creates a contractual obligation you may be unable — or unwilling — to honour if awarded. And a response that does not commit to the specified approach will score poorly on compliance grounds. Neither outcome is acceptable.
This is a genuine bid no-bid signal. Our guide to the bid no-bid decision covers the broader assessment framework — but fundamental disagreement with the specified approach on professional or safety grounds should be added to that framework as a standalone disqualifying factor, regardless of how well you score on the other criteria.
The exception is where the clarification process resolves the disagreement — either by confirming the requirement is flexible, or by the buyer correcting a genuine error once it is raised. This is precisely why raising significant concerns through clarification, early in the response window, is so valuable — it gives you the information you need to make a properly informed bid no-bid decision, rather than discovering the issue is unresolvable only after significant resource has been invested.
What Not to Do
Do not ignore the specification and write the response you believe is correct, hoping the evaluator will recognise and reward your superior approach. This is the single most common version of this mistake and it consistently produces poor compliance scores.
Do not use your response to criticise the specification or the buyer’s approach — even implicitly. Phrases like “unlike the approach specified, we recommend…” or “the specification’s requirement for X is not best practice; instead…” position your response in opposition to the buyer’s own document. Evaluators — who may have written or approved the specification — do not respond well to having their document characterised as wrong, however gently.
Do not submit a response that hedges — partially complying, partially substituting your preferred approach, without being clear about which is which. This produces a response that is difficult for the evaluator to score against either the specified requirement or an alternative, and typically scores poorly on both compliance and clarity grounds.
Frequently Asked Questions
What if the specification contains a genuine factual error, not just a methodological disagreement?
Raise it through clarification immediately — factual errors (incorrect site addresses, wrong reference numbers, internally contradictory figures) are different from methodological disagreements and buyers are generally receptive to correcting them. A clarification that identifies a genuine error and prompts a correcting addendum benefits every bidder, including you, and reflects well on your attention to detail.
Should I mention in my response that I raised a clarification about this issue?
If the clarification resulted in a published answer that changes or confirms the requirement, reference the clarification reference number or date in your response where relevant — “as confirmed in the clarification response published on [date], our methodology for [element] reflects…” This demonstrates that your approach is explicitly aligned with confirmed buyer guidance, not just your own interpretation.
What if I am awarded the contract and still believe the specified approach is wrong?
The mobilisation period and the early months of contract delivery are the appropriate time to raise operational concerns with the buyer’s contract management team — based on direct delivery experience rather than pre-contract assumptions. Most public sector contracts include mechanisms for agreed variations to the specification where both parties consent. Raise concerns constructively, with evidence from early delivery, through the contract’s formal governance structure.
Does this apply to private sector tenders too?
The same principles apply, though private sector buyers sometimes have more flexibility to engage informally before a tender is finalised. If you have an existing relationship with a private sector buyer and become aware of a specification issue before the tender is formally issued, raising it informally and early is often more effective than waiting for a formal clarification process. Once a private sector tender is live, the same compliance discipline applies — the specification is what you will be evaluated against.
Navigate Difficult Specifications With Expert Support
Together: The Hudson Collective helps organisations navigate every aspect of the tendering process — including the difficult judgement calls around specification disagreement, clarification strategy, and bid no-bid decisions. Our team holds an 87% win rate across all sectors, working with 3,500+ organisations across 52 countries.
Send us your tender documents and we will tell you exactly where we can give you the edge.
Tell us about your opportunity.
About the author: Written by Joshua Smith, a seasoned bid-writing expert with experience across the UK, Middle East and US, helping organisations secure the contracts they deserve through high-quality, competitive tender responses.