!-- Google tag (gtag.js) -->
top of page

How to Resolve Facade Clashes Before Construction

16 hours ago
6 min read

A facade clash is rarely just a modelling issue. It can become an unbuildable bracket, a blocked drainage route, an inaccessible maintenance zone, or a fire-stopping detail with no room to perform. Knowing how to resolve facade clashes means treating every coordination issue as a potential risk to safety, performance, programme and cost - not simply as an item to close in a clash report.

For complex envelopes, the critical work happens between architectural intent and fabrication-ready information. Curtain walling, unitised systems, stone, terracotta, glazing, screens and feature elements must coexist with structure, MEP services, waterproofing, fire strategy, access systems and interior finishes. A disciplined facade coordination process brings these requirements together before site constraints make change expensive.

Why facade clashes occur

Most facade clashes originate from incomplete definition rather than poor coordination alone. At early stages, the facade may be represented as a conceptual surface while structural zones, service routes and construction tolerances are still evolving. That is appropriate for design development, but it becomes a problem when procurement or fabrication starts before the interfaces have been properly resolved.

The most persistent issues sit at transitions: slab edges, parapets, soffits, movement joints, roof interfaces, plant-room louvres, entrance canopies and curtain wall returns. These are locations where several systems compete for the same physical space. A nominally clear facade zone can disappear once insulation, fire barriers, brackets, drainage, access tracks and structural deflection allowances are included.

Model quality also matters. A clash test is only as reliable as the geometry and information behind it. If facade mullions are generic objects, structural tolerances are absent, or MEP containment has been modelled without supports and access clearances, the coordination model can offer false confidence. The objective is not a clash-free model at any cost. It is a coordinated and buildable solution that recognises real installation conditions.

Start with a facade coordination strategy

Before reviewing individual clashes, establish who owns each interface and what level of information is required at each project stage. The facade contractor, architect, structural engineer, MEP designer, fire consultant, waterproofing specialist and access consultant all influence the envelope. Without clear responsibilities, issues are repeatedly transferred rather than resolved.

The strategy should define the facade systems in scope, critical interfaces, BIM exchange dates, model coordinates, tolerances and approval routes. It should also distinguish between hard clashes, clearance clashes and performance clashes. A hard clash is visible geometry occupying the same space. A clearance clash may prevent installation, adjustment or maintenance. A performance clash may not appear in a standard clash test at all, such as a drainage path interrupted by a bracket or a fire barrier that cannot remain continuous behind a mullion.

For high-risk areas, use enlarged coordination zones rather than relying on the primary project model alone. A detailed model around slab edges, roof terminations and complex openings gives the team enough resolution to review brackets, anchors, packers, membranes, insulation and fire stopping in their actual positions.

How to resolve facade clashes through BIM

BIM is most effective when it supports technical decisions rather than producing large volumes of reports. Begin by federating current, controlled models from all relevant disciplines. Confirm model origin, levels, grids and revision status before testing. A misaligned reference model can generate hundreds of meaningless clashes and distract the team from genuine risks.

Then apply rule-based clash tests that reflect the facade construction sequence. Testing every object against every other object produces noise. Instead, review targeted relationships: facade brackets against reinforcement zones; curtain wall anchors against slab edges; louvres against services; access equipment against roof plant; glazing zones against sprinkler coverage; and insulation or fire barriers against structural penetrations.

Each issue should be reviewed by a person who understands facade construction. Automated detection can identify overlapping objects, but it cannot judge whether a 25 mm adjustment is acceptable, whether a bracket can be redesigned, or whether a proposed diversion compromises drainage and pressure equalisation. The resolution must be recorded in a coordinated detail, not left as a comment in a model review platform.

Prioritise by consequence, not quantity

A report containing 500 clashes does not necessarily indicate a poorly coordinated project. It may contain repeated low-impact conflicts caused by simplified geometry. Conversely, one unaddressed interface at a movement joint can create water ingress across an entire elevation.

Classify issues according to their consequence for structural integrity, weather performance, fire safety, access, manufacturing, installation and programme. Critical issues require a named owner, a decision date and a verified design response. Lower-risk matters can be grouped and resolved through standard detail updates. This approach keeps coordination meetings focused on the decisions that protect the project.

Test constructability at 1:1 detail level

A federated model can show that components fit in principle. It does not prove that they can be installed, surveyed, sealed and maintained. The transition from model coordination to 1:1 facade detailing is where many apparent resolutions are tested properly.

Take a typical slab-edge clash. Moving a bracket may remove the interference with a post-tensioning zone, but the new location could reduce edge distance, obstruct insulation continuity or leave insufficient room for installation tools. The revised detail must account for anchor capacity, slab tolerance, bracket adjustment, thermal separation, cavity barriers, drainage and the sequence in which operatives can physically assemble the system.

This is particularly relevant for unitised facades. Unit joints, stack joints, interlocks and anchors must accommodate floor-to-floor variation, slab deflection and building movement while maintaining air and water performance. A coordination solution that works only at nominal dimensions will fail when actual construction tolerances are introduced.

For bespoke geometry, mock-ups and sample assemblies are equally valuable. They expose issues that are difficult to identify digitally, including panel handling, sealant access, visual alignment, reflected light, gasket compression and interfaces with adjacent trades. The cost of testing a critical detail early is small compared with modifying fabricated units or completed work on site.

Do not overlook invisible performance clashes

The most damaging facade conflicts are often hidden after completion. Fire stopping, cavity barriers, membranes, insulation interfaces and drainage provisions need the same level of coordination as visible cladding panels.

A cavity barrier cannot be treated as a generic line in a model. It must maintain continuity around brackets, rails, joints and changes in cavity depth while allowing the facade system to move as designed. Similarly, a membrane detail must accommodate penetrations and laps without creating a route for water to bypass the drainage plane.

Facade access is another frequent blind spot. A building maintenance unit, davit, monorail or rope-access anchor may avoid a physical clash with the facade, yet still be unable to reach recessed glazing, deep fins or shaded atrium areas safely. Access requirements should be reviewed alongside the facade geometry from early design stages, not after the external appearance has been fixed.

Close issues with accountable decisions

A clash is not resolved when it disappears from a coordination report. It is resolved when the agreed change has been incorporated into the relevant models, drawings, specifications and fabrication information, then checked against the original requirement.

Use a clear issue workflow: identify the conflict, explain its consequence, assign an owner, agree the technical response, update the affected information and verify closure. Include the reason for the decision. This record is essential when later changes affect the same interface or when site teams need to understand why a detail differs from a typical condition.

Changes must also be communicated at the right level. A relocated support may require revised structural calculations. A modified mullion profile may affect thermal performance, sightlines and procurement. A diverted service may require access panel changes in the interior. Coordination is a design-management discipline, not a drawing exercise.

Maintain control through construction

Site conditions can reintroduce facade clashes even after detailed design is complete. Surveyed slab edges may differ from assumptions, embedded plates may be misplaced, services may be installed outside their allocated zones, or substitute materials may alter build-ups. The response should be controlled, rapid and evidence-based.

Before authorising a site adjustment, assess its effect on structural capacity, weathering, movement, fire performance and appearance. Record the final condition in as-built information. Regular facade inspections during installation can identify recurring interface problems before they spread across an elevation.

Facade Design Manager approaches coordination as an assurance process: aligning architectural intent, BIM information, engineering analysis and buildable details before risks reach the site. The result is not merely fewer clashes. It is a facade package that can be manufactured, installed and maintained with confidence.

The best time to resolve a facade clash is when it is still a precise question in a coordinated detail. Give every critical interface the technical attention it deserves, and the project retains control over quality, programme and long-term building performance.

 
 

Recent Posts

See All
bottom of page