CID common mistakes
CID · Understand the traps and how to avoid them.
Treating the program as a fixed list of rooms and skipping the adjacency, area, and net-to-gross relationship analysis, so the bubble diagram and block plan never get built before layout begins.
Candidates coming from drafting-heavy backgrounds equate programming with taking a room list from the client, and they underestimate how many exam scenario questions hinge on circulation efficiency, departmental adjacencies, and grossing factors rather than on final room shapes.
What to do instead
For every programming scenario, write out required area, occupancy, adjacency priorities (primary/secondary/undesirable), and net-to-gross factor before considering geometry. Practice converting a written program into a bubble diagram and then into a block plan, and be able to justify adjacency decisions in one sentence each.
Applying occupancy and egress calculations to the wrong area basis, mixing net and gross square footage, or forgetting that occupant load factors are applied per use and per space rather than to the whole building.
The numbers appear simple, so candidates rush and use total building area, or they memorize a single occupant load factor and apply it to corridors, assembly, and business spaces alike, which then corrupts exit width and door count answers.
What to do instead
Build a one-page reference of occupant load factors by use and drill problems where a mixed-use floor plate must be broken into zones. Always state the area basis explicitly, then derive occupant load, required egress width, and number of exits in sequence, checking each intermediate value.
Answering code questions from habit or local practice instead of from the model code framework the exam assumes, especially for egress components, fire-resistance ratings, and allowable area and height adjustments.
Practitioners rely on familiar local amendments and on plan reviewers catching errors, so they never internalize how height and area tables interact with sprinklers, frontage, and occupancy separation, and they misread questions that ask which code path applies.
What to do instead
Study the code as a decision tree: determine occupancy classification, then construction type, then allowable height and area with all modifiers, then egress. For each practice question, write the code section logic you used. Flag any rule where your local amendment differs so you do not import it into exam answers.
Specifying assemblies, finishes, or systems by product name or by what was used on a past project without tracing the selection back to a stated performance requirement and a referenced standard.
Specification writing is often delegated or copied forward, so candidates never practice linking a design intent to a measurable criterion, and they confuse descriptive, performance, and proprietary specification formats.
What to do instead
Practice writing three-part spec sections from a design narrative, forcing each product choice to cite a performance attribute and an ASTM or other referenced standard. Be able to explain when a proprietary spec is defensible and what substitutions and equivalency language must accompany it.
Choosing materials on appearance alone and ignoring fire rating, moisture and durability exposure, substrate compatibility, and maintenance lifecycle, then being unable to answer questions about why a assembly fails in service.
Candidates study finishes as a visual palette exercise and skip the physical behavior of materials, so they miss questions about vapor retarders, movement joints, adhesion compatibility, and finish schedules tied to wet areas.
What to do instead
For each major material family, make a card listing fire performance, moisture sensitivity, substrate and adhesive compatibility, typical failure mode, and maintenance cycle. Practice reading a finish schedule and identifying the one entry that is wrong for its location and stating why.
Treating lighting design as fixture selection and layout only, without computing illuminance targets, checking uniformity and glare, or reconciling connected load and control zoning with the reflected ceiling plan.
Candidates separate lighting from power and from ceilings, so they miss integrated questions where fixture layout, control zones, emergency circuits, and ceiling coordination must agree, and they skip lumen method calculations as too mathematical.
What to do instead
Drill the lumen method until you can estimate fixture counts for a given target illuminance and room cavity ratio. For each lighting layout, produce a control zone diagram and an emergency circuit overlay, then cross-check fixture locations against ceiling grid, sprinkler, and diffuser positions.
Sizing mechanical and electrical equipment from rules of thumb without checking the underlying load assumptions, diversity, ventilation requirements, or the effect of envelope and occupancy changes on the calculation.
Rules of thumb are what practitioners use for early budgeting, and candidates never see the sensitivity of equipment size to ventilation rates, internal gains, and diversity factors, so they cannot reason about why a proposed system is undersized or inappropriate.
What to do instead
Practice a simplified cooling load and a ventilation calculation from first principles, then vary one input at a time to see the effect. Memorize the drivers (envelope, internal gains, outdoor air, diversity) and be able to explain in one sentence why a given system type suits a given building use and scale.
Producing drawings and schedules that are internally inconsistent, such as a door schedule that does not match plan tags, a finish schedule that conflicts with the enlarged details, or a reflected ceiling plan that disagrees with the lighting plan.
Candidates treat each sheet as an isolated exercise and never practice cross-sheet coordination, which is exactly what the exam tests through scenario questions about constructability, RFIs, and drawing set completeness.
What to do instead
Build a coordination checklist and run it on every practice set: tags versus schedules, plans versus details, plans versus sections, dimensions versus grid, and drawings versus specifications. Practice writing a short RFI for a deliberately introduced inconsistency and identify which sheet governs.
Misunderstanding the sequence and contractual weight of project phases, so answers confuse design development with construction documents, treat a schematic estimate as a bid, or misplace the owner's decision points and approval gates.
Candidates learn phases as labels rather than as deliverables with defined levels of completeness and cost accuracy, and they have not practiced mapping scope, fee, and risk to each phase, so questions about scope creep and phase overlap defeat them.
What to do instead
Make a phase table listing deliverable completeness, typical cost estimate accuracy, owner approvals, and the consultant effort at each stage. Practice classifying a described activity or dispute into its phase, then state what documentation should have existed at that point.
Answering professional practice questions by picking the most technically correct option rather than the one consistent with standard of care, contract terms, and the architect's authority during construction administration.
Candidates study law and ethics as abstract definitions and do not rehearse the recurring situations, such as observing versus supervising, certifying payment, rejecting nonconforming work, and handling owner-directed changes, so they default to engineering logic instead of contractual logic.
What to do instead
Work through scenario sets on standard of care, payment certification, shop drawing review, change orders, and site observation, and for each answer cite the contractual basis in one sentence. Memorize the boundary between the architect's design authority and the contractor's means and methods, and practice identifying who bears each risk.