Which fields need a source?
Record the client field, response, unit, source, owner, reviewer and status. Use the client's format for issue and an internal working copy for extra controls.
| Field | Record | Check |
|---|---|---|
| Client field | Exact requested item | Preserve heading |
| Response | Approved value or statement | Source |
| Unit | Required unit | Consistent |
| Assumption | Open basis | Approval |
| Status | Draft or accepted | Review trail |
What should happen when data is missing?
Mark the field open and raise a question or internal action. Never copy a value from an unrelated project or generic example.
- Source and revision
- Unit and basis
- Owner
- Reviewer
- Open action
How should the response be checked?
Reconcile schedule values with the narrative, drawings, estimate and supplier returns before issue.
Common questions
What else should the bid team know?
What should a technical schedule response include?
It should contain the client field, approved response, unit, source, assumption, owner and status.
Who reviews a technical schedule response?
The response writer coordinates it and the responsible technical reviewer approves the data.
Can a response template replace the issued tender?
No. The issued request and addenda control the final submission.
Primary sources
- Commonwealth Procurement RulesAustralian Government Department of Finance
- The Construction PlaybookUK Cabinet Office
- Federal Acquisition Regulation Part 15Acquisition.gov