Which questions should the review answer?
Use the issued opportunity information and a short evidence register. Separate facts in the request from internal judgements about fit, capacity, risk and approval.
| Area | Question | Evidence |
|---|---|---|
| Opportunity | Is the request current and complete? | Invitation and addenda |
| Scope | Can the team define the battery limits? | Scope documents |
| Submission | Can every mandatory returnable be supplied? | Returnables list |
| Risk | Which positions need approval? | Issue register |
How should a decision be recorded?
Record the decision date, decision owner, assumptions, open questions and conditions. If the team proceeds, turn each condition into a bid action with an owner and due date.
- Current opportunity and closing date
- Known technical and commercial boundaries
- Required approvals
- Evidence available and missing
- Decision and conditions
What should happen after a go decision?
Create the document index, returnables register, scope map and review calendar. The go decision starts control work. It is not a compliance finding.
Common questions
What else should the bid team know?
What should a go or no-go review record?
It should record the opportunity identity, close date, scope basis, submission obligations, fit questions, risks, evidence and decision conditions.
Who reviews a go or no-go review?
The bid lead owns the decision, with technical, estimating and commercial reviewers contributing to the rows in their area.
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