Most facade contractors know RDH as the building enclosure engineer on the owner's team. But it is not the only way we work.
On complex facade and cladding projects, RDH can be engaged directly by the trade contractor, operating as a technical resource within your scope rather than above it. This is a different kind of relationship, and for many contractors, one they did not know was available.

The building enclosure engineer retained by the owner is responsible for design intent and overall performance. That function is essential, but it does not fully cover execution-level technical support for the contractor: resolving interface conditions that fall between trades, reviewing non-standard details before they reach the field as change order disputes, or providing the technical documentation a contractor needs to move substitution approvals faster and respond to deficiency claims with confidence.

That gap is where RDH adds value when engaged on the contractor’s side. For owners and architects: this role is complementary to the building enclosure engineer you’ve already retained. The project BEE is accountable for design intent and overall performance. A contractor-side consultant is accountable to execution. Different scope, different client, same building.

 

Where enclosure failures can happen

In RDH’s experience across institutional, cultural, residential, and civic projects, enclosure performance issues arise most often at interfaces between systems and trades rather than within individual assemblies. Roof-to-wall transitions, cladding-to-window integration, penetrations through air and water control layers: these are the conditions where sequencing constraints, tolerance questions, and scope boundaries converge. They are also the conditions least likely to be fully resolved in design documentation.

A detail package focused on the transitions within your scope is one of the most effective ways to address this risk before it reaches the field.

How RDH can support a facade contractor

Here are some common engagement scenarios by project phase, and how we can help. Note that the actual scope is defined at the time of engagement based on project complexity, identified risk, and other specifics.

Bid and Pre-Qualification

  • Review enclosure scope for risk and complexity
  • Support cost planning for non-standard details
  • Identify interface conditions that may require more clarification

 

Pre-Construction

  • Develop a focused detail package for high-risk transitions
  • Review specs and flag constructability challenges
  • Support substitution requests

 

Construction

  • Provide field review and installation observation for critical interfaces
  • Conduct targeted performance testing
  • Resolve interface conditions before an RFI is needed, or prepare the technical basis for one when it is

 

Value Engineering

  • Review proposed alternates for constructability, durability, service life, and warranty alignment
  • Bridge technical dialogue between contractor, design team, and other disciplines

 

Warranty and Closeout

  • Review warranty documentation and flag potential exclusions
  • Support deficiency resolution

 

Complementary, not duplicative

This model works whether RDH is already engaged as the project’s Building Enclosure Engineer or not. When both roles are present, they operate in parallel: independent design oversight at the project level, execution-level support within the contractor’s scope. When RDH is engaged by the contractor alone, the same principles apply.

Market Sectors

RDH works across virtually every market sector. This engagement model is relevant wherever facade contractors are managing complex enclosure scope: institutional and civic facilities, cultural and community buildings, residential and mixed-use development, industrial and infrastructure. The underlying need, execution-level enclosure expertise within the contractor’s scope, applies regardless of building type or project scale.

Technical Expertise. Real-World Impact.

Built on the best of building science. Subscribe for updates.

This field is for validation purposes and should be left unchanged.