A freelance development contract should spell out who is hiring whom, what work is being delivered, how payment and approval work, who owns or may use the code, and what happens if the project changes or ends. Use the ten clauses below as a checklist to tailor—not as a universal legal form or a guarantee of enforceability. The cited guidance comes from Australia, Queensland and the UK; get advice under the law that applies to your engagement, especially for ownership, liability, worker status, regulated data or cross-border work.
1. Parties, authority and signatures
Name each contracting person or business accurately, using the legal name and address appropriate to the jurisdiction and entity. If a company is the client, identify the company rather than only the employee who commissioned the work. Confirm that each signatory is authorized to bind the party they represent, and make sure the agreement is signed by all required parties. Australian government contractor guidance calls for party details and signatures, while UK government guidance discusses authorized signatories in its institutional context; neither source establishes a single identification rule for every country.
As an Amazon Associate I earn from qualifying purchases.
Australian Government guidance on preparing a contract; UK government KAM Guide: IP in agreements.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute2. Scope, deliverables and schedule
Describe the expected work or result specifically enough that both sides can tell what completion means. For software work, define the deliverables—such as source code, documentation, deployment or configuration files, and handover materials—as relevant to the project. State what is included and excluded, the formats or environment required, the start date and target dates, and the client inputs or access the developer needs. Where a dependency or client decision can affect timing, say how it affects the schedule.
#1 Best Overall
- 4-page 8.5" x 11" laminated Contract law quick reference guide
- Th law chart takes the reader through all aspects of contract formation and enforcement with clear summaries and effective cross references to areas such as Torts and Criminal Law.
- The most commonly employed American Contract terms are defined in clear reference tables.
- Glossary of terms and corresponding definitions
- Easy-to-read to promoted memory retention. Great learning aid.
A phrase such as “build an app” leaves major questions unanswered. The Australian government guide says a contract should describe the work or result and relevant dates, and contrasts detailed descriptions with generic ones. UK government IP guidance likewise recommends defining scope, contributions, responsibilities and timescales. These are useful drafting principles, not a universal legal test for a valid scope.
Australian Government contract guidance; UK government KAM Guide.
3. Fees, invoices and expenses
Write down how the fee is calculated, the currency, any applicable taxes, what an invoice must contain, when it is due, and which costs the client will reimburse. If the agreement provides for work to pause after non-payment, state the trigger and process. Any late-payment terms should be checked against applicable local law rather than assumed lawful everywhere.
Choose a pricing model that suits how predictable the work is. A fixed fee can make the total price clearer but needs a well-defined scope and payment triggers; hourly or daily billing can accommodate changing requirements but makes the final total less certain. For a fixed-fee engagement, consider whether payment is due on completion or in installments, and define each milestone and its payment trigger. Australian guidance recognizes hourly or daily fees, fixed fees, invoice timing, costs and progress payments; its examples are Australian guidance, not global standards.
| Model | What to state | Main drafting consideration |
|---|---|---|
| Hourly or daily | Rate, how time is recorded, invoice interval, and any agreed limits or approval process | The final amount depends on time worked; make any budget guardrail clear. |
| Fixed fee | Total fee, included work, excluded work, and payment due dates or milestones | Define deliverables and acceptance triggers so that payment timing is understandable. |
| Milestone installments | For each installment, the milestone, amount or proportion, and payment trigger | Connect the trigger to an identifiable event, not an undefined sense of progress. |
Australian Government guidance on fees, invoicing, costs and progress payments.
Rank #2
- Large area for complete description of work proposed
- Includes space for customer to sign his/her acceptance of proposal.
- 1-part form includes carbons to create 2 part forms if necessary.
- Space at top for company stamp.
4. Milestones, testing, acceptance and revisions
Set a review process for each delivery: how the client receives it, how long review takes, how the client reports a problem, and what happens if no response arrives. Define acceptance using project-specific, observable criteria—for example, agreed features working in a named test environment—rather than an unqualified promise that software will be “bug-free.” Distinguish a defect that fails an agreed requirement from a new feature or changed preference.
- Specify the number of included revision rounds and what counts as a revision.
- Set a defect-reporting period, the information a report must include, and the developer’s agreed remedy or retest process.
- For milestone payments, connect acceptance to the milestone criteria and review process stated in the agreement.
Australian government guidance specifically recommends identifying what makes milestone work acceptable and discussing responsibility for defects, the defect period and how faults are reported. The appropriate technical tests and remedies depend on the project and negotiated contract.
Recommended Free Tools
Australian Government guidance on milestones, defects and acceptance.
5. Change control
Give both parties a written way to approve changes to deliverables, dates or fees. Before changed work starts, record what is changing and its expected effect on price and schedule, and obtain agreement from both sides. Identify who may request and approve changes so an informal message from someone without authority does not silently expand the work.
Australian government guidance recommends documenting variations, requiring mutual agreement and explaining the change and its effects. See its contract-preparation guidance.
6. IP ownership, licenses and third-party materials
Receiving a copy of code does not, by itself, answer who owns it or what the client is allowed to do with it. Separate newly created project work—often called foreground or project IP—from the developer’s pre-existing reusable tools, client-provided materials, and third-party or open-source components. Make the intended rights explicit for each category.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →| Approach | What it means for the agreement | Questions to settle |
|---|---|---|
| Assignment | Ownership of the specified rights is transferred, subject to the agreed terms and applicable law. | Which project materials are covered, what formalities are required, and when does the transfer take effect? |
| License | The owner grants permission to use specified material without transferring ownership. | What uses, users, territories, duration, modification or sharing rights are permitted? |
| Developer background tools | Pre-existing reusable tools remain distinct from newly created project IP; the client may need rights to use tools embedded in the deliverable. | Which tools are included, and what continuing license does the client receive? |
| Third-party or open-source material | Its terms are distinct from ownership of the developer’s project work. | What components are included, and what obligations or limits do their licenses impose? |
State whether project work is assigned or licensed, when the rights take effect, the client’s permitted uses, and the developer’s retained rights in reusable tools. Also decide how relevant client-supplied and third-party materials are treated. Australian and Queensland guidance describes creator ownership as a general position subject to exceptions; it should not be generalized into a rule for every jurisdiction or engagement. UK government guidance recommends addressing background and foreground rights, ownership, access, use and duration.
Australian Government guidance on contractor IP; UK government guidance on IP in agreements; Business Queensland guidance on consultant agreements; Business Queensland guidance on IP and contracts.
7. Confidentiality and data handling
Define what information is confidential, how it may be used, who may receive it for the work, and how it must be protected. Include any appropriate exceptions, such as information already public or independently developed, along with the duration of the obligation and the process for returning or deleting protected material at the end of the engagement.
If the project involves personal, regulated or sensitive data, add requirements specific to the data, project and governing jurisdiction; the cited contract guidance does not establish those privacy or security rules. Australian, UK and Queensland sources support defining confidential information and who may receive or use it.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteAustralian Government guidance; UK government KAM Guide; Business Queensland consultant-agreement guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. Warranties, liability, indemnity and insurance
Identify any specific promises about the deliverables, what remedy applies if a promise is breached, and how the parties allocate defined losses or third-party claims. If the contract includes liability limits or exclusions, negotiate their scope rather than relying on a generic cap; no single limit is appropriate for every project, and enforceability depends on the applicable law and circumstances.
Read an indemnity in light of the risks it covers and the matters the developer can control. Check whether the obligations align with available insurance, including any insurance the contract requires. Australian guidance warns that an indemnity can shift loss to a contractor and recommends considering control and insurance; UK guidance recommends clear, proportionate warranties, indemnities and liability terms. Neither supports a universal clause or guaranteed outcome.
Australian Government guidance on indemnity, loss and insurance; UK government guidance on warranties, indemnities and liability.
Free tools Windows power users keep installed
One-click scans. No signup required.
9. Term, termination and handover
Set the contract’s duration and how either party may end it, including any notice period, opportunity to fix a breach, or right to terminate for convenience. Explain what is payable on termination, including completed work and approved costs, and define any agreed transition assistance. Specify how credentials, client materials, code and other work products are handed over, and how continuing licenses and confidential information are treated.
Best Value
UK government guidance recommends addressing IP, materials and access at termination. Australian guidance discusses cancellation costs and remedies for faulty or incomplete work. Payment rights and termination rules depend on the governing law and the contract’s terms.
UK government KAM Guide; Australian Government contract guidance.
10. Governing law, disputes and notices
Name the governing law and the agreed forum for resolving disputes, particularly where the parties are in different countries or regions. Include valid notice methods, the addresses or contacts for formal notices, and an escalation path—for example, named representatives attempting negotiation before any agreed mediation or other process. Make sure the steps and forum fit the engagement and are reviewed under the applicable law; cross-border contracts can involve different legal frameworks.
Australian and UK government guidance discusses dispute processes and governing law or forum, but the cited materials do not establish a single suitable choice for every freelancer. Australian Government guidance; UK government KAM Guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
