06 · Standards & compliance

Engineering sign-off: what makes a P.Eng. comfortable

Last updated 2026-04-21
Draft published
First-pass content live. Engineering review and Opnor-team validation in progress — see the "author backlog" callouts at the bottom.

Every Opnor audit deliverable carries a P.Eng. (Professional Engineer) sign-off. It's not a formality — it's the legal accountability that makes the audit defensible against a Hydro-Québec reviewer, a capital committee, or an OEQ (Ordre des ingénieurs du Québec) audit. This article covers what the sign-off actually means, what a P.Eng. needs to see before signing, and what makes a buyer's audit deliverable easy or hard to review.

What a P.Eng. sign-off means

A Professional Engineer signing an audit report is taking personal professional responsibility for the engineering analysis it contains. In Quebec, that's OEQ-regulated; in other Canadian provinces, equivalent regulators (PEO, APEGA, etc.) apply. If the analysis is materially wrong — savings claims that don't hold up, ECMs that fail in implementation because of an engineering error, capital committed on a deliverable that the reviewer should have caught — the P.Eng. is on the hook.

That accountability is the buyer's protection. A vendor without P.Eng. sign-off has no professional liability for the deliverable they hand you. If the savings don't materialize and the project goes over budget, the recourse is contractual, not professional.

What the engineer needs to see before signing

The OEQ's standard of practice requires the signing engineer to:

  • Have personally observed (or had a directly-supervised junior engineer observe) the major loads in operation. Hence the on-site walk-through requirement on Level-2 audits.
  • Trace every savings number to a defensible engineering formula. Black-box ML outputs without traceable math don't pass review.
  • Document the data quality of every input (the confidence-scoring model is built for this).
  • Apply realization factors that account for known sources of theoretical-vs-real divergence.
  • Flag any ECM where confidence is below the threshold needed to advance to capital allocation.
  • Include a methodology section sufficient for a peer reviewer to reproduce the analysis.

Opnor's deliverable structure is built to satisfy these requirements directly. The Audit Engine produces traceable formulas (not ML scores), the confidence model documents data quality per asset, the cost engine outputs AACE-classified estimates, and the report template includes the methodology section the reviewer needs.

What makes review easy or hard

Engineers who've signed off on a lot of audits develop a sense of which deliverables are trustworthy on first read and which need deep auditing. The signals:

Easy to review
Per-asset savings table with formulas. Confidence scores per asset. Realization factor explicit and justified. ECMs flagged by confidence, not just by absolute savings. Cost estimates AACE-classified with a contingency rationale.
Hard to review
Aggregate savings only, no per-asset breakdown. ML-based savings predictions without underlying formulas. Single confidence score for the whole site. Cost estimates without AACE classification. ECM list ranked only by absolute savings (no payback context).

A buyer evaluating audit vendors can ask one question that surfaces this gap fast: "Show me the formula behind a single ECM's savings number on my plant." Vendors with traceable methodology will pull up the formula and walk you through it. Vendors with model-based approaches will deflect to capability descriptions.

The 'audit-grade' label
Some vendors describe their deliverables as "audit-grade" without a P.Eng. sign-off. The phrase is unregulated. Without the sign-off, the deliverable can't be submitted to Hydro-Québec under SEA, can't be used to authorize regulated capital expenditure in most jurisdictions, and carries no professional liability. Treat "audit-grade" without sign-off as a marketing term, not an engineering claim.

Who signs at Opnor

Every Opnor deep-dive audit is signed by a P.Eng. registered with OEQ for Quebec engagements (or the equivalent provincial body for non-Quebec work). The signing engineer is named on the report cover and is the contact for any review questions from Hydro-Québec or from the buyer's capital committee.

For non-audit deliverables (the free Energy Makeover Report, the EMD), no P.Eng. sign-off is included — these tiers are screening tools, not engineering deliverables. The 2-week Deep-Dive Audit is the tier that carries sign-off and is the only tier that's SEA-eligible as a funded engineering deliverable.

What this means for buyers outside Quebec

For audits in other Canadian provinces, the equivalent regulator (Professional Engineers Ontario, APEGA in Alberta, EGBC in BC) defines the local standard of practice. The Opnor team includes engineers registered in multiple jurisdictions; for a non-Quebec audit, the sign-off comes from an engineer registered locally.

For audits in the US or international engagements, the framework shifts to AEE Certified Energy Manager (CEM) credentials and ASHRAE Level-2/3 compliance. Opnor team members hold CEM credentials and the deliverable format adapts accordingly. Different stamp on the cover; same engineering rigour underneath.

🚧 Author backlog (Opnor team to fill)
  • Document Opnor's signing-engineer roster and registration coverage by province
  • Add a sample sign-off statement (the boilerplate text that appears on Opnor audit reports)
  • Cross-reference the OEQ Code of Ethics requirement clauses that apply to energy-audit deliverables