Scope a BECx design-phase peer review of roof-to-wall, wall-to-window, and wall-to-foundation transition details
domain: astm.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the review is required under ASTM E2813's mandatory independent, third-party design-phase peer review for both Fundamental and Enhanced BECx
Focus the review on continuity of the air barrier, water-resistive barrier, and thermal control layers across each transition (roof-to-wall, window-to-wall, below-grade-to-above-grade foundation transition)
Check each transition detail against the enclosure attributes ASTM E2947 expects to be addressed: moisture control, air flow, heat flow, water vapor flow, and structural performance at the interface
Flag details lacking clear continuity, sequencing notes, or compatible-materials call-outs for redesign before construction documents are finalized
Cross-reference transition details against the project's continuous-insulation and thermal-bridging analysis to confirm the reviewed detail doesn't create an unaddressed thermal bridge
Log review comments and resolutions in the Cx issues log per the project's BECx documentation plan
Known gotchas
A design-phase transition-detail review checks drawings/details for continuity on paper — it does not replace field verification (pre-cover inspections, mockup testing) that confirms the detail was actually built as reviewed
Transition details are a common source of enclosure failures precisely because they involve multiple trades (roofing, waterproofing, glazing, framing) — confirm the review explicitly covers trade-to-trade interface responsibility, not just the detail geometry
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?