energy savings: What the inputs describe
Estimate annual HVAC energy and cost savings from a baseline, reduction percentage, and local energy price.
The Thermostat Savings result is a scenario check; final decisions still need project climate, schedule, envelope, and equipment assumptions.
If Electricity price ($/kWh) changes later, keep the old energy savings worksheet so the difference can be traced.
Using the output for energy savings
Use the Thermostat Savings result to rank scenarios, not to declare a final load or utility bill prediction by itself.
Break irregular energy savings work into separate runs when Baseline monthly HVAC energy (kWh) or Expected reduction (%) changes instead of averaging the conditions.
A clean-looking result can still be wrong if the scope changed underneath it for energy savings. Compare Baseline monthly HVAC energy (kWh) and Electricity price ($/kWh) against the same drawing date or field visit before carrying the number forward.
Before saving the energy savings result, consider whether Heating Cost Calculator should estimate energy and cost for a modeled heat load and operating period.
energy savings: Estimate questions
Does the calculation include comfort or humidity for energy savings before comparing scenarios?
No. Comfort, humidity, ventilation balance, and control behavior need separate review even when the energy arithmetic is correct on the energy savings worksheet.
When is a low and high case useful for energy savings when Expected reduction (%) is uncertain?
Use two cases when the operating schedule, weather, insulation level, or equipment performance is uncertain with Baseline monthly HVAC energy (kWh) as the audit point. The spread is often more useful than a single point estimate before carrying energy savings forward.
Is this enough for final equipment selection for energy savings when a supplier value changes?
Not by itself. It is a transparent screening calculation; final sizing can require climate data, envelope details, infiltration, occupancy, equipment curves, and a recognized load method with Baseline monthly HVAC energy (kWh) as the audit point. Keep Baseline monthly HVAC energy (kWh), Expected reduction (%), and Electricity price ($/kWh) on the same energy savings scope basis.
Which input should be sensitivity-tested for energy savings when energy savings conditions are not uniform?
Start with Baseline monthly HVAC energy (kWh), then vary Electricity price ($/kWh). Energy results can swing when operating schedules, efficiency assumptions, or weather assumptions move together for this energy savings scope.
Why might a utility bill disagree with the result for energy savings when ordering or sizing depends on it?
Bills combine weather, schedules, standby loads, rate tiers, taxes, and equipment cycling that a single calculator cannot fully reproduce while checking Baseline monthly HVAC energy (kWh).
Scope checks
- Confirm Baseline monthly HVAC energy (kWh) for energy savings from the latest drawing, field measurement, or product schedule.
- Keep Expected reduction (%) and Electricity price ($/kWh) tied to the same energy savings scope revision before saving the result.
- Test a realistic low and high operating case instead of relying on one default scenario for this energy savings scope.
- Use project climate, envelope, schedule, and equipment data for a final decision for energy savings.
Before final use
A correct energy savings calculation can still miss climate, infiltration, thermal bridges, solar gain, occupancy, equipment curves, and controls, so review those items outside the worksheet.
energy savings: Before carrying the result forward
The Thermostat Savings Calculator uses dedicated thermostatSavings inputs rather than a generic package or area substitute. Check each displayed energy savings assumption against product data, field conditions, and the decision described in the result.
Check whether Baseline monthly HVAC energy (kWh) and Expected reduction (%) describe the same physical condition before trusting the energy savings result.
Look for the condition that makes energy savings non-repeating: a different room, slope, product size, zone, rate, or access constraint. That condition usually deserves its own run instead of being averaged into Baseline monthly HVAC energy (kWh).
Data to collect before calculating
Use actual values where the label asks for them; old quotes and rule-of-thumb allowances should not drive the energy savings result.
- Baseline monthly HVAC energy (kWh)
- Document where this energy savings value came from if the result will be reused.
- Expected reduction (%)
- Use a project-specific value for Expected reduction (%) before relying on the energy savings result.
- Months in comparison period
- Keep this energy savings input on the same scope basis as the rest of the form.
- Electricity price ($/kWh)
- Use the rate basis that matches the energy savings quantity; a mismatched price can distort the total.
When energy savings has repeated areas, calculate the unusual condition separately before adding it to the total.
Calculation basis
The Thermostat Savings calculation is useful when assumptions are changed deliberately instead of left as a single default case.
Resolve drawing and field conflicts around Baseline monthly HVAC energy (kWh) for energy savings before calculating; averaging them can make the estimate less useful.
A quick calculation check for energy savings
Inputs used in the example: Baseline monthly HVAC energy (kWh) = 900, Expected reduction (%) = 8, and Months in comparison period = 12.
Output from the sample: 864 kWh saved.
Use the sample to catch unit mistakes before entering the real energy savings numbers.