Study the IDPX by practicing scenario decisions, not by re-reading standards. For every practice question, write down three things before answering: which document or standard governs, which party owns the decision, and the next written action a designer would take. Score yourself against a rubric each week. This converts isolated facts about finishes, egress, clearances, and contracts into connected judgments you can produce quickly when a scenario stacks several of them in one problem.
The decision-ownership trap: who actually makes each call
Practice scenarios are built around role boundaries: what the interior designer specifies and recommends versus what contractors, consultants, and the architect of record decide. Classify every scenario action by owner before you evaluate its content.
A scenario option can be technically correct and still wrong because the wrong party performed it. An interior designer generally develops finish specifications, furniture selections, space plans aligned with the client program, and non-structural documentation. Actions that touch structural systems, electrical service sizing, or stamped engineering usually belong to licensed engineers of record, with the designer coordinating rather than executing. Training this split helps you eliminate options that overstep scope.
Apply the framework with a sorting drill. Take any practice scenario and label each described task as designer-owned, contractor-owned, consultant-owned, or owner/client-owned. For example, means and methods of installation sit with the contractor; the designer specifies performance and compliance requirements. Note that jurisdiction, project delivery method, and local licensure laws can shift these boundaries, so treat the framework as a reasoning habit to verify against the rules governing your own jurisdiction, not a fixed legal answer.
- Designer-owned: finish specifications, furniture systems, space planning documentation, coordination of non-structural work
- Contractor-owned: means and methods, construction sequencing, site safety during installation
- Consultant-owned: structural, mechanical, electrical, and code-engineered elements requiring a licensed engineer of record
- Owner-owned: budget approval, scope changes, final acceptance of the space
| Scenario task | Typical owner | Designer's role |
|---|---|---|
| Selecting carpet tile for a private office | Interior designer | Specify, document in schedule, verify suitability |
| Reinforcing a floor for a heavy file system | Structural engineer | Flag the load, coordinate, never detail the fix |
| Choosing wall base installation adhesive | Contractor | Specify performance class, not installation method |
| Approving a mid-project furniture substitution | Owner, on designer recommendation | Evaluate substitution against spec requirements, document it |
From occupancy classification to finish class: tracing one code chain
Finish classes become meaningful when you can trace them from a scenario: start from occupancy type, location within the means of egress, and sprinkler status, and reason forward to the required interior finish class.
Interior finish classes are the vocabulary this chain produces. Model codes commonly group wall and ceiling finishes into Class A, B, and C by flame spread and smoke developed index ranges: roughly 0-25 flame spread for Class A, 26-75 for Class B, and 76-200 for Class C, with paired smoke developed limits. Requirements then tighten along egress routes and vary with occupancy type and whether the building is sprinklered, which is why a finish acceptable in one room can fail in the corridor or stair beside it.
Worked scenario one: a designer lists finishes for the lobby, exit access corridor, and exit stairway of a nonsprinklered assembly occupancy. A tempting mistake is extending one Class B wall fabric across all three zones because it meets a budget target. The better decision traces the chain location by location: exit stairways in that condition typically demand Class A, exit access corridors typically require Class B, and general lobby areas may permit Class C, so the specification differs per zone — and each requirement is then verified against the adopted code edition. This matters because a single location-based finish miss in a vertical exit can force revision of an entire specification set.
Clear floor space versus turning space: separating two accessibility concepts
Two clearance concepts that are easy to blur: a clear floor space (an approach area for a fixture or appliance) and a turning space (room to rotate a wheelchair). Naming which one a scenario describes is half the answer.
A clear floor space, commonly referenced as roughly 30 by 48 inches in the accessibility standard, positions a wheelchair user at a fixture, control, or counter so reach ranges work. A turning space, commonly referenced as a 60-inch circle or equivalent T-shape, allows rotation within a room. A corridor can be wide enough for passage yet too narrow to combine a turning space with door maneuvering clearance, so the scenario's geometry, not a single dimension, drives the decision.
Scenario two, on a smaller scale: an accessible single-user restroom shows a 30 by 48 inch clear floor space beside the water closet and a door swinging into the room. A plausible mistake is declaring compliance because the fixture clearance exists. The better decision checks the whole spatial chain: door maneuvering clearance, fixture clearances, turning space, and accessories such as grab bars and dispensers must coexist without overlapping conflicts. Why it matters: compliance is evaluated as an assembly of clearances, and moving one element can invalidate another, which is why layering clearances on one plan is a habit worth building.
- Clear floor space: an approach position at a specific element; check reach ranges over counters and controls
- Turning space: a rotation volume within a room; verify it is not consumed by door swing or fixture clearances
- Door maneuvering clearance: depends on approach direction and latch side; check it before confirming room layout
- Verification habit: sketch the room's clearances overlapped on one plan before judging any option
Contract structures and pricing types in client scenarios
Scenario material can include payment disputes and scope changes. Knowing lump sum, cost-plus, and unit price structures lets you predict how each party's incentives shift when scope changes mid-project.
Lump sum pricing fixes the contract price for a defined scope, so the contractor carries quantity risk and the owner gains cost certainty. Cost-plus reimburses actual costs plus an agreed fee, giving flexibility for undefined scope but less cost certainty. Unit price assigns a rate per measured unit, fitting work whose quantities are uncertain. When a scenario asks how a change should be priced, identify the current structure first, because the fair mechanism differs under each one.
The binding rule underneath all of them: changes are executed in writing through the contract's modification procedure, and substitutions are evaluated against the specification's requirements, not accepted conversationally. So a scenario in which a designer verbally agrees to a cheaper furniture line over a phone call contains a flaw even if the substitution itself is excellent. The better decision is a written change request documenting the substitution's evaluation against the spec, the price adjustment mechanism, and the owner's written approval. That documentation trail is what both good practice questions reward and real projects require.
| Pricing type | Best fit | Cost certainty | Key scenario signal |
|---|---|---|---|
| Lump sum | Well-defined scope, complete documents | High for owner | "Fixed price" or "single contract sum" |
| Cost-plus | Undefined or evolving scope | Low until complete | "Reimbursable costs plus fee" |
| Unit price | Uncertain quantities of repeating work | Per-unit only | "Rate per square yard" or per item |
Specification anatomy: front end, divisions, and the substitution rule
Evaluating any specification scenario starts with knowing what a specification contains: the front end sets legal and administrative conditions, technical divisions define materials, and substitutions must satisfy documented requirements.
Front end documents, often called general and supplementary conditions, govern relationships and procedures: bidding requirements, contract forms, insurance, payment procedures, and change processes. Technical sections organize products and workmanship into divisions, with furniture and finish work appearing alongside the construction trades they coordinate with. When a scenario references "the documents," identify whether it means the drawings, the specifications, or both, because the documents are read together and a conflict between them is itself a scenario problem.
Practice the substitution evaluation as a written procedure. A proper evaluation compares the proposed product against the specified performance: function, code compliance, finish durability, warranty, and lead time, then documents the designer's recommendation. A scenario option that says a substitution was accepted because "the contractor said it was equal" is flawed regardless of the product. Similarly, an option where the designer revises the spec verbally during site observation is flawed; the correction flows through a documented directive or change. Building this reflex keeps administrative questions from feeling like guesswork.
Reading project phase questions: what changes at each stage
Every described action has a phase: a recommendation made during design development is normal, the same act during construction administration is a change. Match each described action to its project phase before judging it.
Across schematic design, design development, construction documents, bidding or negotiation, and construction administration, the designer's deliverables shift from concepts to drawings and specifications, then to evaluation of bids, and finally to submittal review, site observation, and punch lists. A scenario describing review of a contractor's shop drawing sits late in the sequence; a scenario about refining finishes with the client sits mid-sequence. An option that puts observation duties in design phases, or client presentations in construction administration, does not fit the sequence.
The phase lens also clarifies authority. During bidding, the designer's role is typically clarifying documents and evaluating bids rather than negotiating price on the owner's behalf without authority. During construction administration, the designer observes for conformance with the documents but does not supervise the contractor's means and methods, and does not accept work on the contractor's behalf. These distinctions are teachable and testable without memorizing any jurisdiction's specific statutes; the reasoning is general professional practice.
A weekly scenario-drill exercise with a self-check rubric
Build one-page decision maps from practice scenarios: mark egress routes, assign finish classes, layer accessibility clearances, and write the governing document for each decision. Score each map against the rubric below.
The exercise: take one practice scenario per week and produce a single annotated diagram or written decision map. Mark the egress path, write the interior finish class you would require at each zone with your reasoning, overlay the accessibility clearances the scenario's fixtures need, and list each decision with its owner and its governing document or procedure. Spend no more than one hour, because the point is judgment speed, not drafting polish. Compare your map against the practice question's answer and note specifically which step you skipped, not merely which answer you missed.
Use these milestone scores as learning targets, not as predictions of exam outcomes: 4 or higher in consecutive weeks suggests your decision chains are forming; a 2 or 3 in a category tells you which topic to study next, not that you will struggle on exam day. Pair the drill with a realistic sequence: weeks one and two on the decision-ownership framework and finish classes; weeks three and four on accessibility layering; week five on contracts and specifications; week six on project phases and change procedures; final week on timed, full practice scenarios with the rubric applied under time pressure.
- Readiness check 1: given a mixed-occupancy floor plan snippet, you can assign a defensible finish class to each zone and name the variable that changes it
- Readiness check 2: given a restroom or workroom scenario, you can identify at least one clearance interaction a single-dimension check would miss
- Readiness check 3: given a scope-change story, you can name the pricing structure, the required written procedure, and the owner's role in approval
- Readiness check 4: you can sort a ten-item task list into designer, contractor, consultant, and owner responsibilities without hesitation
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.