--- title: "Public Sector Tender Submission Checklist: Documents, Approvals and Portal Receipts" canonical: "https://prestigecommercialconsulting.co.uk/articles/public-sector-tender-submission-checklist-documents-approvals-portal-receipts" author: "Prestige Commercial Consulting Limited" category: "Supplier Readiness" published: "2026-11-02" modified: "" read_time: "6 min read" keywords: ["UK public procurement", "Supplier Readiness", "supplier readiness", "public procurement frameworks"] --- # Public Sector Tender Submission Checklist: Documents, Approvals and Portal Receipts Use this public sector tender submission checklist to control documents, approvals, portal uploads and receipts before your team treats a bid as submitted. A public sector tender submission checklist should answer a simple question: can the team prove that the approved response reached the buyer through the required route? A completed document folder does not answer it. Neither does an expression of interest, an upload confirmation or a colleague saying the bid is ready. Submission is a separate piece of work, with an owner, checks and evidence. Treating it that way reduces avoidable errors after the writing has finished. The method below is practical bid-management advice, not a statutory checklist or a guarantee that a buyer will accept a response. ## Confirm the deadline, route and current instructions Start with the current notice, tender documents, amendments and published clarification answers. Record the opportunity reference, lot, procurement stage, closing date, exact time and stated time zone. Check whether a clarification deadline, participation deadline and final tender deadline are different. Name one submission owner and a deputy. Both should understand the portal permissions, account recovery route and buyer contact instructions. Test access early enough to resolve problems through the published support channel. Keep a short instruction log identifying the version checked and the person who checked it. If the buyer changes a document, reopen affected checks. A deadline recorded in an early alert should not silently override a later formal amendment. ## Build a document and response inventory Use one row for every required return, including answers completed directly in the portal. A useful inventory records: - The buyer's question or document reference and the relevant lot. - Required file format, attachment location and any size or word limit. - Response owner and independent reviewer. - Approved version, approval date and final filename. - Signature or declaration requirements and authorised signatory. - Portal status, submission evidence and any outstanding action. Mark genuinely inapplicable items with the permitted explanation rather than leaving uncertainty. Check that required spreadsheets retain their formulas and structure, PDFs open correctly and attachments are legible. Avoid putting unnecessary personal information into the return. Include the evidence requested, using the buyer's permitted redaction or confidentiality arrangements where relevant. ## Check supplier information separately from the bid Find a Tender registration and a tender response are related tasks, not interchangeable evidence of completion. The [central digital platform guidance](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/guidance-central-digital-platform-and-publication-of-information-html) explains how core supplier information is stored and shared. Confirm that the organisation's information is current and has been shared in the manner required for this procurement. Separately check the buyer's portal questions and supporting documents. A current supplier-information record does not complete the technical response, pricing schedule or tender declarations. The [electronic communications guidance](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/guidance-electronic-communications-html) explains the framework for electronic procurement communication. It does not make every portal work identically. Follow the buyer's actual submission route; do not assume an email or a shared-drive link is an acceptable substitute. ## Approve one consistent final response Ask the reviewer to compare the documents against one another, not simply proofread each file. Do the price, staffing, delivery timetable, subcontractor arrangements and technical commitments describe the same offer? Are qualifications or assumptions permitted, and have material contractual departures been approved internally? Make the approval record precise: who approved which version, which price and which exceptions? A director's approval of yesterday's draft is not clear approval of a changed commercial offer. Move the agreed files into a controlled final-submission set and stop informal editing. If a material change is necessary, identify the affected documents and obtain renewed approval. Keep earlier drafts distinct so they cannot be uploaded accidentally. ## Complete the portal submission and verify its state Schedule time for uploading, reviewing and submitting, with a sensible margin before the buyer's deadline. Uploading files may save a draft rather than submit a response. Some systems require a separate declaration, confirmation or final submission step. Review every online section and attachment against the inventory. Use any available preview or download function to check what is actually saved. After submission, confirm the displayed state and capture the acknowledgement or reference. The [guidance on assessing competitive tenders](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/assessing-competitive-tenders-html) explains that a buyer may disregard a tender for breaching a published procedural requirement, including lateness or a prescribed word limit. This is a legal possibility, not a claim that every mistake automatically produces the same outcome. If a technical problem occurs, use the specified support route promptly and retain the error, timing and contact record. Do not assume the deadline has moved. ## Worked example: an upload that remained a draft Consider a fictional training supplier with a noon deadline. Its team finishes the technical response and pricing workbook the previous afternoon. At 9am, the submission owner uploads both files and sees them listed. The internal tracker is marked complete. A second-person check finds an unanswered declaration and a portal status of Draft. The owner completes the declaration, rechecks the approved files, submits and saves the timed acknowledgement. The tracker now identifies the actual submission event. The useful control was not a larger bid team or another rewrite. It was a distinction between approved, uploaded and submitted, supported by an independent check. The example is fictional and does not describe a Prestige client or tender result. ## Keep the receipt and close the internal handover Retain the approved return, relevant instructions, approval record, submission acknowledgement and any replacement-submission history together. Record the response version and time, not just a screenshot without context. If the portal permits later edits, confirm whether resubmission is required and retain evidence of the final state. Our [conditions of participation guide](https://prestigecommercialconsulting.co.uk/articles/conditions-of-participation-procurement-act-2023-sme-guide) addresses eligibility evidence; our [bid/no-bid guide](https://prestigecommercialconsulting.co.uk/articles/bid-no-bid-public-tenders) covers the earlier investment decision. [Prestige's supplier support](https://prestigecommercialconsulting.co.uk/supplier-support) can help structure response preparation, evidence controls and submission awareness. The supplier retains responsibility for its bid, approvals and submission. This is general procurement information, not legal advice. Check the current tender instructions, applicable regime and buyer requirements before acting. ## About this article Published by [Prestige Commercial Consulting Limited](https://prestigecommercialconsulting.co.uk/about). Canonical HTML: [https://prestigecommercialconsulting.co.uk/articles/public-sector-tender-submission-checklist-documents-approvals-portal-receipts](https://prestigecommercialconsulting.co.uk/articles/public-sector-tender-submission-checklist-documents-approvals-portal-receipts) This article provides general procurement information and does not constitute legal advice.