A terracotta exterior wall facade system is more than a coloured panel. It combines fired-clay units, clips, rails, brackets, anchors, cavity layers and building interfaces under coordinated architectural and engineering responsibility. The project succeeds when each layer has a clear role, current evidence and an approved detail.
Define the wall strategy before the panel
Begin with project location, building use and height, exposure, substrate and programme. The design team should define how the wall manages structure, water, air, heat, fire, movement, acoustic requirements and maintenance access. Identify the authority requirements and current project criteria that control the proposal.
State whether the terracotta is an open-jointed rainscreen facing and show the intended cavity, drainage and ventilation paths. The panel should not be described as the sole weather barrier, insulation or fire-resisting layer. Review the terracotta rainscreen overview, then develop project-specific details.
Issue a basis-of-design narrative with typical sections, critical interfaces and a system risk register. Record unresolved inputs such as structural survey data, anchor zones, window geometry or fire-stopping strategy. Early visibility lets the project team close decisions before panel sizes, supports and quantities are frozen.
Schedule every layer and responsibility
Facing
Identify panel code, dimensions, thickness, mass, finish, orientation, joints, corners, cuts and special pieces.
Support
List clips, rails, brackets, anchors and fasteners, with materials, finishes, adjustment and supply responsibility.
Cavity
Coordinate insulation, membranes, drainage, ventilation, fire barriers, closures and required inspection access.
Interfaces
Resolve base, windows, slab edges, parapets, roofs, soffits, corners, penetrations and adjacent wall systems.
Create a responsibility matrix for design, calculations, shop drawings, testing, samples, mock-ups, manufacture, installation and inspection. If LOPO supplies panels while another party designs rails or anchors, mark the interface explicitly. The facade coordination guide helps structure this review.
Engineer the support configuration
The facade engineer should assess the exact panel and support layout under project wind, self-weight, seismic demand where applicable, building movement and substrate tolerances. Confirm support spans, bracket locations, anchor design, edge restraint, panel engagement and replacement access. A standard detail requires adaptation to the building.
Coordinate differential movement between fired clay, metalwork, structure, windows and adjacent construction. Allow adjustment without forcing panels outside approved tolerances. Show how loads transfer around openings and at changes in support direction. Any substitution in profile, size, clip or rail should trigger engineering review.
Resolve water, fire and opening interfaces
Open joints can admit water to the cavity, so the wall needs continuous drainage and appropriately detailed membranes and flashings. Avoid ledges or blocked paths that trap runoff. Show head, sill, jamb, base and parapet conditions at large scale, including continuity into adjacent systems.
The project fire consultant should define required classifications, cavity barriers, perimeter conditions and acceptable evidence. A panel test does not automatically establish whole-wall performance. Coordinate fire barriers with brackets, rails, ventilation and windows so one requirement is not solved by compromising another.
Approve geometry and appearance together
Set the facade module from architectural datums and openings. Define colour direction, texture, gloss, orientation, joint width and colour, corner treatment and acceptable fired variation. Confirm which sizes and finishes are currently available on the selected profile instead of relying on an old promise of unlimited customization.
Review several representative samples, then full panels and a multi-unit mock-up with actual joints, supports and adjacent materials. Retain labelled control samples. Include cut edges, corners, soffits and flashings so the approved appearance reflects conditions that will be built.
Build a current evidence and quality package
Map each specification requirement to a report, calculation, drawing, sample or mock-up. Check method, date, product identity, dimensions, finish, support and scope. Product evidence may address dimensions, absorption, strength, freeze–thaw exposure, impact or fire classification; assembly evidence addresses the complete configuration as required.
If project testing is specified, define the representative wall area, interfaces, installation responsibility, sequence, observation and acceptance criteria before construction. A visual mock-up and a performance mock-up may serve different purposes. Record which decisions each one closes and how approved changes are incorporated into production documents.
Define production inspections for dimensions, bow, twist, squareness, edge quality and appearance. Connect drawing, die, finish, batch, inspection and crate records. Change control should cover clay body, profile, finish route and hardware. Marketing references to water protection or durability must be replaced by measurable project criteria.
Coordinate installation and handover
The approved installation plan should cover survey, substrate checks, setting out, brackets and rails, cavity components, panels, joints, interfaces, cleaning and inspection records. Use the installation workflow as an organizing reference, subject to engineered project details.
Commercial schedules should distinguish panels, specials, support components, engineering, tests, samples, mock-ups, packing, freight, site handling and spares. Align scope with the responsibility matrix so a missing interface does not emerge as a late variation or unowned design task.
At handover, provide final drawings, calculations, reports, product and batch codes, inspections, cleaning trials, maintenance guidance, replacement method and labelled spares. Confirm safe access for inspection and repair. This record is part of the system, not an optional addition after panel delivery.