Closeout binder, assembled as you go
Substantial completion hits, and the owner wants the closeout package. Now someone is digging through email for the inverter O&M manual, calling the module supplier for a warranty certificate, and...
The problem
Substantial completion hits, and the owner wants the closeout package. Now someone is digging through email for the inverter O&M manual, calling the module supplier for a warranty certificate, and trying to find out whether the megger test report from the string testing ever got saved anywhere other than a technician's tablet.
None of this is hard. It is scattered. Documents arrive during the job from subs, suppliers, inspectors, and the crew, and they land in inboxes, shared folders, text threads, and the back of a truck. By the time anyone needs the full set, the person who received a given document may be on another site.
The cost is time at the worst moment. Final payment and retainage often depend on the package being complete. A missing sign-off or an unsigned test report can hold things up for weeks over paper that existed all along.
How the agent workflow works
The agent works from a closeout checklist built from the contract's closeout requirements and the specs. Each line is a required item: O&M manuals by equipment type, warranty documents, commissioning and test reports, inspection sign-offs, as-builts, training records, lien waivers.
It watches the places documents actually show up: the project email inbox, the shared project folder, and the daily log entries. When something arrives, it reads the file name, the contents, and the surrounding message, and matches it to a checklist line. It then drafts a filing action: rename the file to the project convention, move it to the right folder, mark the line as received.
It also reads for problems. A warranty certificate with the wrong project name, a test report with no signature, an O&M manual for a different inverter model than the one in the submittals. These get flagged, not filed.
Once a week, the agent produces a short missing-items list sorted by responsible party, with draft reminder messages for each. A line might read: "Racking sub: structural inspection sign-off, not received. Draft follow-up attached."
The human checkpoint is firm. The superintendent or project engineer approves every filing, every flag resolution, and every outgoing reminder. Nothing is sent to a sub or owner without a person reading it. Nothing is marked complete on the checklist until a person confirms the document is the right one.
When daily logs mention an event that generates paper, like "AHJ inspector signed off on rough electrical" or "commissioning of inverter block 2 finished," the agent adds an expected-document line and watches for the paperwork to follow.
What you need to set it up
- A shared folder structure with one folder per closeout category, created at project start.
- A closeout checklist in a spreadsheet or similar, built from the contract and specs. Plan a few hours for this, mostly reading the closeout section carefully.
- An AI agent tool that can read your project email and shared folder and write to the checklist. Access should be read-plus-draft, not send.
- Daily logs in a form the agent can read, such as typed entries rather than photos of handwriting.
- One named person who reviews the agent's queue. Ten minutes a day is a reasonable target.
Where it breaks
The checklist is only as good as the specs. If the contract requirement is buried in a division you did not read, the agent will not look for it. A person has to review the checklist against the contract once.
Documents that never touch the inbox or folder are invisible. If a tech keeps test results on a device or a sub hands over a paper binder on site, the agent cannot see it until someone uploads it.
Scanned documents with poor quality, photos taken at an angle, or handwritten forms can be misread. The agent may match a document to the wrong line or miss that a signature is absent. This is why filing needs human approval.
Similar equipment causes mismatches. On a site with several inverter models or multiple buildings, the agent can attach a manual to the wrong asset. Check model numbers.
It cannot judge whether a document is acceptable to the owner, only whether one exists and looks consistent. A test report with passing-looking numbers still needs an engineer's eye.
Finally, reminders get ignored if they come from a tool nobody respects. The weekly list works when the superintendent actually brings it to the sub meeting.
The bottom line
This workflow does not make closeout easier. It moves the work to when the documents are fresh and the people who have them are still on the job. The agent keeps the list and reads the incoming paper. A person decides what counts.
Set it up in the first weeks of the project, check the checklist against the contract, and review the queue daily. At substantial completion, you are confirming a package that is mostly built.