Agreement · Technology, Media & Telecommunications / IT Contracts
Software source code escrow agreement (three-party: supplier, customer and escrow agent)
A three-party escrow agreement for business-critical software: deposit materials and update cycle, verification, release events that do not rely on insolvency alone, the release procedure and dispute window, the customer’s licence on release, fees and termination.
- Kind
- Agreement. A contract between two or more parties.
- Where it applies
- Australia
- AI use
- Yellow AI can help in set ways. A lawyer checks specific points before use.
- Law stated as at
- 18 October 2026
- Status
- Maintained. Checked on 18 October 2026 against the 2 authorities it cites, for Australia.
- Version
- 1
- Source
- Written for this library
When to use it
Use when a customer depends on licensed or hosted software it cannot easily replace and wants access to source code, build instructions and data if the supplier stops supporting it. Escrow agents often have their own standard form; use this to prepare the customer’s mark-up or where the parties appoint a firm or trustee as agent.
How AI may be used
AI may draft the agreement from the agreed release triggers and deposit list and compare an agent’s standard form with it, but a lawyer settles the release events, the licence on release and the insolvency analysis.
AI may
- Fill the parties, software, deposit list, update frequency and fees into the approved agreement from the term sheet
- Compare an escrow agent’s standard terms with this agreement and list the differences in release events, verification and liability
- Prepare a diary of deposit and verification dates for the customer’s contract manager
AI must not
- Must not choose or change the release events, or advise whether a release trigger will survive the supplier’s insolvency
- Must not receive or process the deposited source code itself
- Must not certify that a deposit is complete or verified
The lawyer checks
- Release events include operational triggers (failure to support or fix within set times, ceasing to supply) and do not depend only on administration or financial position, which s 451E may stay
- The licence on release is wide enough to maintain, modify and have third parties support the software, and binds successors of the supplier
- Deposit materials cover everything needed to build and run the software, including build scripts, third-party components, configuration and, for hosted software, data and infrastructure details
- The agreement fits the main licence or SaaS agreement, including termination and dispute clauses
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is for signed-in accounts. It is free. When you sign in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- SaaS / cloud services agreement (Australian law, business customers)
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area