7 Customer Commitments That Must Reach Solar Delivery

A customer can hear a clear commitment on Tuesday and meet a delivery team three months later that has never seen it. The salesperson remembers a preferred module color. Design sees a generic product family. Procurement sees an approved alternate. The contract says something more precise than all three.

This guide is for solar sales, operations, design, procurement, project management, installation, and service leaders. It identifies seven commitments that need controlled ownership from agreement through handover. It is a workflow guide, not legal, financial, tax, engineering, or regulatory advice. SurgePV publishes this article and sells solar design and proposal software.

The Federal Trade Commission’s consumer guidance tells buyers to read agreements and understand what they are signing. A solar company earns the other half of that trust by making sure the people who deliver the project can find and follow the approved obligations.

Build one commitment register from controlling records

A commitment register is a project index of statements that can change delivery. Each entry links to the controlling source and records exact language, status, accountable owner, required action, due point, dependency, acceptance evidence, customer communication, and approved revision history.

Do not copy every sentence from the agreement into a spreadsheet. Extract decision-changing obligations and preserve a link to the complete source. A paraphrase helps an operator understand the task, but it cannot quietly replace contract language or qualified interpretation.

The register should include commitments created after signature too. A site finding may produce an approved design change. A manufacturer substitution may change appearance or warranty documents. A utility or authority response may change sequence. Record the new decision and its authority instead of editing the original promise until the conflict disappears.

Use statuses that tell the next person what to do: confirmed, pending customer action, pending company action, dependent on third party, superseded by approved change, disputed, and complete with evidence. “Noted” and “in progress” reveal almost nothing.

The solar sales and design handoff explains how customer context becomes a usable technical brief. The commitment register extends that discipline through procurement, field work, commissioning, billing, and service.

Commitment 1: the customer’s purpose and decision boundary

The delivery team should know why the customer chose the project and which outcome the agreed system is intended to support. Cost management, resilience, emissions reporting, available roof use, tenant expectations, aesthetic priorities, or another objective can shape design and communication. None should be rewritten as a guaranteed result.

Record the customer’s stated purpose in source language, then link it to the agreed project decision. “Reduce exposure to daytime electricity purchases” is an objective. It is not a promise that a bill will fall by a fixed amount. “Keep the street-facing roof clear” can be a binding design constraint if it appears in the approved scope or change record.

Preserve priorities that explain tradeoffs. If the customer selected lower capacity to protect roof access, the later team should not treat unused area as a design error. If resilience was discussed but storage was excluded, the boundary must remain visible so an installer is not asked to explain backup behavior that the purchased system does not provide.

At kickoff, read back the purpose and exclusions. Ask the customer to correct factual context without reopening every settled term. Route requested changes through the agreed process.

The project intake guide begins with the decision the next work must support. After sale, that decision still matters because it tells delivery which facts are material and which revision would alter the customer bargain.

Close this commitment with an approved objective statement, documented exclusions, and links to the scope or decision record. Do not close it with “customer wants solar.”

Commitment 2: the site and scope boundary

Scope commitments define the property, buildings, meters, roofs or land areas, system type, included work, allowances, owner work, exclusions, interfaces, and acceptance boundary. A single overlooked interface can turn a clear price into a dispute even when the equipment itself is correct.

Reconcile sales scope with current site evidence. A preliminary proposal may assume roof condition, access, electrical capacity, trench path, equipment location, structural suitability, or authority treatment. Delivery must know which items were verified later, which remain open, and how changed conditions affect price or schedule under the agreement.

Create a work-package matrix for design, survey, engineering, permitting support, utility coordination, procurement, installation, monitoring, restoration, commissioning, training, documentation, and service as applicable. Use included, excluded, allowance, owner-supplied, third-party, and unresolved. Link each row to the governing source.

Do not treat exclusions as fine print that operations can discover later. If roof work belongs to the owner, identify the completion evidence and project gate. If communications hardware depends on customer internet access, record that dependency. If utility construction sits outside the installer scope, explain the interface without predicting the utility’s action.

Site revisions require impact analysis. A new obstruction can affect layout, energy forecast, equipment quantity, price, and customer expectations. Update connected outputs and retain the reason, evidence, approver, and communication.

The documentation mismatch guide shows how conflicting layout, stringing, equipment, and site records can reach the field. The scope register should stop that drift before work is released.

Commitment 3: the approved design and equipment basis

Customers may remember a module brand, visible layout, equipment location, color, monitoring feature, or proposal rendering as part of what they bought. Delivery needs to know which representation is contractual, which was preliminary, and which later choice superseded it.

Record exact equipment identifiers or the permitted selection method. Include quantities and relevant configuration at the current project stage. Attach manufacturer documents and approved design revisions. Do not reduce the commitment to a logo if the actual agreement names a model, rating, appearance, warranty, or substitution rule.

Control substitutions through a decision record. State why the change is proposed, the alternative, technical review, appearance effect, energy-model effect, electrical and balance-of-system effect, warranty and service effect, price or schedule effect, approving authority, and customer communication required by the agreement.

Keep preliminary and released drawings visibly different. A customer-facing rendering can support discussion without authorizing procurement or construction. Delivery should know which release status governs each activity and which reviews remain.

If new survey evidence changes the array, explain the fact and mechanism. Do not simply replace the proposal image. Show which roof boundary, obstruction, setback, access condition, equipment constraint, or customer decision changed, then link the approved revision.

The solar design review checklist provides distinct thresholds for concept, coordination, permit, procurement, and construction packages. Put the customer’s design commitments into the review at every relevant release.

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.

Commitment 4: price, payment, and financing representations

The delivery record must preserve the project price boundary, allowances, payment triggers, customer obligations, change mechanism, offer validity, financing relationship, and any cancellation or transfer terms that apply. Finance promises should never survive only as a monthly-payment screenshot.

The Consumer Financial Protection Bureau’s solar financing issue spotlight discusses common market structures and consumer risks, including hidden markups and fees in some arrangements. Its separate consumer advisory warns consumers to scrutinize complex loan terms.

Use the signed agreement and current finance documents as controlling sources. Record cash price, financed amount, lender, fees, interest and payment terms, security or lien features, tax-credit assumptions, dealer-fee treatment, disbursement triggers, and customer acknowledgments only where those items apply and are supported. Do not infer missing terms.

Keep the solar company, lender, broker, tax adviser, and customer roles distinct. A salesperson should not promise tax eligibility or financial outcomes. Tax, credit, legal, and lending questions need current primary sources and qualified advice for the customer’s jurisdiction and circumstances.

Payment milestones should correspond to documented events under the agreement. Delivery needs the evidence required for each request and the person authorized to approve exceptions. Do not move a milestone because an internal dashboard says “complete” while the contract defines a different trigger.

Changes should show original scope, reason, added or removed work, price effect, schedule effect, approvals, and revised payment plan. A verbal “we’ll take care of it” can become a disputed obligation when no authorized record follows.

The CFPB has also reported on markups, fees, and confusing terms in solar loans. A clean internal handoff cannot cure an unsuitable agreement, but it can stop the delivery process from inventing a friendlier version of the signed terms.

Commitment 5: production and savings assumptions

A production estimate or savings scenario can dominate the buying decision, so its basis must reach delivery intact. Preserve the model name and version, weather source, site geometry, shade treatment, equipment, loss assumptions, reporting period, tariff and consumption inputs, escalation or future-load scenarios, and stated limitations.

Label the output. Modeled annual energy is not measured future production. A savings scenario is not a guaranteed bill outcome. Actual results can change with weather, site condition, equipment, availability, operations, tariffs, export treatment, consumption, and other factors.

If the survey or equipment choice changes, rerun every affected forecast under controlled revision. Record the changed input, reason, model owner, reviewer, output effect, and customer communication. Do not keep the old high-energy chart beside a smaller released layout.

Keep energy and money separate. Energy-yield modeling estimates production under stated conditions. Financial modeling applies customer, tariff, price, financing, and other assumptions. A team can update one without remembering the other, so the commitment register should connect both and flag a stale dependency.

Do not preserve a sales shortcut as a technical commitment. A broad savings phrase may need clarification against the proposal and contract. Route material ambiguity to authorized reviewers rather than asking a designer to reverse-engineer the customer’s expectation.

The questions to answer before showing projected savings offers a deeper review of consumption, tariff, system, timing, and uncertainty. The handoff control here is provenance: which scenario did the customer see and which one now governs delivery communication?

If the customer requests a new scenario after sale, label it as an evaluation until the required parties approve its effects. A model run does not silently amend scope, price, equipment, schedule, or contract terms.

Commitment 6: schedule, dependencies, and communication

Customers experience delivery through dates and updates. Preserve every authorized milestone, prerequisite, customer action, third-party dependency, notice requirement, contact channel, and update cadence. Separate a target, estimate, contractual date, authority window, and internal task deadline.

Build the schedule from dependencies rather than repeating the close date backwards. Site access, customer documents, roof work, design release, engineering, equipment, financing, authority review, utility work, inspections, weather, commissioning, and payment may interact. The applicable chain differs by project.

Never promise authority, utility, lender, insurer, manufacturer, or third-party action that the company cannot control. Record the submission or coordination commitment the company does own, along with evidence and customer update rules.

Assign a communication owner for each phase. The customer should know who sends the next update and when, even if the update reports a blocker rather than completion. Silence around a missed internal target creates a bigger trust problem than a precise explanation delivered early.

When a dependency slips, state the fact, source, affected tasks, options, owner, and next decision date. Avoid using a new unsupported final date to calm the conversation. Update the controlled schedule and every customer-facing reference.

Carry access and operating restrictions into field planning. A commercial site may require shutdown windows, escorts, inductions, security, tenant notices, or restricted work areas. Those are delivery inputs, not minor preferences for the crew to discover at the gate.

Use the 14-day solar proposal follow-up checklist for the pre-close communication period. After close, move every material response into the project register instead of leaving it in the follow-up thread.

Commitment 7: commissioning, warranties, and service ownership

The customer should receive a usable account of what completion means and what happens next. Record required inspections, startup and commissioning activities, monitoring setup, training, closeout documents, acceptance process, warranty sources, product registration, maintenance responsibilities, service contacts, and open items.

Distinguish warranty issuers. A module manufacturer, inverter manufacturer, installer, finance provider, and monitoring or service provider can carry different obligations. Preserve the current documents, covered events, remedies, exclusions, transfer rules, claim steps, customer duties, and contact routes as applicable.

Do not describe external product warranties as an installer guarantee. Do not describe a monitoring alert as preventive maintenance unless the agreement defines that service. Do not promise a response time or lifetime relationship that the responsible service organization has not approved.

Commissioning records should identify the installed configuration, completed checks, exceptions, corrective actions, monitoring status, responsible people, and release decision according to the project’s requirements. Company commissioning does not replace authority, utility, or engineering approval.

At handover, give the customer one index to current records. Include the appropriate as-built documents, equipment information, approvals, warranties, monitoring access, operating guidance, and issue route. Mark superseded files so the customer does not rely on an old layout later.

Create the service case before closing the project if an issue remains. Name owner, customer communication, next date, and completion evidence. A project should not become “complete” merely because the invoice is paid or the installation crew leaves.

The commercial solar page provides context for connected business and project workflows. The commitment principle applies at any scale: a handover works when a new person can act without reconstructing the sale from memory.

Run the handoff as an acceptance meeting

Do not make handoff a file-transfer notification. Bring sales, project ownership, and required technical or commercial roles together for an acceptance review proportionate to project risk. The receiving owner should be able to accept, return, or conditionally accept the package.

Use this sequence:

1. Confirm customer, legal entity, site, project, and agreement identifiers.
2. Read back the project purpose, boundary, and major exclusions.
3. Review each of the seven commitment classes and linked sources.
4. Reconcile conflicts between proposal, agreement, drawings, and later records.
5. Assign an owner, due point, and escalation route to every open item.
6. Confirm the next customer communication and responsible person.
7. Record acceptance, conditions, returned items, and approved changes.

The receiver should reject vague entries. “Sales to confirm” needs a person, source, question, effect, and due point. “Customer aware” needs the relevant communication record and should not be used as a substitute for consent where approval is required.

Preserve disagreement. If sales and delivery interpret a commitment differently, link the sources and route the issue to the authorized contract, technical, finance, or management reviewer. The meeting should not settle material ambiguity through group confidence.

Use the CRM page as product context for connected project information, while keeping the governance boundary clear. A system of record helps people retrieve decisions. It does not decide what a contract means or whether a technical conclusion is acceptable.

How should a solar customer commitment be recorded?

A solar customer commitment should be captured by preserving the controlling source and exact wording, classifying the obligation, assigning a delivery owner and change authority, naming the trigger and due point, linking dependencies, and defining completion evidence. The register should also show the customer-facing explanation, status, superseded versions, and every design, equipment, price, finance, schedule, warranty, or service output affected.

Begin with the source hierarchy used by the company and project. A signed agreement, approved exhibit, authorized change, lender document, warranty, customer selection, and email clarification can carry different authority. Preserve the full record and route interpretation conflicts to the appropriate authorized reviewer rather than choosing the friendliest sentence.

Use one copy-ready entry for each decision-changing commitment:

Solar customer commitment entry

Customer, site, project, and agreement: [controlled identifiers]

Commitment class: [purpose, scope, design, equipment, price, finance, model, schedule, communication, warranty, or service]

Controlling source and exact wording: [document, section, revision, and date]

Operational interpretation: [task description that does not replace the source]

Current status: [confirmed, pending party action, third-party dependent, disputed, superseded, or complete]

Delivery owner and change authority: [roles]

Trigger, due point, and dependencies: [events and records]

Outputs affected: [design, model, equipment, scope, price, schedule, contract, handover]

Customer communication: [approved wording, owner, and date]

Completion evidence: [record that closes the item]

Change history: [prior wording, reason, approval, effective date, and superseded outputs]

Avoid entries such as “customer aware,” “sales promised,” or “operations handling.” Each hides the statement, authority, action, and evidence. If the customer merely expressed a preference, preserve it as a preference until the controlling process turns it into scope or an approved decision.

Use status to control work. A pending customer selection may block procurement while leaving survey work open. A utility-dependent milestone may allow company preparation but prevent a final date promise. Name the affected decision instead of stopping or releasing the whole project indiscriminately.

Illustrative workflow example, not a customer result: A proposal rendering shows a particular equipment location, while the agreement permits later coordination. The register preserves both sources and labels the customer expectation. Delivery does not assume the image controls or ignore it. The project owner routes the location through the approved design and contract process, communicates the supported outcome, and updates every affected drawing and customer record after authorization.

The example demonstrates why exact source and operational ownership belong together. Neither sales memory nor a detached image should decide the field instruction. The register brings the conflict to the roles authorized to resolve it.

Who owns a solar customer commitment after the sale?

Ownership of a solar customer commitment should follow the delivery decision: design owns design inputs, procurement owns released equipment actions, finance or authorized commercial roles own payment records, project management owns coordinated dates and communication, and service owns handover duties. One project coordinator should maintain the register, while reviewers retain authority for technical, financial, legal, safety, utility, and contract matters.

Separate four roles: source custodian, action owner, change approver, and informed stakeholder. One person may hold several in a small company, but the register should keep their responsibilities distinct. The salesperson can supply context without remaining the permanent operational owner of every promise.

Use an ownership map:

Do not route every material question to a generic project manager. That role can coordinate evidence and communication but may not have authority to interpret a contract, approve a technical exception, change financing, accept safety risk, or speak for an authority or utility.

Define alternates for absence and response expectations for time-sensitive decisions. A customer commitment should not wait indefinitely because one approver is unavailable. The alternate needs equivalent authority, and the decision still needs a record.

At each phase transition, the receiving owner accepts, conditions, or returns the relevant commitments. This creates an active handoff rather than a notification. One consolidated correction request is better than several departments discovering the same missing source at different times.

What should happen when a customer commitment cannot be fulfilled?

When a solar company cannot fulfill a commitment, it should stop work, confirm the source and authority, assess consequences, develop supported options, obtain approvals, and explain the conflict promptly for review. The resolution must update the commitment register and every dependent document without erasing the original promise or relying on an informal waiver that the controlling records do not support.

Contain the mismatch at its source. If equipment is unavailable, stop the affected procurement and installation release. If a site condition changes scope, stop the affected design, price, and schedule fields. Do not freeze unrelated work unless the conflict genuinely reaches it.

Use this resolution sequence:

1. Preserve the original commitment, source, customer-facing representation, and current project revision.
2. Identify the new evidence or event that prevents fulfillment and who established it.
3. Map the effect across design, equipment, production, price, payment, finance, schedule, warranty, service, and contract records.
4. Route technical, commercial, financial, legal, safety, authority, utility, lender, manufacturer, and customer decisions to the responsible roles.
5. Develop supported options and state the implications and remaining uncertainty of each.
6. Communicate the conflict in plain language before the affected work advances.
7. Record the authorized customer decision or other controlling resolution.
8. Issue new source revisions, expire superseded outputs, and verify completion evidence.

Avoid a quiet substitute. An equipment replacement, layout change, altered schedule, different payment trigger, or revised service route may be operationally reasonable and still require authorization and customer communication under the governing documents. Internal urgency does not create consent.

If the company made an unsupported promise, acknowledge the specific mismatch without shifting blame to software or a downstream team. The resolution still needs qualified review and an accurate current agreement. Then repair the intake, approval, proposal, or handoff control that allowed the statement to detach from delivery.

Keep the original promise visible in history after resolution. A future service or dispute review may need to know what the customer saw and why it changed. Replacing the text in place produces a clean current screen but destroys the explanation.

Close the issue only when the resolution appears in every dependent record and the customer has received the required communication. A signed change beside an old crew package, forecast, payment request, or service record leaves the project inconsistent.

Control changes without erasing the original promise

Every project changes. Change control protects trust by showing how the approved bargain moved. Keep the original commitment, trigger evidence, proposed revision, impact assessment, authorized approval, customer communication, effective date, affected documents, and completion evidence.

Do not edit a field in place and call the history complete. The team needs to know what the customer previously saw and why the later record differs. This is especially important for layout, equipment, energy, price, financing, milestone, and warranty changes.

Assess connected effects before approval. A module substitution can affect quantities, layout, stringing, bill of materials, forecast, appearance, warranty, procurement, and proposal. A schedule change can affect finance conditions or customer operations. A site discovery can alter several commitment classes at once.

Use role-based approval. The person who notices the issue may not have authority to approve technical, financial, or contract effects. Record the responsible reviewer and keep external approvals distinct from company decisions.

Communicate material changes in plain language, but preserve the formal record. State what changed, why, effect, options, required customer action, and next step. Do not bury the change in a new attachment with no explanation.

The customer may reject a proposed change or request another option. Keep that decision and route it under the agreement. Delivery pressure does not create consent.

Audit the promise system with completed projects

Sample projects from different salespeople, designers, managers, and project types. Trace each commitment from source to handoff, owner, change, customer communication, and closeout evidence. Look for missing links rather than asking whether everyone “usually” communicates well.

Study disputes and near misses. Which customer questions repeated after handoff? Which scope item surprised procurement? Which layout did the crew receive? Which energy figure stayed in a proposal after the design changed? Which payment request used the wrong trigger? Which warranty contact failed at closeout?

Separate individual error from system design. A careful project manager can rescue a weak handoff by reading every email, but that hidden effort does not make the workflow sound. Improve the intake field, required source, owner rule, acceptance gate, or change process that made recovery necessary.

Track returned handoffs by reason. Use internal counts only after defining the sample, period, and classification. Do not publish a universal benchmark from one team’s operating data.

Review permissions and retention. Customer, financial, property, and contract records require appropriate access, approved systems, and applicable company or legal policies. A commitment register should point to controlled records rather than copying sensitive data into every tool.

Recheck after the fix. A new form can collect more fields while people still attach the wrong proposal. Audit whether the receiving owner can make the next decision from current evidence.

Make the customer experience match the agreement

The best handoff is invisible to the customer. They do not have to repeat their priorities, forward the same document, mediate internal disagreement, or discover that a confident promise belonged to nobody.

That experience comes from visible operational work. Purpose reaches design. Scope reaches procurement and the field. Equipment decisions reach the model and proposal. Commercial terms reach billing. Forecast assumptions reach customer communication. Dates reach planning. Warranties and service duties reach closeout.

No software can repair an unauthorized promise by itself. A connected solar proposal workflow can reduce transcription and retrieval failures when teams still define owners, sources, review limits, and change authority.

The seven-commitment register gives leaders a practical test. If a receiving project manager cannot locate the source, understand the obligation, name the owner, and show the next evidence, the commitment has not reached delivery yet.

Frequently Asked Questions

Which solar customer commitments belong in a handoff register?

Record any statement that can change scope, design, price, payment, forecast interpretation, timing, customer action, communication, acceptance, warranty, or service. Include written contract terms and approved later changes. Do not promote every conversational preference into a commitment; preserve its source and status so the responsible owner can confirm what controls delivery.

Can the signed solar contract serve as the entire handoff?

The contract is a controlling source for many obligations, but delivery teams also need approved exhibits, site evidence, design revisions, customer selections, finance documents, change records, correspondence, and open decisions. Build the register from those sources without paraphrasing away legal meaning. Route interpretation conflicts to authorized contract or legal reviewers.

Who should own a customer promise after solar sales closes?

Assign an accountable delivery role to each commitment, plus the person authorized to approve changes. Ownership can differ across design, procurement, finance, project management, installation, commissioning, and service. The salesperson remains available for context, but memory should not become the only source or the permanent owner of operational fulfillment.

How should a solar team handle a promise it cannot fulfill?

Escalate before the affected work continues. Confirm the exact source, assess technical and commercial effects, identify options, obtain authorized approval, and communicate clearly with the customer. Record the agreed change and update every dependent document. Do not hide the conflict, substitute a friendlier interpretation, or rely on an informal verbal waiver.

How can companies audit whether commitments survived delivery?

Sample completed projects and trace each register entry from source through owner, decision, evidence, change history, customer communication, and closeout. Study missed dates, repeated questions, disputed scope, forecast confusion, finance corrections, substitutions, and service contacts. Fix the handoff field or release gate that allowed context to disappear, then verify later projects.