Turn the tender documents into a response plan

The purpose of a response plan is to prevent omissions and contradictory commitments. Start it before drafting polished prose. One person should be able to trace every required answer back to the document that asks for it.

Common to all countries

Read for obligations, scoring and delivery

Collect the current notice, instructions, specification, response forms, price schedule, proposed contract and published amendments. Use the file names the buyer provides, while keeping a dated internal record of versions. Assign someone to monitor updates until the process allows you to stop.

Make a first pass for scope and deadlines, then a detailed pass for requirements. Distinguish mandatory conditions, scored questions, contractual obligations, pricing instructions and submission rules. The Scottish Government’s bidding guidance emphasises reading the documents, using the requested formats and asking questions through the appropriate process. The matrix below is an original way to organise that work.

Source	Required response	Owner	Evidence and check
Specification §3	Coverage during stated hours	Delivery lead	Rota matches hours and cost model
Quality question 2	Mobilisation plan within word limit	Bid writer	Dates, responsibilities and dependencies checked
Price schedule row 8	Unit rate per visit	Finance	Unit definition and calculation checked
Submission instructions	Required files and final submission	Bid coordinator	Portal checks and receipt retained

Add an internal deadline and status to each row. Use precise references so a reviewer can find the original wording. Where one requirement affects several answers, connect the rows instead of letting each writer interpret it independently.

Ask questions that remove uncertainty

A clarification request should identify the document and clause, state the ambiguity and ask one answerable question. Avoid telling the buyer more about your confidential solution or pricing than is necessary: questions and answers may be circulated under the applicable process.

Luma reads “response within two hours” but cannot determine whether it means acknowledgement or arrival. A useful question is: “For specification §3, does the two-hour response requirement mean acknowledgement of the request or arrival on site, and during which service hours is it measured?” This affects staffing and cost, so it belongs in the clarification log before Luma finalises its offer.

Record when the question was sent, through which channel, who owns it and how the answer changes the response. Do not quietly convert an unanswered question into your preferred assumption. If the documents remain inconsistent, use the prescribed route to establish the applicable position.

Control changes across the whole offer

Suppose an amendment adds Saturday opening. The coordinator records the new version, identifies the affected requirements and asks delivery and finance to update their work. The technical answer, rota and price must all describe the same service.

Hold a short integration review before submission. Look for conflicting numbers, people, dates and definitions across files. A convincing narrative cannot compensate for a cost model based on a different scope.

Country specific — what to verify

Check the deadline and channel for clarification questions, how official answers and amendments are issued, and the permitted communication with the buyer. Verify rules on site visits, confidentiality and the hierarchy of documents. Do not invent a universal rule that one document always overrides another.

If a material ambiguity remains close to the deadline, escalate it internally and use the available official process. An informal assurance does not, by itself, establish that a written requirement has changed.

Put it into practice

Build ten rows from a real tender. Include at least one pricing instruction, one mandatory condition, one scored response and one contractual commitment. Draft a focused clarification question for the most consequential uncertainty.

Self-check: a colleague should be able to work from a row without guessing what to produce. For the two-hour example, a good answer identifies the clock definition and service hours; “we will be responsive” leaves the operational and pricing problem unresolved.