SubPro Book a fit call

Construction submittal software that carries the record to closeout.

Every submittal dispute ends with someone producing the record. SubPro builds the cited log and the submittal packages, then keeps statuses, revisions, and transmittals moving, so closeout opens on a record instead of a reconstruction.

Book a fit call Read why SubPro exists
Project dashboardLog, submittal packages, and schedule on one screen
The SubPro project dashboard showing the submittal log, submittal packages, and schedule for one job

Give every desk the same record

General contractors

Turn one project manual into a cleaner starting log before anyone chases responsible parties and dates.

Preconstruction teams

Spot the major submittal obligations early and hand operations a log instead of a blank tracker.

Document control

Page references, review notes, and matched product data stay on the row, so the next reviewer is not starting over.

Closeout owners

Whoever inherits the last month inherits final statuses, stacked revisions, and transmittal dates on file.

A jobsite field trailer at night: a laptop open on a plan table beside a leaning stack of tabbed project manual volumes and rolled drawings
The record starts in the trailer, in the first week, when the project manual is still the only source of truth on the job.

Hold the whole thread, spec page to binder

A construction submittal lives a long life: defined in the project manual, logged, assembled, reviewed, revised, sent, returned. Most software picks one slice of that life, and every handoff between tools is a chance for the record to lie.

SubPro removes the handoffs instead of refereeing them. The log is born cited. Submittal packages attach to their rows instead of a folder named FINAL_v3. When a question needs the manual rather than the log, the built-in chat answers with the page it lives on.

A site office shelf of white labelled binders beside a row of colored folders, one binder lying open on the desk below, a hard hat by the window
The thread used to live on a shelf: one binder per division, the spec page somewhere in another.

Outlive the month-three spreadsheet

Week one: a color-coded tracking spreadsheet, current. Month three: the PE who owned it moved jobs and four rows say "see email." Then closeout asks whether the fire-stopping product data was approved, and answering from a dead spreadsheet is a two-week archaeology project.

The record dies because keeping it alive was somebody's second job. The fix is a record that updates because the work went through it.

A dusty site office desk with a coffee-stained printed spreadsheet under a stapler, a closed laptop under a film of dust and a dead potted plant by the window
Month three is where the hand-built spreadsheet stops matching the job.

Answer closeout with a lookup

Eighteen months after substantial completion a cabinet door delaminates, and the owner's rep asks whether the installed product matched the approved submittal. The row shows the approved revision, the transmittal that carried it, and the spec page that required it.

SubPro is not a closeout binder generator, and the approval judgment stays with your PM, PE, and the design team. The record simply exists, cited and dated, when someone closes the job out.

Watch the record at four points in the job

  1. Day oneEvery required submittal as a row, grouped by division, each carrying its page. The team's first contact with the log is reviewing it.
  2. The review weeksRows confirmed, reassigned, and argued about. Flags mark substitutions and owner decisions. Submittal packages land on their rows.
  3. The long middleSubmittals go out under dated transmittals. An addendum rewrites two sections and the rows revise in place, history intact.
  4. The last monthFinal statuses, approved revisions, transmittal dates, and the citation trail back to the spec book. The reconstruction becomes an export.

Draft one mechanical division's front stage

Equipment data

Rows for air handlers, pumps, and terminal units in Division 23 Mechanical, HVAC, each tied to its source page.

Coordination drawings

A row for mechanical coordination drawings, flagged where three trades will argue over who owed them.

Controls submittals

Building controls and sequence-of-operations rows kept distinct, so each is reviewed on its own.

Handoff to tracking

The reviewed Division 23 set exports as a cited register for your approval workflow.

A sheet metal worker on a scissor lift fastening a rectangular duct run hung on threaded rod under an exposed concrete deck, a work light clamped above
Division 23 arrives as rows before the first duct goes up: hangers, supports, and the bracing that gets skimmed.

Follow a small section's whole life

Section 10 44 00 Fire Protection Specialties is a dozen rows of extinguishers and cabinets that still generate paperwork for a year. The product data and cabinet shop drawings are born cited. The architect kicks back the cabinet finish, and the first submission stays in the row's history under the revision. The resubmission goes out under a dated transmittal, and two years later the fire marshal's question takes one click.

Gloved hands running a caulking gun along a joint between two concrete slabs, backer rod set in the joint and masking tape on either side, overcast daylight
Section 07 92 00 is four rows and one joint. The log follows it from product data to the last bead.

Take the objections seriously

"The GC makes us use their portal anyway." Then use it. SubPro is where your side gets done: the cited log, the assembled submittal packages, your statuses and history. The exports drop into whatever the GC runs, and your record outlives their portal access.

"We do not need another system to update." Agreed. Status moves because a reviewer clicked approve. History exists because a revision was uploaded.

"Software reading our spec book makes people nervous." Every extracted row carries the page it came from, and the project manual is deleted after the run, never retained, never used for training. The data handling page has the detail.

"We are too small for this." Small teams have it worst: a nine-person specialty contractor has a PM doing submittals at night. Pilots start with one project manual for that reason.

Lean on the document library

Product data on file

Over 11,000 manufacturer documents in the open library: product data, safety data sheets, installation guides.

Manufacturers indexed

Over 800 manufacturers cataloged by division in the manufacturer index.

Sources you can defend

Every entry keeps its origin, and the document rights process stands behind it.

A building supply counter with stacks of product catalogs and a paint chip board, a contractor in a work jacket reading an open catalog binder, a shelf of brochures behind him
The binders on the supplier's counter hold the same literature the library holds, already matched to the row.

Construction submittal software FAQ

Where does SubPro fit in the construction submittal process?

The whole span. It reads the project manual and drafts the cited log, assembles the submittal packages, then keeps statuses, revisions, and transmittals current until closeout opens on a complete record.

Do I still need my submittal tracking tool?

Only if a GC requires one. SubPro tracks the submittals it builds: status, revision history, and the transmittal record per item. Where a mandated portal exists, the XLSX and PDF exports drop your record in without a retyping project.

Does SubPro manage approvals or closeout?

It keeps the record for both. Your PM, PE, and design professionals still make the calls. SubPro contributes the paper trail those calls sit on: what was submitted, revised, sent, and returned, ready when closeout asks.

Can we start on a job that is already underway?

Yes. Run the project manual whenever you arrive. The cited draft becomes a baseline to reconcile against whatever log exists, which is usually the fastest audit that log has ever had.

Start the record on one job.

Before status and closeout comes a first draft. One project manual from a live job is enough to see the record take shape.

Book a fit call Build my log instead