If you’re working with the same customers, suppliers, or contractors again and again, you’ve probably had this thought: “Do we really need to negotiate and sign a whole new contract every time?”
That’s exactly the problem a framework agreement is designed to solve.
This (2026 updated) guide explains what a framework agreement is, when it makes sense to use one in New Zealand, how it’s different from other “umbrella” documents, and what you should include so it actually protects your business (instead of creating confusion later).
What Is A Framework Agreement?
A framework agreement is a contract that sets the ground rules for a business relationship, so the parties can enter into multiple future transactions without renegotiating the same core terms each time.
You can think of it as the “master” deal that covers the recurring legal issues, while the “smaller” deals (like purchase orders, statements of work, bookings, or work orders) fill in the specific details each time.
In practice, a framework agreement usually covers things like:
- How pricing will work (e.g. rate cards, discounts, indexation, or quote process)
- How you’ll place and accept orders
- Payment terms (invoice timing, interest on late payments, set-off, etc.)
- Service standards and deliverables (often by reference to future SOWs)
- Who owns intellectual property created during the relationship
- Confidentiality and data handling
- Liability caps and risk allocation
- How disputes get resolved
- How and when the relationship can end
The goal isn’t to lock you into buying or selling a fixed amount (although sometimes it can). The goal is to make future contracting faster, clearer, and more consistent.
Is A Framework Agreement Legally Binding In NZ?
It can be, but it depends on how it’s drafted and what it says.
Some framework agreements are drafted as a binding contract immediately (so the general terms apply right away, and each future order becomes binding once placed and accepted). Others are more like a “contracting structure” that isn’t intended to create binding obligations until you sign each statement of work or issue a purchase order.
This distinction matters because if your framework agreement is vague about whether it’s binding, you can end up in a frustrating grey area where:
- one party thinks a deal has been locked in, and
- the other party thinks you’re still negotiating.
As a general rule, if you want certainty, your agreement should be clear about:
- what is binding now (e.g. confidentiality, IP, liability, dispute resolution), and
- what becomes binding later (e.g. scope, quantities, delivery dates) and how that happens.
When Does A Framework Agreement Make Sense For Your Business?
A framework agreement can be a great fit when you have repeat transactions, ongoing projects, or rolling work with the same party, but you don’t know all the details upfront.
Common examples we see in NZ businesses include:
- Professional services (consulting, marketing, design, IT support) where work comes in phases
- Software and IT where you’re delivering regular updates, integrations, or support
- Construction and trades where each job has different site conditions and scope
- Supply relationships where customers order the same type of goods on repeat
- Labour and recruitment where placements happen on an as-needed basis
Signs You Might Need One
If any of these sound familiar, it’s usually worth considering a framework agreement:
- You’re constantly reusing the same contract template, but it keeps getting edited inconsistently.
- Each new project starts with “Can you just send your standard terms again?”
- You’re relying on quotes, emails, or purchase orders, and you’re not sure what terms actually apply.
- You’ve had a dispute over scope creep, delays, payment timing, or who owns the work product.
- You want a smoother onboarding process for new customers or suppliers.
Putting the right “umbrella terms” in place early is one of those legal foundation steps that can save you a lot of back-and-forth (and headaches) later.
Framework Agreement vs Master Services Agreement vs Terms Of Trade: What’s The Difference?
A lot of businesses use these terms interchangeably, and that’s where problems start. The labels matter less than the legal effect, but it still helps to understand the typical differences.
Framework Agreement vs Master Services Agreement (MSA)
A Master Services Agreement is usually a type of framework agreement for services. It sets the overall legal terms, and then each piece of work is described in a statement of work (SOW).
In other words:
- Framework agreement is the broader concept.
- MSA is a common “services” flavour of framework agreement.
If your business delivers ongoing services, you’ll often pair a framework agreement with a Master Services Agreement structure where each job is governed by an SOW.
Framework Agreement vs Terms Of Trade / Standard Terms
Terms of trade (or standard terms and conditions) are often used for repeat sales of goods or services. They’re typically drafted as one set of terms you apply across customers, and then each transaction happens via invoice, quote, or order confirmation.
Framework agreements are often more “relationship-based” and negotiated between two parties, whereas terms of trade can be more standardised and rolled out widely.
If you’re selling to many different customers, having strong Terms Of Trade can be the more scalable option. If you’re dealing with one major client (or supplier) repeatedly and you need bespoke negotiated terms, a framework agreement might be the better fit.
Framework Agreement vs Statement Of Work (SOW)
A framework agreement usually sets the legal rules, while a statement of work sets the commercial detail for a specific project.
A typical structure looks like:
- Framework agreement: liability, warranties, confidentiality, IP, payment mechanics, termination, dispute resolution.
- SOW / work order: deliverables, milestones, timing, project-specific assumptions, project-specific fees.
Getting this relationship right is crucial. If your SOW accidentally contradicts the framework agreement (or doesn’t clearly override it), you can end up arguing about which document controls.
Framework Agreement vs Heads Of Agreement
A heads of agreement is usually used when you’re still negotiating the bigger deal and want to document key commercial terms before the final contract is signed.
A framework agreement is usually the opposite: it’s designed to be the ongoing contract you use after the relationship is established.
If you’re still at the “let’s outline the deal first” stage, a Heads Of Agreement might be useful, but you’ll still want the final binding agreement done properly before real work starts.
What Should You Include In A Framework Agreement?
A good framework agreement isn’t just a longer contract. It’s a contract that is built for repeat use, with clear “plug-in points” for future orders or projects.
Below are the clauses we commonly see businesses needing (and the issues they’re designed to prevent).
1. Scope And How Future Work Is Agreed
This is the heart of the framework agreement: how do future jobs become binding?
For example, your agreement might say that work is performed only when:
- the customer signs a statement of work, or
- you accept a purchase order in writing, or
- you issue a written order confirmation.
You’ll also want clear rules for:
- variation requests (including how scope creep is handled),
- change control and approvals, and
- what happens if timelines shift because the customer hasn’t provided required inputs.
2. Pricing, Invoicing, And Payment Terms
Repeat work relationships often fail because of payment friction, not because the parties disagree on the “big picture”.
Your framework agreement can cover:
- whether pricing is fixed, hourly, or milestone-based
- deposit requirements
- invoice timing
- interest on late payments and recovery costs
- what happens if work is paused due to non-payment
If you want maximum clarity for customers (and less chasing), you can also build in process steps like “payment due within X days of invoice” and “disputed invoices must be notified within Y days”.
3. Intellectual Property (IP) And Ownership Of Deliverables
IP is one of the most common “surprise disputes” in ongoing service relationships.
For example, if you’re a developer, designer, engineer, marketer, or consultant, you may be creating valuable work product. You should be clear on:
- what IP the customer already owns (their pre-existing materials)
- what IP you already own (your tools, templates, code libraries, know-how)
- who owns the new deliverables created during the engagement
- what licence (if any) is granted back to the other party
This is also where you address whether you’re allowed to reuse general learnings, and whether the customer can reuse your background tools after the relationship ends.
4. Confidentiality And Data Handling
Even if you’re not a “tech company”, most businesses share sensitive information in an ongoing relationship: pricing, customer lists, product plans, supplier terms, and internal processes.
Your framework agreement should set out confidentiality obligations, and if personal information is involved, you should think about your Privacy Act obligations too. In many cases, businesses will also need a website Privacy Policy (especially if you’re collecting customer information online or through a booking system).
If your relationship involves handling personal information on behalf of the other party (for example, you process bookings, run email campaigns, manage customer support, or provide outsourced admin), you may also need a separate data processing arrangement, depending on the situation.
5. Warranties, Liability, And Risk Allocation
This section is where you set realistic expectations and manage risk.
Common framework agreement points include:
- warranties about services being provided with reasonable care and skill
- exclusions for indirect or consequential loss (where appropriate)
- liability caps (e.g. capped to fees paid in a set period)
- indemnities for things like third-party IP infringement (depending on the deal)
It’s important to get these clauses tailored. A generic limitation of liability clause can cause more problems than it solves if it doesn’t match how you actually deliver goods or services.
6. Term, Termination, And What Happens After It Ends
Ongoing relationships don’t always end dramatically. Sometimes budgets change, priorities shift, or someone just wants to move on.
Your agreement should cover:
- how long the framework agreement runs (fixed term vs ongoing)
- termination for convenience (and any notice period)
- termination for breach (and cure periods)
- what happens to work in progress
- final payments and handover obligations
- return or deletion of confidential information
If you plan to keep certain terms in place after termination (like confidentiality, IP licences, payment obligations, dispute resolution), the agreement should say so clearly.
What Laws In New Zealand Are Relevant To Framework Agreements?
A framework agreement is a private contract, but it doesn’t exist in a vacuum. You still need it to align with New Zealand’s legal rules, and your obligations will depend on what you’re supplying and who you’re dealing with.
Consumer And Fair Trading Rules
If you’re dealing with consumers (not just other businesses), you need to be especially careful around how you describe services, pricing, turnaround times, and performance claims.
Two key laws often relevant here are:
- Fair Trading Act 1986 (misleading or deceptive conduct, false representations, unfair practices)
- Consumer Guarantees Act 1993 (guarantees that services are carried out with reasonable care and skill, among other things, when dealing with consumers)
A framework agreement can help you set consistent service terms and payment rules, but it can’t “contract out” of certain consumer protections in many scenarios. If you sell to both consumers and businesses, you may need different sets of terms depending on the customer type.
Privacy And Confidentiality
If the relationship involves personal information (customer details, employee data, mailing lists, health information, etc.), you need to comply with the Privacy Act 2020. Practically, that means having appropriate collection, storage, access, and disclosure processes in place.
Your framework agreement can allocate responsibility (for example, who responds to privacy requests, who notifies about breaches, and what security standards apply), but you still need to make sure your real-world practices match what the contract says.
Employment And Contractor Considerations
If you’re providing labour or ongoing people-based services, be careful about whether people are genuinely contractors or employees in substance. Misclassification can create real risk (wages, leave, tax, and other obligations).
Where you do engage staff directly, it’s important your internal documents match your client commitments, including having a properly drafted Employment Contract where relevant.
If you outsource parts of delivery to contractors, that’s where you want clear contractor agreements and flow-down obligations, so you don’t promise a client something your subcontractor isn’t actually bound to deliver.
Common Mistakes With Framework Agreements (And How To Avoid Them)
A framework agreement can be incredibly helpful, but only if it’s set up in a way that fits how you actually do business.
The “We’ll Sort The Details Later” Trap
If the agreement is too vague about what’s binding and when, you can end up with disputes about whether there’s a contract at all for a particular job.
Fix: Be clear about the mechanism for forming each new job (SOW, purchase order, order confirmation) and what happens if the documents conflict.
Many businesses use a mix of documents: their own terms, a client’s procurement terms, purchase orders, SOWs, and email threads. If you don’t set priority rules, you may end up in a “battle of the forms” where it’s unclear which terms apply.
Fix: Include a clear order of precedence clause (e.g. SOW overrides the framework agreement for scope and timing; the framework overrides the purchase order; variations must be in writing, etc.).
Not Updating The Agreement As The Relationship Grows
You might start with simple tasks, and then suddenly you’re handling customer data, building core infrastructure, or working across multiple business units.
Fix: Review the agreement periodically, and update schedules like pricing tables, service levels, and data handling requirements as the work evolves.
Relying On Templates That Don’t Match NZ Law Or Your Business Model
It’s tempting to use a free template (or reuse a contract from a past role), but framework agreements are especially prone to “copy/paste” problems because they need to interact cleanly with future SOWs and orders.
Fix: Use the article as a roadmap, but get the agreement drafted or reviewed so it reflects your actual risk profile and processes. If you’re already using broader customer contracts, it may be better to tighten up your standard Service Agreement approach rather than creating something new that doesn’t integrate with your sales workflow.
Key Takeaways
- A framework agreement sets the legal “ground rules” for a relationship so you can enter into multiple future transactions without renegotiating core terms every time.
- Framework agreements are especially useful for repeat work where scope, pricing, or timing may change from project to project.
- To avoid disputes, your agreement should clearly explain how future work becomes binding (for example, through a signed SOW or accepted purchase order) and which document takes priority if terms conflict.
- Strong framework agreements usually cover payment terms, variations, IP ownership, confidentiality, liability, and termination mechanics so you’re protected from day one.
- Your contract needs to align with key NZ legal obligations, including consumer law (Fair Trading Act 1986 and Consumer Guarantees Act 1993 where relevant) and privacy compliance under the Privacy Act 2020.
- Templates can be risky for framework agreements because the details need to match your real-world workflow and the way you’ll manage future orders and statements of work.
If you’d like help drafting or reviewing a framework agreement (or setting up the right contract structure for ongoing work), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
