What Is A Change Control Clause In A Contract?

Mia runs a small web development studio in Wellington. She agrees to build a client a new eCommerce site for a fixed fee, with the scope set out in a proposal. Halfway through, the client asks for a loyalty programme, extra payment options and three more rounds of design changes.

Each request feels reasonable on its own. But by the end of the project, Mia's team has worked dozens of extra hours, the launch date has slipped, and the client is surprised when Mia sends an invoice for the extra work.

This is exactly the kind of situation a change control clause is designed to manage. It gives you a clear process for handling changes to the project, so you don't end up absorbing unpaid work just to keep the client happy.

If your business works on projects, retainers, software builds, design work, consulting, implementation or other scoped services, this clause can make a real difference to your cash flow and client relationships.

What Is A Change Control Clause?

A change control clause is a contract clause that sets out how changes to the agreed scope, timeline, fees or deliverables will be requested, assessed, approved and documented.

In plain English, it's the part of your contract that says: if the client wants something different from what we've agreed, here's how we deal with it.

A good change control clause usually covers:

• what counts as a change to the project
• who can request a change
• how the request must be made
• what details the request needs to include
• how you'll assess the impact on price, timing and resources
• whether work starts before or after written approval
• how the change is recorded in the contract

This can be called a change control clause, change request clause, variation clause or project change process. The name matters less than the practical effect: you want a simple, enforceable process that stops project changes from becoming vague promises.

Do You Need A Change Control Clause In New Zealand Contracts?

Yes, you should seriously consider one if your services are based on a defined scope or project plan.

New Zealand contract law generally allows parties to vary a contract if they both agree to the change. The problem is proving exactly what was agreed, especially when changes happen through emails, Slack messages, calls or casual comments in meetings.

Without a clear variation process in your contract, you may run into questions like:

• was the extra work included in the original fixed fee?
• did the client actually approve the extra cost?
• did your team agree to the change by starting the work?
• was the deadline extended because the client changed the scope?
• who is responsible for delays caused by new requirements?

Those questions can be expensive and stressful to sort out later. A change control clause gives you a shared process from day one, so everyone knows how changes will be handled.

For many New Zealand businesses, this clause sits inside a services agreement, master services agreement, software development agreement, implementation agreement or consulting agreement. It can also work alongside a statement of work or proposal.

If you use a template, be careful. Many templates say changes must be agreed in writing, but don't explain what the client must approve, what happens to fees, or whether you're entitled to pause work until the change is signed off. Documents work best when they're tailored to how your business actually delivers projects.

What Should A Change Request Process Include?

A change request process should include enough detail to turn an informal client request into a clear business decision.

You don't need to make it overly formal. For many small businesses, a simple written change request and written approval will be enough. The key is making sure the process is clear and easy to follow.

1. A Clear Definition Of A Change

Your clause should explain what counts as a change. This might include any request that affects:

• the project scope
• the deliverables
• technical requirements
• design requirements
• integrations or third-party tools
• deadlines or milestones
• fees, expenses or payment timing
• your team's workload or resourcing

This helps avoid the classic client response: we thought that was already included.

2. A Written Request

Your contract can require the client to submit change requests in writing. That could be by email, through your project management tool, or through a formal change request form.

The request should usually describe:

• what the client wants changed
• why they want the change
• any preferred deadline
• any related materials, specifications or examples

Under the Contract and Commercial Law Act 2017, electronic communications and electronic signatures can be legally effective in many commercial situations if the legal requirements are met. That means your process can often work by email or e-signing, as long as the contract is set up properly and the parties clearly consent to that method.

3. Your Impact Assessment

Your clause should give you time to assess the request before you're expected to act on it.

Your response might set out:

• the extra fees or revised quote
• any effect on milestones or delivery dates
• any assumptions or exclusions
• whether the change affects other work already underway
• whether third-party costs are involved
• when the change can be scheduled

This is where the clause protects your margin. You're not just saying yes to extra work. You're making sure the client understands what the change will cost and how it affects the project.

4. Written Approval Before Work Starts

Your clause should say whether you need written approval before starting the changed work.

For fixed-fee work, this is usually very important. If your team starts before approval, the client might later argue they didn't agree to pay extra. A clear rule helps your team say, politely and confidently: we can do that, but we need to approve the change and pricing first.

5. A Record Of The Approved Variation

Once approved, the change should become part of the contract. That might happen through:

• a signed variation document
• an approved change request form
• an email trail that clearly confirms the agreed change
• an updated statement of work
• a new quote accepted by the client

The best option depends on the size and risk of the project. A $500 design tweak may not need the same paperwork as a $60,000 software integration.

How Does A Change Control Clause Stop Scope Creep?

A change control clause helps stop scope creep by creating a pause point before extra work is absorbed into the project.

Scope creep usually doesn't happen all at once. It builds up through small comments and requests, such as:

• can you just add one more page?
• can we have another version of the design?
• can the system also connect to this other platform?
• can we push the launch forward even though we changed the brief?

For service businesses, saying yes too often can quietly turn a profitable project into an unprofitable one.

A scope creep contract clause doesn't mean you need to be rigid or difficult. It simply gives you a professional way to respond. For example:

Yes, we can look at that. It's outside the current scope, so we'll send you a change request with the extra cost and timing impact before we start.

That kind of wording keeps the relationship friendly while protecting your business.

It also helps manage your team internally. If your contract says all scope changes need written approval, your staff have a clear rule to follow. They don't have to guess whether a client request is included or worry about upsetting the client by asking for approval.

Can You Charge Extra For Changes After The Contract Is Signed?

Yes, you can charge extra for changes after the contract is signed if the original contract and the agreed variation support that charge.

The starting point is always the contract. If your agreement clearly defines the original scope and states that out-of-scope work is charged separately, you'll be in a much stronger position.

Your pricing approach might be:

• a fixed fee for each approved change
• hourly rates for additional work
• day rates for extra consulting or development time
• a revised project fee
• a separate quote for the new work

If your client is a business, your contract can usually allocate commercial risk in a fairly direct way. If your client is a consumer or a small business customer covered by consumer law protections, you also need to think about the Fair Trading Act 1986 and the Consumer Guarantees Act 1993.

Under the Fair Trading Act, you shouldn't mislead clients about pricing, inclusions or likely costs. If you describe a project as all-inclusive but then try to charge for ordinary parts of the agreed scope, that can create problems.

Under the Consumer Guarantees Act, services supplied to consumers must be carried out with reasonable care and skill, be fit for purpose where the client has relied on your skill and be completed within a reasonable time if no time is agreed. If both parties are in trade, you may be able to contract out of parts of the Consumer Guarantees Act, but only if the legal requirements are met and doing so is fair and reasonable.

The practical point is simple: be clear upfront about what is included, what is excluded and how changes are priced. That clarity is good for compliance and good for the client relationship.

What Documents Work With A Change Control Clause?

A change control clause works best when it sits inside a broader set of project documents that all say the same thing.

For many project-based businesses, that might include:

• Services agreement: your main legal terms, including payment, liability, IP, confidentiality, termination and change control.
• Statement of work: the project-specific document that sets out scope, deliverables, milestones, fees and assumptions.
• Proposal or quote: the commercial offer that the client accepts, ideally linked to your terms.
• Change request form: a short document used to record each proposed change, your pricing and the client's approval.
• Project plan: a timeline or delivery plan that can be updated when approved changes affect timing.

It's also worth checking your intellectual property and confidentiality clauses when the change involves new materials, software, content, branding or data.

For example, if a client asks you to build an extra software module, your agreement should say who owns the code, what licence the client receives, and whether you can reuse general know-how or pre-existing tools. Copyright usually arises automatically in New Zealand, but ownership can be more complex when contractors, employees, clients and third-party materials are involved. Trade marks are a separate issue and are handled through IPONZ if registration is needed.

If a change means you'll handle new personal information, your privacy documents may also need a check. The Privacy Act 2020 requires New Zealand businesses to handle personal information in line with the Information Privacy Principles, including collection, use, storage, access and disclosure rules. A new integration, data migration or analytics feature can change the privacy risk profile of a project.

Common Mistakes To Avoid

The most common mistake is having a change clause that looks fine on paper but doesn't match how your business actually works.

Here are a few traps to watch for:

• Relying on vague wording: A clause that says changes must be agreed between the parties may not tell you enough about approval, fees or timing.
• Starting work before approval: This can make it harder to show the client agreed to pay for the extra work.
• Letting anyone approve changes: Your contract should make clear who has authority to approve changes for the client, especially in larger organisations.
• Forgetting timing impacts: Extra work often affects delivery dates. Your change request should deal with that upfront.
• Not training your team: Your account managers, developers, designers and consultants need to know when to pause and raise a change request.
• Mixing up bug fixes and new features: In software projects, your contract should distinguish between fixing defects in agreed work and building extra functionality.
• Not updating related documents: If the scope changes but the project plan and statement of work stay the same, confusion can creep in later.

Let's go back to Mia's web studio. If her contract says extra features require a written change request, her team can respond to the loyalty programme request by preparing a short variation. It can set out the extra fixed fee, the revised launch date and any assumptions about third-party software. The client can then make an informed decision before Mia commits resources.

That doesn't remove every risk, but it gives both sides a much cleaner path than trying to sort out scope and pricing after the work is done.

Key Takeaways

• A change control clause sets out how project changes are requested, assessed, approved and documented.
• It's especially useful for software, consulting, design, implementation and other scoped services where unpaid scope creep can damage your margin.
• Your contract should define what counts as a change and whether written approval is needed before extra work starts.
• A good variation process should cover fees, timing, assumptions, authority to approve changes and how the approved change becomes part of the contract.
• New Zealand laws like the Fair Trading Act 1986, Consumer Guarantees Act 1993, Contract and Commercial Law Act 2017 and Privacy Act 2020 may affect how your project terms work in practice.
• Your change control process works best when your services agreement, statement of work, quote and project documents all line up.

If you'd like help with your service contracts, change control clauses, statements of work or project variation process, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.