Facade Specification Mistakes That Delay Australian Projects

Every facade project in Australia must demonstrate compliance with the National Construction Code (NCC) and relevant standards. However, the path from initial design to successful project completion is often complicated by common specification errors that can lead to significant delays, cost overruns, and even compliance failures. Understanding these pitfalls early can save considerable time and resources.

This article explores some of the most frequent mistakes in facade specification, offering practical insights to help project teams foster greater clarity and ensure smoother, more compliant outcomes.

1. Superficial Understanding of NCC Requirements and Intent

One of the most fundamental mistakes is a surface-level interpretation of the NCC. While clause numbers are important, a true understanding of the intent behind the regulations is crucial.

Focusing on Clause Numbers, Not Intent: Simply referencing a clause number without understanding its practical implications or the underlying safety objective can lead to specifications that are technically correct but practically unworkable, or worse, don’t achieve the desired performance outcome. The NCC is a performance-based code, and understanding the “why” is as important as the “what.”
Outdated or Incomplete NCC Reference: The NCC is updated regularly, and state or territory variations can apply. Specifying against an outdated edition or failing to account for local amendments can render a specification non-compliant from the outset. Always ensure the latest applicable version is referenced.
Over-reliance on “Deemed-to-Satisfy” Without Context: While “Deemed-to-Satisfy” (DTS) provisions offer a clear pathway to compliance, they are often prescriptive. Relying solely on DTS without considering the specific project context, or without understanding the full scope of a DTS solution (e.g., all components of a tested system), can lead to issues. Performance Solutions, while more complex, often offer greater flexibility and can be more appropriate for unique facade designs, provided they are rigorously developed and documented by qualified professionals.

Valmond & Gibson, as experienced industry operators, are deeply engaged with the practical application of NCC requirements. We understand that translating regulation into practice requires careful consideration of both the letter and the spirit of the code.

2. Misinterpreting AS 1530.1 and Non-Combustibility

The requirement for non-combustible materials in certain facade applications is a critical fire safety measure in Australia. Yet, misunderstandings around AS 1530.1 testing are common.

Confusing “Fire-Retardant” with “Non-Combustible”: This is perhaps the most dangerous and persistent misunderstanding. “Fire-retardant” materials are designed to resist ignition or slow the spread of flame, but they are still combustible. “Non-combustible,” as defined by AS 1530.1, means the material will not ignite or sustain combustion under specified test conditions. These are fundamentally different classifications, and confusing them can lead to severe compliance breaches.
Assuming All Aluminium Panels are Non-Combustible: While solid aluminium is non-combustible, not all aluminium facade products are. Aluminium composite panels (ACPs) with combustible cores, even those marketed as “fire-resistant,” do not meet AS 1530.1 non-combustibility requirements. Specifications must explicitly call for materials tested to and compliant with AS 1530.1 where non-combustibility is required.
Not Requiring Actual Test Reports for All System Components: A facade is a system. Even if the primary cladding panel is non-combustible, the subframe, insulation, and other ancillary components must also meet the required fire performance. Specifications should demand evidence of AS 1530.1 compliance for each individual material where non-combustibility is mandated, not just a general statement.

At Valmond & Gibson, our non-combustible aluminium facade systems, such as interloQ interlocking panels, are rigorously tested to AS 1530.1, and we provide comprehensive documentation to support this. We believe in clear, unambiguous evidence of compliance.

3. The “Or Approved Equivalent” Trap Without Clear Criteria

The phrase “or approved equivalent” is a common inclusion in specifications, intended to offer flexibility. However, when used without clear, measurable criteria, it becomes a significant source of risk and delay.

Creating Ambiguity and Inviting Non-Compliant Substitutions: Without a precise definition of what constitutes an “equivalent” product in terms of performance, testing, documentation, and aesthetic, this clause opens the door to substitutions that may not meet the design intent or, more critically, the compliance requirements.
Shifting the Burden of Proof Too Late: The responsibility for proving equivalence often falls to the builder or installer, typically well into the construction phase. This can lead to frantic searches for documentation, delays while certifiers review submissions, and potential re-specification if the proposed alternative is rejected.
Lack of Specific Performance Benchmarks: An “equivalent” should not just be similar in appearance. The specification must define equivalence across all critical performance parameters: fire resistance, structural capacity, weatherproofing, thermal performance, durability, and even specific testing methodologies.

To mitigate this, specifications should either name specific products with no alternatives, or provide a detailed checklist of criteria that any proposed “equivalent” must meet, along with the required supporting documentation.

4. Incomplete or Generic Documentation Requirements

Certifiers and building authorities require a clear audit trail of compliance. Specifications that are vague about documentation needs inevitably lead to delays.

Not Specifying What Documentation is Needed: It’s not enough to say “provide compliance documentation.” Specifications should explicitly list the required documents: AS 1530.1 test reports, product data sheets, installation guides, maintenance manuals, warranties, and any relevant engineering certifications.
Expecting Generic Data Instead of Project-Specific Packs: While generic product brochures are useful, certifiers often require documentation that directly relates to the specified product and its application on that specific project. Manufacturers like Valmond & Gibson provide detailed compliance packs tailored to project requirements, which should be explicitly requested in the specification.
Underestimating the Certifier’s Audit Trail Needs: Certifiers need to trace every component back to its tested performance. Missing links in this chain, such as a lack of evidence for a specific batch or component, can halt approvals.

A well-crafted specification anticipates the certifier’s needs, ensuring all necessary documentation is identified and requested upfront. This proactive approach streamlines the certification process.

5. Ignoring the Importance of Installation Instructions

Even the most compliant product can fail if installed incorrectly. Specifications often overlook the critical role of manufacturer’s installation instructions.

Compliance Relies on Correct Installation: A product’s fire rating, weatherproofing, and structural performance are validated under specific installation conditions. Deviating from these instructions can void warranties and, more importantly, compromise the facade’s performance and compliance.
Specifications Should Reference and Mandate Adherence: A robust specification will explicitly state that all facade components must be installed strictly in accordance with the manufacturer’s current written instructions. It should also require the builder to provide evidence of installer training or experience with the specified system.
Detailing Site-Specific Considerations: While manufacturer instructions are general, the specification can add site-specific details, such as sequencing, interface details with other trades, and quality control measures during installation.

Valmond & Gibson provides comprehensive installation guides for our systems, understanding that correct installation is integral to achieving the specified performance. We also offer technical support to installers to ensure best practice.

6. Specifying Components Without Considering System Compatibility

A facade is a complex system, not a collection of isolated parts. A common mistake is to specify individual components without fully understanding how they interact.

The Facade as a System: Cladding panels, subframe, insulation, vapour barriers, membranes, sealants, and fixings must all work together. Specifying a high-performance panel with a subframe that creates thermal bridging, or an incompatible sealant, undermines the overall system performance.
Interactions and Performance Trade-offs: Consider thermal bridging, condensation risk, structural integrity, and differential movement. For example, a specification for a high-performance curtain wall system like our 165CW Australian-designed and extruded system must consider the thermal performance of the entire assembly, not just the glass or spandrel panel.
Early Engagement with System Suppliers: Engaging with experienced suppliers early in the design process can help identify potential incompatibilities and optimise system integration, avoiding costly redesigns later.

7. Overlooking Lead Times, Availability, and Local Supply Chain

Practical logistics can derail even the best-designed specifications.

Generic Specifications Lead to Sourcing Issues: Specifying a generic product without considering its actual availability, manufacturing lead times, or minimum order quantities (MOQs) can lead to significant project delays when the builder attempts to procure it.
Importance of Understanding Manufacturing Capabilities: For custom colours or profiles, understanding the manufacturer’s capabilities and typical production schedules is vital. Australian-made systems, like our 165CW curtain wall, can offer advantages in terms of lead times and supply chain reliability compared to imported alternatives.
Stock vs. Custom Options: Clearly defining whether a stock colour or a custom finish is required, and understanding the implications for lead times and cost, is essential.

A commercially disciplined specification considers the practicalities of procurement and supply, aligning product choices with project timelines and budget.

8. Aesthetic vs. Performance Trade-offs

While aesthetics are crucial for facade design, they must be balanced with performance and long-term maintainability.

Prioritising Visuals Over Performance: Sometimes, a specific aesthetic choice (e.g., a highly reflective finish, a complex panel geometry) can have unintended consequences for thermal performance, glare, or maintenance. The specification should clearly outline performance requirements alongside aesthetic ones.
Not Considering Long-Term Maintenance: The specification should include requirements for cleaning and maintenance, and the chosen materials and finishes should be suitable for the building’s location and expected lifespan. Neglecting this can lead to premature degradation and increased operational costs. For example, understanding the difference between powder coat and anodised finishes and their respective durability is key.

A balanced specification achieves the desired aesthetic while ensuring the facade performs robustly over its lifetime and is practical to maintain.

9. Insufficient Engagement with Stakeholders During Design

Facade design is a collaborative effort. Isolating the specification process from key stakeholders is a recipe for problems.

Early Input from Manufacturers and Builders: Engaging with facade manufacturers and experienced builders during the design phase can provide invaluable practical insights, flag constructability issues, and identify potential cost efficiencies before they become expensive problems.
Pre-empting Certifier Questions: Consulting with a certifier early can help ensure the specification aligns with their interpretation of the NCC and that all necessary documentation pathways are clear. This proactive approach saves time and avoids surprises during the approval process.
Specifications as a Collaborative Document: The best specifications are not created in a vacuum but are refined through input from architects, facade engineers, builders, and suppliers, ensuring they are comprehensive, practical, and compliant.

Closing

Facade specifications are the bedrock of a successful project. By proactively addressing these common mistakes — from deeply understanding NCC intent and AS 1530.1 requirements, to clearly defining “equivalents,” ensuring robust documentation, and fostering early collaboration — project teams can significantly reduce risks, minimise delays, and achieve facades that are not only aesthetically pleasing but also high-performing and fully compliant. Valmond & Gibson is committed to supporting the industry with clear information and reliable, compliant facade systems.

Need detailed compliance documentation or technical guidance for your next facade project? Connect with the Valmond & Gibson team to discuss your requirements.

Last updated: 17 March 2026

Facade Specification Mistakes That Delay Australian Projects