Why "we've read the tender" isn't the same as "we're ready to respond"
Most bid teams read a tender collectively and informally: someone skims it, flags the obvious bits, and drafting starts against a shared understanding that's never actually been written down consistently. That works for a simple, short tender. It falls over fast on anything with mandatory gates, multiple contributors, or a document set that changes mid-process via addenda — because nobody can point to a single source of truth for what's actually required, by whom, by when.
The structure that works: group by response section, not by source document
A tender pack is organised the way the issuer wrote it — by document. A response plan should be organised the way your team will actually work — by response section. The same nine requirements from a tender pack, once grouped, might become: a governance narrative, a technical/commissioning methodology, an H&S compliance evidence pack, a commercial/liability position, and a submission checklist. That's a materially smaller number of real work items than the raw requirement count, because several individual requirements usually roll up into one response deliverable.
Every item needs three things, not just a description
- An owner. Not "the technical team" — a named person accountable for that specific section.
- A status. Not started, in progress, evidence gap, ready for review, submitted — a small, honest set of states everyone uses the same way.
- A citation back to source. The exact document, section and page the requirement came from, so anyone can verify the response actually answers what was asked — not what the team assumed was asked three weeks ago.
A worked example
From the tender pack in our alliance RFT teardown, the response plan breaks down roughly like this:
| Response item | Owner | Priority |
|---|---|---|
| Governance narrative (alliance structure, accountable lead, delivery partners) | Technical Lead | Mandatory |
| Design & commissioning methodology | Technical Lead | Requirement |
| Health & safety compliance evidence | HSEQ Manager | Mandatory |
| Liability & contract terms position | Commercial Lead | Requirement |
| Submission checklist & addenda acknowledgement | Bid Manager | Mandatory gate |
Keep it live when the tender changes
An addendum after week one is normal, not exceptional, on anything but the simplest tenders. When one lands, the useful question isn't "did we read it" — it's "which specific response items does it actually affect, and who owns re-checking them." A response plan that's linked back to source, item by item, can answer that in minutes. One that lives only in people's heads usually can't answer it at all before it's too late.