When this is useful
- A code, label, or program file needs clean supporting documentation.
- Drawings, specs, invoices, or product data need to align before submission.
- You want to reduce avoidable rework without overstating approvals.
Compliance & Documentation
Code Compliance Support
Project-specific compliance documentation support aligned to the selected pathway and AHJ expectations.
Fit and next step
Use this scope when it helps the next decision.
The quote request can start with the service selected. Files are still optional at intake.
What you receive
- A clear list of required inputs and current gaps.
- Documentation notes aligned to the chosen pathway or label workflow.
- Boundaries on what Kates Energy can support and what administrators confirm.
There can be more than one way to demonstrate energy-code compliance. The useful work is choosing and documenting a pathway early enough that drawings, specifications, envelope assumptions, and mechanical assumptions tell the same story.
Kates Energy supports that technical file. The authority having jurisdiction (AHJ) remains the source for permit expectations and acceptance.
A good fit when
- the team is comparing available compliance pathways
- design decisions are changing and assumptions need control
- drawings and specifications need a consistency check
- an AHJ submission needs a clearly organized supporting package
What the scope can include
- pathway and deliverable clarification with the project team
- review of the inputs needed for the selected method
- alignment checks across relevant drawings, schedules, and specifications
- modelling or calculation support where included in the agreed scope
- an assumptions and open-items record for handoff
What to prepare
Share the building type, jurisdiction, project stage, current drawings and specifications, mechanical information, and any AHJ direction already received. Identify the permit milestone and the person responsible for the final submission.
Boundaries
We do not replace the AHJ, promise permit approval, or make unresolved design decisions on behalf of the responsible project professionals. A review is tied to the documents and assumptions supplied at that time; later changes may require an update.
Next step
Request a quote with the jurisdiction, building type, current design stage, intended pathway if known, and submission timing. If the pathway is still open, say so—the first useful task may be a bounded comparison rather than a full documentation package.
Related services
Often used alongside this scope.
These pairings reflect the existing service map and keep the page focused on adjacent decisions, not extras.
Compliance & Documentation
Labels Support
Readiness and documentation alignment for EnerGuide, ENERGY STAR, and Built Green workflows.
Diagnostics
Envelope Analysis
Assembly and transition review to identify continuity risks and practical correction opportunities.
Compliance & Documentation
CSA F280-12 Heat Loss and Peak Load
Heat loss and peak load documentation to support equipment sizing with clear assumptions.
Related resources
Short reads that help frame the scope.
These links stay close to the topic so the next conversation starts with context, not blank paper.
ghg / emissions
GHG analysis: why emissions outcomes can differ from energy outcomes
Why two upgrades with similar energy savings can have different emissions impacts—and how to compare pathways.
energuide / energy-star
Label readiness checklist (EnerGuide / ENERGY STAR / Built Green)
A practical pre-checklist to reduce friction in labelling workflows: specs alignment, documentation, and verification readiness.