Solar Capacity Planning for Sales, Design, and Installation Teams

A sales forecast, a design queue and a crew calendar describe different states of work. Cross-stage capacity planning reconciles their entry conditions, task loads, shared qualified resources and release dependencies before the company commits to more work.

This page owns the interface plan between teams. The growth-capacity model owns scenario calculations and cash timing; the quarterly planning checklist owns the periodic decision packet. Here, the question is whether one stage’s accepted output can become the next stage’s authorized work.

Map Work by Stage Rather Than Department

List actual work states, entry evidence, tasks, responsible roles, required review, exit disposition and receiving owner. A project can enter a department more than once through customer changes, missing evidence, substitutions or field questions. Count those tasks without counting the same customer as a new opportunity.

NASA’s interface-management guidance discusses interface responsibilities, controlled change and communication between parties. It is an analogy for explicit handoff responsibilities, not a solar approval rule.

Define a Capacity Unit That Reflects the Work

Keep unique opportunities, design tasks, proposal versions, crew assignments, qualified review hours and installed kWdc separate. A project count is useful only when its work class and scope are comparable. A large roof and a small complex retrofit may create different task patterns.

Match workload and capacity at the same role, task and time-window resolution. Use actual company records or clearly labeled estimates. Do not assume that an hour assigned to sales follow-up is interchangeable with electrical review or installation work.

Reconcile Shared Resources Before Adding Department Totals

A senior reviewer, survey specialist, project manager or technical owner may appear in several team plans. Assign one calendar basis to each shared resource and reconcile its allocations, required duties and authorized work.

Hypothetical shared-role check: suppose one appropriately authorized role has 60 usable hours in a planning period after separately recorded duties and absences. Sales-support review requests consume 25 hours, design review 30, and installation-change review 20. Total requested work is 25 + 30 + 20 = 75 hours, an arithmetic excess of 15 hours.

Do not give each department its own copy of the 60 hours. Nor does the gap authorize overtime, delegated approval or hiring. The responsible owners must decide whether commitments, sequence, support or scope can change without bypassing required review. These are invented task loads, not observed productivity or a safe workload.

Separate Load From Readiness and Waiting

Distinguish ready work, evidence requests, customer decisions, external reviews, equipment conditions and internally blocked tasks. Waiting may consume coordination or hold a calendar slot while requiring little primary task time. Record both effects without treating elapsed waiting time as labor hours.

The longest queue is a diagnostic signal, not proof of the limiting constraint. Determine what actually prevents accepted work from completing and what would happen if that stage changed. Several constraints can interact, and a bottleneck can move as scope or resources change.

DOE’s soft-cost overview discusses non-hardware work and delays across jurisdictions and utilities. It does not supply a conversion factor from lead count to installation throughput.

Protect Forecasts From Becoming Commitments

A forecast can support a scenario without granting permission to schedule installation. Retain contractual scope, design acceptance, supplier conditions, qualified releases, local authority and utility status, site readiness and customer responsibilities. Target dates remain conditional where their prerequisites are unresolved.

Use the installation-readiness review for the release package. An internally free crew calendar cannot promise another party’s approval date or equipment delivery.

NASA’s technical-planning guidance connects workflow, resource constraints and changed assumptions. Apply the planning principle carefully; local solar processes and responsible reviewers govern actual execution.

Copy-Ready Cross-Stage Plan

• Planning period, observation date and permitted decision use.
• Accepted commitments and current project states.
• Stage entry, task, review, handoff and exit definitions.
• Load by task class, role and period, including returns and exceptions.
• Shared resource calendar and reconciled assignments.
• External dependency, source, owner and conditional timing.
• Receiving owner’s acceptance, evidence request or escalation.
• Customer promise permitted, conditional or withheld.
• Candidate intervention, responsible authority and affected stage.
• Changed assumption and successor-plan trigger.

Review this plan at the cadence the actual work requires. Compare the same definitions over time and let the people performing and receiving work challenge an unsupported assumption. Use the capacity-leverage checklist when evaluating a proposed intervention.

Frequently Asked Questions

What should cross-stage capacity planning reconcile?

Reconcile current project states, accepted work, stage tasks, qualified roles, shared resource assignments, handoff entry conditions and external readiness in the same time window. Department headcount or lead totals alone do not establish deliverable capacity.

Can the same reviewer’s hours appear in several team plans?

The reviewer may serve multiple teams, but its usable calendar must be reconciled across all assignments and duties. Do not give each department a separate copy of the same available hours.

Does the longest queue prove the bottleneck?

No. Queue length or age is a diagnostic signal. Investigate readiness, work type, shared reviewers, external decisions and what prevents accepted completion; constraints can interact and move.