Study guide
17.1 Synthesizing the Three Sections
NCIDQ Interior Design Qualification Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 About the NCIDQ Exam 1.2 Eligibility & Application Routes 1.3 Test-Taking Strategies & Item Types 1.4 The 2026 NCIDQ Blueprint Overview
2 Study Planning, Codes & Logistics
2.1 Building a Study Plan 2.2 Codes & Reference Standards Overview 2.3 Fees, Schedule & Logistics
3 IDFX: Existing Conditions
3.1 Existing Conditions: Initial Code Analysis 3.2 Existing Conditions: Evaluating the Building
4 IDFX: Pre-Design
4.1 Pre-Design: Site Analysis 4.2 Pre-Design: Best Practices of Design 4.3 Pre-Design: Project Research & Development 4.4 Pre-Design: Determining Design Intent
5 IDFX: Programming
5.1 Programming: Validating the Project Program 5.2 Programming: Programmatic Diagrams 5.3 Programming: Determining User Needs
6 IDFX: Space Planning & Preliminary FF&E
6.1 Space Planning: Completing Space Plans 6.2 Space Planning: Creating Initial Drawings 6.3 Preliminary FF&E: Identifying Finish Materials 6.4 Preliminary FF&E: Identifying Significant FF&E
7 IDFX: Schematics
7.1 Schematics: Refining Design Intent 7.2 Schematics: Performing Code Review 7.3 Schematics: Visualizing Design
8 IDIX: Codes & Life Safety
8.1 Codes & Life Safety: Performing Code Review 8.2 Codes & Life Safety: Life Safety & Occupancy Plan
9 IDIX: Integration & FF&E
9.1 Integration: Integrating Equipment & Building Systems 9.2 Integration: Developing Finish Plan & Specifications 9.3 Integration: Developing Furniture Plans & Specifications
10 IDIX: Construction Documents
10.1 Construction Documents: Details & Sections 10.2 Construction Documents: Elevations 10.3 Construction Documents: Demolition Plans 10.4 Construction Documents: Construction Plans
11 IDIX: RCP & Consultant Coordination
11.1 Construction Documents: Reflected Ceiling Plans 11.2 Consultant Coordination: Coordinating Consultant Drawings & Specs 11.3 Consultant Coordination: Power, Data & Communication Plans 11.4 Consultant Coordination: Signage & Wayfinding
12 IDIX: Construction Specifications & Schedules
12.1 Construction Specifications & Schedules: Developing Construction Specifications 12.2 Construction Specifications & Schedules: Developing Schedules
13 IDPX: Feasibility Studies
13.1 Feasibility Studies: Identifying Project Stakeholders 13.2 Feasibility Studies: Managing the Project Team 13.3 Feasibility Studies: Evaluating Project Feasibility & Due Diligence
14 IDPX: Scheduling, Budgeting & Contracts
14.1 Scheduling & Budgeting: Managing the Project Schedule 14.2 Scheduling & Budgeting: Managing the Project Budget 14.3 Contracts & Procurement: Facilitating the Procurement/Bid Process 14.4 Contracts & Procurement: Managing Proposals & Contracts
15 IDPX: Approvals, Permitting & Construction Process
15.1 Approvals & Permitting: Obtaining Project Approvals 15.2 Approvals & Permitting: Participating in the Permit Process 15.3 Construction Process: Facilitating the Construction Process 15.4 Construction Process: Participating in Change Management
16 IDPX: Site Observation & Project Close-Out
16.1 Project Closeout & Evaluation: Performing Site Visits 16.2 Project Closeout & Evaluation: Conducting Project Close-Out
17 Final Review: Synthesizing the NCIDQ & Exam-Day Readiness
17.1 Synthesizing the Three Sections 17.2 Common Pitfalls & High-Yield Topics 17.3 Exam-Day Readiness & Final-Week Plan
17.1 Synthesizing the Three Sections
Key Takeaways Explain This Topic AI
The NCIDQ is one continuous design pipeline split across three sections: IDFX establishes the problem, IDIX documents the solution, and IDPX delivers and administers it.
Each section maps to two design phases: IDFX = existing conditions through schematics; IDIX = design development through CDs/RCP/specs; IDPX = feasibility through contracts/CA/closeout.
Three code threads run through all sections: occupancy/construction type, finishes/FF&E procurement, and building-systems coordination — each flowing IDFX → IDIX → IDPX and looping back when a downstream check fails.
Construction documents become Contract Documents the moment the IDPX contract is executed — they are no longer just drawings, they are legal instruments.
Recognizing cross-section handoffs is itself testable; vignettes often span two phases and ask which document or calculation governs the next step.
Last updated: August 2026
Why Synthesis Matters
The NCIDQ is not three isolated tests — it is one continuous design pipeline split across administrations. IDFX establishes the problem (existing conditions, programming, schematics), IDIX documents the solution (construction documents, reflected ceiling plans, specifications), and IDPX delivers and administers it (feasibility, contracts, construction administration, closeout). Exam items frequently cross these boundaries: a code interpretation from IDFX reappears as a life-safety plan in IDIX and as a permit submittal in IDPX. Recognizing the handoffs is itself a testable skill — vignettes often describe a scenario spanning two phases and ask which document or calculation governs the next step.
The Design-Phase Pipeline
Each section maps to two design phases, and the phases feed each other in sequence. Treating the three sections as a pipeline — not three silos — is the single most useful mental model for the exam.
Section Design Phases Covered Primary Deliverables
IDFX Existing conditions; pre-design; programming; schematics Existing-conditions report, program, concept diagrams, schematic design package
IDIX Design development; construction documents Detail/elevation/demolition plans, RCP, finish/FFE schedules, specifications
IDPX Feasibility; project coordination; contracts; CA; closeout Feasibility study, schedule, budget, contract, submittal log, punch list, certificate of occupancy
The arrow is one-directional in real projects but circular on the exam: a question may show a programming decision (IDFX) and ask how it surfaces in a spec (IDIX) or a contract allowance (IDPX). The pipeline diagram below shows the forward flow plus the loop-backs where a downstream check sends work back upstream.
Cross-Section Code Threads
Three code-driven threads run through all three sections. Following each thread end-to-end is the fastest way to lock in the code material, which is the most cross-cutting content on the exam.
Thread 1 — Occupancy and Construction Type
IDFX code analysis classifies the occupancy group (e.g., B, A-3, M), calculates the occupant load (IBC Table 1004.5), and confirms the construction type (Type I through V) against the building's height and area. That determination flows into IDIX, where the life-safety plan sizes egress widths (7 in. per occupant for stairs, 5 in. for level egress), locates fire barriers and smoke compartments, and sets door ratings. It terminates in IDPX, where the permit submittal packages the code analysis for the AHJ and the certificate of occupancy is issued at substantial completion.
Thread 2 — Finishes and FF&E
IDFX programming selects finishes and FF&E against the program and budget; IDIX documents those selections in the finish schedule and binds them into specifications (MasterFormat Divisions 06, 09, 12); IDPX procures them through submittals and shop drawings , checking conformance to the spec before installation. A finish that fails a code review in IDIX (e.g., a non-compliant wall finish in an exit access) sends the design back to IDFX schematics — the pipeline loops, it does not only flow forward.
Thread 3 — Building Systems Coordination
IDFX existing-conditions documentation records the as-built structure, mechanical, plumbing, and electrical conditions; IDIX coordinates the reflected ceiling plan with lighting, diffusers, sprinklers, and structure to avoid clashes; IDPX reviews shop drawings and RFIs during construction administration, confirming field conditions match the coordinated set.
Section Handoffs Worth Memorizing
Programming → CDs: the program (IDFX) is the source of truth for every space's area, adjacency, and function; the CDs (IDIX) dimension and detail those spaces.
Specs → Procurement: the specification (IDIX) defines what is bought; the contract and submittal process (IDPX) governs how it is bought and verified.
CDs → Contract: the construction documents (IDIX) become Contract Documents the moment the IDPX contract is executed — they are no longer just drawings, they are legal instruments.
Substantial completion → CO: substantial completion (IDPX) triggers owner occupancy and the certificate of occupancy (closing Thread 1); final completion triggers final payment.
Master these four handoffs and the three threads, and most cross-section vignettes become predictable: identify the phase in play, follow the relevant thread, and pick the document or calculation that sits at the next handoff.
A Worked Cross-Section Vignette
Consider a scenario that appears on the exam: an architect is converting a single-tenant retail space (Group M) into a restaurant (Group A-2). Walk the three threads in order.
IDFX (schematics): reclassify occupancy from M to A-2, recompute the occupant load using the A-2 net-versus-gross floor area rule, and confirm the existing construction type can carry the new occupancy's height and area limits. The schematic code review is where this change is first validated — not in CDs.
IDIX (construction documents): the life-safety plan now sizes egress for the larger A-2 occupant load, locates the required fire barrier between the kitchen and dining area, and updates the finish schedule so all wall finishes in the exit access meet the A-2 interior finish class. The RCP is re-coordinated for kitchen hood suppression and makeup air.
IDPX (professional practice): the permit submittal packages the updated code analysis and life-safety plan for the AHJ; the contract is amended (a G701 change order) because the occupancy change expands the scope; and at substantial completion the AHJ issues a new certificate of occupancy reflecting A-2.
This single scenario touches all three sections, all three code threads, and three of the four handoffs. When a vignette feels overwhelming, label each clue with its section, then follow the threads in sequence — the answer usually sits at the next handoff in the pipeline.