Your solar development team is excellent. They’ve permitted dozens of projects. They know which environmental consultants to call, which civil engineers have relationships with local planning departments, which attorneys can navigate interconnection agreements. They’ve built a machine.

Now the market is demanding storage. Your interconnection queue position requires a battery component. Your offtaker wants dispatchable capacity. The economics of solar-only projects are compressing while hybrid and standalone storage pencil better every quarter.

So you tell your team to “add storage” to the next project. How hard can it be? It’s the same site, the same interconnection, the same county. You’re just adding some containers next to the inverters.

Six months later, your permit application is rejected. The Fire Marshal wants a Hazard Mitigation Analysis your team has never produced. Your civil engineer designed the pads to the wrong tolerances because nobody gave them a Design Basis Memo. Your electrical engineer undersized the station service transformer because they used solar auxiliary loads, not BESS thermal management loads. Your attorney is fielding questions about decommissioning bonds and battery recycling that weren’t in any solar permit you’ve ever pulled.

Your team isn’t incompetent. They’re facing a development process they’ve never encountered—one that requires disciplines, deliverables, and coordination protocols that don’t exist in solar development.

Welcome to the 504-task reality.

The Discipline Stack You Didn’t Know You Needed

Solar development requires a well-understood team: civil engineer, environmental consultant, electrical engineer, real estate attorney, and a development manager to coordinate them. These disciplines talk to each other in predictable ways. The civil engineer needs the wetland delineation before finalizing grading. The electrical engineer needs the interconnection requirements before sizing the substation. The workflows are established.

BESS development adds three disciplines that most solar teams have never worked with:

1. Fire Protection Engineer (FPE)

Solar projects don’t require fire protection engineering. Panels don’t explode. Inverters don’t emit toxic gases. The Fire Marshal reviews your site plan for access roads and hydrant locations—routine items handled by your civil engineer.

BESS projects require a dedicated Fire Protection Engineer who understands NFPA 855, UL9540A test interpretation, and the specific failure modes of lithium-ion battery systems. The FPE produces the Hazard Mitigation Analysis (HMA)—a document that doesn’t exist in solar permitting—and serves as your expert witness when the Fire Marshal has questions your civil engineer can’t answer.

The FPE’s work product governs your site layout. Their spacing requirements, setback calculations, and explosion control methodology determine how many megawatt-hours you can fit on your parcel. If you start civil engineering before the FPE establishes the fire safety design basis, you will redesign.

2. BESS Owner’s Engineer (BOE)

Solar projects use standardized equipment. Panels are commoditized. Inverters are mature. Your electrical engineer has designed dozens of systems and knows the parameters by heart. You don’t need a dedicated “solar technology expert” on your team.

BESS technology is not standardized. Different OEMs use different cell chemistries, different thermal management systems, different container configurations. Each technology has different degradation characteristics, different auxiliary power requirements, different foundation tolerances. The parameters that govern your electrical and civil design are technology-specific—and they’re not in your engineer’s standard library.

The BESS Owner’s Engineer bridges this gap. They evaluate OEM technologies, produce the Design Basis Memo that governs engineering, validate degradation curves against independent models, and review the technical exhibits in your Battery Supply Agreement. They’re the translator between the OEM’s product specifications and your engineering team’s design requirements.

Without a BOE, your civil engineer doesn’t know what pad tolerances to specify. Your electrical engineer doesn’t know what auxiliary loads to assume. Your development manager doesn’t know whether the OEM’s warranty claims are credible. You’re designing in the dark.

3. Decommissioning Planning

Solar decommissioning is straightforward. Remove the panels, pull the racking, restore the site. The materials are inert. Disposal is standard. Most jurisdictions require a decommissioning plan, but it’s a routine document your civil engineer produces as part of the permit package.

BESS decommissioning involves hazardous materials. Lithium-ion batteries require specialized handling, DOT-compliant packaging, and disposal at certified recycling facilities. The cost assumptions are different—you’re not scrapping steel, you’re managing a hazmat logistics chain. Many jurisdictions now require decommissioning bonds sized to cover battery disposal costs, and they’re scrutinizing the cost estimates more carefully than they ever scrutinized solar decommissioning.

Your civil engineer can produce the decommissioning plan document, but they need inputs they’ve never needed before: battery recycling methodology, hazmat transport costs, salvage value assumptions. Those inputs come from the BOE or FPE, not from civil engineering experience.

The Coordination Problem

Adding three disciplines to your team is hard enough. The deeper problem is that these disciplines must coordinate with each other—and with your existing team—in ways that don’t happen automatically.

Consider the information flows required for a BESS permit application:

• The FPE needs the UL9540A test report from the OEM to establish spacing requirements
• The BOE needs to validate that UL9540A report and incorporate spacing into the Design Basis Memo
• The Civil Engineer needs the Design Basis Memo before starting site grading design
• The Civil Engineer also needs the FPE’s water supply calculations to size on-site storage tanks
• The Electrical Engineer needs the BOE’s auxiliary load profile to size the station service transformer
• The Electrical Engineer needs the FPE’s isolation requirements to design the emergency shutdown logic
• The FPE needs the Electrical Engineer’s single-line diagram to verify the E-stop integration
• The Civil Engineer needs the FPE’s decommissioning methodology to complete the bond calculation

None of these handoffs are optional. If any link breaks—if the Civil Engineer starts grading design before receiving the Design Basis Memo, if the Electrical Engineer sizes transformers without the auxiliary load profile—you’ll discover the error during permit review or, worse, during construction.

In solar development, these coordination failures are rare because the disciplines have worked together for years. The civil engineer knows what the electrical engineer needs. The workflows are muscle memory.

In BESS development, these coordination failures are common because the disciplines are new to each other. Your civil engineer has never received a Design Basis Memo from a BOE. Your electrical engineer has never coordinated emergency shutdown logic with an FPE. The workflows don’t exist until someone creates them.

The 504 Tasks

When we mapped the complete BESS development process—from initial site screening through Notice to Proceed—we identified 504 discrete tasks organized across five phases:

Phase 100: Feasibility & Screening Desktop analysis to confirm site viability before committing capital. Environmental screening, preliminary code review, capacity yield analysis, and fatal flaw identification. This is where you kill bad sites—before you’ve spent money on engineering.

Phase 200: Site Investigation Field work to validate desktop assumptions. Wetland delineation, Phase I environmental assessment, ALTA survey, geotechnical borings, and utility locates. This phase produces the data your engineers need to design.

Phase 300: Design & Entitlements Engineering design and regulatory approvals. Civil plans, electrical single-line diagrams, the Hazard Mitigation Analysis, stormwater management, and the permit applications themselves. This is the longest phase—and the one where coordination failures are most expensive.

Phase 400: Procurement & Closing Finalizing commercial agreements and real estate. The Battery Supply Agreement, EPC contract, interconnection agreement execution, ALTA survey updates for title insurance, and financing closing. This phase converts your permitted project into a funded construction-ready asset.

Phase 500: Pre-Construction Services Technical support during construction mobilization. Issued-for-construction drawings, construction staking, RFI responses, and SWPPP inspections. This phase ensures the project you designed is the project that gets built.

Each phase contains dozens of tasks, each with predecessor dependencies, responsible parties, and deliverables. The civil engineer can’t start Phase 300 grading design until Phase 200 geotechnical borings are complete and the BOE has issued the Design Basis Memo. The FPE can’t finalize the HMA until the civil engineer provides the site layout. The permit application can’t be submitted until the HMA, civil plans, and electrical drawings are complete and coordinated.

Miss one dependency, and your schedule slips. Miss several, and your permit gets rejected.

Why Solar Teams Struggle

Solar developers who attempt BESS without restructuring their approach typically fail in one of three ways:

Failure Mode 1: The Missing Discipline

The team doesn’t engage an FPE or BOE because they don’t know they need one. The civil engineer designs the site using OEM marketing materials as the “design basis.” The permit application doesn’t include an HMA because nobody told the team it was required. The Fire Marshal rejects the application, and the team scrambles to find specialists—now on an emergency timeline with fees to match.

Failure Mode 2: The Broken Handoff

The team engages the right disciplines but doesn’t coordinate them. The BOE issues a Design Basis Memo, but nobody sends it to the civil engineer. The FPE establishes spacing requirements, but nobody updates the site plan. The electrical engineer sizes transformers using assumptions that don’t match the BOE’s auxiliary load profile. The errors compound until someone notices—usually during permit review, when fixing them requires rework across multiple disciplines.

Failure Mode 3: The Schedule Collapse

The team understands the dependencies but doesn’t manage them. The geotechnical report is late, which delays the civil design, which delays the permit application, which misses the planning commission deadline, which pushes the project into the next quarter. Meanwhile, the interconnection agreement has a milestone that assumes the original schedule. The project falls into a cascade of missed deadlines and extension requests.

Each failure mode has the same root cause: the development team is running a solar process on a BESS project. The tasks are different. The disciplines are different. The dependencies are different. Without a process designed for BESS, talented teams produce failed projects.

The Owner’s Representative Model

The solution isn’t to hire all these disciplines in-house. For most developers—especially solar teams adding storage to their portfolio—building permanent FPE and BOE capabilities doesn’t make economic sense. You need these disciplines for each project, but you don’t need them full-time.

The solution is an Owner’s Representative model: a development manager who understands the BESS-specific workflow, coordinates the specialist disciplines, and ensures the handoffs happen correctly.

This is different from traditional project management. A generic PM can track tasks and chase deadlines, but they can’t evaluate whether the Design Basis Memo is technically sound. They can’t assess whether the FPE’s spacing requirements are conservative or aggressive. They can’t catch a broken handoff they don’t understand.

The Owner’s Representative brings domain expertise to project management. They know which tasks have predecessor dependencies. They know which deliverables must flow between disciplines. They know when an OEM’s claims should be challenged and when a consultant’s estimate should be validated. They don’t replace your engineers—they ensure your engineers have the inputs they need, when they need them.

The Takeaway

BESS development isn’t solar development with batteries added. It’s a different process with different disciplines, different deliverables, and different failure modes. The solar team that treats storage as incremental complexity will discover—expensively—that they’re running the wrong playbook.

The 504-task reality isn’t meant to intimidate. It’s meant to clarify. When you understand the actual scope of BESS development, you can staff appropriately, budget accurately, and sequence correctly. When you pretend it’s “solar plus batteries,” you learn these lessons through permit rejections and schedule collapses.

The developers who build successful BESS projects are the ones who respect the complexity. They engage the disciplines they need. They coordinate the handoffs that matter. They run a process designed for the project they’re actually building.

Carina Energy provides BESS Development-as-a-Service, including Owner’s Representative services, specialist coordination, and Smartsheet-based project controls for utility-scale storage projects. Contact us to discuss your project.

Related Reading:

• The Fire Code Trap: Why Your BESS Permit Just Got Rejected
• Mineral Rights: The Silent BESS Project Killer
• The RFI vs. RFP Split: Why Locking Your OEM Too Early Destroys Economics