Westgate Town Centre Limited (In Liquidation) v Westgate Properties Limited

This appeal came out of a major Auckland development that ran over many years and many documents. The parties were not dealing with a single sale agreement or a simple construction contract. They were trying to build a new town centre through a mix of planning instruments, funding arrangements, works agreements and cost-sharing documents.

The developers were a group of related companies within the New Zealand Retail Property Group. On the other side were Waitakere City Council at first, and later Auckland Council and Auckland Transport after Auckland local government was reorganised.

The project vision was ambitious. The new Westgate Town Centre was meant to sit across Fred Taylor Drive from the original Westgate Shopping Centre. The developers said they worked with the council on an integrated, compact, pedestrian-friendly town centre and changed their own commercial plans to support that model.

Later, they said the public bodies had moved away from that vision. They claimed Fred Taylor Drive was treated as an arterial route, Northside Drive East was not built, Maki Street South upgrades were delayed, and the bus interchange was not delivered where expected. They sued for breach of contract and claimed very substantial losses.

The High Court rejected the claims. The developers appealed to the Court of Appeal on four specific issues. The appeal failed on every ground.

The legal issue was not whether the developers' preferred town-centre outcome was sensible or commercially attractive. The real question was narrower and more practical: what did the contracts actually require?

The Court applied standard New Zealand contract interpretation principles. It said the aim is to identify the meaning the document would convey to a reasonable person with the background knowledge reasonably available to the parties at the time. Context matters, but the text remains central.

The Court also dealt with implied terms. It repeated that implying a term is a high hurdle. If a contract does not provide for an eventuality, the usual inference is that the parties did not make a contractual provision for it. That point becomes even stronger where the alleged obligation is large, expensive or politically significant.

The Court also treated the public-law setting as part of the context. Some outcomes depended on councils and Auckland Transport exercising statutory functions. That did not decide the case by itself, but it helped explain why broad aspirations would not lightly be read as binding commitments unless the contracts said so clearly.

The developers argued that Fred Taylor Drive had to be widened and designed as a town-centre road that integrated Original Westgate with the new centre. They relied on the broader planning vision and on contractual documents including the infrastructure funding agreement and cost sharing arrangements.

The Court rejected that argument. It said the parties had agreed from the outset that their shared vision did not create binding contractual obligations unless more specific agreements later did so. That point was consistent with the memorandum of understanding and with the overall structure of the later contracts.

The Court found that neither the Infrastructure Funding Agreement nor Cost Sharing Agreement 1 imposed an obligation to consult with the developers over the design and construction of the widening of Fred Taylor Drive. It also held that the quality standards relied on in the Demarcation Schedule did not create the binding specifications the developers alleged.

Some of those standards were too general. Some were guidelines. Some were statements of vision. The Court said a reasonable person in the parties' position would not have treated them as contractually binding design standards for a major road project. If standards of that importance were intended to bind, they would be expected to be stated explicitly and with enough precision to be objectively identified.

On the second issue, the developers said there was an implied term requiring Waitakere City, and later its successors, to construct Northside Drive East, including a bridge over State Highway 16. They argued this was needed to make the wider redevelopment work properly.

The Court refused to imply that term. It said there was no contractual commitment to construct Northside Drive East. More than that, the Infrastructure Funding Agreement expressly recognised that there was no such agreement. That made the implication argument especially difficult.

The Court accepted the general idea that contracts may carry an implied obligation not to prevent performance by destroying the circumstances on which performance depends. But it held that this principle did not help the developers here. Construction of Northside Drive East was not necessary to avoid undermining the actual contractual commitments regarding Fred Taylor Drive.

The scale of the alleged obligation also mattered. Funding and constructing a major road and bridge is a significant commercial and public commitment. The Court said that if a commitment of that scale had been intended, it would have been stated expressly. It was not, so it could not be implied.

The third issue was timing. The developers argued that Maki Street South was not upgraded within a reasonable time and that this breached an implied term.

The Court rejected that claim as well. It held that the contractual documents initially left key details to be discussed and agreed by the parties. Once agreement was reached, the work was carried out in a timely manner. On that basis, there was no breach of an implied term to carry out agreed work within a reasonable time.

This part of the judgment is useful for any staged project. Businesses often assume the clock starts running from the moment a broad commitment appears in a framework agreement. But if important design, costing, engineering, access or process matters are still unresolved, proving delay can be much harder.

In practical terms, if you want a real delivery deadline, do not leave the trigger uncertain. Tie the obligation to a date, milestone, approval event or clearly defined condition precedent. Otherwise, one side may later argue that the work only became due once the missing details were settled.

The bus interchange issue is one of the most practical parts of the case. The developers argued that WDA 3 created a binding obligation to situate the bus interchange in Zone 2 of the development. They said the location commitment stood on its own, and that later detail about construction and operation did not qualify it.

The Court disagreed. It examined the wording of WDA 3 closely and said the document showed both areas of agreement and areas still left open. There was agreement about the intended location and about a proposed easement structure in general terms. But there were still unresolved matters involving Auckland Transport, including the terms of the easement, design and specifications, service levels and construction arrangements.

The Court also noted that Auckland Transport was not a party to WDA 3. That mattered because further negotiations were required before Auckland Transport could be subject to any commitment regarding the location. The agreement recorded in WDA 3 reflected the state of affairs at the time, but did not itself impose a meaningful contractual obligation to deliver the interchange there regardless of unresolved matters.

The Court held that the shared understanding about location was subject to final agreement on those further matters. Because those matters remained at large, the arrangement was effectively an agreement to agree and did not create the enforceable obligation the developers alleged.

The Court added that even if some contractual obligation had existed, it did not consider the developers had shown the High Court was wrong to find no breach by Auckland Council or Auckland Transport.

This decision is not just about a large Auckland town-centre project. It has a durable lesson for ordinary businesses that sign heads of agreement, development frameworks, infrastructure arrangements, staged implementation contracts or collaboration documents.

The lesson is that a commercial story and a legal obligation are not the same thing. Parties may genuinely share a vision. They may spend years acting on it. They may even record intended outcomes in plans, schedules or recitals. But if the operative clauses do not clearly impose the obligation, a court may not enforce the outcome one side expected.

The case is especially important where the other side is a council, transport agency or another public body. In that setting, statutory functions, approvals and public spending decisions form part of the contractual context. That means businesses should be careful about assuming that future infrastructure, approvals or public cooperation are locked in unless the contract says so clearly.

For a business owner, the practical response is disciplined drafting. Separate background vision from binding promises. List each critical deliverable. Allocate responsibility for design, funding, procurement and approvals. Use objective standards. Set dates or trigger events. And if further agreement is still needed, say what happens if it never arrives.

If you are negotiating a development or infrastructure deal, use this case as a drafting checklist. The aim is to reduce the gap between the project everyone talks about and the obligations a court will actually enforce later.

These checks are particularly useful where the project depends on public infrastructure, future approvals, third-party cooperation, staged works or later design decisions.