Quick answer
The structured process for reviewing, approving, and revising solar system designs before they proceed to permitting and installation — including peer review checkpoints, engineering sign-off, customer approval, and version tracking to catch errors before they become costly field problems.
Key Takeaways
- A structured design review workflow catches up to 80% of errors before they reach the field, where fixes cost 100x more
- Four review types work together: self-review checklists, peer review, engineering review (PE stamp), and customer approval
- The error cost multiplier is steep — $10 to fix in design, $100 in permitting, $1,000 in the field, $10,000 in warranty
- Version tracking prevents the most common review failure: building from an outdated design revision
- Companies with formal review workflows report 60–70% fewer permit rejections and installation change orders
- Cloud-based solar design software enables real-time collaborative reviews, replacing slow email-based markup cycles
What Is a Design Review Workflow?
A design review workflow is the sequence of review checkpoints a solar system design passes through before it moves to permitting and installation. Each checkpoint has a specific reviewer, a defined scope, and pass/fail criteria. The goal is to catch errors when they are cheap to fix — on screen — rather than expensive to fix — on the roof.
In practice, most solar companies run some version of a design review. The difference between companies with low change-order rates and those with high ones is whether the review is formalized or ad hoc. An ad hoc “quick look” misses errors that a structured checklist catches every time.
A single misplaced conduit run or incorrect inverter selection caught during design review saves an average of $800–$1,200 in field rework costs per residential project. For a company installing 500 systems per year, that translates to $400,000–$600,000 in avoided waste — dwarfing the cost of the review process itself.
Types of Design Reviews
Self-Review Checklist
The original designer reviews their own work against a standardized checklist before submitting to anyone else. Covers panel placement, string sizing, setback compliance, electrical calculations, and BOM accuracy. Catches 40–50% of all errors — the fastest and cheapest review stage.
Peer Review (Designer-to-Designer)
A second designer reviews the work with fresh eyes. Peer review catches errors the original designer is blind to — assumption errors, overlooked obstructions, and code misinterpretations. Most effective when the peer reviewer has not seen the site before, forcing them to evaluate the design on its own merit.
Engineering Review (PE Stamp)
A licensed Professional Engineer reviews structural and electrical calculations, verifies code compliance (NEC, ASCE 7, local amendments), and stamps the permit package. Required by most AHJs for systems above a certain size. This review focuses on safety and regulatory compliance rather than layout optimization.
Customer Approval Review
The homeowner or building owner reviews the final design, confirms panel placement preferences, and signs off on system size, production estimates, and financial terms. This is both a quality checkpoint and a legal step — documented customer approval protects against disputes later.
Review Stages at a Glance
| Review Stage | Who Reviews | What They Check | Common Errors Caught | Time Required |
|---|---|---|---|---|
| Self-Review | Original designer | Panel layout, string sizing, setbacks, BOM | Misplaced panels, wrong module count, setback violations | 15–30 min |
| Peer Review | Second designer | Design assumptions, code compliance, obstruction mapping | Overlooked shading, incorrect roof pitch, wiring errors | 20–45 min |
| Engineering Review | Licensed PE | Structural loads, electrical calculations, NEC compliance | Undersized conductors, inadequate racking, grounding errors | 1–3 hours |
| Customer Approval | Homeowner / building owner | Panel aesthetics, system size, production and cost estimates | Panels on wrong roof face, size mismatch with budget | 1–7 days (response time) |
The Error Cost Multiplier
$10 in design → $100 in permitting → $1,000 in the field → $10,000 in warrantyThis multiplier is consistent across construction industries, and solar is no exception. An incorrect string size caught during self-review takes 2 minutes to fix — a quick edit in cloud solar design software. The same error caught during permit review requires a resubmission, a new stamp, and a 2–4 week delay. Caught in the field, it means a truck roll, rewiring labor, and potentially new equipment. If it reaches a warranty claim, it means a return visit, customer dissatisfaction, and possible legal exposure.
The multiplier is not linear. Each stage roughly adds a zero to the cost because each stage adds new dependencies: permit fees already paid, crews already scheduled, materials already ordered, and customer expectations already set.
According to NREL’s analysis of solar soft costs, design-related errors account for a significant share of rework in residential installations. Companies that implement formal design review processes report catching approximately 80% of errors that would otherwise reach the field. The remaining 20% are typically site-specific conditions that no amount of remote review can fully predict — roof conditions hidden under shingles, electrical panel issues behind closed covers, or structural problems invisible from aerial imagery.
What Each Review Should Cover
Self-Review Checklist
The self-review is the designer’s last pass before handing off. It should be a written checklist, not a mental scan. Key items:
- Panel layout — All panels within roof boundaries, respecting fire setbacks (IFC pathways), ridge/eave/rake offsets, and obstruction keep-out zones
- Module selection — Correct module model, wattage, and dimensions match the BOM and the layout
- String sizing — Voc at lowest expected temperature is within inverter maximum input voltage; Vmp at highest expected temperature is within MPPT range
- Inverter selection — DC/AC ratio is within acceptable range (typically 1.0–1.35); clipping losses are acceptable
- Electrical — Wire gauge, conduit sizing, overcurrent protection, rapid shutdown compliance, and grounding are all specified
- Structural — Racking system matches roof type; attachment spacing meets wind/snow load requirements per ASCE 7
- Production estimate — Annual kWh figure passes a sanity check against rules of thumb (e.g., 1,200–1,600 kWh/kWp in most U.S. locations)
- BOM completeness — Every component needed for installation is listed with correct quantities
Peer Review Focus Areas
The peer reviewer is not re-doing the design. They are looking for what the original designer missed:
- Assumption validation — Is the roof pitch correct? Was the azimuth measured accurately? Are the shading objects modeled at the right height?
- Code compliance — Do setbacks match the local AHJ requirements (which may differ from defaults)?
- Constructability — Can the installation crew actually build this? Are conduit runs realistic? Is there attic access where the design assumes interior wiring?
- Edge cases — What happens at the design boundaries? Snow guards near arrays, drainage paths blocked by racking, or fire access paths too narrow for firefighter equipment
Engineering Review Scope
The PE review is the compliance gate. It covers:
- Structural engineering: wind loads, snow loads, seismic loads, roof attachment pullout calculations
- Electrical engineering: conductor ampacity, voltage drop, fault current, arc flash ratings
- NEC code compliance: 690 (solar), 705 (interconnection), 710 (standalone), rapid shutdown per 690.12
- Local code amendments and AHJ-specific requirements
Customer Approval Essentials
The customer review package should include:
- Roof layout showing panel positions on the actual aerial image
- System specifications: panel count, total wattage, inverter model
- Annual production estimate with monthly breakdown
- Financial summary: total cost, incentives, payback period, savings over system lifetime
- Contract terms and warranty information
Practical Guidance
- Use the self-review checklist every time. Do not skip it even on simple residential projects. The most common errors happen on “easy” designs because designers let their guard down. Print the checklist or keep it pinned in your solar design platform.
- Step away before self-reviewing. Review your own design at least 30 minutes after completing it. Fresh eyes catch errors that tired eyes miss. If possible, review the next morning.
- Document your design assumptions. When you estimate a roof pitch from imagery, note it. When you assume a main panel ampacity, record it. Peer reviewers and PEs can only validate assumptions they can see.
- Track every revision with version numbers. Never overwrite a design file. Save as v1, v2, v3. Cloud-based design platforms handle this automatically, but if you are working in CAD or standalone tools, disciplined versioning prevents building from an outdated revision.
- Assign peer reviews randomly. If the same two designers always review each other, they develop shared blind spots. Rotate assignments so every designer reviews a variety of colleagues’ work.
- Track error rates by type and designer. Build a simple spreadsheet logging every error caught during review: error type, review stage where it was caught, and designer. After a few months, patterns emerge — one designer might consistently miss setback requirements while another struggles with string sizing.
- Set SLAs for each review stage. Self-review within 1 hour of design completion. Peer review returned within 4 business hours. PE review completed within 2 business days. Customer approval followed up within 3 days. Without SLAs, reviews become bottlenecks.
- Use collaborative design tools. Email-based review cycles with PDF markups are slow and error-prone. Cloud-based solar software lets reviewers comment directly on the design, tag specific components, and track resolution status — cutting review cycle time by 50% or more.
- Verify the design version before starting work. The number one preventable installation error is building from an outdated design. Confirm the version number and PE stamp date match the approved permit set before unloading materials.
- Feed field findings back to the design team. If you consistently find the same discrepancies between designs and actual site conditions, report them. Your field experience makes the review checklist better for future projects.
- Conduct a pre-installation design walkthrough. Spend 10 minutes on site comparing the design layout to the actual roof before drilling the first hole. This is your final review checkpoint — cheaper than discovering a problem after panels are mounted.
- Document deviations with photos and notes. If you must deviate from the approved design in the field, photograph the as-built condition and note the reason. This supports the as-built drawing update and protects the company during inspection.
Streamline Design Reviews with Collaborative Tools
SurgePV’s cloud-based platform lets your team review, comment, and approve designs in real time — no more emailing PDFs back and forth.
Book a DemoNo commitment required · 20 minutes · Live project walkthrough
Building an Effective Review Process
Start Small, Then Formalize
Companies new to structured design reviews should start with a self-review checklist and one peer review before PE submission. Once the team is comfortable with the process and the error-tracking data shows which review stages catch the most issues, expand the workflow.
A common progression:
- Month 1–2: Introduce a self-review checklist for all designs
- Month 3–4: Add mandatory peer review for all systems above 10 kW
- Month 5–6: Extend peer review to all designs; begin tracking error rates
- Month 7+: Use error data to refine checklists and target training at common failure points
Common Review Workflow Failures
| Failure Mode | What Happens | How to Prevent It |
|---|---|---|
| Skipping self-review on “simple” jobs | Basic errors (wrong panel count, missing setbacks) reach peer review | Make the checklist mandatory regardless of system size |
| Peer reviewer rubber-stamps | Reviewer skims without checking — errors pass through | Require written comments on at least 3 specific items |
| Outdated design version built | Field crew uses v2 when v4 was approved | Single source of truth in cloud-based design platform |
| Customer approval delays | Project stalls for weeks waiting for homeowner sign-off | Set a follow-up cadence: Day 1, Day 3, Day 7 |
| PE review bottleneck | All designs queue behind one engineer | Maintain relationships with 2–3 PE firms for overflow |
The fastest way to improve design quality is not to add more reviewers — it is to improve the self-review checklist. Analyze your last 50 permit rejections and installation change orders. Categorize the root causes. Add a specific checklist item for each recurring error. Within two months, you will see a measurable drop in downstream problems.
Impact on Project Economics
| Metric | Without Formal Review | With Formal Review |
|---|---|---|
| Permit rejection rate | 15–25% | 3–8% |
| Installation change orders | 20–30% of projects | 5–10% of projects |
| Average rework cost per project | $800–$1,500 | $100–$300 |
| Design-to-install cycle time | 4–6 weeks | 2–3 weeks |
| Customer complaints (design-related) | 10–15% of customers | 2–5% of customers |
| Warranty claims (design-related) | 3–5% of systems | Under 1% of systems |
The numbers show a clear pattern: the time invested in design review is returned many times over in avoided rework, faster permitting, and fewer warranty claims. For a company installing 200+ systems per year, a formal review workflow pays for itself within the first quarter.
- NREL Soft Costs Research — Analysis of non-hardware costs in solar installations, including design-related rework and permitting delays.
- U.S. DOE SETO — Research programs targeting solar soft cost reduction through improved design processes and standardization.
- Construction Industry Institute (CII) — Foundational research on the cost multiplier of errors caught at different project stages across construction disciplines.
Frequently Asked Questions
How long does a full design review cycle take?
For a typical residential system, the full cycle — self-review, peer review, PE review, and customer approval — takes 3–7 business days. Self-review and peer review together take 1–2 hours of actual review time. PE review adds 1–3 business days depending on the engineer’s queue. Customer approval varies the most, from same-day to a week or more. Using cloud-based design tools with built-in review features cuts the cycle by reducing handoff delays between stages.
Do small residential projects really need a formal design review?
Yes. Data consistently shows that small residential projects have the same error categories as larger systems — wrong string sizing, missed setbacks, incorrect panel counts. The review can be lighter (a 15-minute self-review checklist plus a quick peer check), but skipping it entirely means errors pass through to permitting and the field. A $10 fix in design beats a $1,000 fix on the roof every time, regardless of system size.
What is the most common error caught during design review?
Fire code setback violations are the single most common error caught during peer and PE review. Designers frequently apply default setback values without checking the local AHJ’s specific requirements, which can differ significantly from IFC defaults. The second most common error is string sizing mistakes — usually Voc exceeding the inverter’s maximum input voltage at the site’s record low temperature. Both errors result in permit rejection if not caught during review.
About the Contributors
Solar-industry contributor
Nimesh Katariya contributes to SurgePV content concerning solar project workflows. This profile intentionally does not assert certifications, project totals, seminar counts, or technical-review authority without retained verification evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
