Describe concrete deliverables
Broad phrases such as consulting or project preparation may conceal different expectations. List outputs, formats and exclusions. Reports, design files, training and maintenance require different arrangements. Specific work items help identify uncertainty during review.
Separate delivery from acceptance
Sending a file does not necessarily establish agreement on its completeness. Distinguish drafts, interim outputs and final delivery. Discuss review time, the person responsible for feedback and how incomplete work will be identified. The arrangement should reflect the particular project.
Make changes visible
An expanding scope can affect both time and price. Discuss how an included revision will be distinguished from additional work and who can request it. Prepare proposals, meeting records and important messages alongside the contract and flag differences in scope.
Connect payments with ongoing obligations
Map advance, milestone and final payments to the schedule. List expenses, subcontracting, access needs and post-delivery support. Identify expectations about use of the resulting files or content. The Code of Obligations provides a general framework, while the classification and applicable provisions require review of the particular work.
Before your consultation
- Deliverables and excluded work
- Delivery, feedback and payment schedule
- Proposal, contract and change correspondence
Frequently asked questions
Which document should I bring if the proposal and contract differ?
Bring both and the correspondence showing how the terms changed.
Is stating a revision count enough?
The scope of a revision, who requests it and how additional work is distinguished should also be clarified.
General information only; not a substitute for legal advice on a specific matter.