The demo always goes well. Somebody shares a screen, a submittal log fills itself in from a project manual nobody had to read, and everyone in the room quietly does the math on what that saves.
Six weeks later a project engineer is sitting at the same desk at four in the afternoon with Division 08 open in one window and a manufacturer site in the other, building the thing that actually gets sent to the architect. Both of those are true at once. The reason is that the word submittal means two different jobs depending on who says it, and the software market has quietly split along that line without telling anyone.
So when six products describe themselves with nearly the same sentence, the question that sorts them is not which one is best. It is this: when the thing finishes running, what am I holding?
There are four answers in circulation. A list of what the project manual requires. A place to route paperwork and see who is sitting on it. A red line report on something somebody already built. Or the submittal package itself, covered, transmitted, ready to go out the door.
Most of the money wasted in this category is someone buying the first answer while believing they bought the fourth.
The job, in order
On a commercial job with a 1,200 page project manual, submittals break down roughly like this.
- Read every section and pull out what has to be submitted. Division 07 sealants, Division 08 door hardware, Division 09 paint, on down. This is the submittal log, also called the register.
- Decide who owes each item and when, against the schedule.
- Gather the actual content. Manufacturer product data, cut sheets, shop drawings, samples, test reports, certifications.
- Assemble it into a submittal package with a cover sheet and a transmittal, in the format the general contractor requires.
- Route it, track the review, handle the rejection, resubmit.
Those are not one job. Reading a project manual and chasing down a cut sheet have almost nothing in common except the word on the invoice, and they get done by different people at different points in the schedule. Which is why the tools that do them well are built by different companies, aimed at different buyers, and priced on different things.
The comparison
Features move, so check the current documentation before you sign anything. This is what each product says about itself as of September 2026. There is a denser version of this on the submittal software comparison page, checked capability by capability against each vendor's own documentation, if you want the grid without the argument around it.
| Tool | Primary buyer | What it reads | What you hold at the end | What is still on you |
|---|---|---|---|---|
| Spreadsheet | Anyone | Nothing. You read | A log you typed | Steps 1 through 5 |
| Pype AutoSpecs (Autodesk) | General contractor, sub, owner | The spec book | A draft submittal log | Sourcing, assembly, routing |
| Procore Submittals | General and specialty contractor | Spec sections, through Submittal Builder | The log, then a routed workflow with status, lead times and revisions | Sourcing and assembly of the content |
| Bluebeam | Architects, engineers, GCs, subs, estimators | PDFs you already hold | Marked up, stamped, combined PDFs and an exportable log | The log, the sourcing, the submittal record |
| Submittal.com (BuildSite) | GC, owner, trade contractor, supplier | Your input, plus a product library | An assembled submittal package and a closeout book | The spec reading, in part |
| BuildSync | Subcontractor, general contractor, engineer | The spec book, or a package you already have | An assembled submittal package for mechanical, electrical and plumbing equipment, or a compliance report on one | Every other division, and judgment on each flag |
| SubPro | Trade contractor or general contractor | The spec book | The register, then the submittal packages, each row cited to its spec page, tracked to closeout | Your review before it goes |
What the log tools promise
Autodesk writes about its own boundary more clearly than anyone else in this set. AutoSpecs promises "comprehensive and accurate draft submittal logs in minutes," identifies action submittals and closeout items and QA material, compares one issue of a project manual against the next, and then publishes the result into a project management platform.
Every verb on that page points at the list. Draft the log, compare the log, publish the log.
That is a good product with a clearly marked edge, and it is built for the general contractor, who owes the log. The subcontractor owes the contents, which is a different debt entirely. So when a sub buys a log generator and then finds a week of cut sheet gathering still waiting, nobody oversold anything. They bought step one when their problem lived at step three.
Procore sits beside this rather than against it. The Submittals tool organizes and manages the workflow: submitter and approver roles, sequential or parallel review, status per item, submittal packages for bulk processing, and a Submittal Builder that generates submittal items out of spec sections. What you get from it is visibility. On a job with four hundred items and six reviewers, everyone can finally see the same answer to "where is the sealant submittal," which used to be a phone call and a guess.
What it will not do is go and find the product data for 08 71 00 door hardware and lay it out in order. It is the road, and a very good one. It was never the truck.
Where the assembly tools sit
Submittal.com takes the opposite position and takes it on purpose. Their framing of the register is the most honest sentence any company in this category has published: "The Log: Manual OR Fully Automated. One takes forever, the other happens too fast." Their answer is semi automated, with control where the user wants it.
Behind that sits a product library with twenty years of accumulated data and a closeout assembler for operation and maintenance manuals and warranty books. Their published proof is a customer conversation about one section, sixteen items, six manufacturers, put together in a little over an hour where it used to take a day and a half. That is a real tool with a real library, and the scope judgment stays with you: it will not read your project manual and tell you what belongs in the package.
BuildSync does both halves, and it is the closest thing in this set to a direct competitor for a sub. Its subcontractor page is headed "Submittal Package Generation and Review Software for Subcontractors" and tells you to "Build compliant submittal packages from scratch." It has its own product database, it names manufacturers, and it says the finished article "comes out looking like your team built it," with your cover sheet and your table of contents.
The limit is scope, not ambition. Generation is bounded to mechanical, electrical and plumbing equipment, and their own FAQ repeats it. Shop drawing review, they say plainly, is outside what the product does. So if your trade is Division 08 or Division 09, the build half of that product is not aimed at you yet.
They also publish the number nobody else will say out loud: $805 to correct a single rejected submittal, against industry rejection rates they put at 30 to 40 percent. They show their working too, which almost nobody does. The figure comes from their own survey of construction professionals, and they publish the arithmetic behind it rather than asserting a round number. It is still a vendor researching a problem the vendor sells against, so weigh it as that rather than as an independent study. Naming the fear is still the right instinct. Assembly is tedious, but a package coming back marked Revise and Resubmit with three weeks of float already gone is a different kind of problem.
The gap this leaves
Line those four artifacts up and there is a hole in the middle of them.
One tool reads the project manual and produces the list. Another routes the paperwork. A third inspects a finished package for errors. But the step where somebody sits down with a 1,200 page project manual and turns Division 08 into an ordered stack of correct manufacturer product data with a cover sheet on it is still, almost everywhere, a person with two monitors and a cold coffee.
That step is where the hours go. Forty hours across a project is an ordinary number for a mid sized sub on a spec heavy job, and very little of it draws on anything the person learned in twenty years of doing the work. Mostly it is reading, matching, downloading and stapling.
Go back to the table and read the first three rows together rather than one at a time. Reading the book, finding the documents, building the package. Almost every product in this category does one of those three well and hands you the other two. AutoSpecs reads and stops. Procore reads and routes, and the documents are yours to gather. Submittal.com has a genuine library and genuine assembly, and tells you honestly that the reading is still your job. BuildSync does all three, which is why it is the closest thing here to a direct competitor, and bounds the building half to mechanical, electrical and plumbing equipment.
Which is the gap SubPro was built into, and the only claim I will make in this article. It reads every division of the project manual for your scope. It then goes and finds the manufacturer documents rather than asking you to, out of a library that currently runs to more than 400 indexed manufacturers and over 16,000 documents, each entry keeping its source. Then it assembles the submittal package behind your own transmittal, one PDF, with the spec page reference on every row so the person checking it can verify a line instead of taking it on faith. Rows it could not resolve arrive flagged rather than stated as confidently as everything else. Someone reviews the package before it reaches you. Your documents come out of the system once processing finishes, and none of them go anywhere near model training.
It also does not stop at the package. The submittal goes out from the app, the response comes back onto the row, waiting rows count the days they have been out, and revisions keep their history. The schedule, the lead times, the addenda comparison and the closeout documents sit on that same record. What it is not is the general contractor's system of record, and it does not want to be. Where the job runs on a platform the submittal still goes into that platform, and the export carries the record across instead of somebody retyping it.
How to buy
Three questions settle most of it.
Do you owe the list or the contents? A general contractor who owes a complete and defensible register has plenty to choose from, and the good log generators are genuinely good. A trade contractor who owes the actual product data has already done the easy half once the log arrives, and has almost nothing to choose from. Worth noting that the two are not always different companies: a self performing general contractor owes both, which is why a couple of products in this set refuse to pick a side.
Where did the hours really go last month? Go and look rather than guess. Hours lost to chasing status and hours lost to assembling content point at completely different purchases, and the second kind will not move at all if you buy workflow software.
What does the general contractor require? Their format is not up for discussion. Whatever you buy has to land in it without somebody reformatting afterward, otherwise the work moved rather than left.
Then one more that costs nothing. Ask every vendor to open a finished submittal package from a real project, redacted if it has to be: the cover sheet, the transmittal, the product data in spec order, the whole object the reviewer actually receives. Some of them will change the subject to a dashboard. That answer tells you exactly which of the five steps their product stops at, which is the only thing you were trying to find out.