What should the first pass establish?
The first pass controls the pack. Record every file, revision, issue date and addendum before interpreting requirements. Keep client instructions, technical documents, drawings, schedules and response forms as separate document classes.
This matters because request documentation can define the scope, submission format, conditions for participation and evaluation criteria in different places. Australian Commonwealth Procurement Rules paragraph 10.6 lists those categories for covered procurements.
| Document class | Capture | Why |
|---|---|---|
| Instructions | Closing method, time, format | Controls a compliant submission |
| Technical | Specification and scope revisions | Controls priced obligations |
| Drawings | Number, title, revision | Controls quantities and interfaces |
| Returnables | Template and owner | Controls the response plan |
Sources: Australian Government Department of Finance: Additional rules: request documentation
How should requirements become actions?
Split combined clauses into one action per row. Give each row a source, an owner, a response status and an evidence field. Keep a requirement separate from the team's interpretation of it.
If two documents conflict, preserve both references and raise the conflict. Do not silently choose the convenient reading.
- Requirement: what the issued document asks for
- Response: what the bidder proposes
- Evidence: the drawing, schedule or statement that supports the response
- Status: open, drafted, reviewed, qualified or complete
What needs human judgement?
Commercial positions, design assumptions, exclusions and ambiguous boundaries need named human review. A reading service can expose and organise them, but it does not provide legal advice or replace the registered engineer responsible for the job.
| Issue | Typical reviewer | Recorded outcome |
|---|---|---|
| Contract condition | Commercial or legal adviser | Accepted position or departure |
| Design obligation | Responsible engineer | Design basis or clarification |
| Price inclusion | Estimator | Included, excluded or allowance |
| Submission form | Bid manager | Owner and due date |
Common questions
What else should the bid team know?
Should the team start with the drawings or the conditions?
Start with the document index and submission instructions. Then review conditions, scope, specifications, drawings and returnables as linked parts of one pack.
What happens when an addendum arrives?
Register the addendum, identify replaced files, compare affected requirements and reopen any row whose source changed.
Is a tender summary legal advice?
No. A summary organises the issued documents. Contract interpretation and legal advice stay with the appropriate adviser.
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