The CEA body of knowledge rewards a specific judgment: matching the depth of analysis to the decision a client must make. A walk-through finding, a detailed system analysis, and an investment-grade package answer different questions, and the domains — from audit strategy and use analysis through HVAC, lighting, motors, controls, and economics — test whether you can tell them apart. This guide builds that judgment through audit-level selection, utility data interpretation, economic screening, and interactive effects, with two worked scenarios, a bill-analysis exercise, a decision table, and a preparation sequence organized around AEE's published body of knowledge.
Matching Audit Depth to the Decision the Client Actually Needs
An audit deliverable is proportional to its purpose. A screening visit, a detailed audit, and an investment-grade analysis differ in measurement effort, uncertainty, and cost — the exam-style skill is selecting the right tier for the decision at hand.
The tiers form a progression. A walk-through or screening audit relies on site observation, brief bill review, and interviews to identify obvious operations-and-maintenance items and low-cost measures. A detailed audit quantifies selected systems with measurements and calculations. An investment-grade analysis adds rigor sufficient for a financing or major capital decision. Frameworks such as ASHRAE Standard 211-2018 for commercial building energy audits and the US Department of Energy's Guide to Energy Audits describe this kind of progression, and AEE's body of knowledge begins with developing an audit strategy and plan.
Worked scenario: a client with a 200,000 sq ft office campus asks for a capital plan to present to its board. The plausible mistake is proposing an investment-grade analysis of every measure, including a $500 thermostat repair — the analysis cost would dwarf the measure value and stall the project. The better decision is to stage the work: a walk-through builds the measure list, simple screening ranks candidates, detailed analysis quantifies the shortlist, and investment-grade treatment is reserved for the financing package. Why it matters: proportionality keeps the audit affordable and makes the final numbers defensible where they count.
| Audit tier | Decision it supports | Data effort | Output emphasis |
|---|---|---|---|
| Walk-through / screening | Whether a deeper audit is worth funding; quick O&M fixes | Site observation, bill review, interviews | Opportunity list with order-of-magnitude savings |
| Detailed audit | Selecting and sizing specific measures for a capital plan | Measurements, logging or trending, load analysis | Quantified savings and costs with stated assumptions |
| Investment-grade analysis | Financing, performance contracting, major capital approval | Rigorous measurement, refined assumptions, verification plan | Defensible savings, risk discussion, implementation path |
Reading Utility Bills: Baseload, Load Factor, and Weather Effects
A year or more of bills reveals baseload, load profile shape, and weather sensitivity. Load factor, degree-day correlation, and use-per-unit metrics convert raw consumption records into testable hypotheses about where waste lives.
Two named concepts anchor this domain. Baseload is the consumption that persists regardless of activity — estimate it from the mildest months, weekend or holiday data, or the overnight minimum — and a high baseload relative to occupied use suggests equipment running when the building is empty. Load factor is total kWh divided by peak kW multiplied by the hours in the billing period; a low value means demand spikes dominate the profile, pointing toward scheduling, staging, or peak-management opportunities rather than steady-state efficiency.
Weather normalization is the third tool: regress monthly energy against heating and cooling degree days so the slope represents weather-sensitive load and the intercept approximates baseload. Months that fall far off the regression line deserve a hypothesis — a schedule change, new equipment, or a fault. Practice the mechanics on real bills, because exam-style scenarios ask you to interpret the pattern, not just compute a number. A regression intercept near your estimated unoccupied load, with a plausible weather slope, tells you the data supports the analysis you are about to build on it.
- Exercise: pull 12 to 24 monthly bills for one building you can visit, and compute each month's load factor from kWh, peak kW, and hours in the period.
- Estimate baseload from the two or three mildest months, then regress monthly kWh on cooling degree days (add heating degree days if the building heats with the same meter).
- Self-check rubric — you are ready to move on when: (1) you can state in one sentence what a low load factor implies for demand-side opportunities; (2) your regression intercept lands near your independent baseload estimate and you can explain any gap; (3) you have named two anomalous months and written one testable hypothesis for each; (4) you can say which single system you would investigate first and why the data pointed there.
Choosing Between Simple Payback, LCC, SIR, and IRR
Simple payback screens quickly but ignores measure life, the time value of money, and all cash flows after payback. Life-cycle cost, savings-to-investment ratio, and net present value answer different investment questions.
Learn each metric's definition and its proper role. Simple payback is first cost divided by annual savings — a screening number only. Net present value discounts future cash flows to today's dollars; the savings-to-investment ratio is the present value of savings over the present value of costs, useful for ranking independent measures within a fixed budget; life-cycle cost compares mutually exclusive design options by total discounted cost; and the internal rate of return is the discount rate at which net present value reaches zero. Picking the wrong metric for the question is the classic exam-style trap, because each metric can rank the same two measures differently.
Worked scenario: compressed-air leak repair costs $8,000 and saves $6,700 per year with an expected measure life of 2 years (payback about 1.2 years), while a compressor heat-recovery project costs $30,000, saves $5,000 per year, and lasts 15 years. The mistake is dropping heat recovery because its payback is six years — simple payback systematically favors short-lived measures and ignores everything after the payback point. The better decision is to report both metrics with measure life stated: discounted over each measure's own life, heat recovery's 15-year savings stream can beat the leak repair's 2-year stream. Why it matters: a capital plan ranked on payback alone under-invests in durable measures and misrepresents their value to the client.
Handling Interactive Effects Between Building Systems
Measures interact: lighting changes alter heating and cooling loads, envelope work shifts HVAC runtime, and compressed-air fixes change compressor cycling. Quantifying one measure in isolation can overstate or misstate package savings.
The lighting example is the standard illustration. Reducing lighting power cuts the cooling load, which adds savings in an electrically cooled building, but removes useful heat in a heating-dominated building, creating a heating penalty — in fuel, cost, or emissions terms depending on the heating source. Which direction dominates depends on climate, operating hours, heating fuel, and system type, so the claim itself must stay conditional. Envelope measures behave similarly: tightening a building can reduce HVAC energy but also change how internal gains and ventilation interact.
Build a habit for scenario questions: for each measure, classify its secondary effects on other systems, decide whether each interaction is material enough to model or small enough to bound with a stated assumption, and write the assumption down. A plausible mistake is an LED retrofit analysis in a gas-heated warehouse that claims the cooling savings while silently ignoring the heating penalty in fuel cost; the better analysis reports both, in dollar terms, with the climate and hours assumptions visible. This documentation habit connects directly to the reporting domain that follows.
Planning Data Collection: Nameplates, Spot Checks, Logging, or BAS Trends
Nameplate data, spot measurements, short-term logging, and BAS trending serve different purposes. The skill is matching the method to the quantity, its variability, and the confidence the eventual recommendation requires.
Map methods to system domains. Nameplates, drawings, and schedules establish capacity and context for everything. Spot measurements verify that reality matches the nameplate — for example, comparing measured motor current to full-load amps. Short-term logging captures duty cycles for intermittent equipment such as compressors, exhaust fans, or DHW heaters. BAS trending captures schedules, setpoints, and runtime across weeks, making it the tool of choice for controls and schedule findings. Lighting needs fixture counts and burn-hour estimates; motors and compressed air need load and runtime data; domestic hot water needs fuel use, temperature, and draw patterns.
The two mistakes to practice avoiding are opposite extremes. Logging every point for weeks inflates cost and delays the report; leaning on nameplates for highly variable loads produces numbers no better than guesses. A reasonable default: constant loads get a nameplate plus one spot check, variable loads get logged or trended, and controls findings get trends across at least a full weekly cycle. Whatever you choose, record dates, conditions, and instrument calibration — frameworks such as ASHRAE 211-2018 expect a documented measurement approach, and your savings claims inherit the credibility of the data behind them.
Structuring the Audit Report Against ASHRAE 211 and the DOE Guide
A usable report connects findings to recommendations, assumptions, and an implementation path. Frameworks such as ASHRAE Standard 211-2018 and the DOE Guide to Energy Audits describe the deliverables clients and compliance programs expect.
AEE describes the auditor's aim as providing survey results, risk mitigation analysis, an implementation plan, and, where called for, an investment-grade analysis — build your mental report template around that arc. Core elements include a facility description, the historical use analysis from the bill review, a measure list with savings and cost bases, an assumptions register, and an implementation sequence. When you study, practice assembling these pieces for a paper building rather than memorizing a generic outline, because the connecting logic is what scenario questions exercise.
A concrete drill: take one measure finding — say, a dirty evaporator coil or a fixed-speed pump running against a throttling valve — and write the full recommendation: condition found, proposed action, savings basis, cost basis, and every assumption the number depends on. Then apply the recomputation test: a colleague working only from your stated assumptions should be able to reproduce your savings estimate. If they cannot, the documentation is incomplete. That recomputation test is a self-check you can run on every practice answer and later on real deliverables.
A Preparation Sequence and Readiness Checks for the CEA Domains
Sequence study around the published body of knowledge: audit strategy and use analysis first, then data and economics, then the system domains, then reporting and mixed scenarios. Close each domain by writing decisions, not just definitions.
An adaptable sequence: spend the first block on audit strategy, the audit tiers, and utility use analysis, completing the bill exercise until the rubric passes. Next, drill economic metrics by re-ranking the same measure set under payback, SIR, and LCC until ranking differences feel predictable. Then work through the system domains — lighting, HVAC, domestic hot water, motors, drives and compressed air, envelope, controls, and on-site generation and storage — writing one short scenario per domain that includes an interaction. Finish with report structure and mixed case analysis. Compress or stretch the blocks to fit your available weeks.
Readiness checks before you sit the exam: compute and interpret load factor and a degree-day regression without notes; select the correct economic metric for three different decision types and say why; assign a data collection method to each system domain with a one-line justification; explain one interaction for each major domain and how you would bound it; outline a complete audit report from memory and pass the recomputation test on a practice measure. Treat these as learning milestones, not predictions of any score. Administrative details — eligibility, scheduling, and fees — are maintained by AEE on its certification page rather than here.
- Block 1: audit strategy, audit tiers, utility use analysis; complete the bill exercise and rubric.
- Block 2: economic metrics — payback, NPV, LCC, SIR, IRR — and metric selection drills.
- Block 3: system domains with one written scenario each, including a system interaction.
- Block 4: reporting structure, mixed case analysis, and the readiness checks above.
- Pair the sequence with practice question sets and re-attempt missed questions after writing the underlying decision in your own words.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.