Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing

What this looks like in solar installation and O&M services

A commercial installer learns that an ordered inverter will arrive later than planned. Procurement identifies an alternative, the technical team needs to review it, and the customer may need a revised proposal. Finance cannot simply replace the item description on the existing billable scope. A workflow can route the evidence and record the approved decision, then prepare the permitted purchasing and commercial updates under the same change reference.

Records, ownership, and update rules

Work through the process

1. 01
   Start a distinct change record

   Create a reference connecting the original item and proposed replacement. Include the affected project, quantity, supplier evidence and reason. Do not overwrite the original equipment requirement while the proposal is under review, because other teams may still be working from the accepted baseline.
2. 02
   Route technical evaluation

   Provide the qualified reviewer with the required specification and proposed alternative evidence. The workflow can assemble the documents and track the decision; it should not decide compatibility or compliance. Record any conditions that must travel with the accepted substitution.
3. 03
   Calculate commercial consequences

   Have the responsible team identify changes to price, timing, quantities and other contractual commitments. Keep supplier cost changes separate from the customer-facing commercial decision. A lower supplier price does not automatically determine the revised customer charge.
4. 04
   Collect approval for the actual revision

   Tie customer and internal approvals to the final scope version. If the proposed equipment or price changes after review, reopen the affected approval. Preserve partial decisions where only some equipment or project phases are accepted.
5. 05
   Apply and reconcile downstream updates

   Route purchasing changes and billing revisions through verified actions and authorized owners. Store the resulting order or billing references under the change record. Confirm that the old requirement is superseded only after the accepted revision is applied, and prevent repeated triggers from creating duplicate requests.
6. 06
   Preserve the decision when the swap is rejected

   A rejected alternative remains useful project history. Record the reason, reviewer and affected equipment requirement without replacing the active specification. Procurement can then investigate another option without repeating the same technical question. Sales should see the resulting commercial or timing issue, but the rejection itself should not automatically create a customer price change. Keep the next proposed alternative as a separate version so its approvals cannot accidentally inherit the rejected proposal's context.

Handle the exceptions explicitly

Technical approval includes conditions

Keep those conditions attached to the handoff and verify the responsible team accepts them.

Customer approves timing but not price

Leave the commercial revision unresolved until the required scope and price decision exists.

Original equipment already shipped

Route the return or disposition decision separately instead of pretending the order was never placed.

What to verify before expanding

• Original and proposed equipment remain distinguishable.
• Qualified review precedes the accepted specification change.
• Approvals identify the exact commercial revision.
• Purchasing and billing updates retain the same change reference.

Technical references

• Stacksync HubSpot connector and object support
• Acumatica construction management
• Stacksync event triggers