Commercial Solar Commissioning and Closeout Checklist

A commercial solar commissioning checklist should prove what was installed, how it was tested, which approvals apply, what the owner received, and what remains open. It should not turn “panels installed,” “inspection passed,” “meter changed,” “monitoring online,” or “permission to operate” into interchangeable claims.

Treat closeout as a chain of evidence. Preserve the approved design, controlled as-builts, equipment and serial register, local inspection records, utility authorization, commissioning test report, monitoring baseline, training file, warranties, spares, O&M handoff, punch list, and owner signoff. Record an exception when evidence is unavailable rather than marking the row complete.

This is a neutral owner checklist, not a test procedure or a statement that a Sunburst project has passed any gate. The actual contract, approved plans and specifications, equipment instructions, authority requirements, utility documents, and qualified project team control acceptance.

Keep nine acceptance statuses separate

A project can move through these statuses in different sequences, but one does not automatically prove another.

Status	Evidence to request	What it does not prove by itself
Approved design baseline	Contract requirements, approved drawings/specifications, submittals, utility conditions	Field installation matches the design
Construction or mechanical completion	Contractor completion record and field status	Final inspection, safe energization, or function
Permit inspection status	AHJ inspection and correction records for the identified permit scope	Utility authorization or owner acceptance
Utility status	Interconnection documents, meter/witness records, written authorization tied to the installed configuration	Every contract test or closeout item is complete
Commissioning status	Approved procedures, recorded results, exceptions, corrections, and retests	Future production or warranty coverage
Monitoring handoff	Meter/device map, data receipt, accounts, credentials, exports, known gaps	Active human review or complete performance confirmation
Operations turnover	Manuals, training, safety/emergency information, warranty/O&M contacts, spares	All punch-list items are closed
Punch-list status	Item register, responsible party, due date, evidence, reinspection/retest, closure	The owner has accepted remaining risk
Owner acceptance	Authorized signed record with exceptions and responsibilities	A promise beyond the controlling contract

Use a status such as not started, submitted, under review, accepted, accepted with exceptions, rejected, superseded, or not applicable. Add the responsible party, evidence link, revision/date, reviewer, and next action. A green dashboard without source documents is not a closeout file.

The commercial solar proposal checklist should define these deliverables before award. This page shows how a property owner checks the records after construction.

Start with the approved design intent and commissioning plan

Commissioning should test a documented design, not reconstruct the intended system after installation. Begin with a controlled baseline containing:

• owner project requirements and operating objectives;
• signed construction and equipment scope;
• issued-for-construction and approved permit drawings;
• specifications and approved submittals;
• structural, civil, roof, electrical, fire, communications, and monitoring requirements as applicable;
• utility application, study, agreement, protection, metering, export, and operating conditions;
• equipment manufacturer installation and commissioning instructions;
• approved substitutions, requests for information, design clarifications, and change orders;
• responsibilities for testing, witnessing, correction, retest, reports, training, and acceptance; and
• the commissioning plan, procedures, instruments, prerequisites, hold points, criteria, and schedule dependencies.

The Department of Energy’s current PV installation and commissioning guidance recommends planning and budgeting commissioning before construction. For commercial, industrial, and utility-scale projects, it points to the applicable IEC 62446 framework for documentation, array testing, and whole-system testing.

That federal guidance is a useful category framework. It is not a project specification, South Carolina mandate, Sunburst procedure, or substitute for the edition and requirements actually adopted by the contract and authorities. Do not copy a generic checklist’s technical values into an acceptance plan without qualified review.

Create a requirements traceability matrix

Link every material requirement to the evidence that closes it.

Requirement source	Requirement ID	Installed evidence	Test/inspection evidence	Exception or change	Reviewer/status
Contract/specification	Record clause	Drawing, submittal, photo, equipment row	Report and result	Change order or open item	Named party
Permit/AHJ	Record sheet/note	Approved/as-built condition	Inspection record	Correction notice	Named authority/party
Utility	Record agreement/condition	One-line, settings, meter/protection	Utility-required evidence	Revised application/change	Named utility/party
Manufacturer	Record document/version	Exact installed configuration	Required startup/test record	Approved deviation	Named qualified party
Owner requirement	Record requirement	Installed feature/document	Demonstration/training	Accepted exception	Authorized owner

This matrix prevents an important detail from falling between drawings, a commissioning report, and the punch list. It also shows whether a substitution changed testing, utility, warranty, or monitoring requirements.

Deliver a controlled approved and as-built drawing set

The permit set, construction set, and as-built set serve different purposes. The as-built record should show the final installed condition and identify who prepared it, when, from which field information, and under what review or approval status.

Depending on the project, the turnover set may include:

• site plan and equipment locations;
• array layout and module map;
• roof zones, attachment or ballast layout, structural details, reinforcement, and penetrations;
• ground-mount foundations, grading, drainage, stormwater, fencing, roads, vegetation, and underground utilities;
• carport structure, drainage, clearances, protection, traffic, lighting, and accessible-space interfaces;
• electrical one-line and three-line diagrams where used;
• string, branch, homerun, conductor, conduit, trench, junction, disconnect, panel, switchgear, transformer, protection, grounding and bonding records;
• rapid-shutdown, labeling, placard, fire-access, emergency, and shutdown information;
• meter, current transformer, sensor, gateway, communications, network, monitoring, and data architecture;
• point of interconnection and utility-owned versus customer-owned boundary;
• equipment settings and protection/control records where appropriate; and
• safe progress or completion photographs linked to locations and dates.

Do not accept a folder called “final drawings” without a document register. Each file needs a title, document number, revision, date, status, author, reviewer/approver where applicable, and superseded-file relationship. Store native files when the contract requires them, not only flattened PDFs.

For rooftop work, the solar roof structure guide explains the structural design and field-verification boundary. At closeout, record the final structural/attachment package and unresolved roof observations; do not assume the electrical commissioning report certifies the roof.

Reconcile field changes

For every deviation or substitution, record:

1. original requirement and installed condition;
2. reason for change;
3. affected design, structural, electrical, monitoring, safety, warranty, permit, and utility interfaces;
4. technical review and manufacturer evidence;
5. owner, designer, AHJ, utility, or other authorization as applicable;
6. changed tests and acceptance criteria;
7. price and schedule treatment under the contract; and
8. final as-built and equipment-register update.

A redlined construction drawing can be useful source evidence, but it is not automatically the controlled final as-built. Define the contract’s final-document standard.

Reconcile every installed component and serial number

Create an equipment register that ties physical assets to drawings, submittals, test records, monitoring, warranties, and spares.

Useful fields include:

• asset and stable ID;
• manufacturer, exact model, serial number, rating, quantity, and installed location;
• module/string/branch/inverter or other parent-child mapping;
• firmware, grid profile, settings version, or software identifier when material;
• approved submittal and substitution record;
• listing/certification and installation documentation used by the project;
• permit and utility document relationship;
• commissioning report/test identifier;
• monitoring device/site/account relationship;
• warranty document, registration status evidence, start-date source, and contact;
• spare or replacement relationship; and
• photograph/nameplate evidence where safely captured.

Compare the register with purchase and delivery records, field observations, as-builts, monitoring inventory, commissioning data, and warranty records. Resolve duplicates, missing serials, swapped locations, damaged/replaced equipment, and devices visible in one system but absent from another.

Do not say the installed equipment is contract-compliant because the count matches. Model, rating, compatibility, configuration, condition, approved substitution, and documentation also matter. Do not energize, open, or access electrical or roof equipment solely to complete an owner spreadsheet; qualified personnel should collect technical evidence under the site safety plan.

Separate AHJ inspection from utility PTO

South Carolina commercial solar can involve building, electrical, structural, fire, zoning, land-disturbance, stormwater, or other reviews depending on the site and scope. Record the actual authorities and permits rather than using “city approved” as a blanket status.

For each permit or review, retain:

• authority name and jurisdiction;
• permit/application number and exact scope;
• approved plan and revision;
• inspection type, date, inspector record, and status;
• correction notice and response;
• reinspection or final status; and
• certificate or other closeout record when applicable.

The South Carolina Building Codes Council publishes the statewide code-adoption boundary, while local authorities administer project requirements. The applicable editions, modifications, and interpretations depend on the filing and jurisdiction. Keep the actual permit and final record rather than writing a broad code-compliance statement into the owner checklist.

Utility interconnection is a separate record set. Retain:

• legal utility and account/meter identity;
• application and installed-system capacity/configuration;
• studies, agreements, conditions, upgrades, fees, and correspondence;
• utility-reviewed drawing, protection, controls, settings, metering, and export/nonexport records as applicable;
• construction authorization or other pre-energization milestone where used;
• completion submission, inspection/witness, correction, meter, and settings records;
• written permission to operate or other provider authorization tied to the installed configuration; and
• subsequent changes, amendments, and ongoing obligations.

The commercial interconnection guide owns the application-to-PTO process. At closeout, verify the resulting evidence. Do not infer utility authorization from a local final inspection, equipment energization, an operating inverter, visible monitoring data, a changed meter, or a verbal update.

Use the South Carolina utility directory to locate the named provider, then keep its current project-specific documents. A city or county does not prove the utility.

Build a commissioning test evidence register

The owner does not need a pile of unconnected test sheets. It needs a register that shows what requirement each test addressed and what happened after an exception.

For every inspection, electrical test, functional demonstration, controls check, or monitoring verification, record:

• test ID and system/component boundary;
• requirement source and approved procedure/version;
• prerequisite and safe operating condition;
• responsible tester and required qualification;
• date, time, location, environmental or operating condition as relevant;
• instrument make/model/ID and calibration status where required;
• witness and witness role;
• expected criterion under the approved project documents;
• actual recorded result and units;
• status: pass, fail, not tested, not applicable, interrupted, or pending;
• exception and immediate safe disposition;
• corrective action, responsible party, and due date;
• retest or reinspection evidence; and
• final reviewer and signoff.

Possible record groups include physical installation observations, array and circuit test records, grounding/bonding and protection records, inverter/equipment startup, controls/settings, disconnect and shutdown functions, metering/communications, functional sequences, and whole-system performance tests. The exact list and values must come from the applicable contract, plans/specifications, equipment instructions, code/AHJ, utility, and qualified commissioning team.

This article intentionally does not provide a technical test procedure. PV systems contain hazardous DC and AC voltage, elevated work, and equipment-specific sequences. Owners should use qualified personnel working under the approved safety and commissioning plan.

Distinguish a test from an acceptance conclusion

A recorded test demonstrates only the condition, configuration, instruments, method, and time represented by the report. It does not by itself establish:

• utility PTO;
• compliance outside the tested scope;
• future energy production;
• warranty coverage or remedy;
• absence of every latent defect;
• active monitoring/O&M service; or
• owner acceptance under the contract.

DOE’s distributed-energy construction and acceptance framework separates commissioning from formal acceptance and calls for as-builts, installed-equipment verification, reports, witnessed records, punch-list corrections, training, manuals, spares, utility documents, and warranty records. Use those as evidence categories, not as federal acceptance rules for a private project.

Establish a monitoring baseline and complete the data handoff

“Portal online” is a starting condition, not a complete monitoring handoff. Verify the physical and logical data chain.

Map the measurements

Record:

• production meter, inverter measurement, revenue meter, export/import meter, weather sensors, irradiance, temperature, and other points actually included;
• meter and current-transformer direction, scaling, unit, interval, timestamp convention, time zone, and data owner;
• device-to-inverter, string, array, site, gateway, and account mapping;
• communications route, local network/cellular/cloud dependencies, and fallback behavior;
• calibration or configuration evidence required by the project;
• data retention, raw/export/API access, backup, platform subscription, and administrator rights; and
• known gaps, estimates, duplicate points, commissioning-mode data, or date/time discontinuities.

Compare the portal inventory with the equipment and serial register. Verify that the owner receives the roles and credentials promised by contract and that access does not depend solely on one departing employee or contractor.

Record the baseline without promising production

The turnover packet can include a baseline model or expected time series, its source files, design configuration, weather/resource basis, losses, availability assumptions, degradation treatment, metering boundary, and version. It can also include a defined initial data-review period and exception process.

Do not label a short operating window “proof of annual production.” Weather, grid events, curtailment, facility conditions, outages, data quality, equipment configuration, and the modeled reference can affect comparison. The commercial solar data guide provides the source/units/time/exception discipline for the handoff.

If alerts or ongoing review are part of the project, identify the threshold, recipient, review hours, ticket process, escalation, and responsible provider from the controlling contract. A monitoring platform does not establish that Sunburst or anyone else actively watches or responds to every alert.

Turn over safety, labels, instructions, and training

Closeout should leave facility personnel able to identify normal status, avoid unsafe action, follow owner-approved procedures, and reach the right party. It does not turn the facilities team into solar electricians.

Record labels and operating information

The project-specific package may include:

• installed equipment, disconnect, rapid-shutdown, electrical-source, directory, hazard, emergency, and access labels required by the approved design and authorities;
• label/placard schedule and safe photographs showing location and legibility;
• one-line/site diagram and shutdown information available at the required location;
• emergency contacts for owner, utility, installer/EPC, O&M provider if contracted, equipment support, roof/site, fire/safety, and insurer;
• normal and abnormal indicators;
• safe owner-level shutdown or emergency information from approved documents;
• restrictions on reset, restart, energization, roof access, enclosure access, and electrical work;
• utility outage/return and site emergency interfaces; and
• severe-weather or casualty evidence-preservation and inspection route.

Do not improvise shutdown or reset instructions in the closeout meeting. Use the approved as-built system and manufacturer/utility/AHJ procedures.

Document training as a deliverable

The training record should identify:

• audience and responsibilities;
• trainer and qualifications where required;
• date, location, agenda, duration, and materials;
• system overview, boundaries, controls, monitoring, access, safety, emergency, warranty, service, roof/site, and record topics actually covered;
• live or simulated demonstrations performed under an approved procedure;
• attendees and acknowledgement;
• questions, answers, missing information, and follow-up owner; and
• refresher or new-personnel provision if included.

Training completion does not transfer responsibility for unqualified service, electrical work, engineering, utility settings, or authority decisions to the owner. Record those boundaries.

Reconcile warranties, spares, and O&M responsibility

Turnover should map each warranty to the exact installed equipment or work and identify the party who can act under it.

For each warranty or obligation, retain:

• complete controlling document and version;
• warrantor, beneficiary, administrator, and claim contact;
• equipment/work covered and model/serial relationship;
• start-date source, term, registration evidence, maintenance/notice conditions, and transfer rules;
• exclusions, limitations, required evidence, claim procedure, and remedy;
• diagnosis, travel, roof/site access, removal, shipping, return, labor, replacement, permits, utility work, recommissioning, and monitoring responsibility; and
• open claim, unresolved registration, or conflict with another agreement.

Do not treat a brochure or term length as coverage proof. Use the public Sunburst warranty overview as a question framework, then apply the actual signed project and manufacturer documents. This article does not state a warranty outcome or that Sunburst administers a particular commercial claim.

Inventory contract spares

For every spare or special tool required by contract, record:

• item/model/part number and compatible asset;
• quantity and condition;
• storage location and environmental/security needs;
• owner and custodian;
• shelf-life, inspection, firmware, or preservation needs where applicable;
• issue/consumption approval and record; and
• replenishment, obsolete-part, substitution, and disposal responsibility.

Spare delivery is not the same as installed compatibility. Tie the item to approved documentation.

Define the operating handoff

Identify the owner, asset manager, monitoring administrator, O&M provider, warranty contacts, roof/site providers, network/IT contacts, utility contact, and emergency route. State the start date and scope only from the controlling agreements.

SB-A092’s commercial O&M agreement checklist remains a separate post-PTO decision. Commissioning closeout should deliver its inputs—asset register, as-builts, baseline, tests, manuals, warranties, spares, credentials, and open items—without promising an O&M service.

Control the punch list and conditional acceptance

Every punch-list item needs more than a description and due date.

Record:

• stable item ID;
• date/source and exact location/equipment;
• observed condition with safe evidence;
• related requirement/drawing/specification;
• category: safety, authority/utility, functional, monitoring/data, warranty/record, workmanship, site/roof, cosmetic, or other;
• effect on energization, operation, acceptance, payment, warranty, or owner use under the actual contract;
• interim safe condition or restriction;
• responsible party and corrective scope;
• dependencies, owner access/authorization, and due date;
• evidence required for closure;
• reinspection, retest, document revision, or utility/AHJ action;
• reviewer, closure date, and owner acceptance status; and
• reopened-item rule if the correction does not hold.

Do not let a critical safety or authority item disappear inside a long cosmetic list. Conversely, do not label every record correction a safety defect. Use qualified review and the contract to determine severity and consequence.

Define conditional versus final acceptance

If the contract permits conditional, substantial, phased, or partial acceptance, the signed record should identify:

• exactly which system/phase and deliverables are accepted;
• open items and risk/operating restrictions;
• who owns correction, access, retest, and document update;
• retainage, payment, insurance, care/custody/control, warranty commencement, and loss allocation only as the contract provides;
• date and evidence required for final closure; and
• what happens if an item is not closed.

This page does not recommend a payment milestone or legal acceptance language. Owner counsel, technical advisers, insurer/lender, and authorized contract administrator should review the actual agreement.

Scope any independent review in writing

An independent commissioning authority or owner engineer can add a separate perspective, but “third-party review” is not a complete scope.

Define:

• organization, qualifications, licenses/credentials where applicable, insurance, and conflicts;
• reporting line and who may rely on the work;
• design-review stage and documents reviewed;
• construction observations, sampling basis, inaccessible areas, and exclusions;
• tests written, performed, witnessed, or only reviewed;
• instruments and data access;
• authority to stop work or only report observations;
• punch-list creation, correction review, retest, and closure role;
• permit/utility/structural/roof/fire/controls/network boundaries;
• report format, findings classification, reliance limitation, and record ownership; and
• later-season, anniversary, refinancing, transfer, or O&M reviews if separately contracted.

DOE’s commissioning guidance recommends considering third-party verification across multiple lifecycle phases. That does not mean every commercial project must buy every review or that Sunburst supplies one. Match the scope to project risk, procurement structure, lender/insurer requirements, owner capability, and contract.

Build one indexed digital turnover folder

Use a folder and register that another qualified person can navigate without the original project manager.

Suggested top-level structure:

1. contracts, scope, responsibility matrix, and acceptance criteria;
2. approved design, submittals, RFIs, substitutions, and changes;
3. permits, inspections, AHJ corrections, and final records;
4. utility application, studies, agreements, meter/witness, and PTO records;
5. controlled as-builts and completion photographs;
6. equipment/serial/settings register and manufacturer documents;
7. commissioning plan, procedures, instruments, results, exceptions, and retests;
8. monitoring architecture, baseline, data dictionary, accounts, exports, and exceptions;
9. safety, labels, emergency, operations, manuals, and training;
10. warranties, registrations, claims, spares, and O&M contacts;
11. punch list, corrective evidence, conditional/final acceptance, and responsibility signoff; and
12. superseded archive with clear version control.

Keep a master index with file title, document number, revision, date, status, author, reviewer, related equipment/site, superseded document, owner, retention, confidentiality, and storage location. Protect credentials in an appropriate secure system rather than a broadly shared spreadsheet.

At final review, ask a facilities or asset-management recipient who was not immersed in construction to locate one inverter serial, its test record, warranty, drawing location, monitoring association, open item, and service contact. Difficulty following that chain reveals a handoff gap.

Confirm the Sunburst closeout scope before contract award

Sunburst’s public commercial solar service states that the company handles commissioning and activation generally. Public materials do not define the commissioning plan, tests, as-built package, serial register, monitoring baseline, training, warranties, spares, punch-list treatment, acceptance record, or independent-review scope for a commercial project.

Bring the proposed acceptance matrix and owner-required deliverables to a commercial solar assessment and request a written closeout scope. Ask the signed proposal to identify what Sunburst supplies, what the owner or another contractor supplies, which tests and reviews apply, who signs each record, and what remains outside scope. Do not rely on this checklist as proof of any included deliverable or project result.

Ask us for the turnover index during the bid stage rather than at substantial completion. A Sunburst commercial closeout package includes the approved and as-built drawing set, the installed component and serial register, AHJ inspection records kept separate from the utility’s written permission to operate, the commissioning test evidence, the monitoring baseline and account handoff, labelling and owner training, and the warranty and spares reconciliation — all indexed in one folder that belongs to you.

Our commercial solar service treats that package as part of the contracted scope, backed by our lifetime full-system and roof-penetration warranty on the installation work. If long-term performance monitoring matters to your facilities team, the same discipline is what makes later diagnosis of underproduction possible instead of speculative.

Related: proposal comparison, interconnection evidence, commercial solar by city. Request a commercial assessment to see the closeout scope in writing.

Final owner review questions

1. Which drawing/specification and acceptance revisions control?
2. Does every requirement link to installed, inspected, tested, and closeout evidence?
3. Is the final as-built set controlled, indexed, and reconciled to field changes?
4. Do models, serials, quantities, locations, settings, monitoring, and warranties agree?
5. Are all permits, inspections, corrections, and final records tied to their exact scope?
6. Is written utility authorization retained for the installed configuration?
7. Does every test record show procedure, criterion, instrument, result, exception, correction, and retest?
8. Are monitoring points, units, time, mapping, accounts, data export, baseline, and gaps documented?
9. Are safety labels, shutdown/emergency information, contacts, and access restrictions current?
10. Is training documented with attendees, materials, questions, and responsibility boundaries?
11. Are controlling warranties, registrations, serial maps, conditions, exclusions, and claim roles present?
12. Are contract spares identified, stored, and assigned?
13. Is the post-PTO monitoring/O&M owner and scope documented without assumptions?
14. Does every punch-list item have an owner, due date, safe disposition, evidence, and closure path?
15. Does any conditional/final acceptance state the exact exceptions and retained responsibilities?
16. Is third-party review defined rather than assumed?
17. Can a future facility manager, service provider, insurer, lender, buyer, or reviewer navigate the folder?
18. Does the signed Sunburst scope match every closeout statement on which the owner relies?

Frequently asked questions about solar closeout

Is a passed electrical inspection the same as project completion?

No. A passed inspection means the authority having jurisdiction accepted the installation against the adopted code for the permitted scope. Completion also requires the utility’s written permission to operate where applicable, the commissioning tests the contract defines, the turnover documentation, training and the punch-list resolution. Treat them as separate statuses with separate evidence.

What is the difference between permission to construct and permission to operate?

Permission to construct allows the work to proceed under the approved permit. Permission to operate is the utility’s written authorization to energise and, where relevant, export. Operating equipment before receiving it can violate the interconnection agreement and, in some cases, void protections. Keep the two dates and documents separate in your project record.

Who should hold the monitoring account after turnover?

The owner. Ask for the platform, the account ownership, the administrative rights, the data-retention terms and the baseline data set at handoff. Where a contractor retains access for service purposes, that should be a permission granted by the owner rather than the owner receiving access from the contractor.

What belongs in the commissioning test record?

The tests performed, the conditions during each test, the acceptance criteria applied, the measured results, the equipment settings recorded, who witnessed the test and any deviations with their resolution. A summary sheet that states “system commissioned” without measured results is not a test record.

Can final payment be tied to closeout deliverables?

Yes, and it commonly is. Define the deliverables and the acceptance criteria in the contract before award, then tie the final milestone to their delivery. Retaining a defined amount pending documented acceptance is a standard construction practice, not an adversarial one.

What spares and consumables should be identified at turnover?

Anything the manufacturer’s operations and maintenance documents call for, plus items with long lead times such as specific inverters, monitoring gateways, communication devices and fuses. The register should name the exact model, the quantity supplied, where it is stored and who is responsible for replenishment.

Sources and methodology

This checklist was researched on August 10, 2026. Primary sources include:

• U.S. Department of Energy FEMP, Install and Commission a Photovoltaic System
• U.S. Department of Energy FEMP, Distributed Energy Project Phase 5: Construction and Performance
• U.S. Department of Energy FEMP, Technical Specifications for On-site Solar Photovoltaic Systems
• National Renewable Energy Laboratory, Photovoltaics Standard Work Specifications
• National Renewable Energy Laboratory and partners, Best Practices for Operation and Maintenance of Photovoltaic and Energy Storage Systems
• South Carolina Energy Office, Interconnection guidance

Federal and laboratory sources provide a planning framework, not a project specification, test result, South Carolina approval, or Sunburst deliverable. Replace this general checklist with the actual contract, approved plans/specifications, equipment instructions, filing-date requirements, AHJ and utility records, commissioning procedures, and qualified professional judgment for the project.