How to Review Grow Light As-Built Records Before Final Payment

A grow light as-built record should answer one commercial closeout question before final payment: what was actually installed, where is it installed, which approved product rows does it match, and who accepted any deviations? Treat the record as project evidence for procurement, cultivation, facilities, and the supplier. It is not a substitute for local electrical inspection, safety approval, crop-performance validation, or a commissioning report written by the installer.

1. Separate as-built evidence from sales documents

A quotation, purchase order, packing list, and layout proposal are useful starting points, but none of them prove the final installation. The as-built package should state the project name, room or greenhouse bay, installed date range, fixture families, controller model, approved drawing revision, open punch-list items, and the person authorized to release each area. If a buyer is holding final payment, this record should make the remaining commercial question narrow: approved, rejected, or accepted with named exceptions.

2. Match installed fixtures to current product rows

Current Sanity data lists the Number LED TB600 greenhouse toplight as a 600 W fixture with 2100 umol/s PPF, 3.5 umol/J PPE, AC 200-480 V input, 150 degree beam angle, 0-10 V dimming, passive thermal management, 7.0 kg listed weight, and five-year standard warranty. In an as-built review, those rows should be used to identify the installed equipment and expose deviations. They should not be treated as proof of the site's light level, crop result, energy saving, utility incentive, or final inspection outcome.

3. Record the control row, not just a powered-on screen

Current Sanity data lists the SLC 0-10 V dimming controller with 222 x 162 x 32 mm dimensions and 12 V / 1 A power from an included 100-240 VAC adapter. The closeout packet should add the missing site-specific context: which rooms or bays it controls, which channel names are used, which fixtures sit on each output, what schedule or ramp settings were left in service, and who is allowed to change those settings after handover.

4. Use DLC reporting fields as a documentation prompt

DLC Hort V3.0 is useful closeout context because it emphasizes reported product information such as intended use, dimensions, representative image, dimming and control method, connector or transmission hardware, and integral control capability. Do not turn that into a listing claim unless the exact model and directory evidence are available. Use it as a checklist prompt: the as-built file should show the fixture identity, mounting location, control method, connector or address group, and any product variation that differs from the approved submittal.

5. Keep environmental and wiring evidence visible

UL Solutions describes horticultural lighting safety considerations around PPF and PPE testing, photobiological effects, damp or wet environments, ingress protection, and wiring or connection methods. For final payment review, that context supports a practical evidence row for each area: installed fixture photo, mounting height or location reference, cable routing photo, connector photo where accessible, controller or dimming line evidence, environment notes, and any unresolved safety or inspection exception. Do not accept a generic installed photo when the record cannot be traced to the approved model and room.

6. Retain release evidence, deviations, and owners

ISO guidance on documented information separates documents that support operation from records retained as evidence of results achieved, including release records, acceptance criteria, traceability, and objective evidence. A grow-light closeout file should therefore include more than the final drawing. Add deviation numbers, corrective actions, buyer approvals, open issues, photo dates, record owner, and final release status. If the supplier changed a cable, controller position, label, mounting accessory, or fixture count, the record should show whether the buyer accepted that change before payment release.

7. Build one closeout row per controlled area

A useful row includes area name, fixture model, installed quantity, serial or batch reference if available, mounting reference, controller model, channel or address group, dimming method, approved drawing revision, final photo set, unresolved deviations, acceptance owner, and release decision. Keep rejected or conditional rows in the file. They are often the most valuable evidence if final payment, warranty review, or a repeat-order change becomes disputed later.

Next step for an OEM or project buyer

Before releasing final payment or a repeat order, ask Number for the approved product rows, installed-area table, controller row, photo set, deviation list, and release owner for the first completed room or bay. For private-label or modified projects, bring the as-built template into the OEM/ODM discussion before the sample or first installation is approved.