Practical Completion Date: What to Include in Your Contract for New Zealand Businesses

Alex Solo
byAlex Solo11 min read

A missed completion date can throw a project off course fast. For New Zealand businesses, the problem is often not the date itself, it is the contract wording around it. Founders and managers regularly sign agreements that name a completion date without explaining what counts as complete, what happens if work is only partly finished, or who carries the risk if delays come from variations, weather, supply issues, or customer instructions.

Three common mistakes show up again and again. First, businesses rely on a verbal promise about timing instead of checking the written contract. Second, they treat practical completion and final completion as if they mean the same thing. Third, they forget to set out extensions of time, defect periods, and payment consequences. That is where disputes start, especially before you release the final invoice or hand over the site, fit-out, software, or equipment.

This guide explains what a completion date means in practice, what New Zealand businesses should include in their contracts, and the legal issues to check before you sign.

Overview

A completion date only works if the contract clearly links the date to defined work, testing, handover, defects, and payment. If the wording is vague, each side may have a different view of when the job is finished and whether money is due.

For many SMEs, the safest approach is to define the completion milestone in practical terms and spell out what happens if timing changes. That matters in construction, fit-outs, supply and install projects, software implementation, and other staged work.

  • Define exactly what "completion" or "practical completion" means in the contract.
  • State the completion date, or the method for calculating it.
  • Link completion to deliverables, testing, commissioning, inspections, and handover documents.
  • Set out when extensions of time are allowed and how they must be claimed.
  • Explain what minor defects are acceptable at practical completion and what must be fixed first.
  • Deal with delay damages, price adjustments, retention, or final payment consequences.
  • Record who signs off completion and what evidence proves it.
  • Include a defects liability or remedy period after practical completion.

What Completion Date Means For New Zealand Businesses

A completion date is the agreed point when contracted work must be completed, but the legal value of that date depends on the contract definition around it. In practice, the real question is not just "what day is completion due" but "what must exist on that day for the work to count as complete".

That issue comes up well beyond major building projects. A café fit-out, a refrigeration installation, a website build with custom integrations, a manufacturing line upgrade, or a warehouse security system can all turn on the same question: has the supplier reached the required milestone so the customer must accept handover or make the next payment?

Practical completion versus final completion

Practical completion usually means the work is substantially complete and can be used for its intended purpose, even if minor defects or incomplete items remain. Final completion usually sits later, after defects are corrected and any final contractual requirements are finished.

If your contract uses the phrase practical completion, do not assume everyone shares the same meaning. One party may think a short snag list is acceptable. The other may expect every item, document, and sign-off to be done first.

That is why the contract should state whether practical completion allows minor omissions, and if so, what kind. For example, the agreement might permit non-essential touch-up work but not allow missing compliance certificates, failed testing, unsafe conditions, or anything that prevents ordinary use.

Why the definition matters commercially

The completion date often controls much more than timing. It can affect payment release, possession, risk transfer, insurance responsibility, liquidated damages, retentions, and the start of a defects period.

For example, if you are the customer on a retail fit-out, practical completion may determine when you take occupation and start paying rent under a commercial lease. If you are the supplier installing equipment, completion may determine when the customer must make the balance payment. If the contract is unclear, both sides can be exposed.

This is where founders often get caught. They focus on the price and target delivery date, but not on the mechanics that decide whether the date has actually been met.

What a clear completion clause should cover

A usable completion clause should make the milestone objective, not emotional. It should avoid wording that depends on one side's general satisfaction unless the contract also says what that means.

Most business contracts with a completion date should cover:

  • the scope of work that must be finished
  • any testing, commissioning, training, or acceptance criteria
  • the documents to be handed over, such as manuals, certificates, as-built plans, warranties, or login credentials
  • the standard for minor defects or snag items
  • the process for certifying or confirming completion
  • the consequences if completion is delayed
  • the process for fixing defects after practical completion

That level of detail helps both sides before they spend money on setup, staff scheduling, stock ordering, relocation, or go-live planning based on an assumed handover date.

Before you sign a contract with a completion date, make sure the timing clause works with the rest of the agreement. A good date on page one means very little if the variation, delay, payment, and defect clauses point in different directions.

1. Is the scope precise enough to measure completion?

The contract should describe the work in a way that lets a third party tell whether it is done. If the scope is vague, completion becomes a moving target.

Look closely at plans, specifications, schedules, and assumptions. If an item matters to your business, it should be recorded. Relying on emails, calls, or sales discussions outside the written agreement is risky, especially before you accept the provider's standard terms.

2. Is there a fixed date, or only an estimate?

Some contracts use a hard completion date. Others promise completion within a number of working days after a deposit, access, or delivery of information. Others describe timing as an estimate only.

If the timing is critical, the contract should say that clearly. It should also say what counts as the start date and whether business days, working days, or calendar days apply. Those details often decide whether a delay has actually occurred.

3. What events allow the date to move?

Most projects face changes. The legal question is whether the contract gives a fair and workable process for extending the completion date.

Check whether extensions are allowed for:

  • customer-requested variations
  • late approvals or information from the customer
  • restricted site access
  • supplier shortages or imported item delays
  • weather events, if relevant to the work
  • third party delays, such as council inspections, utility connections, or landlord consent
  • unexpected site conditions or hidden defects in existing infrastructure

The clause should also say how notice must be given. If a supplier loses the right to an extension because it failed to notify within a short timeframe, that should be obvious before you sign.

4. Who decides that practical completion has been reached?

The contract should identify the person or process that confirms completion. Without that, one side may simply declare the work complete and issue an invoice, while the other refuses to accept handover.

Common approaches include certification by an independent contract administrator, written confirmation by the customer, or an agreed inspection process. Whatever method is used, the standard should be objective and documented.

5. What happens to payment at completion?

Payment terms should line up with the completion wording. If the final instalment becomes due at practical completion, the contract should define that term carefully.

Check whether the agreement deals with:

  • deposit and progress payments
  • retention sums or withheld amounts
  • release of the final payment on practical completion
  • separate payment after defects are remedied
  • the right to set off costs for unresolved defects or delay

New Zealand businesses should also think about the practical cashflow impact. If you are the customer, avoid a clause that forces final payment before you receive critical handover items. If you are the supplier, avoid a vague acceptance process that lets the customer stall payment indefinitely.

6. Does the contract deal with delay consequences?

A completion date is much stronger when the contract states what happens if it is missed. That may include liquidated damages, service credits, milestone shifts, termination rights, or a requirement to remedy delay at the supplier's cost.

Liquidated damages need careful drafting. The amount should reflect a genuine pre-estimate of likely loss, not a penalty figure picked to pressure the other side. If the number is unrealistic, the clause may be harder to enforce.

7. Is there a defects period after completion?

Practical completion usually should not mean the end of all supplier responsibility. A defects liability or remedy period gives a structured window for fixing minor defects that appear after handover.

The contract should state:

  • how long the defects period lasts
  • how defects must be reported
  • how quickly they must be fixed
  • what happens if the supplier does not return
  • whether any retention or security remains in place until the defects period ends

That protects the customer from being left with unresolved snag items and protects the supplier from open-ended obligations.

8. Do other documents create conflicting dates?

It is common to see a proposal, purchase order, scope document, and main contract all refer to timing differently. If those documents are inconsistent, a dispute can start before the work even begins.

Make sure the agreement has an order of precedence clause or another method for resolving conflicting terms. This matters before you rely on a verbal promise that the supplier says will be "captured later".

Common Mistakes With Completion Date

The biggest mistake is treating a completion date as a simple diary entry. In reality, it is a legal trigger that can affect payment, risk, access, defects, and liability.

Using the date without defining completion

Many contracts state a completion date but never say what completion means. That leaves too much room for argument. A supplier may say the work is substantially finished. A customer may say the job is unusable because training, testing, or certificates are missing.

A better clause defines the milestone in business terms. If your team cannot use the site, system, or equipment for its intended purpose, practical completion may not have been reached.

Confusing minor defects with unfinished work

Minor defects can often be fixed after practical completion. Major omissions usually cannot. The problem is that many contracts never draw the line.

For example, a paint touch-up might be a minor defect. Missing fire compliance documentation for a premises fit-out probably is not. A small cosmetic panel issue on installed equipment may be minor. Failed performance testing on the equipment probably is not.

The contract should say that practical completion is not achieved where outstanding items prevent safe use, legal compliance, or ordinary business operation.

Failing to document extensions of time

Delays often happen because the customer changes the scope, gives late instructions, or cannot provide site access. If those events are not documented under the contract process, the supplier may struggle to justify a later completion date.

On the other side, customers often accept informal delay explanations without asking for formal notices and revised programmes. That can weaken their position later if they need to enforce delay rights.

Linking final payment to vague customer satisfaction

A contract that says payment is due when work is completed "to the customer's satisfaction" invites disputes. Satisfaction is subjective unless the agreement sets objective standards.

A more practical approach is to link payment to measurable criteria, such as installed items matching the scope, required testing being passed, and specified documents being delivered.

Ignoring downstream business commitments

Founders often sign supplier contracts without checking the promises they have already made elsewhere. A delayed completion date can affect lease obligations, customer delivery commitments, staffing, and stock timing.

If your business plans depend on completion, the contract should reflect that. You may need stronger delay rights, milestone reporting, or the ability to terminate if the project slips beyond a specified point.

Assuming standard terms are balanced

Standard terms often favour the party that drafted them. A supplier's standard contract may give broad rights to extend time, narrow customer remedies, or allow automatic sign-off. A customer's template may set unrealistic completion obligations and broad liability clauses.

Before you sign, check whether the timing clauses are commercially workable for the project you are actually doing, not just legally familiar boilerplate.

Relying on practical completion without a handover process

Even if the work is done, disputes can continue if handover is messy. Keys, passwords, manuals, warranties, compliance records, training notes, spare parts, and maintenance instructions should all be addressed in the contract where relevant.

That is especially important for SMEs that do not have a large internal project team. If handover is not organised, valuable time gets lost after the stated completion date while each side argues about missing items.

FAQs

Is a completion date legally binding in New Zealand?

Usually yes, if the contract clearly states the date or a method for calculating it and the agreement is otherwise valid. The real issue is how the contract defines completion and what remedies apply if the date is missed.

What is the difference between practical completion and final completion?

Practical completion usually means the work is substantially complete and fit for its intended use, with only minor defects left to fix. Final completion usually happens later, after those defects and any remaining contractual requirements are dealt with.

Can a completion date be extended?

Often yes, but only if the contract allows for extensions of time and the required notice process is followed. Variations, delayed customer instructions, site access issues, and third party delays are common triggers.

Should final payment be tied to the completion date?

It can be, but the contract should tie payment to an objective completion milestone, not a vague feeling that the job seems done. If key documents, testing, or defects are still outstanding, the payment trigger should reflect that.

What if the contract does not define practical completion?

That creates room for dispute. If the term is not defined, each side may rely on different expectations about what counts as complete, so it is better to add a clear definition before you sign.

Key Takeaways

  • A completion date is only useful if the contract clearly explains what counts as completion.
  • Practical completion and final completion are not the same thing, and the contract should define both if both matter.
  • Before you sign, check the scope, timing trigger, extension rights, sign-off process, payment consequences, and defects period.
  • Objective acceptance criteria reduce disputes about whether work is truly complete.
  • Delay clauses should be realistic, documented, and aligned with the rest of the agreement.
  • Do not rely on verbal assurances about timing, handover, or minor defects if the contract says something different.
  • Clear contract drafting matters most before you spend money on setup, commit to your own customers, or release final payment.

If you want help with contract drafting, delay clauses, payment milestones, or practical completion definitions, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.