Treat every PRAC scenario as a decision under constraints using this guide's method. Before reading the options, list what the situation fixes: exits, structure, risers, rated assemblies, accessible routes, client requirements. Reject each option by naming the constraint it violates, choose the option supported by given facts plus a design principle, and flag jurisdiction-specific values for verification rather than inventing them. Practice this process on real plans with a written rubric until it runs automatically.
A decision-based approach to PRAC scenario items
The practicum is the practical application portion of the NCIDQ Examination. This guide treats its scenario items as decisions to make and justify within described project situations, and teaches you to prepare accordingly.
CIDQ, the organization that develops and administers the NCIDQ Examination, describes it as measuring core competencies for safe, functional design practice across its parts. The practicum portion, described by exam-prep catalogs as the practical application section, expresses that competency through project situations: a plan with notes, a client request, a fixed constraint, and options to choose between. This guide therefore teaches decision quality as the core study skill — for each practice item, you should be able to name the given fact that drove your choice, not just circle an answer.
This changes how content review pays off. Knowing that corridors relate to means of egress is background knowledge; noticing that a proposed wall reduces the clear width labeled on the plan is the applied act. Convert each content area into application triggers: under life safety, the trigger is any change touching an exit path; under accessibility, any new door, ramp, counter, or route; under documents, any revision that other trades' drawings already locate. Triggers turn facts into a scan you can run on every item.
Inventory constraints before you evaluate any option
Before comparing options, inventory what the scenario fixes: exits, structure, risers, rated assemblies, accessible routes, client requirements. A decision that ignores a fixed constraint is wrong regardless of its other merits.
Skim each scenario for what is fixed before reading the options. List exits and exit paths, structural elements, shafts and risers, rated assemblies, plumbing and mechanical locations, accessible routes, and client or employer requirements. Then read each option against that list. Options you reject should be rejected by naming the fixed constraint they violate; the option you choose should be supported by at least one scenario fact plus one design principle. If you cannot articulate either, your answer is a guess wearing confidence.
The inventory also separates constraints from variables. Exits, structure, and existing sprinkler layouts are usually given as fixed; furniture, finishes, and non-load-bearing partition positions are often yours to move. Misclassifying these is a concept-level difficulty: treating a fixed element as movable produces confident but invalid layouts, while treating a movable element as fixed produces over-cautious, cramped solutions. Practice tagging each scenario fact as fixed or variable until the classification is automatic. The table below maps common cues to the response each deserves.
| Cue in the scenario | What it signals | How to respond |
|---|---|---|
| A proposed change near an exit path or labeled corridor | Egress continuity and clear width are at stake | Compute the resulting clear width from the given dimensions before judging the option |
| Occupied space adjacent to storage, utility, or hazardous use | Separation or a rating may be involved | Look for rating notes in the scenario; flag rather than assume a value |
| A door, ramp, counter, or new route | Accessible-route continuity question | Trace the route from arrival point to destination and check clearances at each element |
| New or relocated equipment, fixtures, or ceiling elements | Coordination with other trades' layouts | Check the plan for existing sprinklers, structure, and mechanical work before placing anything |
| A specification or detail choice | Application must match context | Compare the product's stated use with the assembly it will serve, not with a past project |
Worked scenario: a meeting-room revision that pinches an egress corridor
In an egress scenario, protect the existing compliant path before anything else: an option that reduces clear width, breaks continuity, or blocks an exit loses regardless of its other merits.
Imagine a plan labels a corridor at 44 in. clear width, and the client wants glass-walled meeting rooms added along one side. Your standard base partition is 6 in. thick, with door frames that project into the corridor. A plausible mistake is selecting that standard assembly on autopilot: 44 minus 6 leaves 38 in., and the frame narrows it further, so the revision quietly shrinks a path the drawing certifies. The better decision is to compute the remaining width first, then shift the rooms, adopt a thinner assembly, or pick an option that does not encroach, and note the calculation.
Notice what made the decision work: arithmetic on dimensions the scenario supplied, not recall of a code minimum. In review, redo the arithmetic and write one sentence naming the decisive fact — 'the 44 in. label is the condition I must preserve.' That habit is the transferable skill, because a different scenario may supply different numbers and a different element. What stays constant is the principle: an egress path that currently works is an asset, and your design must hand it back intact.
Worked scenario: a ceiling-plan change that ignores the sprinkler layout
Coordination scenarios test whether your revision respects elements other trades own. Check the plan for existing sprinklers, structure, and mechanical layouts before placing anything new, and route or flag conflicts rather than ignore them.
Suppose a reflected ceiling plan shows sprinkler heads spaced across a room, and a design change adds a linear cove with lighting along one wall. A plausible mistake is drawing the cove on the finish layer only, treating the sprinkler layout as untouchable background — the cove may conflict with head locations or conceal them. The better decision is to overlay the layers mentally, identify the specific conflicts, then choose an option that reroutes the cove, adjusts it, or explicitly flags head relocation for coordination with the sprinkler designer.
This matters because documents direct construction: an uncoordinated revision becomes a field conflict between your ceiling and someone else's safety system. The study lesson is layer awareness — for any change you draw, list every other layer it touches. In the drill in the next section, you will commonly find your first inventory missed overhead elements entirely; observing that on paper, before it matters, is the point of the exercise. Coordination reasoning is checklistable, which makes it one of the most trainable scenario skills.
Grading your own answers with stated reasons, not gut feel
Score practice decisions on process, not intuition: did you inventory constraints, tie every choice to given facts, and separate what you decide from what you verify? Written reasons expose gaps that confidence hides.
Keep a decision journal with a fixed entry format: the constraint list you made, the option chosen, each rejected option with the constraint it violated, and an open-questions list. Compare entries across a study week and look for patterns — rejected options with vague reasons, choices supported by preference instead of facts, inventories that grow longer as your scanning improves. The journal converts one-off practice into trend data, and the trend tells you whether the method is becoming automatic or still depends on conscious effort.
Within each entry, distinguish decide items from verify items. Deciding means choosing among options using principles and scenario facts; verifying means flagging that a jurisdiction-specific value — a rating, a dimension, a listing — needs confirmation against the applicable authority's rules. Both belong in a competent answer, but confusing them is a distinct failure mode: deciding a verify item invents authority, while verifying a decide item stalls the design. Keep both verbs in your answer vocabulary, and record which one each practice item required.
A constraint-inventory drill with a self-check rubric
Run the drill on any floor plan you already have: inventory the fixed constraints, make one partition or layout change, then grade yourself against the rubric. Expect overhead elements and rated assemblies to be your first misses.
Take a plan from your own or a past project and redact identifying information, then run one change per session. Different plan types stress different constraint families, so rotate across office, retail, and healthcare-adjacent layouts over successive sessions. Repeat the same plan a week later without consulting your earlier notes to test whether the inventory itself has improved.
Expected observations from running this drill: first inventories miss vertical and overhead elements — shafts, structure above, sprinklers — and second attempts overcorrect by flagging everything as needing verification, blurring the decide-versus-verify split. Both are normal and visible only because you wrote the inventory down. A shorter, more complete second list is the milestone that matters. Score each session against the rubric below and watch the trend across attempts rather than any single result.
- List every fixed constraint you can find in ten minutes: exits, structure, shafts, rated walls, sprinkler and mechanical locations, accessible routes, client requirements.
- Make exactly one change — move a partition, add a room, rework a route — and write the constraint that justified it.
- For each alternative you considered and rejected, name the constraint it violated; 'less attractive' does not count.
- Rubric (learning milestone, not a score prediction): 2 points if the list names all egress elements and rated assemblies shown; 2 points if every rejected option has a named constraint; 1 point if verify items are flagged rather than decided.
An adaptable preparation sequence and readiness checks
Sequence preparation in three phases: rebuild content as application triggers, drill scenarios with the constraint inventory, then run mixed practice at self-imposed pace and audit your decision journal before exam day.
An adaptable sequence: in the first phase, convert your content notes into trigger lists by domain — life safety, accessibility, coordination, construction documents, ethics in practice. In the second phase, run scenario drills using the inventory method from earlier sections, one domain at a time, with the journal format from the grading section. In the final phase, mix domains so you must first identify which domain a scenario even belongs to, at a self-imposed pace, then spend your remaining stretch reviewing the journal rather than rereading notes.
Readiness checks for this method: you can produce a usable constraint inventory from an unfamiliar plan without prompting; you can state the decisive fact for every choice you make in practice; your journal shows rejected options with named constraints; and your decide-versus-verify split is stable across domains. Treat these as learning milestones about your process, not predictions of any score. Pair this guide with the free PRAC practice questions and the broader study guides collection, and confirm all administrative requirements directly with CIDQ.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.