Module 20: Final Drawing Set, Permit Submission, Construction Revisions, As-Builts, and Occupancy
Learning Objectives
- Assemble a coordinated multidisciplinary drawing package with a controlled drawing index and issue status.
- Distinguish preliminary, coordination, review, permit, approved, issued-for-construction, revised, superseded, record, and as-built information.
- Simulate permit comments, consultant responses, revisions, cross-discipline checking, resubmission, and approval.
- Control RFIs, shop drawings, submittals, field instructions, supplementary drawings, design revisions, revision clouds, and drawing reissues during construction.
- Trace field changes into verified record/as-built information, completion documents, final inspections, occupancy-related requirements, turnover, and archive.
- Complete the course's progressive two-storey building project as a coordinated information package rather than a one-time PDF export.
Controlled Drawing Set
A controlled drawing set is an identified collection of project information whose sheet list, revision, status, issue date, authorization, distribution, and supersession are managed so recipients can determine which information is current for the intended purpose.
Issued for Construction (IFC)
Issued for Construction is a project document status indicating that the information has been authorized under the project's document-control process for construction use. The exact wording, approval route, and legal/contractual effect are project-specific and must not be assumed from the label alone.
As-Built Information
As-built information is intended to document the installed or constructed condition using the field records, measurements, approved changes, and verification required by the applicable contract, professional practice, and regulatory process. The term may refer to contractor-maintained field markups, surveyed installed conditions, final as-built drawings, or another defined deliverable; the project must state who records, prepares, verifies, signs, seals, and accepts it.
Record Drawing
A record drawing is a final project drawing intended to preserve the completed work information assembled under the applicable contract/professional process. It should not be represented as direct field verification by the design professional unless that verification actually occurred. Project definitions and professional obligations govern the label.
The Drawing Set Is a Lifecycle Information System
The project set is not a PDF generated once at design completion. It changes through coordination, permit review, construction questions, approved substitutions, field conditions, design revisions, inspections, and closeout. Every issue must answer: what information is current, for what purpose, who authorized it, what it supersedes, and where the final installed condition is recorded?
Final Multidisciplinary Set — Typical Information Groups
A final coordinated package may include:
- cover sheet and project/general information;
- drawing index;
- general notes, legends, abbreviations, codes/criteria, and project data as appropriate;
- Civil/Site drawings;
- Architectural drawings;
- Structural drawings;
- Plumbing/Sanitary drawings;
- Electrical drawings;
- Electronics/special-systems drawings;
- Mechanical/HVAC drawings;
- fire-related drawings;
- discipline details, sections, risers, diagrams, schedules, and typical details;
- supporting documents required by the applicable permit, contract, authority, or project procedure.
The final drawing index must match the actual issued files. A sheet missing from the index or an index entry pointing to an obsolete sheet is a document-control defect.
Final Drawing-Set Hierarchy
The cover and index organize a coordinated set whose discipline packages remain separately accountable but collectively describe one project.
Document Statuses
Status labels communicate intended use. The project document-control procedure must define them; do not assume a universal industry meaning from the words alone.
| Typical status | Intended information-control meaning |
|---|---|
| Preliminary | early information not authorized for final reliance |
| For coordination | shared so disciplines can reconcile interfaces |
| For review | submitted for designated review/approval process |
| Permit submission | issued to the applicable permitting/review authority |
| Approved | accepted/approved within the stated authority or project process; does not automatically mean IFC |
| Issued for construction | authorized for construction use under the project process |
| Revised | current issue that changes previously issued information |
| Superseded | replaced by a later controlled issue and retained only for history/traceability |
| Record | final information retained as the project record under the defined process |
| As-built | information documenting the installed condition under the project's defined verification requirements |
Never silently overwrite history. Current information and superseded history must be distinguishable.
Controlled Information Status Progression
A common lifecycle moves from development and coordination to regulatory/contract issue and finally to controlled record information; actual project status names may differ.
Permit Submission Is a Controlled Issue
Before a permit package is released:
- use the current coordinated drawing index;
- confirm all required discipline sheets and supporting documents are present;
- confirm professional signatures/seals and responsibility are handled by the persons authorized under applicable law;
- verify project/site identity, owner/project information, and sheet titles;
- verify cross-discipline consistency after the last permit-related revision;
- remove or clearly control obsolete issue markings;
- record the exact submitted revision and date;
- retain the submitted package so reviewer comments can be traced to what was actually reviewed.
Administrative requirements differ by Office of the Building Official, local government, special jurisdiction, project type, and current national/local procedures. The 2018 interagency guidelines for processing construction-related permits were amended by the ARTA-DPWH-DILG-DICT-DTI-PRC-BFP Amended Joint Memorandum Circular No. 2021-01, which remains referenced in current 2026 government BPCO guidance. Always verify the current OBO/LGU checklist, Citizen's Charter, digital submission process, and ancillary permits rather than treating one locality's procedure as universal.
Philippine Building-Permit and Fire-Safety Gates
Under the Fire Code framework, BFP plan evaluation leads to a Fire Safety Evaluation Clearance (FSEC), which is a prerequisite in the building-permit process. After completion, the 2019 Revised IRR of Republic Act No. 9514 requires BFP fire-safety inspection before occupancy and makes the Fire Safety Inspection Certificate (FSIC) a prerequisite for the Certificate of Occupancy. For buildings within Section 9.0.3.1 applicability—those required by use, size, or height to install the specified wet standpipe, automatic fire-suppression, and/or automatic fire-detection/alarm systems—the Fire Safety Compliance and Commissioning Report (FSCCR) is part of the FSIC-for-Occupancy process. BFP Memorandum Circular No. 2024-024 institutionalizes the Fire Safety and Inspection System (FSIS) for covered fire-safety certificate and clearance processing, subject to the circular's implementation and contingency provisions; project teams should verify the current BFP Citizen's Charter, FSIS guidance, and any supplemental procedures rather than assume a paper-only sequence.
Administrative Procedure Source Date — 5 October 2026
For this lesson's administrative workflow, the legal baseline remains P.D. 1096 and the 2019 Revised IRR of R.A. 9514. BFP Memorandum Circular No. 2024-024 institutionalized FSIS and states that issuance of clearances/certificates remains in accordance with the BFP Citizen's Charter; it also permits later supplemental memoranda and contingency procedures. Official BFP regional materials published in 2025 show FSIS online application steps for FSEC and FSIC for Occupancy, confirming active digital implementation. The older BFP Citizen's Charter 2022 is therefore not treated here as the current procedural authority. Before filing, verify the live FSIS process, the current BFP Citizen's Charter/service guide applicable to the station having jurisdiction, and any later national or regional issuance.
Permit Review, Correction, and Resubmission Loop
Trace a controlled permit package through authority review, comment assignment, coordinated revision, resubmission, and approval.
Administrative steps and required documents vary by jurisdiction and project. The workflow teaches document control and response traceability, not a universal local permitting checklist.
Coordinated submission package ready → Submit to applicable reviewing authorities; Submit to applicable reviewing authorities → Reviewer examines package; Route each comment to responsible discipline → Revise, cross-check, and record response; Revise, cross-check, and record response → Resubmit controlled revised package; Resubmit controlled revised package → Reviewer examines package; Reviewer examines package → Are comments, deficiencies, or clarifications issued?; Are comments, deficiencies, or clarifications issued? — No — permit / clearance issued as applicable → Approved / permit package issued as applicable; Are comments, deficiencies, or clarifications issued? — Yes → Receive comments / deficiency notice; Receive comments / deficiency notice → Route each comment to responsible discipline
- Coordinated submission package ready: terminator
- Submit to applicable reviewing authorities: document
- Reviewer examines package: process
- Receive comments / deficiency notice: document
- Are comments, deficiencies, or clarifications issued?: decision
- Route each comment to responsible discipline: process
- Revise, cross-check, and record response: process
- Resubmit controlled revised package: document
- Approved / permit package issued as applicable: terminator
Simulated Permit Comment Log
For training, each reviewer comment should be controlled like a coordination issue:
| Field | Example purpose |
|---|---|
| Comment ID | unique reviewer-comment reference |
| Reviewing authority / discipline | identifies source of comment |
| Sheet / location | points to the submitted information |
| Reviewer comment | transcribed accurately without changing meaning |
| Responsible consultant | assigns technical response |
| Response | explains clarification or change |
| Affected documents | lists every sheet/document revised |
| Revision | identifies resubmitted issue |
| Cross-discipline check | confirms no new conflicts were introduced |
| Status | open / responded / resubmitted / accepted or equivalent project states |
Do not “fix only the commented sheet.” A permit comment can require a chain of coordinated revisions.
From Permit Approval to Construction Issue
Permit approval and construction issue are related but not necessarily identical information events. Before construction release, confirm:
- permit conditions and approved revisions have been incorporated;
- tender/bid clarifications and approved design changes are reflected where applicable;
- coordinated consultant information is current;
- required construction details/schedules are complete;
- issue status and revision are unambiguous;
- the distribution list receives the correct package;
- superseded issues are withdrawn or clearly marked in the controlled system.
The governing contract and project procedures determine whether a permit-approved set, an IFC set, or another controlled construction package is the contractual basis for work.
Construction-Stage Information Streams
Construction generates information that must connect back to the controlled design:
- RFI (Request for Information): asks for clarification where contract/design information is incomplete, conflicting, or uncertain.
- Shop drawing: contractor/vendor-produced fabrication/installation information derived from the design requirements; review does not automatically transfer design responsibility.
- Material/equipment submittal: product data, samples, technical information, certifications, or proposed products for the defined review process.
- Field instruction/site instruction: written direction issued under the project's authority structure.
- Supplementary drawing/sketch: additional information clarifying or developing the issued documents.
- Design revision: authorized change to design information requiring controlled document updates.
- Change order/variation/change control record: contractual/commercial mechanism where applicable; not every drawing revision has identical contractual consequences.
- Field markup/redline: working record of installed deviations or approved field changes used for closeout/as-built preparation.
These information types should not be mixed casually. Each has a different author, purpose, approval path, and effect.
Controlled Construction Revision Lifecycle
Control RFIs, submittals, field conditions, instructions, and design changes so current construction information and the final installed-condition record remain traceable.
A field communication does not become a permanent design change by itself. Changes to controlled design information require the project's authorized technical and document-control process before reissue and closeout.
Construction information need or change arises → Capture RFI, submittal, field condition, instruction, or design change; Capture RFI, submittal, field condition, instruction, or design change → Does the event change design or issued documents?; Does the event change design or issued documents? — No → Respond without changing controlled drawings; Respond without changing controlled drawings → Construct from current authorized information; Does the event change design or issued documents? — Yes → Responsible professionals evaluate; required project authorization is obtained; Responsible professionals evaluate; required project authorization is obtained → Revise affected drawings, schedules, details, and references; Revise affected drawings, schedules, details, and references → Reissue with revision identity and distribution record; Reissue with revision identity and distribution record → Construct from current authorized information; Construct from current authorized information → Capture verified installed condition for record/as-built package; Capture verified installed condition for record/as-built package → Closeout archive retains final controlled record
- Construction information need or change arises: terminator
- Capture RFI, submittal, field condition, instruction, or design change: process
- Does the event change design or issued documents?: decision
- Respond without changing controlled drawings: document
- Responsible professionals evaluate; required project authorization is obtained: process
- Revise affected drawings, schedules, details, and references: process
- Reissue with revision identity and distribution record: document
- Construct from current authorized information: process
- Capture verified installed condition for record/as-built package: data
- Closeout archive retains final controlled record: terminator
Revision Control — Minimum Discipline
When a drawing changes:
- assign the correct revision identifier under the project convention;
- update revision description/date/status;
- use revision clouds or other project-defined change indication when required;
- update the drawing index and transmittal;
- revise all dependent sheets, schedules, details, risers, models, specifications, or calculations affected;
- record the reason/source of change;
- identify what earlier issue is superseded;
- distribute the new issue to controlled recipients;
- prevent site teams from unknowingly building from an obsolete issue;
- preserve an auditable history.
A revision cloud is a visual aid, not the complete change-control record.
Revision Propagation Map
One approved design change can affect multiple information containers; release is incomplete until every dependency is reconciled.
Do Not Let an RFI Become an Uncontrolled Design Change
An RFI response may clarify existing intent or may trigger a design change. If the response changes geometry, performance, material, routing, structural condition, code basis, or other controlled design information, route it through the project's formal design/revision approval process and update the affected documents. A field email or marked screenshot should not quietly become the permanent design record.
Shop Drawing and Submittal Coordination
Review the submittal against the design intent and surrounding interfaces defined by the responsible reviewer. Coordination checks commonly include:
- actual equipment dimensions and connection points;
- weights/reactions and structural support implications;
- access and maintenance zones;
- electrical characteristics and control interfaces;
- drains, piping, ducts, louvers, shafts, and penetrations;
- fire-rating/firestopping implications;
- architectural finish and space impact;
- substitutions that change layout or performance;
- conflicts with previously coordinated disciplines.
If accepted equipment differs materially from the design basis, reopen coordination. “Approved submittal” does not mean every adjacent discipline automatically updated itself.
Field Change Control
When actual site conditions differ from the issued information:
- document the condition accurately;
- stop treating the discrepancy as a drafting-only issue if design intent may change;
- identify affected disciplines and documents;
- obtain the required technical/contractual decision;
- issue controlled revised/supplementary information as required;
- implement the authorized change;
- record the installed condition;
- verify that closeout information captures it.
Field expediency must not bypass structural, fire-safety, electrical, mechanical, architectural, civil, or other regulated professional review.
Record and As-Built Information
A defensible closeout record distinguishes three things:
- what was originally issued;
- what changes were authorized during construction;
- what was actually installed and verified.
Useful closeout evidence may include field redlines, survey/measurement records, approved change documents, RFI responses, shop drawings, equipment data, testing/commissioning records, inspection records, photographs where contractually useful, and final discipline drawings.
The project should define how installed deviations are verified, who incorporates them, and what professional signatures/seals are required. Never label a drawing “as-built” merely because the title block was changed.
Evidence, Record Drawings, and Verified As-Built Deliverables Are Not the Same
Keep the evidence chain explicit:
- Contractor redlines / field markups are evidence of reported field conditions and changes. They are not automatically certified as-built drawings.
- Record drawings may consolidate the final design record, approved changes, accepted submittal information, and field information available under the project process. Their title does not prove that every condition was independently field-verified.
- Installed-condition verification may rely on survey, inspection, measurements, testing/commissioning, equipment records, discipline completion records, photographs, or other evidence appropriate to the system and contract.
- As-built deliverables should state the basis of verification and the responsible preparer/reviewer. Signing, sealing, certification, and acceptance requirements depend on the discipline, contract, permit/authority requirement, and the nature of the information represented.
- Title-block relabeling alone never converts a design drawing into verified as-built information.
When the approved design changed, reconcile the approved amendment/revision trail with the installed-condition evidence before issuing the final record/as-built package.
As-Built Verification Sequence
Closeout information should be derived from verified construction evidence and approved changes, then reconciled before final issue.
P.D. 1096 Sections 308 → 309 — Formal Closeout Chain
Module 06 introduced this statutory chain; the final lifecycle must carry it through to closeout:
- Inspection and supervision — Section 308: the statutory text requires the owner of a permitted building to engage a duly licensed architect or civil engineer for full-time inspection and supervision of the construction work. Apply that text together with later professional laws, the approved project responsibilities, and current OBO requirements.
- Jobsite logbook — Section 308: a construction logbook is kept at the jobsite recording actual progress, tests, weather conditions, and other pertinent data.
- Completion submission — Section 308: upon completion, the supervising licensed professional submits the duly signed/sealed logbook and prepares/submits the Certificate of Completion stating conformity with the Code and approved plans/specifications.
- Final inspection and occupancy — Section 309: the Building Official issues the Certificate of Occupancy only after the required final inspection and submission of the Certificate of Completion, when the building/structure is found compliant; use or occupancy is not authorized before that certificate.
- Fire-safety gate: where applicable, the BFP FSIC for Occupancy is a prerequisite fire-safety document, with FSCCR/testing/commissioning requirements applying to projects covered by R.A. 9514 RIRR Section 9.0.3.1.
- Changed work: approved changes, amendatory/revised-plan records, and required as-built documentation must reconcile what was approved with what was actually constructed.
This is the same closeout logic taught earlier in Module 06, now connected to the final controlled drawing and archive package rather than retaught as a permit-processing lesson.
Completion, Final Inspection, and Occupancy-Related Documentation
Closeout commonly requires coordinated evidence that construction is complete and that approved changes are reflected in the final package. Depending on project and jurisdiction, this may involve:
- certificates of completion and discipline-specific completion documentation;
- final inspections by the Office of the Building Official and other authorities having jurisdiction;
- fire-safety inspection and the applicable BFP Fire Safety Inspection Certificate process;
- approved/accepted changes and amendatory documentation;
- as-built plans when required;
- testing, commissioning, operation, or equipment records where applicable;
- punch-list correction and final verification;
- application for the Certificate of Occupancy and related local/national requirements;
- turnover manuals, warranties, keys/access information, asset/equipment records, and owner training where required.
P.D. 1096 Sections 308 and 309 connect the supervising professional's completion records, jobsite logbook, Certificate of Completion, final inspection, and Certificate of Occupancy. Under the 2019 RIRR of Republic Act No. 9514, BFP inspection and FSIC for Occupancy are additional prerequisite fire-safety gates; where FSCCR applicability is triggered, testing/commissioning and the FSCCR must be completed as required. Section 9.0.3.5 separately addresses Fire Safety Practitioner competency. Amended JMC No. 2021-01 and BFP procedures also require the project team to reconcile approved changes with the occupancy submission/as-built record as applicable. Administrative procedures stated here were checked on 5 October 2026; the exact current OBO/BFP checklist and live FSIS procedure must still be verified at the time of filing.
Occupancy Is an Authority Process, Not a Drawing Status
Marking drawings “final” or “as-built” does not itself authorize occupancy. The applicable authorities inspect/review the project and issue the required certificates under current law and administrative procedures. Maintain the final drawing package as evidence supporting that process, not as a substitute for it.
Turnover and Archive
The archive should allow a future owner, engineer, contractor, auditor, or authority to reconstruct the project information history. Retain, as applicable:
- final drawing index and controlled final/as-built/record drawings;
- permits, approvals, certificates, and official comments/responses;
- approved revisions and superseded history;
- RFI log and material design-impact responses;
- submittal/shop-drawing register and final accepted technical data;
- change-control records;
- testing/commissioning/inspection documents;
- warranties, operation/maintenance information, and equipment records;
- final issue/transmittal history;
- coordination issue register with closure evidence.
Archive rules should follow the owner's, contract's, professional, legal, and organizational requirements.
Project Information Lifecycle
The course culminates in a continuous information chain from client need through design, permit, construction, verification, occupancy, and retained asset records.
Integrated Capstone — Two-Storey Building Final Package
The progressive course project culminates in a coordinated issue containing the discipline information developed across Modules 01–20. A useful illustrative drawing-index structure is:
| Series | Illustrative content |
|---|---|
| G-series | cover, drawing index, general information, general notes/legends |
| C-series | civil/site development, grading, drainage, site utilities |
| A-series | architectural plans, elevations, sections, details, schedules |
| S-series | structural foundations, framing, details, schedules |
| P-series | plumbing/sanitary plans, risers, details, schedules |
| E-series | electrical lighting/power, schedules, diagrams |
| EC-series | electronics/data/security/fire-detection and related special-systems drawings |
| M-series | mechanical/HVAC plans, sections, details, schedules |
| FP-series | fire-protection drawings, risers, details, schedules |
This is a teaching convention only. Actual discipline prefixes, sequence, title blocks, sheet sizes, and numbering systems vary by organization, consultant, contract, client, authority, and project. Do not present this index as a universal Philippine sheet-numbering standard.
What the Learner Should Be Able to Explain at Course Completion
The learner should be able to explain, using the two-storey project:
- how client requirements became controlled design information;
- how architecture and structure exchanged grids, levels, openings, loads, and details;
- how plumbing, electrical/electronics, mechanical, and fire information was coordinated with the building;
- how a three-pass QA/QC review found and closed conflicts;
- how the permit package was frozen, reviewed, corrected, resubmitted, and approved;
- how construction questions and changes were prevented from becoming uncontrolled field decisions;
- how final installed conditions were verified and recorded;
- how occupancy-related documentation and turnover depend on an auditable information chain.
This ability to manage information across the lifecycle is the final competence of the course.
Closeout Review Case: An Approved Change Is Not Yet an Installed Record
An approved construction change appears in the design revision, but the installed position has not been verified. Keep the authorized design decision and the installation evidence as separate records.
Assign the required field verification under the project's agreed responsibilities. Link the observation, approved change, affected sheets, discrepancies, and final record status. Do not label an unverified installation as verified as-built information simply because the design change was approved. Complete the turnover package when its contents and limitations are traceable, superseded documents are controlled, and the required professional and authority closeout steps have their own recorded status.
- A drawing set is a controlled information system whose status, revision, authorization, distribution, and supersession must remain traceable.
- Permit approval, construction issue, field change, and as-built/record status are distinct information events and should not be conflated.
- Construction-stage RFIs, submittals, shop drawings, instructions, and revisions must feed a formal change-control process when design information changes.
- As-built/record information must be grounded in approved changes and verified installed conditions under the project's defined responsibilities.
- The capstone is complete when the two-storey project can be traced from client brief through coordinated design, permit, construction revisions, closeout, occupancy-related processing, turnover, and archive.
References
- Presidential Decree No. 1096 — National Building Code of the Philippines — Supreme Court E-Library; national building-permit and occupancy framework.
- Republic Act No. 9514 — Revised Fire Code of the Philippines of 2008 — statutory fire-safety framework.
- RA 9514 Revised Implementing Rules and Regulations, Revised 2019 — Bureau of Fire Protection.
- BFP Memorandum Circular No. 2024-024 — Fire Safety and Inspection System (FSIS) — national BFP circular institutionalizing FSIS; it requires certificate/clearance issuance to remain aligned with the BFP Citizen's Charter and allows supplemental procedures.
- BFP Region V — First Semester CY 2025 Regional Profile / FSIS Service Guidance — official 2025 BFP regional material showing active FSIS online steps for FSEC and FSIC for Occupancy; used as a dated implementation example, not as a substitute for the current station-specific Citizen's Charter.
- BFP Citizen's Charter 2022 — archived procedural reference — retained only for historical/documentary context. It is not presented as the current procedural authority as of 5 October 2026. Verify the current BFP Citizen's Charter/service guide and live FSIS workflow at filing time.
- ISO 19650-1:2018 — Information management using building information modelling, Part 1: Concepts and principles — lifecycle information-management concepts; still the published edition at the 2026 review date while Edition 2 is under development.
- ISO 19650-2:2018 — Information management using building information modelling, Part 2: Delivery phase of the assets — delivery-phase information-management process; still the published edition at the 2026 review date while Edition 2 is under development.
- Quezon City Department of the Building Official — Citizen's Charter 2026 — current local example referencing Amended JMC No. 2021-01; local procedures must not be generalized to every jurisdiction.