Resources · Report Templates

The nine EEP report types

Every output EEP produces is permit-shaped and sealable by a licensed P.E. / P.Eng. Section structure, source citations, and trace audit follow the EEP Master Rulebook v5 Chapter 15 specification — RPT-001 through RPT-009.

Free Beta Access — All EEP report generation is unlocked during public beta. No charges until launch. Run a project and export RPT-001..009 right now.

Report types — Rulebook v5 §15.3

Each report type addresses a specific audience and stage of the engineering review process. Reports are generated from the same underlying calculation state — they cannot disagree on a number.

RPT-001P.Eng · AHJ

Engineering Calculation Report

Full input summary, calculation trace, assumption list, source references, warnings, errors, overlay status, and Professional Review Notice. The complete record an engineer of record signs and seals before AHJ submission.

InputsTraceStep[]AssumptionsSourceRef[]WarningsErrorsOverlaysPRN
RPT-002Engineer · Owner

Engineering Summary

High-level one-page summary: service size, conductor selection, OCP rating, VD compliance, and key warnings. Designed for stakeholders who don't need the full trace.

Service sizeConductorOCPVD %Key warnings
RPT-003P.Eng · AHJ

Code Compliance Trace Report

Step-by-step CEC 2024 or NEC 2023 rule references for every calculation decision. Many plan examiners require this level of documentation for permit approval.

Per-step ruleCanonical IDsFormulaSubstitutionResult
RPT-004Engineer · Designer

Warning Report

All warnings produced during calculation, classified by severity: INFO · WARNING · CRITICAL. Each warning includes the code, message, affected element, and the CEC/NEC rule reference.

By severityElement IDRule refSuggested fix
RPT-005Engineer · Reviewer

Assumption Report

All assumptions used in the calculation: type (default / mandatory / engineering), source (rule basis), and whether user-confirmed or defaulted. ASM-001 through ASM-008 plus any model-specific assumptions.

ASM-001..008Confirmed / DefaultSource basis
RPT-006Engineer · Reviewer

Source Gap Report

All source gaps encountered with impact assessment and required verification steps. SGP-001 (Section 62 heating) through SGP-006 (HV shielded), plus any new gaps. Tells the engineer what data is missing and what to verify.

SGP-001..006ImpactVerification stepBlocking flag
RPT-007Contractor · Inspector

Panel Schedule Report

Panel schedule with full circuit list, phase balance percentages, OCP sizes, conductor sizes, neutral, EGC, GFCI/AFCI tagging, and continuous-load 125% factor where applied.

Circuit listPhase balanceOCPConductorNeutral/EGC
RPT-008Contractor · Inspector

Feeder Schedule Report

All feeders with conductor size, OCP, voltage-drop results, conduit fill, run length, terminal-temp column used, and overlay status (motor / patient-care / fire-pump / EVSE).

Per-feeder rowConduit fillVD %Overlay status
RPT-009Admin · Engineer · AHJ

Audit Trail

All project actions, calculation versions, user IDs, timestamps, and result hashes. Append-only — no API exists to modify a logged action, by design.

ActorActionTimestampDiffResult hash

Required elements — Rulebook v5 §15.1

Ten elements that must appear in every Engineering Calculation Report (RPT-001) and in any combined export. None of these can be suppressed by any user role.

ElementWhat it containsSource
Input SummaryAll user-provided inputs with values, units, and confirmation status.User input JSON
Assumption ListASM-001..008 plus model-specific. Type, default vs confirmed, basis.AssumptionRegistry
Calculation Trace StepsTraceStep[] for every calculation: stepId · ruleId · formulaId · inputs · substitutedFormula · result · sourceRef.All engine outputs MANDATORY
Code Source AppendixAll canonical IDs used: CEC2024-T2, CEC2024-T5C, NEC2023-T220.12, etc. Never refer to a table by description alone.SourceRef[] aggregated
Warning SummaryAll EngineeringWarning[]: code, severity (INFO/WARNING/CRITICAL), message, rule reference.Engine warnings
Error SummaryAll EngineeringError[]: code, message, blocking flag, rule reference.Engine errors
Source Gap ReportEvery SGP item: what is missing, what EEP displayed, blocking status. SGP-001..006 and any additional.SourceGapRegistry
Export ManifestMachine-readable metadata: timestamp, EEP version, module IDs, input hash, output hash.System metadata
Professional Review Notice"Results require licensed P.Eng/P.E. review." CANNOT BE DISABLED OR SUPPRESSED. Appears on every page.System — hardcoded
Special Overlay StatusStatus of all overlays: RESOLVED / UNRESOLVED / NOT_APPLICABLE. Motor, transformer, patient-care, fire-pump, emergency, EVSE, PV/ESS, pool/spa, heating, hazloc.SpecialOverlayResult[]

Must-not rules — Rulebook v5 §15.2

Hard prohibitions enforced at the API layer

  • No engineering calculation in the report layer. All math lives in TraceStep[]. The report renderer is display-only — no hidden formulas.
  • No code-compliance claim without TraceStep[] + SourceRef. Unverifiable compliance is a liability and regulatory risk.
  • No AHJ approval claim. AHJ decisions are outside EEP scope. The platform never auto-approves a design.
  • ADVISORY_ONLY label must appear in every contractor report. Contractor-tier outputs carry the label hard-coded — no role can suppress it.
  • Professional Review Notice on every export. Disclaimer is hardcoded and mandatory across all roles.
  • Canonical table IDs only. Reference CEC/NEC tables by canonical ID (CEC2024-T2), never by description.
  • No tampering with stored results. All results are hashed. Any modification creates a new version — never overwrites the previous one.

Good engineering practice — Rulebook v5 §15.4

PracticeDetail
Every page carriesProject name · Report date · EEP version · "PRELIMINARY — FOR REVIEW ONLY" stamp until a licensed P.Eng / P.E. reviews and accepts the report.
Tamper-evident storageAll generated reports stored in the project audit log with a hash. Any modification after generation creates a new version — never overwrites.
AHJ submissionAlways include RPT-003 (Code Compliance Trace Report). Many plan examiners require rule-by-rule traceability before permit approval.
Standard disciplineNEC and CEC engines never mix. A project locked to CEC_2024 never produces a citation to NEC, and vice versa. Cross-contamination is impossible at the engine layer.

Export formats

FormatWhen to usePrimary audience
PDFPrimary deliverable. Embedded fonts, A-size or Letter, electronic-seal compatible.AHJ submittal · P.Eng signature
DOCXEditable Word output for jurisdictions that require RFI-style markup.Plan reviewers, RFI handlers
XLSXPanel schedules and feeder schedules as spreadsheets for downstream consumers.Contractors, estimators
SVG / DXFSingle-line diagrams in vector format for import into CAD.CAD operators, drafters
JSONFull TraceStep[] audit log for record retention or external review tools.QA, archives, third-party review
Generate your first report → Read the full spec