EnerGuide ratings vs. rebates: what’s the difference?

An EnerGuide rating is a standardized evaluation output.
A rebate/financing approval is a program decision based on program rules and documentation.

They overlap—but they are not the same thing.

Treat the rating, the upgrade work, and the program file as connected but distinct records. A project can have a useful rating without qualifying for a particular offer, and a program can require evidence beyond the rating itself.

What a rating is good for

• establishing a baseline
• comparing modeled scenarios
• providing standardized outputs for certain workflows

What a rating is not

• a guarantee of program eligibility
• a guarantee of real-world performance (installation quality matters)
• a substitute for complete invoices and product documentation

The practical takeaway

If you want the smoothest path:

1. Review the current program rules with the program administrator before purchase.
2. Confirm which evaluation, timing, products, and records the program requires.
3. Ensure quotes and invoices contain the required information.
4. Keep product labels, exact model numbers, and useful installation photos.
5. Retain the rating documents and the program correspondence as separate evidence.

Questions to resolve early

• Is an evaluation required before work starts or before a purchase?
• Which party confirms product or measure eligibility?
• Do equipment combinations need to appear on a particular list?
• What must appear on the final invoice?
• Which records must be retained after installation?

Answers can differ by program and can change over time. Use the administrator’s current published requirements and direct confirmation for the actual file.

Where support fits

Kates Energy can help organize rating inputs, review documentation for missing fields, and explain what a technical output does and does not establish. That support is not program administration and cannot promise eligibility, funding, financing, or approval.

When requesting a quote, name both goals: the building-performance decision and the program workflow. This prevents a rating deliverable from being mistaken for the whole application file.