Treat every CHD-style scenario as a three-step decision: (1) classify the problem — load, psychrometric process, air-side system, control sequence, or documentation duty; (2) trace the governing relationship or standard clause that constrains it; (3) state the deliverable a reviewer could verify. You lose ground not from missing formulas but from classifying the problem one lane off — solving a ventilation problem with recirculation, or treating a latent load as sensible. Drill with narrative cases, write one-line justifications that cite the constraint, and grade yourself against a rubric that rewards traceable reasoning, not just a number.
Classify before you calculate: the five scenario lanes
Sort any design scenario into load estimation, psychrometric process, air-side system selection, control sequence, or documentation before touching numbers.
Lane-misclassification is the expensive error. A scenario describing 'stuffy conference rooms with high occupant density' is a ventilation and psychrometric lane problem, but a hasty reader may jump to a cooling-load lane and oversize equipment that then short-cycles. Before calculating, write one sentence: 'This is a ___ problem constrained by ___.' That sentence forces you to name the governing constraint — an outdoor-air requirement, a duct sizing limit, a standard's minimum filtration, or a code path.
Each lane has a characteristic deliverable. Load lanes produce BTU/h or W per zone with a diversity assumption stated; psychrometric lanes produce entering and leaving coil conditions with a process line on a chart; system lanes produce airflows and equipment selection logic; sequence lanes produce written control logic; documentation lanes produce coordination notes or submittal requirements. If your answer lacks the lane's natural deliverable, you have not finished the problem even if a number is correct.
- Load lane: zone vs. block loads, diversity, per-zone vs. central equipment sizing.
- Psychrometric lane: state points, process direction, mixing versus coil processes.
- Air-side lane: airflow, static pressure reasoning, ventilation delivery to the zone.
- Sequence lane: sensor, setpoint, mode logic, and failure position.
- Documentation lane: what must appear on drawings or in specifications to be enforceable.
| Scenario cue | Likely lane | First governing check | Natural deliverable |
|---|---|---|---|
| High occupant density, comfort complaints | Ventilation / psychrometric | Outdoor-air requirement per occupant | Supply airflow and OA volume with CO2 or scheduled basis |
| Heat gain through glass, peak afternoon | Envelope load | Solar and conduction components by orientation | Zone cooling load with load breakdown |
| Freeze protection, unoccupied setback | Control sequence | Setback logic and loop interaction | Written sequence with setpoints and failure positions |
| Duct routing near restricted space | Documentation / layout | Clearance and access requirements | Coordination note and drawing annotation |
| Humidity complaints in mild weather | Latent / psychrometric | Coil leaving condition and reheat logic | Coil selection point and control strategy |
Load estimation: zone vs. block and the diversity trap
Zone loads peak independently; block loads sum simultaneous zone peaks only when diversity is justified. Sizing central equipment on the wrong sum drives your whole selection.
A scenario may list five zones with individual peaks at different times — west-facing offices peaking in the afternoon, an east-facing conference room peaking in the morning. Summing the individual peaks gives a central load larger than reality; the block (coincident) load applies diversity. The exam-style decision is which sum to use for which piece of equipment: zone coils and terminal units see their own peak, central chillers and air handlers see the block load, unless a scenario states that zones are always occupied together.
A common mistake is applying a safety factor to a block load and then also to each zone, compounding oversize. The better habit: state your diversity assumption explicitly ('conference room assumed occupied only 8:00–12:00'), size terminal equipment at zone peak, and size central plant at block load with diversity justified. Oversized cooling equipment short-cycles, dehumidifies poorly, and fails part-load conditions — the consequences exam scenarios probe with follow-up symptoms like 'cold, clammy space at 50% load.'
Psychrometric scenarios: reading the process, not the number
Identify whether each step is sensible, latent, or adiabatic mixing, then trace state points in order; mislabeled processes corrupt every downstream selection.
Every psychrometric scenario is a chain: outdoor air mixes with return air, the mixture crosses a cooling coil, air is reheated or tempered, then delivered to a space where room load shifts the state. The exam-style error is treating a cooling coil as sensible-only when the leaving condition has a lower dew point — the process is cooling and dehumidifying, and the latent portion must be accounted for in the load and in reheat need. Label each segment of the process line: mixing is adiabatic (constant enthalpy approx.), coil processes follow the apparatus dew point logic, space processes follow the room sensible heat ratio line.
Practice by hand on a psychrometric chart with fixed state points and ask: 'Given entering 80°F DB / 50% RH and leaving at 55°F DB / 90% RH, what is the total and sensible capacity, and how much reheat restores a 60°F supply?' Worked in order, the numbers stay consistent; skipped, you get a supply temperature that contradicts your coil selection. For a CHD-style answer, your justification is the process path itself — a reviewer must see entering and leaving states, not just a tonnage.
- Always label processes: heating, cooling, cooling+dehumidification, humidification, mixing, fan heat.
- Room sensible heat ratio (RSHR) determines the required supply state — check it against coil capability.
- Fan and duct heat gains belong in the load path; forgetting them shifts supply temperature reasoning.
- High-altitude and low-dew-point climates change properties — read the scenario's city cue before using standard-air assumptions.
Ventilation versus envelope: a worked scenario
Trace whether a comfort complaint comes from insufficient outdoor air or from envelope-driven loads; the fix and the calculation path differ completely.
Scenario: 'A 40-person open office in a warm climate reports stuffiness on mild afternoons; the VAV air handler delivers design airflow, but CO2 readings reach 1,200 ppm.' A plausible wrong turn: increase supply airflow or cooling capacity. But the symptom is per-person ventilation, not cooling — at fixed total airflow with high zone occupancy, the outdoor-air fraction is too low. The better decision: recompute the outdoor-air requirement on a per-person and area basis, verify the air handler's minimum OA position, and consider demand-controlled ventilation; cooling load was never the constraint.
Contrast case: 'A west perimeter office overheats at 3 p.m. even when the system delivers design airflow and the zone temperature tracks the setpoint until 2 p.m.' Here the envelope solar load peaks faster than the system modulates — the lane is load and control interaction. The better decision: recompute the zone load with solar gains by orientation and hour, then check the VAV minimum flow against the load at the solar peak; the fix may be shade or glazing in the narrative, not equipment. Why it matters: the first case's deliverable is an OA schedule change; the second is a load recalculation that may shift a zone's minimum airflow and its sequence logic.
- CO2 above target with adequate total airflow → check outdoor-air fraction, not cooling capacity.
- Symptoms that track solar time → envelope load lane, verify solar components by orientation.
- Symptoms tied to occupancy schedule → ventilation lane, check per-person OA basis.
- Elevated humidity at part load → latent lane; check coil leaving dew point and reheat logic, not just capacity.
Sequences of operation: from narrative to enforceable logic
Turn a written control story into explicit sensor, setpoint, mode, and failure-position statements; vague narrative cannot be commissioned or graded.
Guideline 36-style sequences reward precision: name the sensor, its setpoint, the action, and what happens on power loss. A scenario sentence like 'the system maintains pressure when occupied' is incomplete; the exam-style answer converts it to 'duct static pressure sensor at the end of the longest branch maintains 1.2 in. w.g. during occupied cooling; on loss of signal, VFD ramps to a defined safe speed.' The designer's deliverable is a sequence another engineer could commission without asking questions.
Practice rewriting five vague narrative sequences into structured logic each week. Check your rewrite against a rubric: does every controlled variable have a sensor and setpoint? Is every mode transition triggered by a stated condition? Is the failure position explicit? Are interlocks (freeze protection, smoke, minimum OA) named? If any answer is no, the sequence is not yet design documentation — it is a narrative. This habit also exposes missing equipment: a sequence demanding supply-air temperature reset without a SAT sensor is an unbuildable design, and catching that is exactly the applied reasoning the credential rewards.
- Structure: sensor → setpoint → action → mode → failure position → interlock.
- Every reset strategy needs the sensing point and the reset range stated.
- Staged vs. modulating capacity: the sequence determines equipment selection, not the reverse.
- Unoccupied setback must state which loads are shed and which setback limits apply.
Ethics, safety, and professional documentation duties
Designer-level scenarios test whether you flag unsafe, non-compliant, or under-documented conditions rather than silently accommodating them.
A scenario may hand you a conflict: the duct routing that saves cost blocks access to a fire damper, or the specified filtration level conflicts with fan static pressure limits. The exam-style expectation is that you identify the conflict, name the governing requirement, and propose a resolution path — not that you pick the cheap option and move on. Frame answers as: condition observed, requirement violated or at risk, proposed resolution, and who must be notified (authority having jurisdiction, owner, or commissioning agent).
Documentation duties also include coordination across disciplines: a sequence you write must match the electrical feeder's capacity for fan horsepower, and a load you pass to the structural engineer affects equipment weight. In scenario answers, state the handoff explicitly — 'the increased OA requires fan selection review and a damper actuator torque check.' A complete CHD-style answer treats the design as a system of documents: drawings, specifications, sequences, and coordination notes that a reviewer, contractor, and commissioning agent can each act on.
- Name the AHJ-facing requirement when a code or standard constraint is involved.
- Flag conflicts in writing with a proposed resolution path, not just an objection.
- Coordinate static pressure, electrical capacity, and structural loads across disciplines.
- Keep the commissioning deliverable in mind: sequences and points lists must be verifiable.
A four-week CHD preparation sequence with a weekly rubric
Week 1 classification drills, week 2 psychrometric and load traces, week 3 sequence writing, week 4 full scenario synthesis with a documented self-check score.
Week 1: take 20 narrative scenarios and classify each into the five lanes with a one-sentence governing constraint. Week 2: work 10 psychrometric chains and 5 load sets by hand; write the process path before any number. Week 3: rewrite 10 narrative sequences into structured logic with the sensor-setpoint-action-failure rubric. Week 4: pull it together with 6 full scenarios — each requiring classification, calculation or logic, and a one-paragraph deliverable statement. Keep a decision log: every scenario you get wrong, record the lane you chose and the lane it was.
Expected observations by week 4: your classification sentence becomes automatic (you write it before reading twice), your psychrometric chains stay consistent end-to-end, and your sequences contain no vague verbs. A reasonable self-check milestone: on a 10-scenario set, at least 8 correctly classified lanes, 8 of 10 process chains internally consistent, and 8 of 10 sequences passing the rubric. These are learning milestones to guide review, not predictions of exam outcomes — use the rubric to decide which week to repeat, and pair this work with practice questions and flashcard review on the site's free practice page for the CHD credential.
- Week 1: lane classification + governing-constraint sentences.
- Week 2: psychrometric chains and load sets by hand, process path first.
- Week 3: sequence rewrites scored against the six-point rubric.
- Week 4: full synthesis scenarios + decision log review of every misclassified lane.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.