For the project coordinator or office manager at a commercial specialty subcontractor finishing 5–40 jobs a year — and, secondarily, for small GCs producing the same package upward: Closeout keeps a closeout requirements register on every job, tracks each required document as it is collected, and runs a pre-submission gap audit, so the package submitted is complete on first submission. Retainage — 5–10% of contract value — is the money at stake while an incomplete package sits through rejection cycles; Closeout's work is the register, the tracking, and the audit that finds the gaps before submission.
How it works
- Add a job — project, GC, contract value, and retainage %
- Build the job's requirements register — each required item, its spec-section citation, and its category; six standard categories are offered as an editable starter set
- Track each required document as it is collected — Missing, Collected, or Deficient, with a note
- Watch the live math on every job — retainage dollars at stake (contract value × retainage %), completeness %, and the gap list
- Run the pre-submission gap audit — a printable gap audit report, cited to spec sections, plus a binder index of the collected documents
- Work from the dashboard — jobs ranked by dollars at stake
The scope — audit and assembly only
Closeout's scope is settled, and it is narrow on purpose: audit and assembly only. It keeps the register, tracks what has been collected, audits the package for gaps against the register, and assembles the package and its binder index.
It never guarantees that a GC or an owner accepts a package. Acceptance is the GC's and the owner's decision, not Closeout's to promise. The honest claim is completeness on first submission — a package with nothing missing against its own register — and nothing more. Closeout does not promise acceptance, approval, or that retainage will be released.
A requirements register on every job
Every job carries its own closeout requirements register: each required item, cited to its spec section, with its category. Six standard categories are offered as an editable starter set, so the register starts from a standard shape and is then made the job's own.
Today, requirements are entered into the register directly — item, spec-section citation, and category — by the subcontractor's own team. That entry is how the register is built; the honest state below states plainly what is not claimed about getting requirements in automatically.
Collection tracking — every document, in a state
Each required document is tracked as it is collected, in one of three states — Missing, Collected, or Deficient — with a note kept against it, so a deficiency is recorded, not hidden.
The register's live math runs as collection proceeds: the retainage dollars at stake on the job (contract value × retainage %), the package's completeness %, and the gap list of what is still missing or deficient.
The pre-submission gap audit
Before a package is submitted, Closeout runs a gap audit against the job's register: what the register requires, checked against what has been collected, with every gap named.
The audit produces a printable gap audit report, cited to spec sections, and a binder index of the collected documents — the assembled package's own index. The dashboard ranks jobs by dollars at stake, so the jobs are worked in dollars-at-stake order.
Where it stands — the honest state
Closeout is forming its first subcontractor pilot group now. The door below is a subcontractor pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
Document ingestion is not proven, and it is not claimed. Real spec and submittal documents arrive as scans of widely varied quality, and ingestion across that variety has not been verified — it stands as an engineering verification still to be performed. Until it is performed, requirements are entered into the register directly, as described above, and no robust ingestion of arbitrary scanned documents is promised.
Upload-link collection does not exist yet. There is no upload link today through which a supplier, a GC, or any other outside party can send a document into Closeout — collection is recorded in the register by the subcontractor's own team. Building that collection is gated outreach work; it has not been built and it has not been run.
No price has been set. A price range exists in our market research as a hypothesis; it has not been validated and it has not been decided, so no price is shown here and there is nothing to buy on this page.
The scope does not change in the pilot: audit and assembly only — no guarantee of acceptance, and no promise that retainage will be released, in the pilot or after it.
Subcontractor pilot application
This is a subcontractor pilot application — an application to join Closeout's first subcontractor pilot group, not an account sign-up and not a purchase. Tell us who to reach, your company, and your trade. If you like, tell us how many jobs you typically have in closeout at a time, and how your team assembles closeout packages today. We will be in touch about the pilot group.