Which fields should each question contain?
Write enough context for the recipient to answer without guessing. Preserve the issued document number, revision and section.
| Field | Purpose | Closure |
|---|---|---|
| Source | Trace the question | Document and section |
| Question | Ask one answerable point | Issued wording |
| Impact | Show bid effect | Scope or price action |
| Response | Record the answer | Buyer correspondence |
| Action | Update the bid | Owner and status |
How should questions be prioritised?
Prioritise questions that can change design, price, programme, compliance or the ability to submit. Keep lower-risk wording questions visible without letting them obscure material issues.
- Material scope ambiguity
- Conflicting technical sources
- Missing returnable
- Commercial qualification
- Submission process issue
When is a question closed?
Close it only when the formal response is recorded and the affected bid rows have been reviewed. A received answer with no downstream action is not full closure.
Common questions
What else should the bid team know?
What should a tender question log record?
It should record source, question, owner, approval, issue date, response, effect and downstream action.
Who reviews a tender question log?
The bid team controls the log, while the relevant engineer, estimator or commercial reviewer approves the effect.
Can this page replace the tender instructions?
No. The issued tender, its addenda and the responsible technical, commercial or legal reviewers control the final position.
Primary sources
- Commonwealth Procurement RulesAustralian Government Department of Finance
- Additional rules: request documentationAustralian Government Department of Finance
- The Construction PlaybookUK Cabinet Office
- FAR Part 15: Contracting by NegotiationAcquisition.gov