SubPro Book a fit call

Traditional submittal management is ending.

Not because of any software. The job changed. Every product carries more paperwork, every project carries more changes, and fewer people are left to hold the record together.

It worked for a long time.

Nobody did anything wrong.

For decades a PM kept the submittal record together by hand. The spec book on the desk, the log in Excel, the product data in a folder, the transmittals in email, the stamped copies in a binder and the closeout documents in a box at the end of the job.

A good PM could keep all of that in step. The job moved slowly enough, and the people doing it had done it for twenty years. That isn't a broken process. It's a process built for a job that doesn't exist anymore.

What changed

Four things, and every one of them is on the public record. Under each one is what SubPro does to take the risk out of it.

  1. More paper on every product. A data sheet and a shop drawing aren't enough anymore. Federally funded jobs need Buy America certification for the iron, steel and construction materials: a signed letter from the manufacturer that names the project and where the product was made. Since July 2022, California state jobs need a facility specific environmental product declaration for rebar, structural steel, flat glass and mineral wool insulation, and a product over the carbon limit can't go in. Federal GSA jobs bought under the Inflation Reduction Act need that declaration at bid, with no waiver. Every one of those is a document somebody has to find, check and keep on the right row.

    What SubPro does about it. SubPro reads the whole spec book and puts every document it asks for on the log, with the page that asks for it. A certification or a declaration the book requires is a row from day one, not a surprise at closeout. The manufacturer's documents come from the library with their issue dates, and your company's own documents are used first.

  2. More changes to track. 796 RFIs on the average project. The Navigant Construction Forum studied about 1,300 projects and found 796 RFIs on the average job, with a median of 9.7 days to answer each one. Add the addenda, the substitutions and the resubmittals on top of that. Any one of them can change what a submittal has to show, and every change has to land on the row it touches.

    What SubPro does about it. SubPro reads each addendum and shows the change on the rows it touches. Every submittal keeps its revisions, its time out for review and the stamped copy that came back, so nobody has to remember which version is current.

  3. Fewer people to keep the record. 349,000 new workers needed in 2026. Associated Builders and Contractors puts the need at 349,000 new construction workers in 2026 and 456,000 in 2027, and most of it is to replace people who are retiring. The people leaving are the ones who knew which revision was current and why a substitution got approved. Most of that was never written down. It was in their heads.

    What SubPro does about it. The knowledge goes on the record instead of in someone's head. Every row shows the page it came from, and every review, decision and revision stays with the submittal. When a PM leaves or a new one picks up the job, they open the row and see its whole history.

  4. The gaps already cost money. 48% of rework traces back to bad data and miscommunication. FMI found poor communication and poor project data behind 48% of the rework on U.S. jobs, about $31.3 billion a year, with people losing almost two working days a week hunting for information and fixing problems that shouldn't have happened. A later Autodesk and FMI study put the worldwide cost of bad construction data at $1.85 trillion in 2020.

    What SubPro does about it. SubPro checks each submittal against the schedule on the drawings before it goes out, and flags every row it isn't sure about with the reason, so your PM reads those first. Fewer submittals come back, and less work gets torn out because the wrong product went in.

The real problem was never making submittals.

It's keeping one submittal record true from the spec book to closeout.

Making a submittal is one task. Keeping it right is the whole job: the requirement on page 412, the product that meets it, the document that proves it, the review that approved it, the revision that changed it and the warranty you owe at the end.

Today that record lives in four places at once: a log, a folder, an inbox and a binder. Every time something changes, the copies drift a little further apart. The spreadsheet was never the enemy. The drift between the copies is, and on today's jobs it moves faster than anyone can keep up with by hand.

What comes next is one living record.

Once that record exists, keeping copies in step by hand stops making sense.

The next way to run submittals keeps one record. It reads the project manual, holds every requirement with the page it came from, tracks every revision, keeps every decision and follows the job all the way to closeout.

It's the same thing that happened when email replaced the fax and the drawing set moved off the plan table. Nobody had to argue for it. The job outgrew the old way.

  • Every requirement traceable to its page
  • Every decision kept on the record
  • Every submittal one record, from the spec book to closeout

Where SubPro fits

We built SubPro to be that record.

SubPro reads the spec book and the drawing schedules, builds each submittal with the manufacturer's documents behind it, and keeps every review, revision and closeout document on one record. Your team makes every call. Nothing goes out until a person on your team sends it.

See what a submittal intelligence system is

See one of your own jobs on one record.

Book a fit call and send one project manual. We run it and you judge what comes back.