Module 14: Architectural Drawing Production

A project may organize architectural information into sheet families such as:

• cover, drawing index, general notes, code/permit information, legends, symbols, abbreviations, and key plans;
• site-related architectural drawings where included in the Architect's scope;
• floor plans;
• roof plans and, where applicable, reflected ceiling plans;
• exterior and interior elevations;
• building, wall, stair, toilet, and other sections;
• enlarged plans and room-specific layouts;
• construction details;
• door, window, room, and finish schedules;
• material/finish references and coordination sheets.

The exact sequence should reflect project complexity and office/authority standards rather than a fixed template.

For Philippine building-permit documentation, use the current governing permit framework rather than an office template as the legal source. Section 302(3)–(4) of the 2004 Revised IRR of Presidential Decree No. 1096, as reproduced and upheld in the Supreme Court's 2023 DPWH v. Philippine Institute of Civil Engineers, Inc. decision, identifies architectural documents such as vicinity/location and site-development information, floor plans, elevations, sections, ceiling plans, schedules, and detailed drawings within the architectural-document submission framework. This module teaches how those authorized documents are produced and coordinated; it does not teach the learner to originate architectural design or assume signing/sealing authority.

General information should define only controlled project conventions: drawing symbols, section/elevation/detail callouts, level notation, door/window marks, room identifiers, material symbols, dimension conventions, abbreviations, and references to specifications or consultant documents. Where a large building, campus, phased project, or partial plan could be ambiguous, use a key plan to show which portion of the overall building/site the current drawing represents and how match lines or adjacent zones relate. A key plan is orientational and must not become a second uncontrolled source of dimensions or geometry. Avoid generic notes that conflict with project-specific details or repeat the same requirement in multiple uncontrolled locations.

A floor plan should clearly establish the building grid/reference system, wall positions and thicknesses, structural interfaces, columns where relevant, doors and windows, stairs and ramps, shafts, major fixed fixtures/equipment, room boundaries, and exterior interfaces. Use the authorized architectural geometry as the source of truth; do not independently shift walls or openings to resolve another discipline without approved coordination.

A readable plan commonly includes:

• grid bubbles and controlled dimension strings;
• overall and locating dimensions sufficient to set out the work;
• room names/numbers and, where required, floor/finish references;
• door and window marks linked to schedules;
• floor levels, steps, ramps, and threshold information;
• stair direction, landing information, and section/detail references;
• plumbing fixtures and major equipment where architecturally relevant;
• section, elevation, enlarged-plan, and detail callouts;
• change-of-material, floor-pattern, or other controlled references where needed;
• coordination information such as shafts, risers, equipment zones, sleeves/openings, and ceiling/service interfaces when appropriate.

Where accessibility requirements affect the authorized design, architectural drawings should communicate the relevant accessible route, changes in level, ramps, entrances/doors, maneuvering/clear spaces, toilets, parking/drop-off interfaces, signage/wayfinding, and related details required by the current B.P. Blg. 344 IRR and project approvals. Use the current government-published IRR and the responsible Architect's/code analysis; do not copy generic dimensions from a training example or assume one detail satisfies every occupancy and site condition.

The roof plan should communicate the authorized roof form: edges, ridges, hips, valleys, crickets where designed, parapets, canopies, slopes, high/low points, openings, roof access, penetrations, curbs, equipment zones, gutters, roof drains, scuppers, and downspout locations as applicable. Coordinate roof drainage locations with plumbing/storm systems and roof structure; do not move a drain or penetration solely for drafting convenience.

Check that roof elevations and slopes agree with building sections and elevations, parapets do not conflict with drainage or equipment clearances, penetrations align with shafts and structural openings, and downspouts/roof drains connect to an approved stormwater path. Structural framing, waterproofing build-up, architectural finish, and plumbing drainage may use different reference surfaces; the drawings must state which physical level each callout represents.

Exterior elevations should align with the controlling floor/roof plans and show major façade edges, door/window openings, floor and roof lines, parapets, canopies, finish/material references, vertical dimensions where controlled, grade/site relationships, and level datums. Show enough information to identify changes in material or plane without attempting to duplicate every construction detail.

Interior elevations are useful where room-specific vertical information cannot be read from plan alone, such as toilet walls, counters, cabinetry, wall finishes, equipment, accessories, and special openings. Cross-reference them to the enlarged plan, room/finish information, and relevant details.

Building sections may show floor-to-floor heights, finished floors, structural slabs/beams/columns/walls as coordinated, ceilings, shafts, stairs, roof assemblies, parapets, building envelope, foundation/site interface, and key vertical dimensions or levels. Architectural sections must coordinate with the structural and civil references without pretending to replace the structural design drawings.

Stairs require plan and section agreement. Check flight direction, landings, floor levels, headroom/ceiling interfaces, structural support, openings, handrail/guard interfaces, finish build-ups, and detail references. Applicable code values and accessibility requirements must come from the authorized architectural/code basis rather than from a generic drafting convention.

Create or reference details where local construction cannot be communicated safely by the general plan/section alone. Common families include:

• wall base, head, corner, junction, and façade conditions;
• door jamb/head/sill and threshold conditions;
• window head/jamb/sill and waterproofing interfaces;
• toilet and wet-area waterproofing, floor transition, drain, curb, and wall finish conditions;
• stair nosing, landing, railing/guard, and finish interfaces;
• roof edge, parapet, flashing, gutter, roof-drain, penetration, and expansion/movement interfaces;
• ceiling bulkhead, soffit, access-panel, partition head, and service coordination conditions;
• floor, wall, and finish transitions.

A detail should solve a real information gap, not exist merely to fill a sheet.

A detail can show layer relationships, interfaces, dimensions, levels, materials/finishes, sealants/waterproofing intent, fastener or support references where architecturally controlled, and links to structural or specialist details. Do not invent structural reinforcement, proprietary engineering performance, fire-rated system assembly, waterproofing product requirements, or other specialist design data not present in the authorized documents.

A schedule may include unique marks, sizes, type/designation, material, glazing, hardware-set reference, fire/acoustic or other performance information when authorized, frame information, remarks, and detail references. A plan's unique door/window mark must resolve unambiguously to the corresponding schedule entry. A separate type or elevation designation may intentionally group several marked openings, so it should agree with the schedule's type field rather than being forced to equal every unique occurrence mark.

Room information may identify room number/name, floor, base, wall, ceiling finishes, ceiling height, remarks, and related interior detail references. When finishes vary by wall or zone, use a notation method that avoids ambiguity rather than compressing incompatible information into one generic cell.

Where the architectural scope includes a reflected ceiling plan, coordinate ceiling types/heights, bulkheads/soffits, access panels, lighting and diffuser zones, sprinklers/detectors where shown for coordination, grilles, speakers, ceiling-mounted equipment, and structural/service constraints. The RCP coordinates location and visual/ceiling intent but does not replace the responsible MEP/fire-protection design documents.

A useful trace is:

Plan location → mark/callout → enlarged view or section → detail → schedule/specification reference → current revision.

The reverse trace should also work. A door detail should lead back to the correct door type/mark and locations; a location-specific building or wall section should trace back to its actual cut line, while a deliberately typical section should be identified as typical rather than implying a unique cut location; a finish schedule should correspond to actual room identifiers.

Check grids, column/wall positions, slab edges, openings, beams affecting ceilings or headroom, stairs, roof framing, parapets, equipment supports, façade support zones, and foundation/site interfaces. Architectural drawings should not conceal structural elements that materially affect space or constructability.

Check shafts, ceiling zones, equipment/service clearances supplied by responsible consultants, risers, penetrations, access panels, toilets, wet areas, roof penetrations, drains/downspouts, plant/equipment zones, and external connection points. Resolve conflicts through the controlled coordination process rather than by unapproved geometric edits.

Architectural plans, sections, reflected-ceiling information, door/opening schedules, and details should preserve the authorized fire/life-safety relationships that affect construction documentation—such as means-of-egress geometry, fire/smoke-resistive construction interfaces, protected openings, stairs/shafts, exit discharge, and locations requiring coordination with fire-alarm, sprinkler, standpipe, smoke-control, or other fire-protection systems. Republic Act No. 9514 and the current BFP Revised IRR govern the fire-safety framework; the architectural drawing must coordinate these interfaces without replacing the responsible fire-protection, electrical/electronics, mechanical, or other specialist design.

Building position, entrances, ramps, thresholds, finished-floor elevations, exterior stairs, retaining/site walls, drainage, driveways, parking/pedestrian interfaces, and external finished grades must agree across architectural and civil documents.

A door mark appears on the floor plan but is missing from the current schedule. Trace its location, dimensions, type, level, adjacent construction, and detail references through the controlled set.

Refer missing or conflicting design information to the responsible Architect. After resolution, check the plan, schedule, relevant elevations/sections, and affected interfaces together. Confirm that the callout resolves to a current detail and that the detail applies to this condition. Close the item when the issue set describes one consistent opening. Reusing a visually similar detail without checking its applicability can preserve a hidden contradiction.

• Republic Act No. 9266 — Architecture Act of 2004 (Lawphil)
• Supreme Court, G.R. Nos. 200015 & 205846 (2023) — DPWH v. Philippine Institute of Civil Engineers, Inc.
• Presidential Decree No. 1096 — National Building Code of the Philippines (Senate Legislative Reference Bureau)
• DPWH — B.P. Blg. 344 Accessibility Law: Original and Amended Implementing Rules and Regulations
• Republic Act No. 9514 — Revised Fire Code of the Philippines of 2008 (Lawphil)
• Bureau of Fire Protection — 2019 Revised IRR of Republic Act No. 9514
• ISO 128-1:2020 — Technical product documentation: General principles of representation
• ISO 7200:2004 — Data fields in title blocks and document headers

The 2023 Supreme Court decision is used here as the stable government source reproducing and validating the relevant 2004 Revised IRR Section 302 architectural-document framework. The DPWH B.P. Blg. 344 IRR compilation and the BFP 2019 Revised IRR provide the accessibility and fire/life-safety interfaces referenced in this lesson. The responsible Architect's approved design, project specifications, applicable referral codes, authority requirements, and current consultant documents govern the actual project.