Skip to content

Solar closeout and handover review

Hand over every solar project with nothing missing.

Heliobrief reads your closeout package, extracts equipment models, serials and dates, checks them against each other and your handover checklist, and sends each exception to a named reviewer before the owner sees it.

In development · Early access open to EPCs, owners and O&M teams

HB-024/Westfield Distribution Center
Sample data

Closeout package

  • As-built single-line E-501

    Drawings · 4 pp

  • Equipment schedule

    Equipment · 3 sheets

  • Commissioning report INV-01–05

    Commissioning · 22 pp

  • Utility PTO letter

    Required · not received

Handover readiness8 / 12

Cross-document check

INV-04 model

As-built E-501 · p.2

Corvane CX-110-US

Commissioning report · p.14

Corvane CX-100-US

EX-1041 · Blocking

Model mismatch opened for review. Assign a reviewer to confirm the installed unit.

Source-linked fields

Every extracted model number, serial and date points back to the file and page it came from.

Your checklist, enforced

Handover requirements come from your contract or owner template, not a generic list.

Cross-document checks

As-builts, equipment schedules, commissioning reports and warranties are compared field by field.

A reviewer on every exception

Nothing is resolved automatically. Each finding is assigned, decided and logged by a person.

The closeout problem

The panels are energized. The paperwork isn’t finished.

A commercial solar handover can involve hundreds of documents from a dozen parties. Most teams still assemble and check them in shared folders and spreadsheets, one project manager and one PDF at a time.

  1. 01

    Records arrive from everywhere

    Subcontractors, the utility, the AHJ, equipment manufacturers and the commissioning agent each send their own files, in their own formats, on their own schedule.

  2. 02

    Review is manual and memory-based

    Someone opens the equipment schedule in one window and the commissioning report in another and compares serials line by line. On a 2 MW site that is hundreds of values.

  3. 03

    Mistakes surface after handover

    An inverter swapped during commissioning that never made it onto the as-built. A warranty registered against the wrong serial. The owner or O&M provider finds it months later.

What it costs when it slips

  • Final payment and retainage held until the owner’s engineer accepts the package
  • Warranty claims slowed by serial numbers that do not match the installed equipment
  • O&M teams starting work from equipment records that are already out of date
  • Project managers re-checking the same package for every portfolio buyer or lender

Adding people doesn’t fix it. Every new project brings another folder, another checklist version and another set of serials to compare by hand.

The Heliobrief approach

One workspace per project. Every document classified, every key field extracted and compared, and every gap turned into an owned exception.

See the capabilities

The workspace

Try the review workspace on a sample project.

Switch between three fictional projects, filter the document register, open a record to see its extracted fields, and resolve exceptions to watch handover readiness change.

  • → Click a readiness bar to filter documents
  • → Open EX-1041 in the review queue
  • → Resolve or waive with a note
  • → Export the pack index
Sample data

HB-024 · Commercial rooftop · 486 kWdc / 400 kWac

Westfield Distribution Center

Owner: Northgate Logistics Trust

Handover readiness

50%

6 of 12 checklist items clear

Documents reviewed

8/12

3 awaiting a reviewer

Open exceptions

5

3 blocking handover

Target handover

15 days

24 Oct 2026

Document readiness by category

Open exceptions, last 5 weeksnow 5

Draft insight · verify before sharing

3 blocking exceptions stand between this project and handover. The highest-impact item is inverter model mismatch on inv-04: The as-built single-line lists a CX-110 at position INV-04, while the commissioning report records a CX-100.

Activity

  • HB

    Extracted 31 fields from Electrical_Inspection_Signoff.pdf

    07 Oct, 16:12

  • JE

    Jordan Ellis uploaded OM_Manual_WDC.pdf and Spare_Parts_List.xlsx

    07 Oct, 15:40

  • JE

    Jordan Ellis assigned EX-1042 to Marcus Bell

    06 Oct, 10:05

  • PR

    Priya Raman marked String_IV_Curve_Tests.pdf as reviewed

    05 Oct, 17:22

  • HB

    Opened EX-1041 from a cross-document model check

    05 Oct, 14:51

Interactive demonstration with fictional projects, people and equipment. No files are uploaded or processed, and nothing you do here leaves your browser.

Capabilities

Built around the documents a solar handover actually depends on.

Six connected capabilities take a project from a pile of closeout files to an accepted handover. Each one hands its output to the next.

01 / Sets up step 1

Project workspaces and checklist templates

Each project gets a workspace built from the checklist that governs its handover. Templates set which documents are required, which fields to extract and which comparisons to run.

Everyone works to the same definition of “complete”, project to project.

C&I rooftop handover

Template · 24 items
  • As-built single-line diagram
  • Inverter commissioning report
  • IV curve test results, all strings
  • Utility permission to operate
  • Racking warranty

02 / Feeds extraction

Document intake and classification

Upload files as they arrive. Heliobrief identifies the document type from its content, not its filename, and files it against the matching checklist item.

No more hunting for which scan is the commissioning report.

Drop closeout files or forward from email
  • scan_0931.pdf

    Inverter commissioning report

    High
  • WDC-E501-r3.pdf

    As-built single-line

    High
  • IMG_4471.pdf

    AHJ inspection sign-off

    Medium

03 / Feeds checks

Field extraction with source links

Equipment models, serial numbers, ratings, dates and signature regions are extracted from scanned and native files. Each value links to its page, and low-confidence reads are flagged for confirmation.

Reviewers verify a value in one click instead of re-reading the report.

Commissioning report · page 14

CX-100-US · SN CV1104-20931
Model
Corvane CX-100-US
Serial
CV1104-20931
Rated AC
100 kW
Start-up date
18 Sep 2026

04 / Raises exceptions

Cross-document checks

Configured rules compare the same field across the equipment schedule, as-builts, commissioning records and warranties, and check counts and date order.

Substituted inverters and missing startup records surface before handover, not after.

FieldEquipment scheduleCommissioningWarranty
INV-03 serialCV1104-20877CV1104-20877CV1104-20877
INV-04 modelCX-110-USCX-100-USCX-110-US
INV-06 start-upListedNot foundRegistered

05 / Gates the pack

Exception review queue

Every mismatch, gap or missing signature becomes an exception with its evidence attached and a draft summary. Reviewers assign, resolve, waive or escalate, and each decision needs a note.

Open items have owners, and nothing is closed without a reason on record.

  • Inverter model mismatch

    EX-1041

    Unassigned
  • Startup record missing

    EX-1042

    Marcus B.
  • Warranty date conflict

    EX-1044

    Priya R.

06 / Completes the handover

Handover pack and review history

Reviewed documents are assembled into an indexed pack with an equipment and serial register, any outstanding exceptions, and the full decision history.

Owners, lenders and O&M teams receive a package they can verify themselves.

Handover pack · HB-019

Prepared for owner acceptance

Export
  1. 1Drawings4 files
  2. 2Equipment and serial register2 files
  3. 3Commissioning and testing3 files
  4. 4Warranties2 files
  5. 5Review history1 files

How it works

From first upload to accepted handover in five steps.

Step 1 of 5

Set up the project

Create a workspace and choose the handover checklist that matches the contract: C&I rooftop, ground mount, carport or a custom owner template.

Checklists define the required document types, the fields that matter in each, and the rules used to compare them.

Output · sample project

  • Workspace HB-024
  • Checklist: C&I rooftop handover
  • 24 required items

Who it’s for

For everyone who signs off on a solar handover.

The same project record serves the team that builds the system, the owner who accepts it and the people who maintain it.

Commercial EPCs and installers

The problem
Project managers close out several rooftop and carport systems at once while crews have already moved to the next site.
How they use Heliobrief
They run every project against one closeout checklist and chase missing items from the exception queue rather than from email threads.
The result
Fewer returned packages, and retainage conversations that start from a complete record.

Technology

How We Use Amazon Web Services

Heliobrief’s architecture is designed on AWS around the path a closeout document takes: uploaded once into encrypted project storage, read by Amazon Textract, classified and summarized with Amazon Bedrock, checked by serverless rules, and recorded as fields, exceptions and decisions that reviewers act on. Each stage scales with the number of documents in flight, so a 40-file rooftop and a 400-file ground mount use the same pipeline.

  1. 01

    Document intake

    API Gateway

    Pre-signed uploads per project

  2. 02

    Secure storage

    Amazon S3

    Encrypted, versioned project files

  3. 03

    Processing

    Textract · Step Functions · Lambda

    OCR, orchestration, rule checks

  4. 04

    AI intelligence

    Amazon Bedrock

    Classification and draft summaries

  5. 05

    Review workspace

    DynamoDB · Cognito

    Exceptions, decisions, access control

Services and their role

Every AI output, from document type to drafted summary, is presented to a reviewer as a suggestion with its source attached. Using these services does not by itself make Heliobrief compliant with any specific standard; security controls are validated before customer documents are processed.

  • Amazon S3: Stores uploaded closeout documents, page images and generated handover packs in per-project, encrypted buckets with versioning.
  • Amazon Textract: Reads text, tables, forms and signature regions from scanned commissioning reports, datasheets, permits and as-built drawings.
  • Amazon Bedrock: Classifies document types, normalizes extracted equipment fields and drafts plain-language exception summaries for reviewers to verify.
  • AWS Step Functions: Orchestrates the per-document pipeline from upload to extraction, classification and rule checks, with retries for long-running jobs.
  • AWS Lambda: Runs checklist rules and cross-document comparisons, such as serial counts, model matches and date ordering, as each document finishes processing.
  • Amazon DynamoDB: Holds projects, checklist state, extracted fields, exceptions and the append-only review history behind each handover pack.
  • Amazon API Gateway: Exposes the application API and issues pre-signed upload URLs so documents go directly to storage.
  • Amazon Cognito: Authenticates workspace users and scopes access to the projects and roles each reviewer is assigned.

Progress and early access

Help shape the first release.

Heliobrief is being built with a small group of solar teams who close out projects every month. If closeout review takes more of your week than it should, we’d like to learn how you work.

Company
Founded 2026
Stage
Product in development
Access
Early access by request

What early access includes

  • A walkthrough of the review workspace using sample closeout packages
  • A working session on your handover checklist and the fields you check by hand today
  • Input into the checklist templates and comparison rules we build first
  • Early access terms and data-handling arrangements agreed before any of your documents are processed

Request early access

Tell us about your team and the projects you hand over.

Optional. Project types, typical package size, or how you review closeout today.

We use these details only to respond. See our Privacy Policy.

Pricing

Plans sized to how many projects you close out.

Pricing is set with each early access customer based on active projects and reviewers. Tell us about your volume and we’ll send a proposal.

Starter

For installers closing out a handful of commercial projects at a time.

Custom pricing

  • Project workspaces with standard handover checklists
  • Document intake, classification and field extraction
  • Exception review queue with assignments
  • Exportable handover pack with review history
Request pricing

Growth

For multi-team EPCs

For EPCs and developers running closeout across several teams and project types.

Custom pricing

  • Everything in Starter
  • Custom checklist templates and comparison rules
  • Cross-project exception reporting
  • Reviewer roles for owner’s engineers and external partners
Request pricing

Enterprise

For asset owners and O&M providers standardizing acceptance across a portfolio.

Custom pricing

  • Everything in Growth
  • Owner templates shared with multiple EPCs
  • Portfolio-level handover status
  • Security review and data-handling terms agreed in contract
Contact sales

Company

The Team Behind Heliobrief

Heliobrief was founded in 2026 to give solar project teams a clearer, more reliable way to close out and hand over the systems they build, starting with the documents that most often hold up completion.

Follow Heliobrief on LinkedIn
  • Olamide Adebayo

    Founder

    Sets Heliobrief’s product direction and leads conversations with solar project teams about how closeout reviews run today.

  • Tomiwa Justing

    Co-founder

    Works on the Heliobrief product and platform, from document intake and extraction workflows to the reviewer experience.

Contact

Talk to the Heliobrief team.

Questions about the product, a partnership, or how your team runs closeout today. Send a message or email us directly.