Do I Need A Contract For A One-Off Project?

Yes, you should usually have a written contract for a one-off project, even if the job is small, friendly or only expected to take a week.

That doesn't mean you need a 30-page document for every short engagement. But relying on a few emails can leave big gaps around scope, payment, intellectual property and what happens if the client changes their mind.

The more practical way to think about it's this: your contract should match the risk and value of the project. A $900 design job may only need clear written terms of trade and a signed quote. A $15,000 consulting project will usually need a more detailed client agreement or statement of work.

Do I Really Need A Written Contract For A Small Project?

Yes, in most cases you should have something in writing because small projects can still create real business risk.

In New Zealand, a contract doesn't always need to be a formal document signed with wet ink. A contract can be formed through emails, a proposal, an online acceptance process or even conduct, as long as the key terms are clear and both sides have agreed.

The problem is that informal agreements often miss the terms that matter most when things get bumpy. For example, your email might say the project is to design a landing page for $2,500, but not say:

• whether copywriting is included
• how many revision rounds the client gets
• when payment is due
• whether the client owns the editable source files
• what happens if the client pauses the project for two months
• whether you can use the work in your portfolio

Without those terms, you may spend time arguing about what was included instead of getting paid and moving on.

There's also a compliance angle. If your standard terms are used with lots of small clients, the Fair Trading Act 1986 can affect how far you can go with one-sided clauses, especially for standard form consumer contracts and small trade contracts. A small trade contract is generally one where the annual trading relationship is less than $250,000 including GST. Your terms should be clear, fair and not misleading.

Can Emails Be Enough For A One-Off Project?

Emails can be enough if they clearly record the essential deal, but they often aren't enough to protect you properly.

If you're moving fast, a clean email trail is much better than a phone call and a handshake. At a minimum, your email should confirm the parties, the project, the price, timing and acceptance. You want the client to reply with a clear yes, not just keep talking around the edges.

For example, an email saying Thanks, sounds good might help show agreement, but it won't solve every issue. If your quote didn't mention cancellation, late payment or IP ownership, the email won't magically add those protections.

If you're using email only, try to include:

• Scope: exactly what you're delivering, and what's excluded
• Fees: whether the price is fixed, hourly or milestone-based
• Payment timing: deposit amount, invoice dates and due dates
• Revisions: how many rounds are included and what extra changes cost
• Client responsibilities: what the client must provide, and by when
• Ownership: who owns the final work, draft work, templates and source files
• Cancellation: what happens if either side stops the project

A signed proposal with a short set of terms attached is usually safer than a bare email. It still feels simple for the client, but gives you a clearer project contract in New Zealand terms.

What Should A Small Business Project Agreement Include?

A small business project agreement should include the practical terms that stop confusion: scope, payment, timing, changes, IP, confidentiality and cancellation.

You don't need to overcomplicate it. The goal is to write down the rules for this particular job so both sides know what they're saying yes to.

Here's a fill-in outline you can use as a starting point for a one-off project. It isn't a finished legal document, and a legal professional should tailor it before you use it with clients.

1. Parties: write the legal names, NZBNs if relevant, and contact details for your business and the client.
2. Project Description: describe the job in plain English, including the outcome the client is paying for.
3. Deliverables: list each item you'll provide, such as a report, design file, campaign plan or workshop.
4. Out Of Scope Items: say what isn't included, such as extra pages, copywriting, printing, ad spend or implementation.
5. Timeline: include start dates, delivery dates and what happens if the client misses feedback deadlines.
6. Fees And GST: state the price, whether GST applies, deposit amount, milestones and invoice due dates.
7. Changes And Revisions: set out the number of included revision rounds and how extra work is approved and charged.
8. Client Responsibilities: list what the client must supply, such as brand assets, login access, content or approvals.
9. Intellectual Property: explain what transfers to the client, what you keep, and when ownership or licence rights begin.
10. Confidentiality And Privacy: cover confidential information and any personal information handled under the Privacy Act 2020.
11. Cancellation: set out notice, payment for work done, deposits and any agreed cancellation fee.
12. Liability: include sensible limits, while remembering some rights can't always be excluded under New Zealand law.
13. Acceptance: say how the client signs or accepts, including e-signature or written email acceptance.

If you bring in a subcontractor to help deliver the project, your client agreement, and any separate subconsultant agreement, should also say whether you can subcontract and whether you remain responsible for the work. From 2026, the Employment Relations Act 2000 changes also make contractor classification a live issue. If you treat someone as a contractor, your paperwork and the real working arrangement should line up with the contractor gateway test and wider employment law risks.

Who Owns The Work At The End Of The Project?

It depends on the type of work and what your contract says, so you shouldn't assume the client automatically owns everything once they pay.

For consultants, designers, marketers, developers and other service providers, intellectual property is often the most valuable part of the project. New Zealand's Copyright Act 1994 has default ownership rules, including special rules for some commissioned works. Depending on what you create, the client may own certain copyright by default, or you may keep ownership unless you assign it.

Because the default rules can be messy, your contract should say exactly what happens. This is especially important for:

• logos, brand assets and design files
• website copy, templates and strategy documents
• software, code, integrations and databases
• photography, video, music and other creative content
• course materials, training decks and workshop content

A practical clause might say that the client owns the final approved deliverables once all invoices are paid, but you keep ownership of your pre-existing templates, processes, know-how and draft materials. You might give the client a licence to use those background materials only as part of the final deliverable.

Say Mia designs a logo for a Wellington food brand for a fixed project fee of $2,500 plus GST. If her agreement says the client receives the final logo files after payment, but source files cost an extra $400 plus GST, there's less room for confusion. If the client later asks for editable files, Mia can point to the agreed term instead of having an awkward argument.

If the project involves a brand name or logo, remember that copyright ownership is separate from trade mark protection. Registration through IPONZ is a separate process and isn't automatic just because a design project is complete.

What Happens If The Client Cancels Or Keeps Changing The Brief?

Your contract should say what happens, because cancellation and scope changes are where many small projects lose money.

Scope creep usually starts innocently. The client asks for one more version, then another. A stakeholder joins late and wants a different direction. The project sits idle because the client hasn't sent content. If your terms are vague, you can end up doing extra work for free just to keep the relationship comfortable.

For changes, use a simple process:

1. Pause: don't start extra work until the change is confirmed.
2. Price: tell the client the extra fee or hourly rate.
3. Time: explain whether the deadline will move.
4. Approval: get written approval by email before you continue.

For cancellation, your clause should be fair and clear. You might require the client to pay for work completed up to the cancellation date, plus any non-cancellable third-party costs you've already committed to. If you use deposits, avoid calling every deposit non-refundable without thinking it through. Under the Fair Trading Act, Consumer Guarantees Act 1993 and unfair contract terms rules, harsh or unclear terms can create problems, especially if you work with consumers or smaller clients on standard terms.

For example, if you've completed 70% of a $4,000 consulting project and the client cancels, your agreement might let you invoice $2,800 less any amount already paid. If there's no cancellation clause, the client may argue the project wasn't finished, and you may spend more time chasing payment than the invoice is worth.

Should I Use A Statement Of Work Or A Client Agreement?

It depends on whether this is a one-off job or part of an ongoing client relationship.

A client agreement usually sets out the legal terms that apply to the relationship. This might include payment rules, IP, confidentiality, liability, privacy, cancellation and dispute-handling steps.

A statement of work, often called an SOW, usually sets out the project details. This includes the specific deliverables, timeline, fees, assumptions and client responsibilities for one project.

For a short one-off project, you might combine them into one document: a signed proposal with project details at the front and terms of trade at the back. That can work well for jobs that are simple but still need clear rules.

For repeat work, a master client agreement plus separate SOWs is often cleaner. You sign the main terms once, then issue a new SOW each time the client wants another project. That saves you from renegotiating IP, payment and cancellation terms every time.

If you use a statement of work template in New Zealand, check that it isn't only describing the job. Many templates have neat boxes for deliverables and dates, but say very little about what happens when the client doesn't pay, delays approvals or asks for extra work. A template can be a useful starting point, but it works best when it's tailored to your services, pricing model and client risk.

A good test is this: if the project goes sideways, could you show the document to the client and clearly answer who must do what next? If not, the document probably needs more detail.

Key Takeaways

• You should usually have written terms for a one-off project, even if the job is small or the client relationship feels friendly.
• Emails can form a contract, but they often miss key terms like scope, revisions, payment, IP and cancellation.
• A simple signed proposal, client agreement or statement of work can be enough if it clearly covers the risks of the project.
• Be specific about who owns the final work, what you keep, and whether ownership only transfers once the client has paid.
• Use a clear change and cancellation process so you don't end up doing unpaid extra work.
• Templates are helpful starting points, but your terms should be tailored to your services, clients and New Zealand legal obligations.

If you'd like help with your one-off project contracts, statement of work terms, payment clauses or IP ownership arrangements, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.