Phase 0 Resource · mep
Electrical Service Sizing Calculation Inputs: Delivery Records
Service sizing requires a coordinated load inventory and the applicable utility and electrical-code criteria. This delivery perspective focuses on connected loads, demand, motors, continuous loads, EV charging, emergency systems, and utility data.
By Apex Grid Engineering · Updated 2026-09-15
Issue a usable delivery record
Service sizing requires a coordinated load inventory and the applicable utility and electrical-code criteria. This delivery perspective focuses on connected loads, demand, motors, continuous loads, EV charging, emergency systems, and utility data. At delivery, the question is whether the next person can identify, open, rely on, and coordinate the correct record. For mep, preserve connected loads, demand, motors, continuous loads, EV charging, emergency systems, and utility data; the governing code or AHJ checklist; current architectural and engineering backgrounds; assumptions that need confirmation; and a record of unresolved decisions. in the transmittal or controlled project index. State what is included, what is excluded, which revision is current, and what action remains with the recipient.
Handoff details that prevent rework
A electrical service sizing calculation inputs: delivery records handoff should identify the recipient, issue date, file names, revision, source documents, professional seal or signature status when applicable, and dependencies outside the package. Explain the practical interface: what the architect must coordinate, what the contractor must verify in the field, what the owner must decide, and what the AHJ may still request. Never treat an uploaded file as proof that another party accepted it.
- Controlled transmittal and revision identifier
- Drawing, calculation, schedule, and specification references
- Field, product, utility, or testing dependencies
- Recipient action and response date when known
- Archive location for superseded and final records
Manage changes after issue
Changes to mep information can be triggered by a substitution, field condition, correction notice, owner decision, or authority comment. Compare the change with the issued basis before replacing a file. Mark affected documents, update the index, explain the reason for revision, and have the responsible professional determine whether the change requires a new calculation, seal, site verification, or AHJ submission.
Closeout is evidence, not a promise
A complete delivery record helps a project team locate what was issued and what remains open; it does not certify concealed construction, guarantee inspection results, or transfer responsibility for work outside the defined scope. Retain the accepted transmittal, response, field evidence, and final revision according to the project record requirements, and identify any deferred or delegated work plainly.
Related Engineering Resources
Frequently Asked Questions
What belongs in the delivery record for electrical service sizing calculation inputs: delivery records?
What happens when the project changes after issue?
Does transmitting a document transfer responsibility?
Discuss your engineering scope
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Start an Engineering Estimate