Creating a Tender Submission Plan

Why a submission plan matters

A tender is a temporary project with a non-negotiable completion date. The buyer will rarely extend the deadline because a supplier underestimated the workload, waited for information or encountered an internal approval delay. A submission plan therefore needs the same controls you would apply to a live contract: scope, milestones, ownership, dependencies, risk management, quality assurance and document control.

Without a plan, teams often start writing the easiest answers first, overlook pass/fail requirements, leave pricing until the final days and discover too late that key evidence is missing. A strong plan prevents this by making the whole requirement visible from day one.

Begin with a controlled document review

Do not begin drafting from the first quality question you see. Download every available document, save it in a controlled folder and complete an initial review. This should include the invitation, instructions, specification, contract terms, pricing schedules, selection information, evaluation methodology, appendices, declarations, technical standards and portal notices.

Record the document title, version, issue date and owner in a document register. Buyers may publish revised schedules or clarification responses during the competition. If writers work from different versions, the submission can become inconsistent or non-compliant.

Confirm whether the opportunity should be pursued

Planning should follow a documented bid/no-bid decision. Confirm that the organisation can meet mandatory conditions, deliver the scope, mobilise on time, accept the commercial risk and provide competitive evidence. A detailed submission plan is wasted if a fundamental requirement makes the opportunity unsuitable.

Where the decision is conditional, record the condition and deadline. For example, the bid may proceed only if insurance confirmation is obtained, a specialist subcontractor accepts the proposed terms or the buyer clarifies a pricing ambiguity. Assign each condition to an owner and escalate it before major writing effort is committed.

Build backwards from the portal deadline

The buyer’s deadline should not be your internal deadline. Work backwards and protect sufficient time for approval, file conversion, upload and portal checks. For a significant tender, the final content freeze may need to be one or two working days before submission. Smaller bids may use a shorter gap, but the principle remains the same.

A practical sequence is:

1. Portal submission and confirmation.
2. Final upload and file verification.
3. Director or authorised signatory approval.
4. Final compliance and consistency review.
5. Pricing approval and quality-price reconciliation.
6. Red-team evaluation review.
7. Technical validation.
8. First complete draft.
9. Evidence collection and response planning.
10. Launch meeting and requirements analysis.

Reverse planning reveals how little true writing time is available once reviews and dependencies are included.

Create a complete requirements matrix

The requirements matrix is the control centre of the bid. It should list every quality response, pricing return, form, certificate, declaration, attachment, signature and portal action. Each row needs an owner, reviewer, due date, status and dependency.

Use one controlled source of truth. Multiple trackers maintained by different people create conflicting information and hidden gaps.

Deconstruct every scored question

Long questions usually contain several requirements. Break each one into command words, topics, evidence requests, outcomes and constraints. Then turn those components into response headings or planning prompts.

For example, a mobilisation question may require the supplier to explain governance, staffing, systems, stakeholder communication, supply-chain readiness, risks and the transition timetable. A response that concentrates only on the programme may appear detailed but still leave most of the criterion unanswered.

• Identify every verb: describe, explain, demonstrate, provide or confirm.
• Highlight mandatory content and named attachments.
• Record the weighting and scoring descriptor.
• Note buyer priorities repeated in the specification.
• Allocate an indicative word budget to each sub-part.
• Identify the evidence needed to support the response.

Assign clear roles and decision rights

A bid needs more than a list of contributors. Define who is accountable for the overall submission, who writes each response, who provides technical evidence, who approves commitments and who signs the final return.

For small businesses, one person may hold several roles. The control still matters: separate writing, checking and approval wherever practical.

Run a focused bid launch meeting

The launch meeting should convert the tender documents into an agreed plan. It is not simply a general discussion about the opportunity. Circulate the key documents and initial matrix beforehand so meeting time is used for decisions.

Cover scope, buyer priorities, evaluation, win themes, mandatory requirements, major risks, evidence gaps, responsibilities, clarification questions, pricing assumptions, review dates and the submission route. End with confirmed actions, owners and dates.

Plan the evidence before writing

Writers lose time when they draft broad claims and then search for proof. For each response, identify the case studies, performance data, processes, CVs, accreditations, customer outcomes and lessons learned that will support the answer.

Create an evidence request log showing the item, source, owner, required date and verification status. Check that evidence is relevant, current, accurate and permitted for use. Where client names or confidential data cannot be disclosed, anonymise appropriately without weakening credibility.

Control clarifications and assumptions

Record all potential clarification questions during the document review. Submit them through the stated channel before the deadline and monitor the portal for responses issued to all bidders. Update the requirements matrix, pricing model and response plans when an answer changes the requirement.

Maintain a separate assumptions log for internal management. Do not introduce unapproved qualifications or assumptions into the final bid where the instructions prohibit them. Commercial and operational owners should agree how ambiguity will be treated.

Link the quality and commercial workstreams

Quality writers and pricing teams must not operate independently. Commitments relating to staffing, supervision, response times, reporting, technology, social value, training, mobilisation and contingency can all affect cost.

Schedule formal reconciliation points where the Commercial Lead checks that the price supports the delivery model and the Bid Lead checks that the narrative matches the priced resource. Resolve contradictions before final approval, not during the upload.

Use milestone-based progress control

Percentage-complete reporting can be misleading. A response reported as 90% complete may still lack its key evidence, approval or contract-specific detail. Define objective stages instead.

1. Planned: question analysed and owner assigned.
2. Evidence ready: required proof has been obtained and checked.
3. First draft: all sub-requirements are covered.
4. Technically validated: delivery owners confirm accuracy and feasibility.
5. Reviewed: scoring and compliance comments resolved.
6. Approved: final content locked for submission.

Use a short daily checkpoint for complex bids. Focus on overdue items, blocked dependencies, new portal information and decisions required.

Protect subject-matter expert time

Operational experts are often supporting live contracts while contributing to a tender. Give them precise requests rather than asking them to “write something about mobilisation”. Provide the question breakdown, word allocation, evidence needed and deadline.

Where possible, the Bid Lead should structure and edit the response while the expert validates the method. This reduces the burden on delivery teams and creates a more consistent submission.

Schedule distinct review gates

Do not combine every type of review into one last-minute proofread. Different reviews answer different questions:

• Technical review: Is the proposed method accurate, safe and deliverable?
• Compliance review: Does the submission meet every instruction and requirement?
• Evaluator review: Does the response justify the highest achievable score?
• Commercial review: Are price, resources, assumptions and commitments aligned?
• Editorial review: Is the document clear, concise and free from errors?
• Final approval: Is the authorised decision-maker satisfied with risk and commitments?

Build time for writers to resolve comments. A review completed minutes before the deadline has little value if no time remains to make corrections.

Manage versions and file names

Use a clear folder structure and naming convention. Avoid files called “final”, “final2” and “final latest”. The Bid Lead should control the master submission and archive superseded versions.

A useful name includes the question number, short title, version and date. Restrict editing rights where possible, use tracked changes during review and accept comments only in the controlled master. Confirm that final PDFs, spreadsheets and attachments open correctly and preserve required formatting.

Prepare for signatures and external dependencies

Forms may require a director, witness, insurer, accountant, parent company, subcontractor or external adviser. Identify these dependencies immediately. Senior signatories may be unavailable on the final day, and third parties may not work to your tender timetable.

Record who must sign, the permitted signature method, the final approved form and the return date. Never sign incomplete commercial documents simply to save time; complete and review them first.

Plan the portal submission

Assign one person to upload and another to verify. Confirm login access, file-size limits, accepted formats and whether individual responses must be entered directly into the portal. Test access early rather than discovering account or permission problems on deadline day.

Upload before the buyer’s deadline, then check every file and response. Save the submission receipt, confirmation email or screenshots permitted by your process. Do not assume that saving a draft means the tender has been submitted.

Worked example: a 15-working-day tender

The exact timetable will vary, but the example demonstrates the need to complete writing well before submission day.

Common planning failures

• Treating the buyer’s deadline as the internal deadline.
• Starting answers before reading the contract and specification.
• Failing to list every form and attachment.
• Giving multiple people uncontrolled copies of the same response.
• Leaving pricing and quality reconciliation until the end.
• Depending on evidence that has not been verified.
• Booking reviews without allowing time to resolve comments.
• Ignoring revised documents and clarification responses.
• Waiting until submission day to obtain signatures.
• Uploading at the last minute without verification.

The WPP submission control board

30-day implementation plan

Master submission-plan checklist

• The opportunity has passed the bid/no-bid gate.
• All procurement documents have been downloaded and registered.
• The buyer’s instructions and portal rules are understood.
• A complete requirements matrix is in place.
• Every response and return has an owner and reviewer.
• Internal deadlines work backwards from an early upload date.
• Questions have been deconstructed and word budgets agreed.
• Evidence requests and clarification questions are tracked.
• Quality, commercial and contract workstreams are linked.
• Technical, evaluator, commercial and compliance reviews are scheduled.
• External dependencies and signatures are controlled.
• Versions, file names and master documents are managed.
• Final approval is planned before upload.
• Portal access has been tested.
• A second person will verify the submitted package.
• Submission confirmation will be 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

• No single accountable bid lead
• Multiple uncontrolled file versions
• Commercial work disconnected from quality promises
• Reviews scheduled after internal deadlines

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.