A practical operating system for winning public contracts.
The final submission check protects against avoidable compliance and portal errors. It should be completed by someone who understands the procurement requirements but is sufficiently independent to challenge the pack.
A strong tender can still be lost in the final hours through an omitted attachment, inconsistent price, unsigned declaration, corrupted upload or missed portal field. The final submission review is therefore not an administrative formality. It is the last controlled assurance stage before the supplier makes a binding offer.
Why the final submission check matters
Public procurement is document-led. Evaluators can normally assess only what has been submitted through the authorised route by the deadline. They may not be able to infer missing information, accept a late replacement or repair a material omission through clarification. A final check protects the quality score already earned during drafting and reduces the risk of avoidable non-compliance.
The objective is not to rewrite the entire bid at the last minute. It is to confirm that the approved submission is complete, internally consistent, readable, authorised and uploaded correctly.
Create a controlled final-review gate
Set a formal review gate before the external deadline. For a normal tender, the internal submission target should usually be at least one working day early. Complex procurements, large upload packs or unfamiliar portals may justify an earlier target.
The final reviewer should be independent enough to challenge the pack. They should use the tender documents, portal requirements and compliance matrix as the source of truth rather than relying on memory.
| Role | Primary responsibility |
|---|---|
| Bid lead | Confirms all responses and evidence are approved. |
| Commercial lead | Confirms price schedules, assumptions and totals. |
| Compliance reviewer | Checks every instruction, declaration and attachment. |
| Authorised signatory | Approves the final offer and required declarations. |
| Portal owner | Uploads, validates, submits and saves confirmation. |
Freeze the document set
Introduce a content freeze before final upload. After the freeze, changes should be controlled and approved. This prevents different team members editing local copies and accidentally reintroducing old text or figures.
- Create one final submission folder.
- Remove drafts, tracked-change copies and superseded documents.
- Apply a clear version and approval status.
- Restrict editing access where practical.
- Record any post-freeze change in a change log.
Recheck the latest procurement documents
Before reviewing the bid, confirm that the team has used the latest issued documents. Buyers may publish clarification responses, corrected schedules, revised specifications or formal extensions during the competition.
Compare the final pack against the portal document list and clarification log. Mark superseded files clearly and verify that every amendment has been reflected in quality, price and programme documents.
Complete the mandatory compliance review
Start with pass/fail requirements because a strong scored response cannot compensate for a mandatory failure. Review every instruction containing words such as “must”, “shall”, “mandatory”, “pass/fail”, “required” or “will not be considered”.
| Control | Final question |
|---|---|
| Eligibility | Are all conditions of participation and declarations complete? |
| Insurance | Are levels, policy types and evidence compliant? |
| Certifications | Are certificates current, correctly scoped and legible? |
| Signatures | Has the correct authorised person signed every required document? |
| Format | Are templates, file types and naming rules followed? |
| Word limits | Is every response within the stated limit? |
Check every portal field
Do not assume that uploading documents completes the submission. Many portals also contain mandatory tick boxes, declarations, numeric fields, drop-down selections and confirmation questions.
Work through the portal screen by screen using a checklist. Save regularly, verify that answers remain populated after navigation and inspect any validation warnings before submission.
Review each quality response against the question
The final reviewer should read the exact question, weighting and scoring description before reading the answer. Confirm that every sub-part has been addressed and that the response explains delivery rather than merely repeating the specification.
Each answer should clearly show the method, responsible people, timescales, controls, evidence, risks, monitoring and expected outcome where relevant.
Check evidence and claims
Every important claim should be supportable. Verify contract names, dates, values, KPI results, staff qualifications and case-study outcomes. Remove unsupported superlatives such as “industry leading” unless the claim is evidenced and relevant.
Confirm that named employees, delivery partners and references have agreed to their inclusion and remain available for the proposed contract.
Reconcile quality, price and programme
Final assurance must test the submission as one integrated offer. A quality response may promise resources, systems or response times that are not funded in the price or allowed for in the programme.
- Staffing numbers match the resource schedule.
- Mobilisation dates match the programme.
- Subcontractors appear consistently across all documents.
- Social value commitments are costed and deliverable.
- KPI frequencies align with management time and systems.
- Assumptions do not contradict the specification or contract.
Complete the commercial arithmetic check
Use a reviewer who understands the pricing model but did not prepare every calculation. Recalculate totals independently and check formulas, units, quantities, rates, percentages, VAT treatment and rounding.
Pay particular attention to hidden spreadsheet rows, broken formulas, copied cells, annual versus monthly values, zero-priced items and provisional sums. Open the final file on a separate device if possible to confirm formulas and presentation remain intact.
Review contract qualifications and assumptions
Check that the submission does not include unapproved qualifications, caveats or standard sales terms. A qualification may make the tender non-compliant or create uncertainty about what is being offered.
Any unavoidable assumption should be consistent with the buyer’s instructions and clarification responses. Where the procurement requires unconditional acceptance, obtain internal legal or commercial approval before submission.
Validate file names and formats
Use concise, professional file names that identify the question or schedule. Avoid ambiguous names such as “final2-new-revised”. Confirm permitted file types, individual size limits, total upload capacity and whether password protection is prohibited.
Open every final file from the submission folder. Check that PDFs are searchable, spreadsheets display correctly, links work where allowed and no document is corrupted.
Remove hidden and inappropriate content
Inspect document properties, comments, tracked changes, hidden rows, notes and revision history. These may reveal internal scoring comments, competitor references, personal data or commercially sensitive information.
Convert approved documents carefully and then reopen the converted versions. Redaction should be permanent rather than created by placing a black shape over visible text.
Check confidentiality and data protection
Submit only the personal and confidential information required. Review CVs, case studies, references and beneficiary evidence for unnecessary personal data. Confirm that confidential markings are used appropriately and do not conflict with any buyer instructions.
Where the tender requests a confidentiality schedule, describe the specific information and justification rather than marking the entire bid confidential.
Confirm signatory authority
Identify who is authorised to commit the legal entity. Check delegated authority, board approval thresholds and any requirement for wet signatures, electronic signatures or witnessed execution.
The bidding entity name, company number, registered address and signatory details should be consistent throughout the pack.
Plan the portal upload
Do not begin the upload minutes before the deadline. Large files, slow connections, portal timeouts and validation errors can all delay submission.
- Log in and verify user permissions early.
- Confirm the deadline and time zone shown by the portal.
- Upload files in a controlled order.
- Match each file to the correct question or slot.
- Download or preview uploaded files where the portal allows.
- Complete portal validation before pressing submit.
Use a two-person portal check
One person should upload and another should verify. The second checker compares the portal contents to the approved submission register and confirms that the correct version is in each location.
For remote teams, screen sharing can provide an effective control, but the checker should still use the independent register rather than simply watching the uploader.
Submit early and verify receipt
Pressing save is not always the same as submitting. Follow the portal process through to final confirmation. Record the submission reference, timestamp and status.
Where the portal allows withdrawal and resubmission, understand the consequences before making changes. Never withdraw a valid submission close to the deadline unless the replacement is fully ready and the risk has been authorised.
Build a complete audit record
Immediately save the final submitted files, submission confirmation, screenshots where appropriate, clarification log, approvals and compliance checklist in a locked archive. This record supports any later clarification, assessment-summary review, mobilisation handover or internal lessons-learned exercise.
Worked final-review example
A contractor preparing a housing repairs tender had completed all quality responses and pricing schedules. The final reviewer identified four issues: a mobilisation response referred to six operatives while the price funded five; an insurance certificate had expired; one portal declaration was unanswered; and a case-study PDF contained tracked comments.
Because the review occurred two days before the deadline, the contractor had time to reconcile the staffing model, obtain updated insurance evidence, complete the declaration and clean the PDF. None of these changes improved the underlying service proposal, but each protected the submission from avoidable risk.
The WPP five-gate submission test
| Gate | Pass standard |
|---|---|
| 1. Compliance | Every mandatory instruction and portal field is complete. |
| 2. Quality | Every response answers the question and is evidence-led. |
| 3. Commercial | Price, programme, resources and assumptions reconcile. |
| 4. Document control | Only approved, clean and readable files remain. |
| 5. Submission | The correct files are uploaded, validated and formally received. |
Master final-submission checklist
- Confirm the deadline, portal and authorised submission route.
- Confirm all amendments and clarification responses are incorporated.
- Freeze and approve the final document set.
- Check every mandatory requirement and declaration.
- Check word counts, page limits and required templates.
- Verify all evidence, names, dates, values and qualifications.
- Reconcile quality, price, programme and resources.
- Recalculate all commercial schedules independently.
- Confirm contract acceptance and approved assumptions.
- Open every final file and check readability.
- Remove comments, tracked changes and hidden content.
- Confirm signatory authority and legal entity details.
- Upload early and complete a two-person portal check.
- Submit formally and save the receipt.
- Archive the exact submitted pack and approvals.
Frequently asked questions
How early should we submit?
Aim to complete formal submission at least one working day before the deadline where practical. Larger or unfamiliar portals justify more time.
Can a buyer accept a missing attachment later?
Do not rely on it. The buyer’s ability to clarify or accept missing material depends on the procurement documents, the nature of the omission and equal-treatment considerations.
Who should perform the final check?
Use someone competent who has not been responsible for every element of the bid. Independence improves challenge and error detection.
Should we make last-minute improvements?
Only where the benefit clearly outweighs the risk and the change can pass approval and consistency checks. Uncontrolled late editing often creates new errors.
What evidence should we retain after submission?
Keep the exact submitted files, portal confirmation, compliance checklist, commercial approval, clarification log and any final change record.
Can we email the bid if the portal fails?
Follow the published instructions and contact the buyer through the authorised channel immediately. Do not assume an alternative method will be accepted without explicit approval.
Apply the guidance in practice
The objective is to complete a controlled final review that protects both compliance and score quality. Treat this as an operational discipline rather than a one-off writing exercise. Assign ownership, keep source evidence and review the approach after each procurement so the business improves over time.
Freeze drafting and confirm approval status
Check every portal field, attachment and declaration
Reconcile pricing across all documents
Confirm filenames, formats, limits and signatures
Submit early and retain proof of receipt
Worked SME example
The final reviewer should use the buyer’s checklist and portal structure, not the bid team’s memory, to verify completeness.
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
- Uploading draft files
- Submitting at the final minute
- Failing to open exported PDFs
- Assuming the portal saves every field automatically
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.
WPP review gate
Before treating this area as complete, confirm that the approach is relevant to the published requirement, approved by the people who will deliver it, supported by evidence, commercially achievable and expressed clearly enough for an evaluator to verify.
- The requirement and scoring method have been read in full.
- Every commitment has an accountable owner.
- Evidence is current, traceable and relevant.
- Delivery assumptions agree with the price and contract.
- An independent reviewer has challenged the final position.
Turn the guidance into action
Use the WPP Procurement Toolkit™ to test readiness, review response strength and make a structured bid decision.
Strengthen a live tender with a professional WPP review.
We review completed submissions for compliance, structure, evidence and alignment with the published evaluation criteria.
Discuss your tender