Common Tender Mistakes That Cost Marks

Why capable suppliers still submit weak tenders

A tender is a controlled assessment, not a general sales conversation. Buyers can normally score only the information submitted by the deadline and in accordance with the published rules. Existing reputation, previous conversations and assumptions about what the buyer already knows rarely repair an incomplete answer.

SMEs often possess strong operational knowledge but fail to transfer it into the response. The bid may describe values rather than methods, present policies instead of evidence, or omit the people, systems, timescales and controls that make delivery credible. The result is a technically capable supplier receiving an average or weak score.

Mistake 1: answering the topic instead of the question

A question about mobilisation may invite a supplier to discuss experience, staffing, communications and risk. That does not mean a broad company overview will score well. The evaluator will usually be looking for a contract-specific sequence: what happens after award, who owns each action, when milestones occur, how dependencies are controlled and how readiness is confirmed.

Before drafting, break the question into individual requirements. Highlight command words such as describe, explain, demonstrate and provide. Identify every sub-part, evidence request, output and constraint. Build the response headings around those elements.

Mistake 2: repeating the specification

Restating the buyer’s requirements demonstrates awareness but not delivery capability. If the specification says emergency calls must be attended within two hours, writing “we will attend emergency calls within two hours” adds little value. The response must explain how the commitment will be achieved.

A strong answer should identify the operational mechanism: call handling, triage, duty rota, geographic coverage, vehicle availability, escalation, backup resource, evidence capture and performance monitoring. It should also explain what happens when demand exceeds normal assumptions.

Mistake 3: unsupported claims

Words such as “excellent”, “robust”, “industry-leading” and “fully compliant” are conclusions, not evidence. Evaluators need to understand why the statement should be believed. Unsupported superlatives often consume word count without improving the score.

Convert claims into verifiable proof. Replace “excellent customer service” with measurable evidence such as response times, complaint resolution performance, satisfaction results, audit findings or a relevant case study. Explain the source and period of the data, and connect it to the proposed contract.

Mistake 4: generic recycled content

A bid library is useful, but copy-and-paste content becomes dangerous when it is not adapted. Generic answers may contain the wrong client name, irrelevant terminology, commitments designed for another contract or processes that conflict with the current specification.

Use previous content as source material rather than finished copy. Rebuild each answer around the current buyer’s outcomes, service model, geography, users, risks, reporting requirements and evaluation criteria. Remove any evidence that is not directly relevant.

Mistake 5: no clear delivery method

Policies show organisational intent. They do not automatically explain what will happen on this contract. A method should describe a repeatable sequence from input to outcome, including responsibility, systems, checks and escalation.

For each major activity, answer six questions: what happens, who does it, when does it happen, what information or system is used, how is quality checked, and what happens if performance falls outside tolerance?

Mistake 6: unclear roles and responsibility

Listing job titles is not the same as explaining accountability. Evaluators need to know who owns mobilisation, operational delivery, quality, health and safety, social value, commercial control and client reporting. They should also understand cover arrangements and escalation routes.

Use named roles where permitted, explain decision rights and show how interfaces are managed. A simple responsibility table can provide more assurance than several paragraphs of organisation description.

Mistake 7: vague timescales

Expressions such as “regularly”, “promptly” and “as required” are difficult to assess and even harder to manage after award. Where the question expects a delivery plan, provide clear frequencies, milestones or response times.

Timescales must be realistic and consistent with the programme, resource model and price. Do not promise immediate action if the proposed staffing or systems cannot support it. Overly ambitious commitments may score well initially but create contractual exposure later.

Mistake 8: evidence that is impressive but irrelevant

A large project is not automatically the best case study. Relevant evidence should match the buyer’s requirement in service type, scale, risk, customer group, geography or delivery environment. The strongest example is the one that proves the specific method being proposed.

Explain the challenge, your actions, measurable result and lesson applied to the new contract. Avoid long company histories that do not support the criterion.

Mistake 9: weak risk management

Many bids state that risks will be recorded in a risk register but provide no explanation of identification, ownership, scoring, mitigation, review or escalation. This makes the control sound administrative rather than operational.

Identify the most credible contract risks and explain preventative controls, contingency actions and triggers. Include risks created by mobilisation, labour availability, materials, access, vulnerable service users, data, subcontractors and demand peaks where relevant.

Mistake 10: KPIs without management controls

Quoting the buyer’s KPIs does not explain how performance will be achieved. A complete response should describe the data source, reporting frequency, validation, ownership, threshold and corrective-action process.

Explain how underperformance is identified early. For example, weekly trend analysis may trigger an improvement action before the monthly KPI becomes a failure. This gives the evaluator confidence that performance is actively controlled rather than simply reported after the event.

Mistake 11: treating attachments as a substitute for the answer

Some procurements allow supporting attachments; others limit or prohibit them. Even where they are permitted, the core response should remain understandable. Do not expect the evaluator to search a 40-page policy for the evidence that should have been summarised in the answer.

Reference attachments precisely and only where the instructions allow it. State what the attachment proves, identify the relevant section and ensure the document is current, legible and consistent with the response.

Mistake 12: ignoring word and character limits

Exceeding a limit can lead to text being disregarded or the response being treated as non-compliant, depending on the rules. Writing far below the limit can also indicate insufficient detail where the criterion is complex.

Allocate the available space according to the question’s sub-parts and weighting. Remove repetition, marketing language and background that does not contribute to the score. Use concise headings, tables and bullets only where permitted and useful.

Mistake 13: inconsistencies between quality, price and programme

Different parts of the tender must describe one credible delivery model. A quality response may promise a dedicated manager, weekend cover and extensive reporting while the pricing schedule contains no apparent allowance for those resources. A programme may show a shorter period than the specification requires, or staffing numbers may differ between answers.

Complete a cross-document consistency review covering names, dates, quantities, resource levels, subcontractors, assumptions, exclusions, programme and price. Resolve conflicts before submission.

Mistake 14: poor pricing discipline

A low price cannot rescue a non-compliant tender, and an unsustainable price can create delivery risk. Common errors include missing items, incorrect formulas, inconsistent rates, unapproved qualifications, VAT mistakes and failure to price commitments made in quality responses.

Use a controlled pricing review with technical, commercial and senior approval. Check every schedule line, assumption and total. Confirm that the resource model, risk allowance, overheads and social value commitments are reflected appropriately.

Mistake 15: careless clarifications

Clarification questions are part of bid risk management. Suppliers lose value when they ask questions that are already answered, identify themselves unnecessarily, wait until the deadline, or seek permission to depart from a mandatory requirement without understanding the consequences.

Maintain a clarification log. Record the issue, document reference, commercial or compliance impact, owner, submission date and buyer response. Share answers with all writers and update affected content.

Mistake 16: leaving compliance until the end

Compliance is not a final proofreading task. It should begin when the tender is downloaded. Build a compliance matrix containing every returnable document, declaration, certificate, schedule, question, limit, format and deadline.

Assign an owner and status to each requirement. Review the matrix throughout the bid and conduct a separate final gateway check before upload.

Mistake 17: one review instead of staged reviews

A single final read rarely identifies strategic gaps, technical weaknesses and compliance errors effectively. Use staged reviews with different purposes.

The evaluator-style reviewer should score only what is written, using the published descriptors. They should identify missing evidence, vague commitments and unsupported claims rather than rewriting the answer according to personal style.

Mistake 18: late portal submission

Submitting close to the deadline introduces avoidable risks: slow uploads, file-size limits, portal timeouts, corrupted documents, password problems and last-minute changes. Buyers are generally constrained by the published deadline and may not accept late tenders.

Set an internal deadline well before the official cut-off. Upload final files early, verify that each document opens correctly and save the submission receipt. Restrict further changes unless they are essential and controlled.

Worked example: why a polished answer can still score poorly

Question

Explain how you will manage resident communication during planned works, including vulnerable residents, missed appointments and complaints.

Polished but weak response

We pride ourselves on excellent customer care. Our experienced liaison team will keep residents informed at all times and resolve any issues quickly and professionally. We have delivered many similar contracts and always put residents first.

This answer sounds positive but does not explain the communication stages, channels, responsibility, vulnerable-person controls, missed-appointment process, complaint timescales or evidence. It may receive a limited score.

Stronger response structure

• Named Resident Liaison Officer and cover arrangements.
• Pre-start contact sequence and accessible communication options.
• Needs assessment and consent-based vulnerable resident register.
• Appointment confirmation, reminder and no-access escalation.
• Daily issue log with ownership and response times.
• Complaint acknowledgement, investigation and close-out process.
• Weekly reporting and satisfaction measurement.
• Relevant evidence from a comparable contract.

The WPP five-gate error prevention system

1. Opportunity gate: confirm eligibility, capacity, strategic fit and commercial viability before bidding.
2. Compliance gate: map every instruction, returnable and mandatory requirement.
3. Evidence gate: confirm each scored answer has relevant proof and measurable controls.
4. Consistency gate: reconcile quality, price, programme, resources and assumptions.
5. Submission gate: verify approvals, files, portal upload and receipt before the deadline.

Record each gate formally. The purpose is not bureaucracy; it is to prevent predictable errors from surviving until submission.

30-day improvement plan

Master pre-submission checklist

• Every question and sub-part is answered directly.
• Headings mirror the evaluation requirement.
• Methods explain what, who, when, how and control.
• Claims are supported by relevant evidence.
• Examples include measurable outcomes and lessons applied.
• Roles, cover and escalation are clear.
• Risks include preventative and contingency controls.
• KPIs include data, ownership, thresholds and corrective action.
• Word and character limits are confirmed.
• Attachments comply with the instructions.
• Quality commitments are reflected in price and programme.
• Names, dates, quantities and assumptions are consistent.
• All mandatory documents and declarations are complete.
• Files are correctly named, current and readable.
• Senior approvals are recorded.
• The submission is uploaded and checked before the deadline.
• The portal receipt is saved.

Frequently asked questions

Worked SME example

Use the same principle with your own contract, evidence and delivery model. The example is not wording to copy into a tender; it demonstrates the level of specificity needed to make a response credible and assessable.

Failure points to remove

• Late submission
• Unanswered sub-questions
• Conflicting commercial figures
• Unapproved changes to buyer templates

Each failure point should be converted into a control within your bid process. For example, a recurring document error should result in an amended checklist, named checker and earlier review date.