Who Owns IP When Architects Use Contractors?

Who actually owns the drawings, concepts and project files when your architecture practice uses a freelance designer?

The reassuring answer is that you can usually control this with the right written agreement. The less reassuring part is that if you leave it to assumptions, ownership can become messy very quickly.

Architectural work often moves through sketches, CAD files, BIM models, renders, specifications, consultant markups and client presentations. If several people contribute to those materials, you need a clear paper trail showing what your practice owns, what the contractor can keep using, and what your client is allowed to do with the final design.

This doesn't have to be complicated. You just need your contractor agreement and your client-facing architecture services agreement to work together.

Who Owns Architectural Drawings In NZ?

In New Zealand, copyright in architectural drawings usually sits with the person who owns the copyright under the Copyright Act 1994, and the answer depends on how the work was created and what your contract says.

Architectural drawings, plans, sketches, renders and models can be protected as artistic works. Copyright can also protect written specifications, reports and some digital files. Copyright arises automatically when the work is created - you don't register copyright with IPONZ in New Zealand.

Copyright doesn't protect every idea in a project. It protects the particular expression of the idea. For example:

• A broad concept like a light-filled coastal bach with indoor-outdoor flow isn't owned in the same way as a finished drawing.
• A specific floor plan, elevation, render or detail drawing may be protected if it's original.
• A CAD block, Revit family, template, design detail or specification may also involve copyright or confidential know-how.

For artistic works, including many drawings, diagrams, plans and models, New Zealand copyright law has special rules for commissioned works. If your practice commissions a contractor to create drawings or plans and agrees to pay for them, your practice may be the first owner of copyright unless your agreement says something different.

That sounds helpful, and it often is. But you still shouldn't rely on the default rule alone. It may not cover every file, every contribution, pre-existing templates, third-party materials, work done before payment terms were agreed, or contractors based overseas. A written agreement gives you a much cleaner answer.

What Happens When Your Architect Contractor Creates The Work?

If your contractor creates drawings or project files for your practice, you should spell out whether your practice owns the IP or receives a licence to use it.

For most architecture practices, the cleanest position is:

• Your practice owns the project-specific drawings, plans, renders, specifications and deliverables the contractor creates for your projects.
• The contractor keeps ownership of their pre-existing tools, templates, standard details and know-how.
• Your practice gets a broad copyright licence to use any contractor-owned background materials that are embedded in the project deliverables.
• The contractor can't reuse project-specific materials for another client or competitor without your written consent.

Say you run Kauri Studio, a small architecture practice in Wellington. You engage Mia, a freelance designer, to help prepare concept drawings and presentation renders for a townhouse project. Mia uses her own rendering presets and some standard joinery details she has developed over time.

You probably want Kauri Studio to own the townhouse-specific drawings and renders, because those are being prepared for your client and your project. But Mia may reasonably want to keep using her general rendering workflow and standard details for future jobs. Your contractor agreement for architecture work should separate those two things clearly.

Project IP Versus Background IP

A practical contractor agreement for an architecture practice should distinguish between:

• Project IP: materials created specifically for your project, such as drawings, concepts, plans, models, documentation, schedules, reports, renders and markups.
• Background IP: materials the contractor already had or uses across multiple jobs, such as templates, design libraries, standard details, software workflows, fonts, textures and know-how.
• Third-party materials: anything the contractor sources from someone else, such as stock images, product data, manufacturer drawings, software assets or consultant files.

If you don't define these categories, you may find yourself arguing later about whether a detail is project-specific or part of the contractor's general toolkit.

Do You Need A Contractor Agreement For Architecture Work?

Yes, you should use a contractor agreement whenever a freelance designer, draftsperson, visualiser or design consultant creates work for your practice.

A handshake arrangement can feel fine when the project is small or the contractor is someone you trust. The issue is that IP problems often show up later - when a client wants native files, a contractor posts unpublished designs online, or you need to reuse a drawing set for variations.

Your contractor agreement should cover more than payment and deadlines. For IP ownership, include clauses dealing with:

• Assignment of copyright: a clear transfer of project IP to your practice, where that's the commercial deal.
• Licence to background IP: a broad, ongoing licence for your practice to use embedded templates, details or methods as part of the project.
• Native files: whether CAD, BIM, Revit, SketchUp, Rhino, Adobe or other source files must be delivered, and in what format.
• Client use: confirmation that your practice can grant the client the licence promised in your client agreement.
• Confidentiality: protection for client briefs, budgets, site information, unpublished designs and business information.
• Portfolio use: whether the contractor can show the work publicly, privately, after completion, or only with approval.
• Moral rights: how attribution, changes to work and waivers are handled.
• Warranties: promises that the contractor's work is original and doesn't infringe someone else's IP.
• Subcontracting: whether the contractor can bring in others, whether a subcontractor agreement is needed, and who owns work created by those people.

Templates can miss architecture-specific details, especially around native files, council submissions, consultant coordination and client licences. Your agreement works best when it reflects how your studio actually delivers projects.

Check The Contractor Relationship Is Genuine

Your IP clause is only part of the picture. You also need to be comfortable that the person is genuinely a contractor and not, in reality, an employee.

Under the Employment Relations Act 2000, the real nature of the working relationship matters. Recent 2026 changes introduced a contractor gateway test designed to give more certainty where the written agreement and the real working arrangement point to an independent contracting relationship.

In practical terms, you should look at things like:

• whether there's a written agreement saying the person is an independent contractor;
• whether they can work for other clients, including other design businesses where appropriate;
• whether they control how and when they do the work, rather than being managed like staff;
• whether they can reject work or negotiate scope;
• whether they provide their own tools, software or equipment where that fits the role;
• whether the arrangement reflects a contractor relationship in practice, not just on paper.

If someone is really working like an employee, you may need to think about employment agreements, leave and holiday obligations under the Holidays Act 2003, and how employee-created IP is handled. That can affect more than IP ownership, so it's worth getting tailored advice before the arrangement becomes business as usual.

How Should Your Client Licence Work In An Architecture Services Agreement?

Your client should receive a clear licence to use the project deliverables, but that doesn't always mean they should own all of your IP.

Many architecture practices prefer to retain ownership of their drawings, design methods, standard details and documentation, while giving the client permission to use the deliverables for the agreed project. This protects your practice while still giving the client what they need.

A well-drafted client licence might say the client can use the drawings and documents:

• for the specific project described in the services agreement;
• for the specific site or property;
• for building consent, pricing, construction and maintenance of that project;
• once your invoices for the relevant stage have been paid;
• subject to any limits around changes, reuse and sharing with third parties.

The licence should also say what the client can't do without your consent. For example, you may want to stop the client from:

• using your concept on a different site;
• handing your drawings to another designer to copy for a new project;
• removing your practice name or attribution from drawings where appropriate;
• modifying technical drawings in a way that creates safety, compliance or quality risks;
• using unpaid work if the project ends before payment is made.

This is where your contractor agreement and client agreement, including any copyright licence terms, need to line up. If your client agreement promises that the client owns all deliverables outright, but your contractor agreement only gives your practice a narrow licence, you may not have enough rights to pass on what you promised.

What About Council, Engineers And Builders?

Your client licence should allow sensible project use. That usually includes sharing documents with the local council, engineers, quantity surveyors, builders and other consultants involved in the project.

You don't want an IP clause that's so tight it slows the project down. The aim is to allow normal project delivery, while stopping reuse outside the agreed project.

Can Contractors Use Your Projects In Their Portfolio?

Yes, contractors can use project work in their portfolio if you allow it, but you should set clear limits.

Portfolio use is common in architecture and design. Contractors often want to show selected drawings, renders or finished project photos to win future work. That may be fine once a project is public, but it can be risky if the work is confidential, not approved by the client, or still in concept stage.

Your contractor agreement can deal with portfolio use by setting rules such as:

• the contractor needs your written approval before publishing any project material;
• unbuilt concepts, client briefs, budgets and site details must stay confidential;
• portfolio use is allowed only after the project is publicly released or completed;
• the contractor must credit your practice in an approved way;
• the contractor can't imply they were the lead architect or had a bigger role than they did;
• the contractor must remove material if your client reasonably objects.

You should also think about the Fair Trading Act 1986. If a contractor's portfolio gives a misleading impression about who designed the project, who led the work or what role they played, that can create commercial and reputational problems.

Privacy and confidentiality can also matter, especially for residential projects, sensitive commercial sites or clients who don't want their premises publicised. If project photos or plans include personal information, the Privacy Act 2020 may be relevant too.

What Are Moral Rights In Architectural Projects?

Moral rights are personal rights held by creators, and they can still matter even where your practice owns the copyright.

Under the Copyright Act 1994, moral rights can include:

• the right to be identified as the author of a work, in some situations;
• the right to object to derogatory treatment of a work;
• the right not to have a work falsely attributed to someone.

Moral rights are different from copyright ownership. They generally can't be assigned in the same way as copyright, but they can often be waived in writing.

For architecture practices, moral rights clauses are useful because project work is often edited by different people. A contractor may create an early concept, your internal team may develop it, an engineer may require changes, and the client may later ask for revisions.

Your contractor agreement can say the contractor:

• consents to reasonable edits, adaptations and development of their work for the project;
• waives moral rights where appropriate and legally effective;
• won't object to changes needed for buildability, compliance, budget or client requirements;
• won't claim authorship of the whole project where they only contributed to part of it;
• will follow your approved attribution and portfolio rules.

This doesn't mean treating contributors unfairly. It simply means your practice can manage the project without needing fresh approvals every time drawings are revised.

Common Drafting Mistakes To Avoid

The biggest mistake is assuming everyone has the same view of ownership. In architecture projects, that assumption often breaks down once files become valuable or a project changes direction.

Watch out for these common gaps:

• No written IP assignment: even if the default law helps you, a written assignment makes ownership much easier to prove.
• No treatment of native files: PDFs aren't the same as editable CAD, BIM or source files.
• No background IP licence: if a contractor uses their own templates or details, your practice needs permission to keep using them in the project.
• Overpromising to clients: don't promise the client full ownership unless you're sure you have the rights to give it.
• No portfolio rules: contractors may post work online before the client has approved it.
• No confidentiality clause: drawings can reveal private site, budget, security or business information.
• No subcontractor controls: if your contractor outsources rendering or drafting, you may need a subcontractor agreement and IP rights from that person too.
• Ignoring overseas contributors: copyright rules and enforcement can differ if your freelancer is outside New Zealand.

A simple way to tighten this up is to map the project workflow. Ask yourself who creates each type of material, who needs to use it, who can edit it, who can publish it, and what happens when the engagement ends.

Key Takeaways

• Architectural drawings, plans, renders and models can be protected by copyright under the Copyright Act 1994.
• New Zealand's commissioned works rules may help your practice, but a clear written contractor agreement is still the safest approach.
• Your contractor agreement should cover project IP, background IP, native files, moral rights, confidentiality and portfolio use.
• Your client agreement should grant a practical project licence without giving away more IP than you intend.
• Check that your contractor arrangement is genuine, especially with the 2026 contractor gateway test and employee classification rules in mind.
• Portfolio use can be allowed, but only with clear approval, attribution, confidentiality and client consent settings.

If you'd like help with your contractor agreements, architecture services terms, client licences or IP ownership clauses, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.