Learning objectives
- Describe deliverables and acceptance in observable terms.
- Identify payment, change and responsibility questions.
- Maintain a reliable record while seeking appropriate legal review.
Identify the parties and the actual work
Confirm the parties’ identities and who has authority to act, using appropriate verification. Describe the deliverables, exclusions, dependencies and inputs each side must supply. “A complete website” leaves room for incompatible expectations. A clear project description separates design, content, hosting, integrations and ongoing maintenance rather than implying that every possible activity is included.
Connect acceptance to payment questions
Ask what evidence will show that a deliverable meets the agreed commercial requirements, who reviews it and what happens if an issue is found. Distinguish a delivery date from an acceptance decision. Clarify the price basis, invoicing events, payment timing and treatment of approved changes. Financial planning should consider when cash is received, not merely the total contract value.
Discuss changes and difficult situations
Projects change when requirements, inputs or external conditions change. Define a route for recording a request, assessing its effect on cost and timing, and obtaining the required approval before extra work begins. Questions about intellectual property, confidentiality, liability, termination and disputes need qualified legal guidance for the actual jurisdiction and transaction; a checklist cannot resolve them automatically.
Keep one agreed version and a practical handover
Use version numbers and a controlled approval record so the team knows which terms are current. Retain authorized changes with the main agreement and assign responsibility for delivery evidence, invoices and notices. Review the commercial brief with the intended legal adviser. International model principles are useful educational references; they are not automatically the governing rules of every agreement.
Four layers of contract preparation
Move from an understandable business brief to qualified legal review; the diagram does not replace legal drafting.
Who and what
Parties, authority, deliverables, exclusions and necessary inputs.
How success is checked
Acceptance evidence, review responsibilities and issue handling.
How work is controlled
Payment events, dependencies and approved change records.
How legal risk is reviewed
Bring jurisdiction-specific questions and the complete brief to a qualified professional.
Comparison
| Vague phrase | Commercial question | Evidence to retain |
|---|---|---|
| Website finished | Which functions, pages and agreed tests define delivery? | Approved scope and test results |
| Payment after completion | Which event triggers the invoice and when is payment due? | Invoice schedule and acceptance record |
| Changes included | Which changes are included and how are others approved? | Dated change request and authorization |
Hypothetical example: a website project
An imagined studio agrees to build a small catalogue website. The customer later asks for online checkout and additional languages.
- Check whether checkout and translation were included in the agreed scope, rather than assuming the word website covers them.
- Record the new request and estimate its effect on work, dependencies, price and delivery dates.
- Obtain the appropriate written approval and update the controlled project record before starting the additional work.
The parties have a clearer basis for discussion. Whether a term is legally valid or a remedy is available still depends on the real agreement and applicable law.
Practical checklist
- Verify identities, authority and the intended transaction.
- Describe deliverables, exclusions and acceptance evidence.
- Clarify payment events and the change process.
- Keep the agreed version and obtain qualified review for legal questions.
Common pitfalls
Copying a template without understanding it
A template may assume a different jurisdiction, transaction or allocation of risk. Unfamiliar wording should become a review question, not a shortcut.
Relying on informal changes that the team cannot trace
Scattered messages can leave delivery staff working from inconsistent instructions. Keep authorized changes with the agreed project record.
Questions and answers
Is a signed document always enough to avoid disputes?
No. Ambiguous scope, missing evidence and inconsistent changes can still cause disagreement. The business process and the legal terms both require attention.
Does this lesson provide a usable legal contract?
No. It provides a commercial preparation framework. Drafting, interpreting or enforcing the actual agreement requires an appropriately qualified professional familiar with the relevant circumstances.
Sources and further reading
- UNIDROIT: international commercial contract principlesUNIDROIT
An official international reference for studying contract concepts, without assuming automatic application to a particular agreement.
- Australian Government: types of contractsAustralian Government — business.gov.au
An introductory comparison of contract forms; local legal requirements must be checked separately.
