Module 8: Architectural–Structural Design Exchange

The architectural team communicates the approved architectural intent and constraints; the structural engineer develops and is responsible for the structural design within the lawful CE scope. Structural feedback may require architectural revision, but the structural engineer does not thereby become the architect of the building. Likewise, an architectural grid or preferred column-free area is an input for engineering review, not a substitute for structural analysis and design.

R.A. 9266 expressly includes structural conceptualization within the scope of architectural practice. That allows the architectural design process to consider and propose the type, disposition, arrangement, and proportioning of structural elements as part of the building concept. It does not replace the structural engineering analysis, design, detailing, and civil/structural documents that must be carried out under the lawful responsibility of the appropriate engineering professional. During coordination, treat architectural structural concepts, grid proposals, and column-free requirements as design inputs to be tested—not as completed structural engineering.

A structural engineer should receive enough controlled information to understand the building geometry, use, vertical relationships, constraints, and anticipated changes. Depending on stage and project, that package includes:

• Floor plans and the current architectural grid proposal
• Principal dimensions and coordinate/control references
• Floor, landing, roof, grade, and other critical levels
• Building sections showing floor-to-floor relationships and headroom-sensitive zones
• Elevations and façade geometry affecting support, offsets, cantilevers, or discontinuities
• Roof geometry, slopes, openings, parapets, canopies, equipment, and drainage-sensitive form
• Stair, ramp, lift/core, shaft, atrium, and other vertical opening geometry
• Wall locations, including walls that must remain free of structural interruption
• Major openings, voids, double-height spaces, courtyards, and penetrations known at the stage
• Functional constraints such as column-free zones, room clearances, circulation, parking, loading, and access
• Equipment zones and known heavy, vibrating, suspended, rooftop, or special equipment requiring structural input
• Architectural limitations on member depth, column/wall location, façade attachment, exposed structure, ceiling zones, or floor build-up
• Site/building relationship and known basement, retaining, podium, or below-grade interfaces
• Future-expansion assumptions, phasing, removability requirements, and anticipated changes
• Open issues and assumptions requiring structural confirmation rather than silent inference

The structural response should make design consequences visible, not merely return a framing plan without explanation. Depending on stage, it may include:

• Recommended structural grid and preferred regularity/alignment
• Proposed column positions and approximate zones/sizes appropriate to the current stage
• Structural wall, shear-wall, bracing, core, or other lateral-system locations
• Beam/girder lines and depth zones that affect ceilings, headroom, windows, doors, and services
• Proposed slab/floor system and principal framing direction
• Long-span, cantilever, transfer, discontinuity, or deep-member conditions requiring architectural accommodation
• Structural openings and constraints on where penetrations may or may not occur
• Stair and landing framing concept
• Roof framing concept, support points, bracing needs, and movement interfaces
• Foundation-system implications, column/wall support footprints, basement/retaining relationships, and areas needing geotechnical/site coordination
• Movement, separation, or joint requirements that affect façade, waterproofing, finishes, bridges/connections, or plan continuity
• Structural implications of heavy equipment, tanks, façade systems, future floors, expansion, or phased construction
• Required architectural decisions, missing information, and assumptions that must be confirmed before detailed analysis/design

Early structural feedback may use zones, indicative member depths, system options, or feasibility constraints rather than final member sizes. The status must be explicit. Preliminary framing information should never be presented to the construction team as final structural design, and detailed structural analysis should not proceed on architectural geometry known to be unstable or unresolved.

For each issue, record the issue ID, location, disciplines, drawing/model references, problem statement, design consequence, proposed options, responsible decision owner, required-by date, status, selected resolution, approving professional, affected documents, and verification evidence. Avoid closing an issue with “fixed” when the final coordinated drawings have not actually been checked.

A structurally convenient column location can intersect a doorway, door swing, accessible route, corridor clearance, or required circulation path. The correct response is not to erase the column from the architectural plan or shift it independently on one sheet. Reconsider the grid, bay geometry, wall/door layout, structural system, transfer option, and downstream foundation/framing effects under the responsible professionals.

A column can be technically feasible but operationally unacceptable when it occupies a classroom sightline, parking maneuvering zone, equipment clearance, retail frontage, bed space, work cell, or other critical use area. Mark the functional no-go zone early and ask structure for alternatives while the framing concept remains flexible.

A beam may conflict with a door/window head, corridor, parking clearance, stair route, ceiling, duct, pipe, cable tray, or architectural opening. The coordination question is three-dimensional: compare structural depth and elevation with the required clear zone, finishes, ceiling/services, and construction tolerances. Possible responses may include architectural level/ceiling changes, structural framing changes, span changes, member redistribution, or service rerouting; no option is automatically acceptable without engineering and architectural review.

A transfer condition may concentrate loads into a deep member or heavily loaded support zone. That can affect floor-to-floor height, ceiling continuity, façade lines, service routing, room use, vibration, construction sequence, and foundation demand. Transfer systems should therefore be exposed as a major coordination issue, not hidden as a late structural detail.

A wall required for structural resistance may conflict with a door, window, storefront, corridor, or desired open plan. The team must decide whether the opening can be moved, resized, structurally framed, or accommodated by a revised lateral-system arrangement. The structural engineer must evaluate system behavior; an opening should never be cut into a structural wall merely because it appears on a later architectural drawing.

Atriums, stairs, shafts, façade openings, loading hatches, equipment openings, and other large voids interrupt slab or wall continuity and require deliberate edge/support framing. Opening geometry and location should be issued before final framing because a “hole in the slab” can change load paths, diaphragm behavior, reinforcement/detailing, member depths, and service coordination.

The architectural stair establishes run, landing, headroom, floor levels, enclosure, and circulation requirements. Structure must return a framing concept that supports landings and defines the floor-opening boundaries. A late change to stair width, orientation, flight count, or landing position can move structural edges and beams and affect adjacent rooms, shafts, ceilings, and services.

Setbacks, cantilevers, sloping façades, large glazing zones, double-height façades, canopies, screens, cladding support, and misaligned vertical elements can create support, deflection, movement, edge-beam, anchorage, and transfer requirements. During exchange, separate the architectural performance/appearance requirement from a proposed structural solution so both teams can test alternatives without losing the design intent.

Footings, pile caps, grade/tie beams, mat edges, retaining structures, pits, tanks, manholes, drainage lines, sanitary/storm pipes, electrical/communications ducts, water lines, and other buried systems can occupy the same volume. Resolve crossings using coordinated plans, sections, and levels. A service line should not be routed through a foundation or structural element without engineering approval, and a foundation should not be shifted casually without checking the supported structural system and geotechnical basis.

Roof geometry should identify ridges/valleys, slopes, parapets, large openings, skylights, canopies, drainage features, tanks, solar/plant/equipment zones, suspended loads, maintenance routes, and façade interfaces as applicable. Structural framing must return support zones, member depth constraints, bracing/lateral requirements, and any movement or vibration considerations that affect architectural and service layouts.

Where the structural design requires joints, separation, differential-movement accommodation, or other discontinuities, architecture must carry the requirement through walls, façades, roofing, waterproofing, finishes, ceilings, bridges/connections, and services. A joint shown only on the structural plan is not coordinated if nonstructural systems are drawn continuously across it without an approved movement detail.

“Future expansion” should state whether the design anticipates added floors, an adjacent wing, additional equipment, changed occupancy, or phased structural completion. Structure must evaluate the specified scenario and communicate the implications for foundations, columns/walls, lateral systems, framing, joints, and temporary/final conditions. Do not assume unused structural capacity exists merely because expansion is desirable.

Re-submit the affected design basis for structural review when an architectural or owner change materially alters any adopted structural input, including:

• Occupancy/use change that changes the design-use assumptions or applicable loading basis
• Increased occupant, storage, archive, library, warehouse, assembly, or equipment loading
• Heavy equipment, concentrated equipment loads, vibration-sensitive or vibrating equipment, or relocated equipment
• Water tanks or other stored liquids whose location, capacity, support, or operating condition changes
• Roof-mounted equipment, solar/plant equipment, screens, canopies, suspended systems, or other added roof loads
• Façade weight, support, anchorage, geometry, or cladding-system change
• Partition/layout change when partition weight, line-load assumptions, removability, or distribution matters to the adopted structural design assumptions
• Floor build-up or finish-weight change, including toppings, screeds, heavy finishes, raised floors, or similar permanent loads
• Added mezzanine, future floor, platform, storage deck, or vertical expansion
• Changed slab/wall/roof opening, penetration zone, atrium, hatch, shaft, or other interruption to structural continuity
• Changed stair/core geometry, including run/landing arrangement, floor opening, lift/core dimensions, or wall locations
• Any other revision that changes the approved structural design criteria, load path, mass distribution, stiffness distribution, support condition, diaphragm/lateral-system assumption, serviceability demand, or foundation demand

The project team should not decide from appearance alone that a change is structurally insignificant. The responsible structural-engineering professional/team determines whether re-analysis, redesign, revised calculations, revised details, or only documented confirmation is appropriate.

A room becomes a storage area while its walls and column positions remain unchanged. This is an input change even though a geometric overlay shows no clash.

Send the revised use, proposed storage arrangement, relevant loading information, source revision, and affected location to the responsible structural designer. Obtain a documented assessment before treating the previous structural basis as current. If the designer requires additional information, keep the issue open. Close it only when the accepted use/design basis and any resulting calculations, notes, schedules, and drawings are aligned. Visual agreement between plans alone does not verify the loading basis.

• Republic Act No. 9266, Architecture Act of 2004 — statutory source for architectural practice, architectural documents, and professional responsibilities.
• PRC: Civil Engineering — Professional Regulation Commission resource for R.A. 544, as amended, and the regulated scope of Civil Engineering practice.
• PRC Professional Regulatory Board of Civil Engineering Resolution No. 05, s. 2026 — current career-progression framework identifying Structural Engineering among Civil Engineering specialization fields and establishing the Professional Civil Engineering qualification pathway.
• Supreme Court, G.R. Nos. 200015 and 205846, March 15, 2023 — decision relevant to professional responsibility for architectural documents under R.A. 9266 and the National Building Code framework.
• National Council on Disability Affairs: 2024 Revised IRR of B.P. 344 — current accessibility requirements relevant to circulation, stairs/ramps, routes, and coordinated building geometry.
• BFP: Revised IRR of R.A. 9514 (2019) — official base RIRR relevant to fire/life-safety interfaces that architectural and structural coordination must preserve; verify later BFP/DILG amendments and supplemental issuances.