Which controls should be ready?
Illustrative example. Confirm the contract edition, document index, amendments, technical scope, programme assumptions and review owners.
| Control | Evidence |
|---|---|
| Form | Named contract and edition |
| Pack | Index of schedules, drawings and amendments |
| Scope | Technical responsibilities and interfaces |
| Assumptions | Price and programme dependencies |
| Review | Contracts, legal and engineering owners |
What is outside the tool?
It is a preparation aid only. It does not give legal advice or perform engineering sign-off.
This is a document-control guide, not legal advice. A contracts professional and qualified legal adviser must decide the contractual position.
Common questions
What else should the bid team know?
Is this legal advice?
No. It is a document-control checklist only.
Are selections stored?
No. Checklist selections remain in the browser.
Who approves the final position?
The bidder's contracts and legal advisers, with responsible engineering review for technical matters.
Primary sources
- NEC4 contract familiesNEC Contracts
- Plant and Design-Build Contract, Second Edition, 2017FIDIC
- Contract standards and current editionsStandards Australia