Scope

What the review covers, and what it does not.

The fine print, in plain English.

Prelaunch draft

Draft of the current pilot preview

This is an honest prelaunch draft, not a finished legal document and not boilerplate. Where a control or commitment is not yet implemented, this page says so instead of promising it.

The one promise

We check paper, not pipes. We compare your closeout documents to your spec and cite the page for every finding. We don't inspect the install, certify code compliance, or guarantee your GC accepts the package — we flag what's likely to be kicked back, before you submit.

What the service is

Closeout Signal reviews the closeout documents you supply for one commercial HVAC or mechanical project, and compares them against the project requirements you supply.

The output is a readiness summary, a prioritized findings report with source references, a requirement checklist, a downloadable action tracker, and a review coverage record.

How the review is performed

Review is AI-assisted. Documents are extracted (with OCR where a text layer is absent), compared against your supplied requirement lines, and each finding is linked back to a document and page.

Not every report is manually reviewed. Unresolved exceptions receive targeted human review. We do not claim that a person reads every page of every package.

What is explicitly excluded

The following are outside the service. If you need them, this is not the right product.

  • Chasing your suppliers or manufacturers.
  • Assembling, indexing or reformatting your closeout package.
  • Engineering opinion or code compliance certification.
  • Verification of installed conditions or site inspection.
  • Any guarantee of acceptance, approval, payment or retention release.
  • Technical accuracy review of record drawings or balancing figures.

Requirement source is your input

A project-specific review depends on you supplying the requirement source — specification sections, a closeout checklist, or a submittal/manual register. We do not infer your project requirements from industry norms.

If no requirement source is supplied, we tell you a project-specific review is not possible instead of producing a generic report.

Certainty and status language

Requirement lines are reported as Found (evidence appears to satisfy it), Problem (an issue was identified), Missing (not found in the supplied files), or Couldn't confirm (unable to verify). None of these means approved: we never report a requirement as Compliant, Approved or Certified, because a document review cannot establish that.

Items we could not read or resolve are reported as Couldn't confirm, with the file and page named. Uncertain items are never silently passed.

Volume, timing and the pilot

The published limits — one project, one contractor package, up to 75 files and 500 total pages, a 14-day recheck of up to 20 files and 100 pages, and a 2-business-day turnaround target — are pilot assumptions being validated.

They are targets and working assumptions, not contractual guarantees. Oversize packages are identified before payment.

The pilot

Free pilot — 5 slots. Mechanical subs get a complimentary closeout review. $395 per project after the pilot.