7 Gates for a Commercial Solar Pipeline

A commercial pipeline can move a project from “qualified” to “proposal sent” while the company still does not know who controls the roof, which meters belong in the analysis, or whether the customer wants to purchase an asset or buy energy. The CRM has advanced. The decision has not.

Gates solve that mismatch by tying work to evidence. A project earns the next package of effort when a named reviewer can see the basis, limitations, and path. It can stop, defer, or narrow without being declared a failed relationship.

These seven gates are for installers, EPCs, developers, sales leaders, designers, and operations teams managing commercial opportunities. They support process control. They do not replace project-specific engineering, authority, utility, tax, legal, insurance, lender, or finance review.

Gate design begins with proportional effort

A gate should protect a decision, not demand final diligence at first contact. Define the work packages your company offers during pursuit. Examples include qualification, remote screening, load analysis, candidate layout, budget proposal, site diligence, technical package, bid response, and contract offer.

For every package, state:

The discipline prevents two extremes. One company produces detailed designs for weak leads because sales wants a persuasive picture. Another demands structural and utility certainty before offering a useful screening conversation. Both spend effort out of proportion to the decision.

EPA’s solar project development process, written for development on potentially contaminated lands and related sites, shows distinct activities from site screening through procurement, design, permitting, construction, and operation. A commercial rooftop process differs, but the separation reinforces a key point: one early project status cannot imply every later decision is complete.

Gate 1: customer decision and authority

The first gate confirms there is a decision the company can support and a credible path to the people who can make it. Record the customer’s objective, requested output, decision date, stakeholders, property and energy-account relationships, procurement path, and next agreed action.

Ask what happens if the screening looks attractive. Does the facilities lead authorize a site survey? Does finance request a capital case? Does procurement issue an RFP? Does a landlord need to consent? Does a parent company control the contracting entity?

This gate should catch opportunities that consist of interest without a path. It should not punish an early contact for lacking final authority. A conditional route can focus on stakeholder discovery or site-control evidence before design hours begin.

Entry evidence might include an identifiable customer and site, a stated business question, initial decision roles, and a lawful basis for contact and data handling. Exit evidence is a written decision brief and next work package.

Stop or defer when the requested work is outside company scope, the contact cannot authorize or reach a meaningful next step, or the customer expects unsupported guarantees. Communicate the boundary plainly.

The commercial solar sales-cycle guide can help maintain stakeholder and timing records after this first gate.

Gate 2: site, load, and source evidence

The second gate asks whether available information is sufficient for the named analysis. It does not ask whether every site condition is final.

Build an evidence index with source, date, identity, coverage, and status. Include property records supplied for the project, roof plans, imagery, site photos, electricity bills, interval data, tariff materials, equipment information, and customer statements as relevant. Mark confirmed, planning assumption, conflicting, missing, or required before release.

For electricity evidence, identify meters, accounts, billing periods, units, tariff source, facility changes, and the loads intended to be served. Monthly bills may support an early consumption view. Timing-sensitive demand, export, storage, or tariff questions may require interval data and deeper analysis.

For site evidence, separate candidate area from verified available area. Note roof levels, obstructions, equipment-service access, drainage, structural records, roof condition, planned work, ownership, and survey gaps. Remote imagery can support a qualified model. It cannot confirm actual dimensions or concealed conditions.

The gate exits to an approved work package, a specific evidence request, site diligence, or stop. “Insufficient information” should identify what is missing and which decision it prevents.

Gate 3: bounded technical screening

Technical screening tests whether a plausible project concept exists within the available evidence. It should cover the interfaces that could reverse the opportunity, while keeping final design and approval claims out of the early output.

The U.S. Department of Energy’s PV system design basics describes modules, mounting structures, power electronics, and site considerations as connected system elements. A screening gate should therefore look beyond module count.

Review candidate array area, major shading and obstruction conditions, preliminary equipment basis, load relationship, likely electrical boundary, access, structural-information path, and known external constraints. State which items are modeled, supplied, observed, assumed, or still unknown.

Use a stop-and-escalate list. Conditions might include conflicting roof geometry, no credible connection concept, planned roof replacement, site access restrictions, equipment outside the current design library, or a requested operating mode requiring specialist analysis. The list must be tailored to company scope and jurisdiction.

Release language should name the supported decision. “Suitable for customer discussion about site diligence” is different from “suitable for procurement or construction.” Preserve the model version and reviewer.

SurgePV can support 3D roof modeling, array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. That scope can help create a connected screening record. It does not complete field or external review.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Gate 4: utility, authority, property, and external path

Commercial projects interact with decision-makers outside the customer and EPC. The gate identifies the parties, current sources, application route, responsibility, and conditions material to the offer.

Create one row for each applicable party: utility, building authority, fire authority, property owner, roof warrantor, insurer, lender, campus or portfolio owner, and other reviewer. Do not assume every row applies. Obtain current jurisdiction-specific guidance and qualified advice.

Record:

• Decision controlled by the party.
• Current source and effective date.
• Information or submission required.
• Applicant or responsible role.
• Unknown fees, studies, conditions, or time dependencies.
• Effect on scope, model, price, or release.

The gate does not require an approval that occurs later. It requires a credible, assigned path and honest treatment of unknowns. A fixed schedule or price may need an allowance, condition, exclusion, or later confirmation.

Avoid the phrase “standard interconnection” unless the company has defined what it means for that utility, system class, and date. A process familiar from another project may have changed or may not fit this one.

Gate 5: traceable financial and commercial basis

The financial gate asks whether the offer’s economic story can be reconstructed from source inputs. It does not certify an investment outcome.

Identify the commercial structure first. An owner purchase, financing arrangement, lease, and PPA allocate ownership, payment, operations, and risk differently. EPA explains that under a solar power purchase agreement, a developer may own, operate, and maintain the system while the host purchases electricity under a contract. Use current qualified review for the actual transaction.

Build an assumption ledger covering project cost basis, scope, energy model, tariff treatment, customer load, degradation if used, operating and maintenance assumptions, equipment replacement, finance terms, taxes, incentives, contract term, and residual treatment as applicable. Each input needs a source, date, owner, and status.

Use current primary authority for taxes, incentives, tariffs, and regulatory claims. State jurisdiction and effective date. Refer legal, tax, accounting, lending, and investment conclusions to qualified advisers. Do not present a modeled payback or savings outcome as guaranteed.

The Department of Energy’s life-cycle cost analysis guidance supports evaluating relevant costs over an appropriate study period. A commercial company should use a method and assumptions approved by its responsible finance reviewers rather than copying federal inputs.

Gate exit requires consistent technical and commercial versions, visible assumptions, reviewed customer language, and a treatment for unresolved inputs. A dense spreadsheet with no provenance fails even if its arithmetic is correct.

Gate 6: delivery and resource readiness

A viable customer offer can still exceed the company’s current ability to deliver it. Review design, engineering, permitting, procurement, field, commissioning, service, project-management, and leadership capacity for the proposed route.

Do not ask only whether a department has hours. Check competence, jurisdiction, project class, equipment familiarity, travel, supplier path, subcontractor availability, review queues, and timing dependencies. A scarce qualified reviewer may be the constraint even when production staff appear available.

Create a responsibility matrix with included work, provider, entry evidence, release point, and change trigger. State what remains customer, owner, utility, authority, supplier, specialist, or third-party responsibility. “Turnkey” is not a substitute for this map.

Review procurement assumptions. Equipment selection may be preliminary, availability can change, and substitutions can reopen layout, electrical, structural, material, cost, model, and proposal checks. Do not promise a named item without current supplier and commercial evidence appropriate to the stage.

Check schedule logic. List decision dependencies rather than one requested completion date. Site access, surveys, design, external review, procurement, outage coordination, construction, testing, and permission to operate may be controlled by different parties. Use ranges or conditions only when the method and evidence support them.

The gate exits when the company can name the delivery path and its open capacity conditions. If the path depends on a partner, confirm role, competence, commercial terms, and handoff before treating capacity as available.

Gate 7: contract-ready risk allocation and handoff

The final pursuit gate confirms that the current technical basis, commercial terms, responsibilities, conditions, and customer decisions agree. Contract-ready does not mean every project condition is final. It means remaining uncertainty is visible and allocated for qualified review.

Check entity names, site identifiers, proposal revision, scope, options, price basis, validity, payment structure, equipment basis, customer decisions, exclusions, change process, and required approvals. Qualified legal and commercial reviewers must handle the agreement in the applicable jurisdiction.

Separate conditions precedent, allowances, options, exclusions, and responsibilities. A broad “subject to survey” statement may fail to explain who orders the survey, what it must resolve, or what happens if the result changes the project. Use operational language that matches the reviewed contract.

Prepare the delivery handoff before signature:

1. Customer objective, stakeholders, and communication history.
2. Original source evidence and current accepted files.
3. Design and financial basis with versions.
4. Approved scope, selections, and commercial terms.
5. Commitments, exclusions, assumptions, and open conditions.
6. External path, applications, and correspondence.
7. Next owner, customer communication, and release calendar.

The solar proposal acceptance handoff guide can hold that transfer. Let the delivery owner reject an incomplete handoff before the project disappears from sales reporting.

Give each gate an owner and service rule

Gates fail when everyone can comment but nobody owns the decision. Assign one accountable role per gate and list required contributors. Separate the person preparing evidence from the person independently reviewing high-consequence claims where appropriate.

Set response rules by work class and consequence, not one universal deadline. An ordinary evidence return and a specialist exception need different queues. Record accepted, returned, and escalated work with reasons.

Use a short gate record:

Avoid approval in private chat. Link the conversation to the project record, capture the decision, and identify the affected version. A later reader should not need to ask who said yes.

Audit gate quality, not just speed

Measure queue age and touch time, but also returned work, late changes, exceptions, customer surprises, downstream corrections, and stopped effort. Segment by project class and requested output.

A fast gate can be weak if it pushes unresolved conditions forward. A slow gate can be weak if reviewers reconstruct missing evidence repeatedly. Inspect cases and reason codes before changing thresholds.

Review false stops as well. A gate may be too strict, unclear, or based on an outdated market assumption. Let staff challenge it with evidence. Preserve the original decision and approve controlled exceptions rather than quietly ignoring the rule.

Run periodic gate reviews:

• Which condition caused the most returns?
• Which late project finding should an earlier gate have exposed?
• Which required evidence never changed a decision?
• Which exception is now common enough for a standard route?
• Which rule depends on a stale external source?
• Which role is carrying hidden review work?

Change one gate deliberately, publish the effective date, and monitor consequences. Do not rewrite the entire pipeline after one difficult project.

What should a commercial solar gate record contain?

A commercial solar gate record should contain the customer decision, requested release, required evidence, evidence owner, reviewer, acceptance rule, open conditions, permitted use, return reason, next action, and regression trigger. Financial and technical conclusions must remain separate, with each approval limited to the role, evidence, and project stage it actually covers. That boundary must travel with downstream output and handoff.

The record should travel with the opportunity. A colored pipeline field is not enough because it cannot show which evidence supported the decision or what the reviewer released. “Technical green” can be misread as engineering approval, constructability, utility acceptance, or final equipment suitability when the actual review was an early screening.

Keep financial and technical records linked but distinct. A technically plausible screening does not establish an acceptable investment, tariff, tax treatment, contract, or finance structure. A commercial scenario does not establish site feasibility, equipment selection, code compliance, interconnection, or engineering approval. The gate design should make both limits visible.

How should a gate return incomplete work?

A commercial solar gate should return incomplete work with the failed acceptance rule, affected release, evidence required, owner, and permitted work while the condition remains open. It should avoid vague rejection and avoid granting broad approval with buried caveats. The return becomes complete when the receiving role can identify the next action without reconstructing the review. Returns become immediately actionable.

Use a stable response vocabulary: pass for stated purpose, pass with named conditions, return for defined evidence, stop for current scope, or regress because the basis changed. “Approved” by itself hides too much. “Pass for preliminary customer comparison with tariff and structural questions still open” carries a usable boundary.

1. Name the gate and requested release.
2. Cite the evidence and revision reviewed.
3. Identify the acceptance rule that passed or failed.
4. State the condition in ordinary customer-safe language.
5. Assign the owner and next evidence or decision.
6. State which work may continue and which may not.
7. Set the event that returns the opportunity to review.

Use this copy-ready gate response:

Opportunity and current scenario:
Gate and requested release:
Evidence reviewed:
Decision: pass, qualify, return, stop, or regress:
Acceptance rule applied:
Open condition:
Owner and next action:
Work permitted now:
Work prohibited until review:
Customer-facing explanation:
Review or regression trigger:

A fast gate is useful only when the request is complete and the decision proportional. Do not reward speed by permitting silent assumptions. Track returns by defined cause and use repeated causes to improve intake, ownership, or training. The goal is better flow with visible evidence, not fewer honest returns.

How do gates respond when project evidence changes?

Commercial solar gates should regress when new evidence changes the basis of an earlier decision, including customer scope, load, site, equipment, scenario assumptions, ownership, delivery, authority path, or contract allocation. Regression should identify every affected output and reviewer rather than treating the old approval as permanent pipeline history. The affected work returns to appropriate formal review before another customer-facing release.

Illustrative example, not a project approval: A commercial rooftop opportunity passes an early site-and-load screening for a preliminary comparison. The customer later adds a future load and asks to include another roof area. The original screening does not automatically cover either change, even if the pipeline stage remains the same.

The gate record sends the affected scenario back to evidence review. The future load needs its own stated basis and owner. The additional roof area needs appropriate site and technical evidence for the requested release. The layout, energy model, equipment output, commercial scenario, and proposal language must share the revised identifier before the next customer issue.

The financial gate also reopens if the changed scenario alters its assumptions. That does not mean every reviewer starts from zero. Unaffected evidence can remain accepted when its source and applicability are clear. Regression targets the branches touched by the change and preserves the earlier decision history.

Use a change-impact table:

This table routes internal work. It does not decide which external authority, engineer, utility, lender, insurer, attorney, tax professional, or other reviewer must approve a live project. Assign those routes according to the actual jurisdiction, agreement, and release.

Keep priority separate from gate status

A strategically important opportunity does not earn a technical or financial pass. It may earn faster evidence collection, executive attention, or a deliberate exception allocation. Keep the gate record unchanged and use the commercial opportunity ranking method to decide which qualified next action receives scarce capacity.

This separation protects both disciplines. Gate reviewers can state what the evidence supports without deciding company strategy. Commercial leaders can allocate attention without rewriting technical or financial findings. When leadership overrides the normal order, the record shows that it accepted an explicit resource or uncertainty decision rather than manufacturing a cleaner gate result.

A practical rollout for the seven gates

Start with one commercial project class and one region. Map recent opportunities through the proposed gates. Identify where current records already support decisions and where the team relies on memory.

Then:

1. Define work packages and release purposes.
2. Draft entry evidence and exit routes for each gate.
3. Assign owners, contributors, and exception authority.
4. Test accepted, returned, deferred, and stopped cases.
5. Train with real sanitized examples.
6. Run live projects under additional review.
7. Examine gate evidence and revise within a controlled change process.

Keep the first version short. A gate that takes longer to interpret than the work it controls will be bypassed. Link to detailed technical or commercial procedures only when the project reaches them.

Adapt the gates for bids and RFPs without abandoning them

A formal request may impose its own stages, forms, deadlines, and evaluation criteria. Map those requirements to the internal gates. Do not let a customer’s submission deadline erase the evidence needed for the company to authorize the bid.

Create a compliance matrix that lists each requested item, the responsible contributor, source, status, internal reviewer, and any clarification or deviation. Separate an answered question from an accepted commercial or technical commitment. A response can state an assumption or exception when the request permits it; the responsible contract team must decide how deviations are handled.

Run an early bid decision before design and estimating effort expands. Review customer fit, decision access, available site and load evidence, bid rules, required securities or qualifications, delivery window, partner needs, and specialist demand. State the maximum pursuit package management is authorizing at that point.

Keep proposal strategy apart from gate evidence. The team may choose how to present experience, method, schedule, or value within approved claims. It may not improve its competitive position by inventing a customer result, hiding a material exception, or promising external approval.

Before submission, reconcile the RFP response, technical concept, commercial schedule, assumptions, clarifications, and internal approvals. Store the submitted version exactly. If the customer issues an addendum, identify affected sections and reopen the necessary reviews rather than relying on one person to remember every consequence.

Measure the cost of diligence by gate

Pipeline governance becomes stronger when the company can see where pursuit effort is spent. Track active hours by role, paid external diligence, travel, site work, supplier input, and repeated work at each gate. Label internal capacity separately from incremental cash cost.

Do not use diligence cost to punish thorough review. Use it to ask whether evidence arrived in the right order. A project that consumed detailed design before site control was understood indicates a sequencing problem. A project that stopped after a focused roof investigation may show the gate prevented far larger unsupported work.

Compare stopped opportunities by the earliest gate that could reasonably have identified the condition from available evidence. Some findings are inherently late. Avoid rewriting history to claim every project should have been screened out at first contact.

Set approval thresholds for unusually expensive pursuit packages. The request should name the customer decision, evidence gap, deliverable, cost or capacity, owner, and stop condition. Leadership can then authorize a bounded experiment rather than giving a vague strategic exception.

Over time, this record supports better bids and staffing. It shows which market segments need specialist resources, which evidence requests delay work, and where partnerships may be more sensible than building every capability internally. Keep the interpretation tied to comparable project classes.

The seven-gate pipeline does not make commercial solar simple. It makes complexity arrive at the appropriate decision. Customer authority comes before expensive diligence. Evidence comes before detailed modeling. External paths and economics become visible before the offer hardens. Delivery and contract responsibilities are checked before sales hands the project away.

That sequence protects scarce work without turning caution into paralysis. A commercial opportunity can advance on qualified evidence, pause for one answer, or stop with a clear reason. The pipeline becomes a record of decisions rather than a collection of hopeful stage names. Release solar proposals from the gate that matches their purpose.

Frequently Asked Questions

What is a commercial solar pipeline gate?

A pipeline gate is a controlled decision that determines whether a project may consume the next level of work. It states the evidence required, reviewer, output allowed, and possible routes. A gate is not a CRM stage label; moving it should reflect a real decision supported by an inspectable project record.

Should every commercial solar opportunity pass all seven gates?

Every pursued opportunity should address the decisions, but the depth and sequence can vary by project, sales motion, jurisdiction, and requested output. A screening study does not need contract-level diligence. Define proportional evidence for each work package and prevent later gates from being treated as complete merely because an early model exists.

Can sales approve a commercial solar technical gate?

Sales can own customer context, qualification, and commercial communication within company rules. Technical gates should be reviewed by people competent and authorized for the stated decision. Structural, electrical, engineering, utility, authority, tax, legal, insurance, and finance matters must stay with the responsible specialists and external decision-makers.

What happens when a project fails a pipeline gate?

Choose a visible route: request specific evidence, narrow the output, commission bounded diligence, change the delivery approach, defer until a named event, route to a competent partner, or stop. Record the reason and owner. Failure at one gate is information, not permission to hide the condition in a disclaimer.

How should a solar company audit its gates?

Review returned work, exceptions, late changes, stopped opportunities, and delivery surprises against the evidence available at each gate. Check whether the rule was clear, followed, and appropriately scoped. Revise gates from documented cases, preserve effective dates, and avoid weakening a control solely because it slows a preferred deal.