Which documents form the review set?
Register the contract conditions, particular conditions, employer's requirements, schedules, forms and amendments. Keep the published form separate from project changes and instructions.
| Document | Purpose | Status |
|---|---|---|
| General conditions | Published contract framework | Licensed source |
| Particular conditions | Project amendments | Issued revision |
| Employer requirements | Technical obligation | Current pack |
| Schedules | Time and commercial data | Completed fields |
| Clarifications | Tender responses | Issued record |
Sources: FIDIC: FIDIC contracts
Which questions should be raised?
Raise questions where scope, design responsibility, notice, programme, payment, testing, acceptance or claims requirements are incomplete or conflicting. The contract instructions control the question channel.
Sources: UK Cabinet Office: The Construction Playbook, FIDIC: FIDIC contracts
What is the boundary of this guide?
It is a document-control method, not legal advice. A qualified contracts or legal adviser must review the actual licensed documents and applicable jurisdiction.
Common questions
What else should the bid team know?
Is this legal advice?
This is document support, not legal advice. A qualified contracts or legal adviser must review the applicable contract and tender position.
Can a register decide whether a clause is fair?
No. It identifies the text, issue, owner and proposed question. A qualified adviser decides the legal or contractual position.
Should the whole contract be sent through the form?
Send a document index and a description of the review needed first. Use a secure, agreed channel for confidential contract files.
Primary sources
- Construction Contracts Act 2004Western Australian Legislation
- NEC4 contractsNEC Contracts
- The Construction PlaybookUK Cabinet Office
- FIDIC contractsFIDIC