Engineer of Record EOR

What the seal asserts, and what it does not

Licensure is jurisdictional. A PE licence is issued by a state board — a provincial association in Canada — and the seal on a permit set must come from someone licensed where the work is built, not where the office sits. NCEES administers the examinations and operates the records programme that makes comity licensure practical, but each board still decides who may seal, what must be sealed, whether digital seals are accepted, and what counts as responsible charge. Those rules are the binding text, not any national standard.

The seal runs outward, not inward. It says a licensed individual stands behind the design; it does not say anyone else has checked it. Approval is a separate act performed by separate parties: the AHJ through plan review and permit, the utility for the interconnection facilities, the owner through its own acceptance process. A sealed set can be rejected in plan review, and a permitted set still needs the seal.

The convention is regional. Much of Europe allocates design responsibility through building-control regimes, national fire and building authorities, and contractual designer duties rather than through an individual's stamp, so a project outside North America may have a clearly responsible designer and no document that looks like a sealed drawing. Do not assume the stamp exists everywhere, and do not assume its absence means nobody is responsible.

Three seals, not one

The civil/structural EOR owns the ground and the load path: foundations and pads under the DC blocks and PCS skids, anchorage, wind and seismic design, bearing capacity, grading and drainage, access roads and fire-service turning radii, and any retaining structures. This is not a detail exercise on modern hardware — a 20-ft container at around 5 MWh is a heavy, tall, wind-exposed object bolted to a pad, and its anchorage detail has to survive the same event the enclosure was listed for.

The electrical EOR owns the one-line diagram, the MV collection system, grounding and bonding, protection coordination and relay settings, cable sizing and ampacity, the arc-flash study, and the AC and DC scope out to the point of interconnection, all against the NEC edition the jurisdiction has adopted. The fire-protection EOR usually holds the seal on the Hazard Mitigation Analysis submitted with the NFPA 855 permit package, along with detection, suppression, the deflagration venting or prevention strategy under NFPA 68 or NFPA 69, and the water-supply analysis.

Because nobody seals the whole plant, the interfaces between the three are where designs fail. A setback the fire-protection EOR justified from unit-level UL 9540A data, then narrowed by a civil re-layout to fit a drainage swale. An anchorage detail that lands on a listed penetration. A cable trench routed under a container clearance the hazard analysis assumed would stay open. Someone has to hold the interfaces, and on most projects that someone is the EPC contractor's lead designer or the owner's engineer, neither of whom can seal on another discipline's behalf.

Where the listed equipment stops and the EOR starts

The integrator supplies a type-tested product. A UL 9540-listed enclosure arrives with its internal DC architecture, rack layout, battery management system, internal detection and suppression already inside the listing scope, and the EOR incorporates that product rather than redesigning it. This is a hard line. Changing what is inside — a different cell revision, a modified thermal-management arrangement, extra penetrations — can push the delivered hardware outside the certified configuration, and the certified configuration is a procurement interface, not a formality.

The EOR's scope begins at the enclosure boundary and runs outward: foundation and anchorage, spacing and setbacks under the adopted NFPA 855 edition, AC and DC terminations, grounding, cable and raceway, protection, and the site-level fire and gas strategy.

Get the listing scope and the UL 9540A report for the exact model in hand before the layout freezes, because any reduced setback the EOR draws rests on that data. And keep the two documents straight when you cite them — UL 9540 is the ESS safety certification, UL 9540A is the fire-propagation test method, and a plan reviewer notices immediately when a sealed submittal names one and plainly means the other.

Issued for permitting versus issued for construction

Drawing states are industry convention, not statute, and the titles vary between firms. An issued-for-permitting set (IFP) is sealed and submitted to the AHJ to demonstrate code compliance: site plan with separation distances, the one-line, the fire and gas strategy, the hazard mitigation analysis. It is complete enough to be reviewed and permitted, and it typically still carries vendor content as preliminary or by-others, because integrator submittals often postdate the permit application by months.

An issued-for-construction set (IFC) is sealed as buildable. It incorporates the AHJ's conditions of approval, the vendor's approved submittals, and the interface details that were open at permit stage, and it is the only set a contractor is entitled to build from. Building from a permit set is a recognisable field failure: the crew discovers a conduit route or a foundation bolt pattern was still preliminary when it was drawn.

The seal itself does not change form between the two — it is the same declaration of responsible charge — but the scope of what is being declared does. On IFP the engineer asserts the design as presented meets the code being reviewed. On IFC the engineer asserts the documents are complete and coordinated enough to construct.

After IFC, changes move through the RFI and field-change process, and revised sheets are reissued and resealed under a revision number; a marked-up print in a site trailer is not a design change. Record drawings capture what was actually installed from contractor-reported field conditions and are generally not a fresh design seal, but confirm what your jurisdiction and your contract require, because practice varies.

The liability tail, and what augmentation does to it

The EOR is not the owner's engineer, who advises without sealing; not the independent engineer, who reviews the sealed set for lenders and carries no licensing liability for it; and not the integrator's product engineering team, who own the listed box while the EOR owns the installation around it. How long the seal can be reached is set by the jurisdiction's statutes of limitation and repose and by whatever professional liability cover the firm carries. Those durations vary by state and are statutory, so never carry an assumption across a state line.

Storage stretches that tail in a particular way. What the EOR seals is fixed at COD, but the plant does not stay fixed — augmentation adds racks and often whole enclosures in year eight or ten to a site permitted years earlier, under whatever code edition the AHJ has adopted by then.

The added capacity is new work: it needs its own sealed design and its own review, and the original hazard mitigation analysis does not stretch to cover it. Reserve the augmentation footprint, the DC bus headroom and the spacing in the permitted layout at the start, or the year-ten addition becomes a fresh permitting exercise with a fresh set of seals.