Every Solar Project Is Different. That's the Point.
Non-residential solar projects have profound differences that engineers see and non-engineers consistently underestimate. That's why AutoCAD persists — and why templates don't work.
Every Solar Project Is Different. That's the Point.
"Why can't you just copy the last one?"
Every solar engineer has heard some version of this from a project manager, a company owner, or a client who doesn't understand why engineering takes as long as it does.
What two "identical" 500kW projects actually share
Two commercial rooftop projects with the same system size can share virtually nothing in their construction documents.
Roof geometry. One building is a flat membrane with minimal obstructions. The other has standing seam metal with 14 HVAC units, 3 skylights, and a parapet that varies in height. The proposal shows a rectangle. The construction documents show a jigsaw puzzle.
Structural conditions. Ballasted racking on the flat roof. Mechanically attached mounts at specific purlin locations on the metal roof. The attachment points dictate panel placement at a precision level that didn't exist at the proposal stage.
Electrical equipment. String inverters on the roof versus a central inverter in a ground-level electrical room 200 feet away. Same system size. Completely different homerun routing, cable lengths, and conduit paths.
AHJ requirements. One jurisdiction on NEC 2023 with module-level rapid shutdown. The other still on NEC 2017 with different labeling rules and a one-off conduit fill requirement. Same state. Different county. Different drawings.
Racking, client standards, equipment specs. Portrait versus landscape orientation changes string routing. One client wants strings labeled S-1, S-2 on layer E-SOLAR-HR. Another wants STR-A01 on ELEC-HOMERUN. Same information. Different everything.
These aren't edge cases. This is every project.
Why AutoCAD persists
Non-engineers look at AutoCAD — 40 years old, not cloud-native, no modern UI — and see legacy software. Engineers see the only tool that imposes no assumptions about their project.
AutoCAD is a blank canvas with precision tools. The engineer controls every layer, block, line weight, and text style. They can match any company standard, any AHJ requirement, any client preference. They can build custom blocks for equipment that doesn't exist in any vendor's library.
Web-based solar tools make different trade-offs — guided workflows and polished interfaces in exchange for control over the output. For proposals, that trade-off makes sense. For construction documents — bespoke technical drawings built to site-specific conditions, client-specific standards, and AHJ-specific requirements — the trade-off breaks down.
Engineers aren't resisting progress by staying in AutoCAD. They're using the tool that handles the reality of their work.
The right kind of automation
None of this means drafting in AutoCAD can't be automated. Drawing polylines along string paths, routing homeruns, measuring cable lengths, placing tags — this work is mechanical and repetitive even though the inputs change on every project.
The key is automating the drafting without automating away the flexibility. Accept the engineer's inputs — their string configuration, their equipment locations, their layer standards — and produce drafting objects that respect those inputs. Don't impose a template. Don't require projects to fit a mold.
Every solar project is different. The tool that handles them all is the one that doesn't pretend otherwise.
Leaf automates drafting in AutoCAD without imposing templates or workflows. Your inputs, your layers, your standards — automated. Start a 14-day free trial — no credit card required.