The APER rewards HVAC&R engineers who can justify decisions, not only compute them. Build psychrometric fluency, separate ventilation from smoke-control objectives, keep an assumptions register, practise refrigerant-safety escalation on paper, and self-mark judgement memos against a written rubric.
From Load Calculation to Defensible Design Decision
A register-level answer converts a load result into a defensible recommendation: name the method, state the assumptions, flag the risks and identify the governing basis. The number alone never demonstrates engineering judgement; the reasoning wrapped around it does.
Worked scenario: a 120 m² fit-out tenancy returns a peak cooling load of 18 kW from a recognised load method. A plausible mistake is applying a blanket 25 per cent safety margin and specifying 22.5 kW. The better decision is to interrogate the inputs first — occupancy diversity, equipment schedules, orientation and any future-use allowance stated in the brief — then size against the calculated peak with a margin justified per assumption. A blanket margin changes the answer without changing the reasoning behind it.
Why it matters: an oversized system in a humid climate cools the space quickly then shuts off before removing enough moisture, leaving the room cool but clammy while the client pays for unused capacity. In an assessment-style answer, the reviewer is checking whether your margin is a decision or a reflex. Train this by taking one old calculation and rewriting it as a half-page recommendation: method used, three key assumptions, the margin applied, and what would make you revisit the sizing.
Psychrometrics You Must Explain, Not Just Solve
Focus on the named relationships: sensible heat ratio (SHR), dew point versus wet-bulb temperature, and mixing versus coil processes on the psychrometric chart. Explaining what each means for moisture control matters more than plotting speed.
Trace one example end to end. Return air at 24°C dry-bulb and 50 per cent relative humidity is cooled to a 13°C supply state. The SHR of the process line tells you how much of the coil's work is temperature reduction versus moisture removal. If the space needs a lower SHR than the coil naturally delivers, reheat, dedicated dehumidification or a different coil selection becomes the discussion — and that discussion, not the plotting itself, is the judgement the line on the chart represents.
Practical exercise: on a blank psychrometric chart, plot that process, mark the supply dew point, and note any condensation risk. Expected observations: the dew point of 24°C/50 per cent air sits near 13°C, so a 13°C supply leaves little condensation margin on poorly insulated ductwork or diffusers in humid conditions. Self-check rubric: two points for a correctly sloped process line, two for a correct dew point mark, two for a one-sentence condensation-risk note. Below five out of six, redo the plot before moving on.
AS 1668.1 Versus AS 1668.2: Life Safety or Air Quality?
AS 1668.1 deals with fire and smoke control in buildings, while AS 1668.2 addresses mechanical ventilation for indoor air quality. Knowing which objective a system serves — life safety, or health and comfort — changes every downstream decision.
Paper scenario: you are asked to review a basement car park serving a mixed-use building. The mistake is treating the car park exhaust system as a smoke hazard management installation because both move large air volumes. The better decision separates the objectives: general ventilation dilutes carbon monoxide for occupants during normal use, while smoke control measures exist for the fire case and follow the fire-engineering basis for that building. Your review note should state which objective each fan and duct element serves, and on what documented basis.
Why it matters: when these objectives blur, ventilation systems get modified during fit-out or value engineering with no check on whether a life-safety function was touched. For study purposes, read each standard for its intent and trigger conditions rather than memorising clause text: what activates the system, who relies on it, and what interface exists with the fire services. Then write a one-paragraph basis-of-design for a building you know, naming both objectives explicitly.
Documentation That Survives a Reviewer's Questions
Strong documentation makes your reasoning auditable: a basis-of-design, an assumptions register with sensitivity notes, traceable calculations and commissioning records that match design intent. Reviewers test whether someone else could reconstruct your decisions.
Worked scenario: an engineer assumes dense occupancy of one person per 10 m² for a café tenancy, sizes the ventilation on it, but records the assumption nowhere except a spreadsheet cell. Months later the tenancy changes use, the assumption is silently inherited, and the ventilation is wrong for the new occupant load. The better decision is an assumptions register: each assumption listed with its source, its sensitivity, and a trigger such as 'review if tenancy use changes'.
Why it matters: assumptions are where design intent quietly disappears, because they are invisible to everyone who did not make them. Practise by taking any recent project and listing five assumptions you made from memory — occupancy, diversity, weather basis, filtration, equipment heat gain. For each, note how you would verify it and what would invalidate it. If you cannot reconstruct five, that gap is precisely what documentation practice fixes, and it is trainable in a single afternoon.
Ethics, Safety and Refrigerant Responsibility on Paper
Professional standards in HVAC&R centre on competence limits, refrigerant responsibility and honest reporting. In Australian practice, refrigerant handling is a licensed activity and system safety requirements sit within the AS/NZS 5149 series for refrigerating systems.
Paper scenario: a split system charged with a lower-flammability (A2L class) refrigerant shows an oily residue, and the tenant reports a hissing sound before the unit stopped. A tempting move is to power the unit back on to 'see if it runs'. The safer paper decision is to treat the leak as real: isolate power, ventilate the space, eliminate ignition sources, and hand over to licensed refrigeration personnel following the safety data sheet and site procedures. This illustration is deliberately conservative; actual procedures come from the SDS, the governing standards and your employer's protocols.
Why it matters: an assessment of professional conduct is less about which valve you touch and more about whether you recognise the boundary of your licence and competence, escalate correctly and document the handover. The ethical dimension has the same shape: if a review request sits outside your experience — say, smoke hazard management in a high-rise — the defensible answer is to say so and recommend specialist involvement rather than improvise. Practise writing two-sentence escalation notes for three tasks outside your current scope.
A Decision Table: Calculation Output Versus Defensible Answer
Use a comparison table to separate what a calculation produces from what a defensible recommendation must add. Across load sizing, ventilation, refrigerant selection and humidity control, the gap between the two columns is the judgement you are training.
Build your own version of this table rather than memorising one. The left column is the raw output you already know how to produce; the right column is what a reviewer needs to see attached to it. Fill the 'common trap' column from your own project history, which makes it specific to your experience. Complete it for two projects you know well.
Once the table exists, convert it into flashcard-style prompts: cover the right-hand columns and recite what a defensible answer adds for each decision area. This converts passive familiarity with your own projects into the active articulation style that review-based assessment rewards, and it takes one focused evening per project to build.
table
Revisit the table after each practice memo and add one row from anything you could not answer fluently. A table that grows from your own gaps stays useful; a finished, static one does not.
| Decision area | What the calculation gives | What a defensible answer adds | Common trap |
|---|---|---|---|
| Cooling capacity | Peak load in kW | Method, diversity and schedule assumptions, stated margin and revisit triggers | Blanket safety margin with no reasoning |
| Outdoor air | A ventilation rate figure | Occupancy basis, the standard part relied on, and how the rate is verified in operation | Reusing a rate from a different building use |
| Refrigerant choice | A fluid with suitable thermodynamic properties | Flammability class, licensing implications and safety requirements for that system | Treating all refrigerants as interchangeable |
| Humidity control | A coil condition on the chart | SHR discussion, part-load behaviour and any reheat or dedicated dehumidification | Assuming sensible cooling alone fixes moisture |
Your Six-Week Sequence and Readiness Checks
Run a six-week cycle: psychrometrics and load reasoning, then ventilation and standards intent, then judgement memos and documentation, finishing with a timed, self-marked mock review against a written rubric. Adapt the weighting to your own gaps.
A realistic sequence: weeks one and two, rebuild psychrometric fluency by plotting ten processes by hand and writing one moisture-control sentence per plot. Weeks three and four, read the ventilation and smoke-control standards for intent and write a basis-of-design paragraph for two buildings you know. Week five, draft one-page judgement memos — decision, method, assumptions, risk, escalation — for three scenarios. Week six, run a timed mock: one scenario, one memo, self-marked against your rubric.
Readiness checks, as learning milestones rather than pass predictions: you can explain the difference between dew point and wet-bulb temperature in two sentences; you can produce a half-page basis-of-design for a familiar building in under an hour; your assumptions register for a past project lists at least five verifiable assumptions with review triggers; and your mock memo clearly separates what you calculated from what you decided. If a check fails, the fix is targeted practice on that single item, not a restart of the whole plan.
- Explain SHR, dew point and wet-bulb without notes
- Separate life-safety from indoor-air-quality objectives in a written basis-of-design
- Produce an assumptions register with sensitivity notes for a past project
- Write a two-sentence escalation note for work outside your competence
- Self-mark one timed mock memo against your rubric and log the weak items
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.