Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records

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

An installer has completed a commercial rooftop project, but serial information is spread across delivery records, field notes and photographs. The customer expects a handover packet, and the project manager needs to know whether the records reflect the equipment actually installed after an approved substitution. A Genie can collect candidate identifiers and compare them with the final scope. Missing or conflicting evidence should become a focused task rather than a fabricated complete asset list.

Records, ownership, and update rules

Work through the process

1. 01
   Define the handover requirements

   Give the Genie the project's actual closeout checklist and accepted scope revision. Specify which documents and identifiers are required for the intended handover. A generic list of solar documents should not override the agreement or the technical team's requirements for this project.
2. 02
   Collect evidence by equipment and location

   Join delivery records, field captures and approved substitutions using project and equipment references. Keep ordered, received and installed states separate. A serial appearing on a shipment record is useful evidence but does not alone prove that the device was installed at the recorded location.
3. 03
   Compare against final approved scope

   Identify missing items, unexpected equipment and identifiers that still refer to a superseded component. Require source references for each difference. The agent can describe the mismatch, while the project or technical owner decides whether the record needs correction or the underlying work needs review.
4. 04
   Prepare the packet and gap list

   Produce a concise inventory of available evidence and one owned task for each missing requirement. Clearly mark provisional identifiers or unreadable documents. Do not make the packet appear complete by generating plausible serial values, dates or acceptance statements.
5. 05
   Review and record the handover

   Have the designated owners validate their sections before customer delivery. Store the approved packet version and delivery reference. If a document changes later, route the revision with a clear explanation and preserve the original delivered version so service teams know what the customer received.
6. 06
   Keep the service handover usable after construction

   Ask the service team to locate a device, its final approved model and the relevant closeout evidence from the completed packet. A folder can be complete for project administration yet difficult to use during a later service call. Retain stable equipment and project references in the handover structure so future users can follow the evidence without relying on a salesperson's memory or a filename that omits the installed location.

Handle the exceptions explicitly

Shipment serial differs from field record

Show both references and ask the asset or field owner to confirm installed identity.

Substituted equipment still has old documentation

Flag the superseded documents and request the approved replacement evidence.

Required completion record is absent

Keep the packet incomplete and assign the responsible qualified team.

What to verify before expanding

• Every listed installed device has a traceable evidence source.
• Ordered equipment cannot automatically become installed equipment.
• Missing technical records remain explicit gaps.
• The delivered handover packet has an approved version and reference.

Technical references

• Stacksync HubSpot connector and object support
• Stacksync NetSuite connector and object support
• Stacksync Genies
• Stacksync event triggers