What is the response row?
Use one row or section for each answerable requirement. Record the question, response, evidence, assumption, owner and approval state. Split a combined requirement when different specialists must approve it.
| Field | Purpose | Reviewer |
|---|---|---|
| Requirement | Preserve question | Bid lead |
| Response | State proposed position | Technical lead |
| Evidence | Support the claim | Quality or engineer |
| Exception | Show a qualification | Commercial lead |
| Status | Control approval | Bid manager |
Sources: Acquisition.gov: Federal Acquisition Regulation Part 15
How should exceptions be written?
State the affected requirement, the proposed alternative, the reason, the effect and the approval needed. Do not bury a departure in a paragraph that appears fully compliant.
Sources: Australian Government Department of Finance: Commonwealth Procurement Rules, UK Cabinet Office: The Construction Playbook
What should be checked before issue?
Check that the response uses the current source, that evidence is authorised, that technical values match schedules and that all departures are visible in the required form.
Common questions
What else should the bid team know?
Can a bid writer invent a capability claim?
No. Every credential, project example, statistic and promise needs an approved source. Unsupported claims should be left out or added to the open questions list.
Who approves the technical response?
The responsible engineer or technical lead approves technical content. The bid writer controls structure, clarity and response compliance.
Does a response template guarantee compliance?
No. The issued tender, addenda and approval record control the final submission.
Primary sources
- Commonwealth Procurement RulesAustralian Government Department of Finance
- The Construction PlaybookUK Cabinet Office
- Federal Acquisition Regulation Part 15Acquisition.gov