Interior Design Project Management Reviewer: Blocks 1–3 Flashcards

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/26

flashcard set

Earn XP

Description and Tags

A vocabulary flashcard deck covering key project planning, site analysis, and programming concepts from Blocks 1 through 3.

Last updated 3:57 AM on 9/25/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

27 Terms

1
New cards

Project Planning

Establishes what needs to be accomplished before proceeding with design and project execution, helping the designer understand project requirements, limitations, resources, and objectives.

2
New cards

Scope

A project variable that establishes what work is included in the project and what is expected to be delivered.

3
New cards

Time

A project variable concerning when project activities happen, including deadlines, phases, sequence of activities, duration, and completion requirements.

4
New cards

Cost

A project variable that identifies what financial resources are available or required, affecting what can realistically be included in the project.

5
New cards

Quality

A project variable concerning the expected level of performance, outcome, and standard the project should achieve.

6
New cards

Project Site

The existing physical environment where the interior design project will take place.

7
New cards

Site Visit

An information-gathering activity performed to understand and document existing physical site conditions before design begins.

8
New cards

OBSERVE (Site Visit)

The first step in a site visit where the designer looks carefully at existing conditions to identify what is present, working, problematic, or impacting the project.

9
New cards

COLLECT (Site Visit)

The second step in a site visit involving the gathering of relevant project information, such as measurements, photographs, existing plans, and client information.

10
New cards

DOCUMENT (Site Visit)

The third step in a site visit where gathered information is recorded into notes, drawings, photos, or checklists for future reference during planning and design.

11
New cards

Site Analysis

The process of evaluating gathered site information to ask 'What exists?' and identify existing conditions, problems, opportunities, and constraints.

12
New cards

Existing Conditions

Physical elements, structures, and site features that are already present at the project location.

13
New cards

Problems (Site Analysis)

Site conditions that may interfere with or hinder the project's objectives.

14
New cards

Opportunities (Site Analysis)

Existing site conditions that could potentially support, enhance, or benefit the project.

15
New cards

Constraints (Site Analysis)

Existing site conditions that limit or restrict possible spatial solutions.

16
New cards

Observation vs. Analysis

Observation describes what is visually present (e.g., 'There is only one entrance'), while analysis determines what that condition means for the project.

17
New cards

Programming

Defining what the space needs before deciding what the space should look like, establishing functional, dimensional, and relational requirements.

18
New cards

Function (Programming)

The component of programming that asks 'What happens?' by identifying activities, users, frequency, privacy requirements, and equipment needed in a space.

19
New cards

Space (Programming)

The component of programming that asks 'What physical spaces are needed?' by determining room types, quantities, sizes, equipment, and dimensional requirements.

20
New cards

Relationships (Programming)

The component of programming that asks 'How do spaces work together?' by establishing adjacencies, direct access, separation, and circulation paths.

21
New cards

Four-Step Client Translation Process

The sequence SAY → ASK → DEFINE → PROGRAM (Client Says → Ask Why → Define Need → Program Requirement) used to turn client statements into clear design requirements.

22
New cards

Need vs. Solution

The principle that designers must investigate and solve the underlying functional need rather than simply providing a client's first proposed solution.

23
New cards

Functional Requirements

Programming requirements that specify what must happen, including activities, users, functions, equipment, storage, and operational needs.

24
New cards

Dimensional Requirements

Physical and quantitative programming requirements concerning space quantities, capacities, area sizes, equipment dimensions, and clearances.

25
New cards

Relational Requirements

Programming requirements specifying how spaces connect or relate to one another, including adjacencies, separation, circulation, access, and public/private relationships.

26
New cards

Program Document

A clear project brief created from client information and site analysis that outlines project goals, space requirements, functional needs, and client-approved projections.

27
New cards

Program vs. Design

Program defines WHAT is needed (requirements and capacity), whereas Design explores HOW those requirements will be provided spatially.