--- title: "Solar closeout Genie for serial and handover evidence" description: "Use Genies to prepare a solar project handover packet with traceable equipment and completion evidence." canonical: https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records last_modified: 2026-09-18 --- # Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Use Genies to prepare a solar project handover packet with traceable equipment and completion evidence. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision A solar project-closeout Genie can assemble equipment identifiers, approved scope, completion records and required handover documents into a review packet. Ask it to show the source and project association for every important item, distinguish installed equipment from ordered equipment, and identify missing evidence. It should not infer commissioning results, technical acceptance or customer approval. Project and technical owners validate the packet before customer handover or any related billing action. Explore the complete [solar installation and O&M services integration and automation hub](https://www.stacksync.com/industry/construction/solar-installation-service) for the systems and processes around this guide. ![Summary card: Solar closeout Genie for serial and handover evidence](https://www.stacksync.com/images/blog-highlights/icp-genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records.webp) ## 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 | Record | Owner | Operating rule | | --- | --- | --- | | Approved final scope | Project manager | Identify the governing equipment and change-order revisions. | | Installed equipment evidence | Field and asset owners | Provide verified device identifiers tied to project locations. | | Completion record | Qualified responsible team | Retain actual recorded completion and test evidence without inferred results. | | Handover checklist | Project administration | Define required documents, reviewers and customer delivery status. | ![Record ownership diagram: Approved final scope, Installed equipment evidence, Completion record](https://www.stacksync.com/images/blog-diagrams/icp-genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records.webp) *Define the record owner and the rule before enabling updates.* ## 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. ![6-step operating sequence: Solar closeout Genie for serial and handover evidence](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## 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. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-solar-installation-service) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real approved final scope example and the exception your team handles most often, for example shipment serial differs from field record. - [AI Project Closeout for Solar Installers](https://www.stacksync.com/use-case/genies-solar-project-closeout) - [Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence](https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence) - [Solar Equipment Supplier EDI: Reconcile Panels, Inverters, and Partial Project Deliveries](https://www.stacksync.com/blog/solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries) - [Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts) - [Check Solar Installation Readiness Across Salesforce and NetSuite](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) - [Blu Banyan and Stacksync: A Partnership Built for the Next Era of Solar and Construction Operations](https://www.stacksync.com/blog/blubanyan-stacksync-partnership) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync HubSpot connector and object support](https://docs.stacksync.com/two-way-sync/connectors/hubspot) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync Genies](https://www.stacksync.com/ai-agents) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can the Genie create missing commissioning evidence? No. It can identify what is missing and route the request. Technical records and results must come from the qualified people and processes responsible for the work. Why use live connected data for closeout? Current project, equipment and change records help avoid assembling a packet from an obsolete scope. The agent still needs explicit evidence and review rather than assuming the latest record is automatically correct. What is a strong closeout pilot? Choose a project with an approved equipment substitution and a late document. Verify that the Genie finds the mismatch, preserves the source references and asks the right owner for the missing evidence. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence 5 min read read](https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence) [App tips Check Solar Installation Readiness Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) [App tips Distinguish Solar End Customers from Installation Partners 7 min read read](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)