Module 15: Structural Drawing Production

A structural production package may draw from:

• design criteria and governing-code basis supplied by the responsible engineer;
• structural analysis/model results and checked design calculations;
• geotechnical recommendations and foundation criteria;
• architectural grids, levels, openings, stairs, façade/support requirements, and space constraints;
• civil finished-floor/site levels and retaining/site interfaces;
• MEPF equipment loads, penetrations, shafts, sleeves, trenches, pits, and embedded-item requirements;
• structural design sketches, mark-ups, preliminary details, member schedules, and connection criteria;
• specifications, material requirements, approved delegated-design boundaries, and construction sequencing assumptions;
• current revision/transmittal information identifying which inputs are authorized for drawing production.

A reviewer should be able to answer four questions for each element: Where is it? What is it? How is it detailed? Which revision/design information controls it? If any answer requires guessing, the drawing set is incomplete or insufficiently cross-referenced.

For Philippine building work, the structural drawing set must identify and remain consistent with the project-adopted governing structural code/referral-code basis and the responsible engineer's design criteria. At this 2026 review, official ASEP material continues to identify NSCP 2015 in current structural-engineering practice, and current 2025 DPWH project documents continue to cite National Structural Code of the Philippines (NSCP), Volume I, 7th Edition (2015) for buildings/vertical structures. Name that edition only where it is actually the adopted project basis; a formally adopted successor, project specification, or authority requirement controls when different. Do not infer or apply an unreleased/newer edition from seminar drafts, secondary summaries, or drafting convention.

Design loads and load combinations, risk/occupancy classification, seismic/wind parameters, material strengths, soil/foundation parameters, analysis assumptions, system selection, member design, reinforcement, connection criteria, and serviceability limits are engineering inputs—not drafting defaults. Structural notes, schedules, details, and specifications must reproduce the checked design basis consistently. If the analysis model, calculations, member schedule, drawings, specifications, or geotechnical/foundation basis disagree, hold the affected information for responsible-engineer resolution before release.

The general-information sheets typically establish project-specific terminology and common requirements such as:

• material designations and strengths supplied by the responsible engineer;
• structural system descriptions and design-basis references;
• load/design criteria that the responsible engineer intends to communicate on drawings;
• levels, datums, grid conventions, member-mark syntax, abbreviations, and symbols;
• concrete/reinforcement, structural-steel, masonry, timber, foundation, and other notes applicable to the project;
• requirements for openings, embedded items, construction joints, temporary conditions, surveys, tolerances, testing, inspection, and submittals where included in the structural scope;
• drawing/specification/reference hierarchy and clarification procedure;
• revision status and issue purpose.

Structural grids often coordinate with architectural grids, but a grid line does not universally represent the centerline of every member. A column, wall, beam, footing, or edge may be centered, face-aligned, or offset from a grid. Show the controlling dimensions/offsets and use the same level datum across plans, sections, schedules, and discipline interfaces.

Depending on the authorized design, a foundation plan may show:

• isolated, combined, strip/continuous, raft/mat, pile-cap, or other foundation systems;
• pile locations and identifiers where applicable, with pile design/install criteria referenced to responsible design documents;
• column, pedestal, wall, pier, and grade-beam locations;
• footing/cap/grade-beam/foundation-wall or retaining-wall marks tied to schedules, where those systems are part of the structural design;
• overall and local setting-out dimensions or coordinate/grid offsets;
• top, bottom, founding, cut-off, or other controlled levels as applicable;
• pits, trenches, sumps, depressions, sleeves, blockouts, embedded items, and major openings;
• construction joints, waterstops, interfaces, and sequencing notes where structurally required;
• sections/details showing reinforcement and vertical relationships;
• references to geotechnical, civil, and architectural interfaces.

The drawing producer should recognize the communication implications of common systems without selecting them independently. An isolated footing needs clear column/pedestal alignment and local reinforcement/detail references; a combined or strip footing needs continuity and support relationships; a raft needs zones, openings, thickening/pedestal details, joints, and level control; piled systems add pile layout, cap geometry, cut-off levels, installation tolerances, testing/specification interfaces, and pile-cap reinforcement.

Plan views should locate vertical elements relative to grids and architectural geometry and identify them with consistent marks. Schedules/details may communicate section size by level, orientation, longitudinal reinforcement or steel section, transverse reinforcement/confinement, splice/coupler zones, base/start conditions, openings/embedded items, and changes through the height. A change in size or orientation must be unmistakably tied to a level or zone.

Stacking errors are serious coordination defects. Trace columns and walls vertically through foundation, floor, transfer, roof, and architectural plans. Where an element terminates, offsets, transfers, changes size, or passes through a slab/beam system, provide the responsible engineer's intended transition detail and reference it consistently.

Show beams/girders in their correct orientation, support condition, offsets, drops/steps where applicable, and relationship to columns/walls/slab edges. Each member should have a unique or grouped mark linked to a schedule/detail system that states the approved section and reinforcement/steel information. Coordinate deep beams, transfer elements, edge beams, façade supports, and ceiling/headroom constraints with architecture and services.

A slab plan may communicate slab type/thickness designation, level/depression, span/support system, primary reinforcement direction where relevant, openings, drops/capitals, thickened zones, edge conditions, construction joints, equipment bases, and local detail references. Distinguish plan geometry from reinforcing plans/details when the information density would otherwise become unreadable.

Coordinate structural roof members with architectural roof geometry, slopes, parapets, drainage points, roof openings, equipment zones, access, solar/other supports where included, and service penetrations. A roof drain or mechanical curb may require trimming/framing or local reinforcement; do not place it graphically through a member and assume the field will resolve the conflict.

Structural stair information may include landings, flights, support beams/walls, slab thickness or stringer/member marks, levels, reinforcement or steel details, connections, and openings. Coordinate the structural geometry with architectural risers/treads, finish build-up, headroom, rail/guard support, and adjacent slab/beam levels.

For each reinforced-concrete condition, communicate the design information needed for unambiguous placement. Depending on the detail, this includes:

• bar diameter/size and grade designation where controlled;
• number of bars or spacing;
• orientation/direction and top/bottom, near/far, inside/outside, or face designation;
• layer and relative position;
• start/end extent, support zone, field zone, additional-bar region, or curtailment point;
• stirrup/tie/hoop/cross-tie size, configuration, and spacing zones;
• anchorage, development, hooks, mechanical anchorage, dowels, couplers, or lap requirements as designed;
• concrete cover and placement constraints from the governing design/project criteria;
• bar marks and links to sections, elevations, or schedules where appropriate.

Plans and sections must distinguish top from bottom reinforcement and identify which direction each set runs. At supports, openings, re-entrant corners, edges, drops, column strips/middle strips, or other designed zones, additional reinforcement should be shown with enough geometric extent to prevent field interpretation by guesswork.

Transverse reinforcement must be linked to the correct member and region. Where spacing changes by zone, define the zone boundaries from a clear reference such as support face, joint face, member end, or another controlled location. Column/beam joint congestion, cross-tie arrangement, hook orientation, and interaction with longitudinal bars should be shown in sections/details when the schedule alone is insufficient.

These are structural force-transfer requirements, not drafting embellishments. Drawings should communicate the engineer's required bar continuation, anchorage location/method, lap or coupler zone, hook condition, extension, and cutoff/curtailment rules in the form intended by the design. Do not derive or change these values during drafting unless the responsible engineer has explicitly assigned and checked that design task.

A plan efficiently locates reinforcement zones and marks; a section clarifies layers, cover relationships, bar arrangement, and local geometry; an elevation shows extents and spacing zones along a member; a schedule organizes repeated member/bar information. Use the view that makes the design intent most unambiguous rather than forcing all information into one crowded plan.

Coordinate column or pedestal starters/dowels, footing/cap reinforcement, pedestal geometry, column orientation, splice/coupler zones, base level, and any construction joint. Where column bars develop into a footing or cap, the section/detail must show the authorized force-transfer arrangement and clear interaction with bottom/top foundation reinforcement.

A beam-column joint can accumulate longitudinal beam bars, column bars, ties/hoops, splices/couplers, slab reinforcement, embedded plates, and nearby penetrations. A two-dimensional schedule that is individually correct can still produce a congested three-dimensional joint. Use joint sections/details and constructability review to detect this before issue.

Openings may interrupt slab reinforcement, beams, tendons, deck, or load paths. Show approved opening dimensions/location, trimming/local reinforcement or framing where designed, and coordinate sleeves/curbs/risers with the service drawings. Unapproved coring or cutting must never be normalized as a field coordination method.

Structural steel design drawings may show grids, levels, framing orientation, member marks/sections, camber or special geometry when designed, braces, openings, base conditions, bearing/seat information, connection-force or connection-design requirements where applicable, and references to details/specifications. The extent of connection design shown depends on the engineer-of-record and delegated-design arrangement.

Document base-plate and anchor-system intent through plan/section/detail information that locates column orientation, plate geometry/mark, anchor layout, grout/interface, pedestal/foundation relationship, level, and embedded-item coordination. Modern structural-steel references commonly use anchor rod; project documents may still use anchor bolt. Treat the project designation consistently and never assume the terms authorize a generic size or detail. Actual plate thickness, anchor-rod/anchor-bolt sizes, welds, hole geometry, edge distances, embedment, and design forces are engineering values, not drafting defaults.

Fabrication/shop drawings convert the design documents into fabrication and erection information under the project's contractual and professional framework. Review of shop drawings checks conformance with the contract design intent and specified information; it is not a substitute for design calculations or sealed delegated-design documents where the project assigns connection or component design to another responsible engineer. Conversely, delegated design does not relieve the engineer of record from clearly defining the required design criteria and interfaces within that engineer's scope. Track RFIs, revisions, connection-submittal requirements, and approved changes back into the controlled structural documents where required.

Review bar layers, clear spacing, intersections, couplers/laps, hooks, ties, anchor rods, embeds, sleeves, waterstops, and placement/vibration access as a combined geometry problem. A detail can satisfy individual callouts yet remain impossible to assemble. Escalate congestion requiring a design change instead of deleting or moving reinforcement informally.

Every reserved opening, sleeve, blockout, or penetration that affects structural member geometry, reinforcement, prestressing, steel framing, load path, or fire/waterproofing interface should have an approved location, size/shape, level, and an appropriate structural reference or documented approval path. Coordinate slab openings, wall sleeves, beam penetrations, pits, trenches, blockouts, roof curbs, embedded conduits, and anchor systems before concrete placement or steel fabrication. Minor penetrations that the governing documents explicitly permit without individual detailing should still comply with those limits; do not assume an unshown penetration is automatically acceptable.

Embedded plates, anchors, inserts, waterstops, dowels, cast-in channels, construction joints, pour strips, and similar items affect both structural force transfer and construction sequence. Draw their location and relationship to reinforcement/member geometry using the responsible engineer's approved information and coordinate ownership with architectural, civil, and MEPF documents.

Permanent structural drawings may depend on an intended construction sequence, shoring/reshoring, temporary bracing, pour sequence, erection stability, or staged loading. Do not imply that a final-state drawing alone defines temporary stability. Where the structural design specifies sequencing or temporary requirements, communicate and cross-reference them explicitly; otherwise preserve the boundary between permanent design and contractor means/methods.

Before issue, perform a controlled comparison among the analysis/design output ↔ checked calculation package ↔ member schedules ↔ structural drawings ↔ specifications. The purpose is to detect transcription, coordination, or revision drift—not to independently redesign the structure. A discrepancy is held and returned to the responsible engineer with the affected mark, sheet/detail, calculation/design source, and revision identified.

The framing plan and member schedule show different sizes for the same beam mark. Identify the location, revision, controlling calculation/design record, and affected sections and interfaces.

Ask the responsible Engineer to resolve the discrepancy; the drafter should not choose a larger size or infer reinforcement from another beam. Propagate the accepted decision through every affected document and revisit headroom, openings, supports, and constructability as applicable. Verify the issued set against the authorized design basis. A complete-looking schedule is not sufficient if its values cannot be traced to the member actually shown on the plan.

• Republic Act No. 544, as amended by Republic Act No. 1582 — Civil Engineering Law (Professional Regulation Commission PDF)
• ASEP — National Structural Code of the Philippines publisher/referral-code context
• ASEP News & Events (January 2025) — technical workshop identifying NSCP 2015 among current/latest standards used in Philippine structural practice
• DPWH 2025 public project plans — current reference to NSCP Volume I, 7th Edition (2015)
• ACI PRC-315-18 — Guide to Presenting Reinforcing Steel Design Details
• ISO 3766:2003 — Construction drawings: Simplified representation of concrete reinforcement
• ANSI/AISC 303-22 — Code of Standard Practice for Steel Buildings and Bridges: current standard page
• AISC — Revisions and Errata for current standards
• ISO 128-1:2020 — Technical product documentation: General principles of representation

At this review date, ASEP's public materials continue to identify NSCP 2015 in current practice, and recent DPWH 2025 project structural notes continue to cite NSCP Volume I, 7th Edition (2015); verify the edition formally adopted for the actual project before issue. ACI PRC-315-18 is reinforcement-presentation guidance rather than a mandatory design code by itself, and ISO 3766 addresses reinforcement representation/scheduling. ANSI/AISC 303-22 is a structural-steel code-of-standard-practice/contracting reference and does not replace the project's governing Philippine structural design basis.