Study guide
5.2 Programming: Programmatic Diagrams
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
5.2 Programming: Programmatic Diagrams
Key Takeaways Explain This Topic AI
Programmatic diagrams translate the written program into visual relationships; they are analytical, not schematic, and show what must be true rather than what the design will look like
An adjacency matrix rates every space pair on a required / desirable / neutral / undesirable scale, revealing the most-connected space that should sit centrally
Bubble diagrams draw each space as a circle sized by area and connected by relationship lines; they are quick, exploratory, and hand-drawn to test alternative organizations
Block diagrams replace bubbles with scaled rectangles inside the actual building shell to test whether the program fits the floor plate
Parti diagrams capture the single organizing idea; stacking diagrams distribute program across multiple floors of a building
Last updated: August 2026
Why Diagrams Come After the Program
The program is text and numbers. Programmatic diagrams translate that text into visual relationships before any design is drawn. They are analytical, not schematic — they show what must be true, not what the design will look like. Diagrams let the designer and client test the program, expose conflicts (two required adjacencies that are mutually exclusive), and communicate the organizing logic to stakeholders. Five diagram types appear on the NCIDQ IDFX, each used at a different moment in the process.
The Adjacency Matrix
An adjacency matrix (also called a relationship matrix ) rates every pair of spaces against a relationship scale. The most common scale:
- Symbol Rating Meaning
- ● (filled circle) Required Must be directly adjacent
- ○ (open circle) Desirable Should be near
- △ (triangle) Neutral No preference
- ✕ (cross) Undesirable Must be separated
Build the matrix by listing every program space along both the top row and the left column. Each cell holds the rating for that pair. Some matrices add a numeric weight (1–4) so the ratings can be summed into a score. Reading a completed matrix tells the designer the most-connected space — the one with the most ● marks — which is often the workroom or copy center and should be placed centrally. A matrix can also expose a fatal conflict: if space A must be adjacent to the exterior wall (for daylight) and space B must also be adjacent to the exterior wall but must be separated from A, no single-floor solution exists and the program must change.
Bubble Diagrams
A bubble diagram turns the matrix into a picture. Each program space becomes a circle (bubble) sized in proportion to its area — a 2,000 sf open office is a large bubble, a 100 sf storage room is a small one. Lines between bubbles show relationships, often using the same symbols (● for required, ○ for desirable). Bubble diagrams are quick, hand-drawn, and exploratory: designers generate several alternatives to test organizations without committing to a layout. They are intentionally loose so the client can understand the logic at a glance and participate in choosing a direction.
Block Diagrams
A block diagram is the next refinement. It replaces circles with scaled rectangles drawn inside the actual building shell — the partition outline, core, and column lines are shown. Each rectangle is labeled with the space name and area. Block diagrams:
- Test whether the program actually fits within the available floor plate
- Show circulation corridors as connecting bars
- Begin to establish orientation (which spaces get windows)
A block diagram is the bridge between program analysis and schematic design. If the blocks do not fit, the program is over-allocated relative to the shell and the designer returns to the client before proceeding.
Parti Diagrams
The parti is the organizing concept — the big idea in a single sketch. It might be an axis, a center, a courtyard, a spine, a grid, or a progression. The parti is drawn before the plan is detailed and is referenced throughout the project to keep the design coherent. A project may have a parti such as "a central daylit atrium with wings radiating outward" that originated in the bubble diagram and is realized in the block diagram. The parti is the one diagram the designer pins above the studio table for the duration of the project.
Stacking Diagrams
A stacking diagram distributes program areas across multiple floors of a building. Each floor is a horizontal band; each program space is a block sized by area. Stacking diagrams answer:
- Which functions belong on the ground floor (lobby, retail, loading)
- Which functions need the top floor (executive suite, mechanical, outdoor terrace)
- Which functions can repeat on multiple floors (typical office floors)
- Where vertical circulation (elevators and stairs) should land
Stacking is produced early in multi-floor projects and is often iterated as the program is refined.
When Each Diagram Is Used
- Phase Diagram Purpose
- Programming Adjacency matrix Test relationship logic
- Programming / concept Bubble diagram Explore alternative organizations
- Schematic preparation Block diagram Test fit within the building shell
- Concept Parti diagram Capture and communicate the big idea
- Multi-floor programming Stacking diagram Distribute program by floor
- Exam Scenario
A 12-space office project has a completed adjacency matrix showing the break room has four ● marks (required adjacency to lobby, restrooms, kitchenette, and open office) — the most of any space. The bubble diagram places the break room centrally. The block diagram tests whether that central location fits the floor plate's core location; if the building core occupies the center, the break room must shift and the diagram is redrawn. This iteration catches the conflict before the design is drawn — the entire purpose of programmatic diagrams.