Skip to main content
Apollo NZ Global

Built Intelligence · Public Realm & Development · Developer projects

Pergolas for Townhouse Developments: How to Standardise Outdoor Living Across Multiple Homes

For townhouse developers, outdoor roof systems are most successful when they are treated as a planned package rather than a last-minute accessory. Ten separate purchases can produce ten different finishes, gutter positions and handover issues. A coordinated specification can instead make patios more consistent, reduce procurement uncertainty and simplify the construction programme.

Apollo NZ Global EditorialPublished 2026-11-19Project intelligence
Final product selection, technical documentation and local approval requirements are assessed for each project.
ORZENZA townhouse pergola application image from Apollo developer supply page

Existing Apollo developer townhouse illustration; indicative, not a completed customer project.

01

Project context

Standardisation does not mean placing the same kit in every backyard regardless of conditions. Corner properties, boundaries, exposure, drainage, orientation and foundation design may differ. The goal is a controlled range of repeatable options, with transparent rules for the units that need special treatment.

02

Start at the masterplan, not the product catalogue

Mark every outdoor area at concept design stage. Identify usable dimensions, orientation, neighbours, privacy lines, doors, paths, building services, boundary setbacks and opportunities for shared drainage. Then group the plots into a small number of recurring types. A development might use compact, medium and full-width patio layouts rather than treating every site as unique.

The schedule should show which homes receive which system and which spaces remain unsuitable or need a different solution. The distinction matters for pricing, marketing, programme coordination and the building consent strategy. A roof fitted after landscaping and services have been completed can create expensive rework.

03

Write one measurable specification for each type

Each pergola type needs a dimensioned footprint, finished height, proposed support line, drainage route, finish schedule, roof operation and any associated blinds or lighting. The product's nominal size is not enough: internal post clearances, overhangs and movement envelopes should be considered against actual patio use.

The schedule should also identify whether the design is freestanding or attaches to the building. Fixing into a waterproofed façade or deck is not a casual adjustment. If a unit's construction differs from the standard detail, the project team should record the deviation and approve a specific interface rather than improvising on site.

04

Standardise colours and visible quality

A mixed set of pergola finishes can make a development look fragmented. Choose a restrained palette that coordinates with cladding, window joinery, fencing and landscape materials. Define the finish in the purchase schedule, including gloss or texture where relevant. A colour name alone may not identify the same coating across different suppliers.

Also decide how roof blades should look when closed, how drainage components are positioned and how any side treatments line up. Architectural consistency comes from controlled visual details, not solely from identical lengths and widths.

ORZENZA shared residential courtyard louvre system application image
Existing Apollo shared-courtyard application illustration; layouts and inclusion require confirmation.
05

Avoid the 'one size fits all' structural mistake

Repeated homes still occupy different micro-sites. A corner townhouse may experience different wind exposure from an enclosed courtyard, and a boundary-adjacent structure can have different legal constraints. Foundations and connections should be assessed for the specific ground and building conditions.

A standard product may be replicated only within its verified installation and design conditions. If the developer intends to use different spans, coastal sites or complex attachments, the proposed system and engineer must be informed early. No catalogue dimension overrides a required project-specific check.

06

Choose the right operational level

Manual louvres may suit some compact outdoor areas where simplicity is preferred. Motorised louvres and retractable roofs create different user experiences and require controls, electrical supply and maintenance provision. A fixed insulated roof serves yet another purpose. Do not specify an operating feature by appearance alone.

For the entire development, consider whether residents need different settings or whether a consistent standard package is more sensible. Lighting, wind and rain sensors or side blinds should be allowed for only when supported by the exact product model, structural design and site wiring plan.

07

Build a quantity and stage schedule

Record unit number, pergola type, quantity, selected finish, accessories, drawing revision, delivery stage and any exception. This is the starting document for both supplier and builder. It helps prevent the wrong product arriving at the wrong property and keeps variations visible before they cause delays.

Delivery should match the site's storage and construction sequence. Supplied frames may require a secure level storage area, careful handling and protection from construction traffic. A bulk order might lower order-processing complexity, but freight, crane needs and last-mile distribution must still be defined.

08

Split supply and local works explicitly

Apollo supplies products on a wholesale supply-only basis. The construction team remains responsible for local site measurement, approvals, foundations, installation, electrical work and waterproofing interfaces unless another contractual party has been appointed. Do not allow the supply quotation to be mistaken for an installed project price.

Ask each contractor to identify its interface: who measures as-built slabs, who signs off roof fixing, who connects downpipes, who operates and tests motors and who hands over owner instructions. A responsibility matrix is especially valuable when multiple subcontractors work across dozens of units.

09

Detail maintenance and homeowner handover

Resident handover should include operating instructions, maintenance requirements, finish-care guidance, safety restrictions, installer documents and genuine warranty terms applicable to the supplied model. If a system has a weather-operating limitation, explain it plainly. Do not pass on a marketing brochure as a complete owner's manual.

Consider access to gutter cleaning and replacement parts, especially in narrow courtyards. The visible roof may be a modest capital item in a project, but poor maintenance access can create disproportionate long-term complaints.

10

Compare tender returns on the same basis

Give bidders the same unit schedule, drawings, product or performance requirements, finish requirements and stage programme. Ask for pricing per type, quantities, freight assumptions, exclusions, lead time and technical evidence. Make exceptions visible rather than hiding them in broad 'subject to site check' language.

A development should compare the installed outcome, even when procurement is supply-only. The supplier's price should be combined internally with local foundations, structural design, electrical works, consent, drainage and installation before a decision is made.

11

Frequently asked questions

Can the same pergola kit be used at every townhouse? Only where the exact model and site conditions are compatible and the project's structural and regulatory checks support that repeat application.

Is a bulk order always cheaper? It can reduce some procurement complexity, but pricing depends on specification, quantity, freight, staging and exclusions.

Can blinds be added later? Only if compatible with the original system and its structural, electrical and clear-opening requirements.

What should the first enquiry contain? A unit schedule, site region, sample drawings, quantity bands, finishes, expected delivery programme and a list of the local works that will be managed separately.

12

A three-tier pergola schedule can control variation

Instead of specifying a separate pergola for every unit, developers can identify a base type, a larger optional type and a limited special-case design. Each tier should define the nominal footprint, actual clearance, roof operation, finish, drainage direction and supported accessories. Unit numbers can then be assigned to one of those types in a single schedule. The exception register should capture site exposure, service conflicts, boundary conditions and alternate fixing details that need engineer or supplier confirmation. This gives builders fewer product combinations while preserving the discretion needed for non-standard lots. A clean schedule also makes buyer upgrade requests easier to price and administer.

13

Align pergolas with property marketing promises

The construction documents, sales renderings and homeowner specifications should tell the same story. If a townhouse is advertised with covered outdoor dining, verify that the actual structure, furniture clearances and weather function match the representation. An illustration of a glass-enclosed terrace must not imply glazing is included when the supplied package contains only a basic louvre roof. Marketing teams should use reviewed product configurations and accurately distinguish upgrade options. Consistency protects the developer and helps residents understand what they will receive. It also reduces the risk of costly changes late in the build because a buyer assumed an optional component was standard.

14

Plan water discharge across the whole site

Repeated small roofs can collectively alter surface runoff on a compact development. The drainage strategy should therefore consider all units and communal areas, not only an isolated pergola gutter. Confirm whether each roof drains to an on-site point, existing downpipe or designed stormwater connection, and verify that such connections are appropriate. Avoid positions where water falls onto boundary walls, decks or shared walkways. This assessment can reveal that the cheapest-looking roof configuration is awkward to maintain or conflicts with existing services. Product details and the civil designer's plan should be reconciled before any unit is ordered.

15

Control factory dimensions against site tolerances

Factory-made pergolas rely on correct dimensions, but as-built slabs, cladding and fences do not always match design drawings exactly. Identify which measurements are controlled by the architect, which must be verified before fabrication and which permit an installation tolerance. Record the measuring party and the sign-off date for each phase. Where a model is genuinely made to measure, confirm lead time and revision rules; do not assume every catalogue kit can be custom-cut without consequences. A controlled drawing register is better than an informal email containing several contradictory widths. This discipline becomes more important when one error could be repeated across dozens of homes.

16

Treat optional screens as a distinct product decision

Track Blinds, glazing and privacy panels can improve how residents use outdoor spaces, but their installation affects clear openings, support locations, wind loads and maintenance. The developer should distinguish the pergola base specification from any later enclosure upgrade and check compatibility before promises are made. Where screens are permitted, standardise widths, colours, operating methods and any power requirements that are genuinely supported by the selected product. A structure may need to be designed for future loads even if the screen is purchased later. Equally, it may be more reliable to prohibit unsupported retrofits than to advertise every possible accessory as available.

17

Create a repeatable homeowner documentation pack

Each townhouse should receive a short, accurate pack for the installed model: product identity, care instructions, roof operating limits, cleaning and inspection, genuine warranty terms, installer contact and as-built interface information where relevant. Include what the resident should do when they notice damage or unusual movement, and who can authorise repairs. For shared or body-corporate-managed areas, clarify maintenance responsibility before handover. A consistent pack is both a customer-service improvement and a way to reduce inconsistent advice from different contractors. It also gives future owners a starting point when they seek replacement parts or ask about alterations.

18

Use procurement gates by development phase

For phased builds, set explicit release gates. Before the first order, approve the reference unit design and product evidence. Before each subsequent batch, confirm unit allocations, as-built constraints, latest drawing revisions and colour availability. Before delivery, verify the site receiving plan and handling arrangements. Before handover, confirm local installation records and homeowner instructions. These gates should be lightweight enough to run consistently but strict enough to prevent wrong configurations being repeated. A developer can use the same process for bike shelters, bin enclosures and other repeatable outdoor products, making future package buying more predictable.

Move from intelligence to project

Apply the thinking to the actual brief.

Open ORZENZA Developer Systems Send a project brief
Project