Tender submissions carry an inherent, unavoidable risk. After weeks of writing, pricing, and gathering evidence, the entire effort distils down to a single upload window. A brilliant method statement cannot save a bid that fails a mandatory compliance check. A competitive price schedule means nothing if the portal times out before the final document attaches. You need a rigorous tender review checklist before submission to protect the work your team has done.
This guide provides the definitive 28-point bid submission checklist used by senior bid managers across the UK. It moves past generic advice to cover the specific, mechanical checks required to survive evaluation under the Public Contracts Regulations 2015 (PCR 2015) and the Procurement Act 2023. Whether you are bidding for a spot on a Crown Commercial Service framework or responding to a local authority ITT, this tender QA process ensures your submission is compliant, complete, and competitive. We cover document naming, portal testing, pricing alignment, and the critical final tender proofread.
What this guide covers
- Commercial and pricing alignment: Ensuring your numbers match your narrative and avoiding abnormal low bid challenges.
- Compliance and mandatory requirements: Passing the pass/fail gateway without unforced errors that lead to immediate disqualification.
- Quality and narrative review: Structuring the tender proofread to catch structural flaws, weak evidence, and misaligned tone, not just typos.
- Portal and upload logistics: Managing the physical submission process safely to prevent technical failures at the deadline.
- Common mistakes: The most frequent errors bid managers make in the final 48 hours and how to prevent them systematically.
Commercial and pricing alignment
Pricing schedules are unforgiving. Evaluators do not infer intent; they read the numbers in the cells. A single formula error can render a bid financially unviable or artificially expensive. The commercial review is the most critical phase of your tender review checklist. You must lock the commercial model before the final quality review begins.
1. Reconcile the pricing schedule with the method statements
Your pricing must reflect the delivery model described in your quality responses. If your method statement promises a dedicated account manager and quarterly on-site reviews, the pricing schedule must include the costs for those resources. Evaluators cross-reference these documents systematically. Inconsistencies suggest a lack of coordination between your commercial and operational teams, casting severe doubt on your ability to deliver the contract as promised.
2. Verify all spreadsheet formulas
Do not trust the buyer's Excel formulas, and do not trust your own without checking. Manually verify the sums in every column and row. Check that any VAT calculations apply the correct rate and are applied only where requested. A broken SUM formula that excludes a row can result in a contract awarded at a loss, binding your business to an unprofitable delivery model for years.
3. Confirm pricing validity periods
Public sector tenders usually require prices to remain valid for 90 or 120 days from the submission deadline. Ensure your commercial sign-off explicitly acknowledges this validity period. If your supply chain costs fluctuate, your pricing model must account for that risk within the allowed parameters. Failing to honour your pricing post-award can lead to contract termination and reputational damage.
4. Check for blank cells
A blank cell in a pricing schedule is a compliance failure. If a cost is zero, enter "0.00" or "Included" if the instructions permit. If a line item does not apply, enter "N/A" and provide a clarification note if allowed. Never leave a cell empty. Evaluators cannot score a blank space, and many procurement teams will reject the entire commercial envelope as incomplete.
5. Ensure rates align with framework caps
If you are bidding for a call-off contract under an existing framework, verify that your proposed rates do not exceed the maximum rates you submitted at the framework stage. Exceeding framework rate cards is a common cause for immediate disqualification. Cross-reference your current pricing against the original framework agreement documents before finalising the numbers.
6. Review abnormal low bid triggers
Under the Procurement Act 2023, contracting authorities must investigate abnormally low tenders. If your pricing is significantly lower than the market average, prepare a robust commercial justification. Ensure your internal review confirms that the low price stems from genuine operational efficiencies, not omitted scope or misunderstood requirements.
Compliance and mandatory requirements
The compliance check is a binary exercise. You either pass or you fail. This section of the bid submission checklist requires cold, methodical verification against the buyer's instructions. Do not let a strong technical proposal fail because of a missing signature or an expired certificate.
7. Verify the exact submission deadline
Confirm the date, the time, and the time zone. "12:00" usually means noon, but verify if it is GMT or BST. Portal clocks dictate the deadline, not your local computer. Missing the deadline by one minute is the same as missing it by a month. Public sector buyers rarely grant extensions for bidder-side delays.
8. Check page, word, and character limits
Adhere strictly to the stated limits. If the limit is 1,000 words, a 1,001-word response may be truncated by the portal, or the evaluator may simply stop reading at the limit. Check whether the limit includes headings, tables, or diagram captions. If the portal uses character limits, confirm whether they include spaces.
9. Confirm document formats
If the buyer requests a PDF, do not upload a Word document. If they request an Excel file for pricing, do not submit a PDF of the spreadsheet. Automated portal systems often reject incorrect file types outright. If the format is not specified, default to PDF for text documents to preserve formatting across different operating systems.
10. Sign all mandatory declarations
Form of Tender, Non-Collusion Certificates, and Conflict of Interest declarations must be signed by an authorised signatory. Check whether the buyer accepts electronic signatures or requires wet ink scans. Ensure the person signing has the legal authority to bind the company, usually a director listed on Companies House.
11. Validate accreditations and insurances
Check the expiration dates on your ISO certificates, Cyber Essentials Plus, and insurance policies (Employer's Liability, Public Liability, Professional Indemnity). If a certificate expires during the procurement process, include a note explaining the renewal status. Do not submit expired documentation without context.
12. Check font sizes and margins
Some buyers specify Arial 11pt with 2cm margins to ensure a level playing field. If you submit Arial 10pt to squeeze in more text, you risk disqualification for non-compliance. Follow the formatting rules exactly. Do not attempt to bypass page limits by shrinking the font size in tables or appendices.
13. Review the clarification log
Read through every published clarification question and answer. Buyers frequently issue updates that change the specification, alter word limits, or introduce new mandatory requirements. Ensure your final submission reflects the latest guidance, not the original ITT document. Missing a critical update from the clarification log is a common unforced error.
Quality and narrative review
The tender QA process for the narrative sections must go beyond basic spell-checking. It requires an objective assessment of how well the response answers the specific question asked and how strongly it aligns with the evaluation criteria.
14. Answer the actual question
Read the question, then read your answer. Did you answer the specific question asked, or did you answer the question you wished they had asked? Break down multi-part questions and ensure every sub-clause is addressed clearly. Use the sub-clauses as headings in your response to guide the evaluator.
15. Map against the evaluation criteria
If the scoring matrix awards 5 marks for "demonstrating added value," highlight exactly where your response demonstrates added value. Make it easy for the evaluator to award top marks. Use their terminology. If they ask for "continuous improvement," do not write about "ongoing optimisation." Mirror their language.
16. Eradicate generic content
Search for and destroy generic marketing copy. "We are a leading provider of innovative solutions" scores zero marks. Replace it with specific evidence: "We deliver IT support to 14 local authorities, maintaining a 99.9% uptime SLA." Specificity builds trust; generalities destroy it.
17. Verify all claims with evidence
If you claim to be highly responsive, provide the average response time from your service desk. If you claim to have a strong safety record, state your RIDDOR statistics. Unsubstantiated claims weaken the entire bid. Link every assertion to a measurable outcome or a verified case study.
18. Check the tone and voice
The tone should be professional, confident, and direct. Avoid passive voice where possible. Say "We will implement the system in four weeks" instead of "The system will be implemented in four weeks." Active voice demonstrates accountability and makes the narrative punchier.
19. Conduct a "Red Team" review
Have someone who did not write the bid read it cold. They should score the responses against the buyer's criteria. If the Red Team cannot find the answer easily, the evaluator will not find it either. This review must happen early enough to allow for meaningful rewrites, not just minor tweaks.
20. Perform the final tender proofread
This is the mechanical check for spelling, grammar, and consistency. Look for incorrect buyer names left over from copy-pasting previous bids. Ensure acronyms are defined at their first use. A bid riddled with typos suggests a lack of attention to detail, which evaluators may extrapolate to your service delivery.
Portal and upload logistics
The final hours before submission are high-risk. Portal failures, internet outages, and file size limits can derail months of work. Treat the upload process as a critical project phase, not an administrative afterthought.
21. Implement a strict naming convention
Name files exactly as requested by the buyer. If no convention is specified, use a clear, logical format: [Company Name]_[Document Title]_[Question Number]. This prevents uploading the wrong file and helps the buyer manage the documents. Consistent naming conventions also reduce panic during the final upload sequence.
22. Check file sizes against portal limits
Many portals restrict individual file sizes (e.g., 20MB maximum). If your method statement includes high-resolution diagrams, compress the PDF before uploading. Do not discover a file size issue ten minutes before the deadline. Test your file sizes against the portal constraints at least 24 hours in advance.
23. Clear all track changes and comments
Before converting Word documents to PDF, ensure all internal comments, track changes, and highlighting are removed. You do not want the buyer reading an internal note that says, "Are we sure we can deliver this for this price?" Inspect the final PDFs to confirm no metadata or hidden text remains.
24. Upload in batches
Do not wait until you have every single document finalised before starting the upload. Upload the compliance documents, policies, and completed sections early. Save the portal progress. This reduces the bottleneck at the end and mitigates the risk of a portal timeout during a massive single upload.
25. Verify the uploaded files
After uploading, open the files from within the portal environment to ensure they are not corrupted and that the formatting has held. Sometimes portals compress or alter files during the upload process. Verifying the files in situ is the only way to be certain the buyer will see what you intended.
26. Check for hidden portal questions
Some portals include drop-down questions or text boxes that only appear when you select certain options (e.g., indicating you are an SME). Click through the entire portal submission flow early to identify any hidden requirements. Do not let a surprise 500-word text box derail your submission timeline.
27. Assign a single submission lead
One person must own the physical submission process. If multiple people are uploading files simultaneously, version control fails, and documents are overwritten. The submission lead clicks the final button and confirms the upload sequence. Everyone else steps back.
28. Save the submission receipt
Take a screenshot of the confirmation screen and save the automated email receipt. This is your proof of delivery if the buyer claims they did not receive the bid. Store this receipt in your bid library alongside the final submitted documents for audit purposes.
Worked example
Here is an example of how a pricing inconsistency can fail a bid, based on a typical scenario in IT Services procurement.
The Scenario: A managed service provider is bidding for a 3-year local government IT support contract under a Crown Commercial Service framework. The buyer evaluates on a 60% Quality / 40% Price split.
The Quality Response: Question 4 asks about service transition and onboarding. The bid writer details a comprehensive 6-week onboarding process, promising two dedicated senior engineers on-site full-time for the duration of the transition to ensure zero downtime and seamless knowledge transfer. The response is strong, specific, and tailored to the buyer's environment.
The Pricing Schedule: The commercial lead completes the pricing spreadsheet independently. Under "Implementation and Transition Costs," they enter a flat fee of £2,500, based on their standard remote-only onboarding model. They do not review the final quality response before locking the commercial model.
The Evaluation: The evaluator scores the quality response highly but cross-references it with the pricing schedule. They calculate that two senior engineers on-site for 6 weeks cannot possibly be delivered for £2,500. The numbers do not align with the narrative.
The Result: The evaluator marks the pricing as abnormally low and unsustainable, raising a clarification question. The bidder must either admit a pricing error (often leading to immediate disqualification for altering the commercial offer post-submission) or commit to delivering the expensive on-site transition at a significant financial loss. A robust tender review checklist, specifically step one (reconciling pricing with method statements), catches this misalignment before submission.
Common mistakes
Even experienced bid managers make unforced errors under pressure. Avoid these common traps by integrating them into your tender QA process:
- Leaving the portal until the last day: Bidders often focus entirely on writing and assume the upload will take ten minutes. Portals require registration, two-factor authentication, and navigation. Register immediately upon deciding to bid and test the upload process days in advance. A portal timeout at 11:55 AM is not grounds for an extension.
- Copy-pasting the wrong buyer name: Reusing strong content from a previous bid is standard practice, but failing to sanitise it is disastrous. Submitting a bid to the Department for Work and Pensions that references your commitment to the Ministry of Justice shows a lack of care and usually results in a low score. Use "Find and Replace" carefully, and always manually proofread.
- Ignoring the word count instructions: Assuming a 10% tolerance on word counts is a risk. If the limit is 500 words, write 490. Evaluators use portal tools that strictly cut off text at the limit. Your crucial concluding sentence will be deleted before the evaluator ever sees it, ruining the impact of your response.
- Failing to answer the specific sub-questions: Buyers often bundle three questions into one prompt (e.g., "Describe your methodology, how you will manage risk, and your reporting frequency"). Bidders often write a brilliant methodology but forget the reporting frequency entirely. Break the prompt down and use sub-headings for each element to ensure complete coverage.
- Submitting expired certificates: Attaching an ISO 9001 certificate that expired two weeks ago is an immediate compliance failure. Maintain a central, updated bid library for all corporate documentation, and assign someone to monitor expiration dates. If a renewal is pending, include the audit confirmation letter.
- Skipping the Red Team review: Internal teams become blind to their own narrative flaws. Skipping an independent review means you submit a document that makes sense to the author but confuses the evaluator. Always allocate time for a cold read by someone outside the core bid team.
- Failing to define acronyms: Public sector procurement is rife with acronyms, but you cannot assume the evaluator knows yours. Define every acronym at its first use. "We use our proprietary CMDB" means nothing if the evaluator does not know what a CMDB is in your context.
Frequently asked questions
Who should perform the final tender proofread?
The final proofread should be conducted by someone who did not write the content. The original author will read what they intended to write, not what is actually on the page. A fresh set of eyes is essential for catching structural errors, typos, and tone inconsistencies.
How early should we aim to submit the bid?
Best practice is to submit 24 hours before the deadline. This provides a crucial buffer to resolve portal outages, file size issues, or missing signatures. Submitting in the final hour is an unnecessary operational risk that frequently leads to disqualified bids.
What happens if we find an error after submission but before the deadline?
Most procurement portals allow you to withdraw a submission, replace the incorrect file, and resubmit, provided the deadline has not passed. However, doing this close to the deadline risks the portal timing out during the resubmission. Only withdraw and resubmit for critical errors.
Do evaluators really check every mandatory attachment?
Yes. The compliance check is the first stage of evaluation. Procurement teams use checklists to verify every required document is present before passing the narrative responses to the scoring panel. A missing insurance certificate or an unsigned declaration usually means immediate disqualification.
How do we handle contradictory instructions in the tender pack?
If the specification asks for a 1,000-word response but the portal only allows 500 characters, you must raise a clarification question immediately. Do not guess the buyer's intent. Use the clarification period to resolve all ambiguities on the public record.
Does the Procurement Act 2023 change the submission process?
The mechanics of portal uploads remain largely the same, but the Procurement Act 2023 introduces stricter transparency and compliance requirements. Buyers have less flexibility to accept non-compliant bids. Your tender review checklist must be more rigorous than ever to survive the initial compliance gateway.
