Your head contractor forwards a "tripartite agreement" with the end client's name at the top and asks you to sign by the end of the week. Or a customer wants your startup to join a three-way services deed alongside the platform you deliver through. However the document arrives, you are facing a tri-party agreement, and the question that matters is what exactly it commits you to.
A tri-party agreement is a single contract that binds three parties at once. It sets out each party's rights and obligations in one place, so the deal does not depend on two separate contracts lining up. It usually does not replace the customer contract, supplier agreement or platform terms you already have. It sits alongside them, and most of the drafting risk comes from how the tri-party agreement lines up with that wider contract ecosystem.
The clauses that carry the deal
No two tri-party agreements look the same, but the clauses below do the real work in almost every one. They are ordered roughly the way you would negotiate them.
Who is signing, and with what authority
This clause fixes the legal identities of the three parties, their roles and the commercial purpose of the arrangement. It should name each party in full, with ACN or ABN and registered address, and say what each one does: customer, head contractor, subcontractor, platform, funder. If a party's role is unclear, every later clause becomes harder to interpret and enforce.
The trap that shows up most often is the wrong entity. A business signs under its trading name, or one director signs when the company's execution rules require more. For a company, s 127 of the Corporations Act 2001 (Cth) sets out how documents are executed without a common seal: two directors, or a director and a company secretary, or, for a proprietary company with a sole director, that director alone where they are also the sole secretary or the company has no secretary. If the signatory lacks authority, the document may not bind the company at all.
- Trap: signing under a trading name, or one director signing when two are required.
- Variant the other side pushes for: each party warrants it has full power and authority to enter the agreement, and that its execution complies with its own rules.
- Drafting minimum: full legal names, ACN or ABN, and the capacity in which each person signs.
What each party must actually do
The scope clause defines what is being provided and what is not, with timeframes, milestones and an acceptance process. In a three-way deal the drafting choice that matters most is who gives instructions and who approves deliverables. If those are left vague, the subcontractor can end up taking direction from the end client while the head contractor claims the deliverables are not what was ordered.
- What is in and what is out: state exclusions explicitly, not just what is included.
- Acceptance and sign-off: who approves deliverables, and what happens if approval is withheld.
- Change control: how scope changes are requested, approved and priced, because three parties guessing at variations is how disputes start.
How the money moves
The payment clause is usually the most sensitive part of a tri-party agreement, because money rarely flows in a straight line. It needs to say who pays whom, what triggers payment, whether payment depends on an upstream approval, and what happens if the end client does not pay. The classic failure is the payment-chain assumption: funds are collected by one party and passed through later, and nobody has written down who carries the risk if the money stops.
If you are at the end of the chain, the options include a direct payment clause, a trust arrangement, or a documented allocation of the risk of non-payment. If the work is construction work, state and territory security of payment legislation may also give statutory rights to progress payments that a contract cannot easily contract out of.
- Triggers: whether payment follows your invoice or an upstream approval such as end-client sign-off.
- Back-to-back risk: if the head contractor only pays when the client pays them, decide in writing who wears the risk of non-payment.
- Late payment and set-off: what interest or remedies apply, and whether disputed amounts can be withheld.
Who wears the risk
The liability clause allocates who pays if deliverables are defective or late. The usual shape is a cap on liability, an indemnity for specific losses, and an insurance requirement. The trap in three-way deals is a one-sided allocation: the biggest party proposes broad indemnities and uncapped liability that shift most of the risk onto the smallest business.
There is a statutory limit on how far that can go. Under s 23 of the Australian Consumer Law (Schedule 2 of the Competition and Consumer Act 2010 (Cth)), a term of a standard form small business contract is void if it is unfair. A contract is a small business contract where at least one party employs fewer than 100 people or has turnover under $10 million, so most startups sit inside the protection. Since penalties can now be imposed for proposing unfair terms, a boilerplate one-sided tri-party agreement carries risk for the party that drafted it, not just the party that signed it.
- Caps: whether the cap applies to all parties equally or only to the smaller ones.
- Indemnities: who covers third-party claims, and whether the indemnity extends to losses the indemnified party caused itself.
- Insurance: public liability, professional indemnity and cyber cover, and who must hold it.
What stays confidential and who guards the data
Confidentiality clauses define what information is protected, how it must be stored, who it can be disclosed to and what happens when the arrangement ends. In a three-way deal the information flows are wider than usual: pricing, code, customer lists and roadmaps move between people who do not otherwise deal with each other.
If personal information is involved, the Privacy Act 1988 (Cth) applies to whoever holds it. Australian Privacy Principle 11 requires an APP entity to take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, modification or disclosure, and to destroy or de-identify it once it is no longer needed. The trap here is overpromising: agreeing in the contract to security standards your systems do not actually meet.
- Scope: what counts as confidential, from pricing to product roadmaps.
- Permitted disclosures: the head contractor, the platform, professional advisers, and anyone else allowed to see it.
- On termination: return or destruction of material, and which confidentiality obligations survive.
Who owns what is built
The IP clause answers three questions: who owns the pre-existing IP each party brings in, who owns new IP created during the project, and who is allowed to use what afterwards. The usual shape is that pre-existing IP stays with its owner under a licence for the project, while new IP ownership is negotiated.
There is a statutory minimum that constrains the drafting. Under s 196(3) of the Copyright Act 1968 (Cth), an assignment of copyright has no effect unless it is in writing and signed by or on behalf of the assignor. An oral agreement, or a clause in a document that is never properly executed, will not transfer copyright. That matters for startups that build software or content for one customer and want to reuse the work elsewhere.
- Pre-existing vs new IP: who brings what in, and who owns what is created.
- Licence scope: exclusive or non-exclusive, for what purpose and how long, and whether use continues after termination.
- The writing requirement: copyright assignments need signed writing to be effective, so the IP clause and the execution of the document need to match.
How the arrangement ends and how disputes are resolved
The termination and dispute clauses plan for the day the relationship stops working. Termination rights can be for convenience or for breach, usually with a cure period. The clause should also say what happens to work in progress and payments already due, and which obligations survive termination, such as confidentiality, IP licences and indemnities.
Dispute resolution usually runs through escalation: negotiation between the parties, then mediation, then court. A tri-party agreement also needs to say which state or territory's law governs and where proceedings can be brought, because three parties may sit in three different jurisdictions.
- Termination triggers: breach, insolvency, convenience, and the notice periods that apply.
- Work in progress: what happens to partially completed work and who pays for it.
- Escalation: the steps before court, and which law governs the agreement.
Optional clauses worth asking for
The clauses above belong in most tri-party agreements. The ones below are situational: include them when the deal triggers them.
- Step-in rights: where a head contractor, funder or customer needs the power to take over performance if a party fails, common in construction and finance arrangements.
- Direct payment and trust clauses: where money passes through an intermediary, so the party at the end of the chain is protected if the intermediary does not pass it on.
- PPSR registration clauses: where goods are supplied on credit, leased or financed. Under the Personal Property Securities Act 2009 (Cth), an unperfected security interest can vest in the grantor on insolvency, and priority between perfected interests generally runs from the time of registration on the Personal Property Securities Register.
- Novation and assignment clauses: where the agreement may need to move to a new party. A novation transfers rights and obligations with everyone's consent and releases the outgoing party; an assignment transfers rights, but obligations stay with the original party unless the others agree.
- Accession or joinder provisions: where a fourth party is expected to join later, so they can be brought in on the existing terms rather than negotiating a fresh document.
How an Artificer Legal lawyer would review your tri-party agreement
When a tri-party agreement crosses our desk, we start with the document and the two-party contracts around it, because the agreement only works if it lines up with the customer contract, supplier terms, platform terms and any employment or contractor arrangements that sit underneath it. We check the entities and execution first, then map the payment chain and stress-test the liability caps and indemnities against the commercial reality of the deal. We look at the IP clause against your plans to reuse what you build, and at the confidentiality and data obligations against the systems you actually run. We also watch for exposure under the unfair contract terms provisions, because a standard form agreement pushed on a small business is exactly where those provisions bite.
The order we negotiate matters. Scope and payment come first, because they decide whether the deal is commercially viable. Liability and IP come next. Boilerplate such as notices and governing law comes last. If you have been asked to sign a tri-party agreement, having a commercial lawyer review the draft before you sign is usually cheaper than litigating the payment or liability clause later.
The payment-flow clause and pay-when-paid risk
When a tri-party arrangement breaks down, the dispute almost always ends up being about money, and the clause that decides it is the payment-flow clause. The question is rarely whether the work was done. It is whether you are entitled to be paid when the party above you in the chain was not paid, or when the end client withholds approval. Agreements that work answer that question in writing. Agreements that fail leave it to what everyone assumed. That is why the drafting choice that makes the difference is allocating the risk of non-payment explicitly, in a clause that matches how the money actually moves, rather than hoping the words "subject to payment" mean the same thing to all three parties.
The rest of the document matters too. A tri-party agreement that names the right entities, defines scope and approval, allocates liability fairly, protects confidential information, deals with IP ownership in signed writing and plans for termination gives each party a predictable set of rights. One that skips those steps simply stores up the dispute for later. If you are drafting or reviewing one, treat the payment flow as the clause to get right first, and check the whole document against the contracts it sits alongside.