See where every project stands: row counts, review progress, and package activity on one screen.
Tracking tools are only useful after the starting log exists. SubPro handles the prep work before tracking starts: spec review, draft rows, review flags, package context, and editable handoff files.
Everything SubPro builds sits in the open: the rows, the evidence behind them, and the packages, all checkable before tracking begins.
See where every project stands: row counts, review progress, and package activity on one screen.
Approvals, edits, source checks, schedule prep, and package creation stay connected to the row being reviewed.
The tracker is not the problem. The empty tracker is. SubPro reads the spec book, shapes the initial register, checks what needs attention, and prepares a package your team can take forward.
Use one project spec set to create a cleaner starting log before the team starts chasing responsible parties, dates, and approval routing.
Spot major submittal obligations earlier, review scope sensitive items, and give operations a more useful handoff than a blank tracker.
Keep page references, review notes, and package support close to the handoff so cleanup is faster and the next reviewer is not starting over.
A construction submittal moves through a predictable arc: the specifications define what is required, someone builds the register and assembles the packages, the packages get routed for review and approval, and the approved records get tracked to closeout. Most software on the market lives in the routing, approval, and tracking stages. That work only starts once the register and packages already exist.
SubPro owns the stage before all of that: reading the spec book, drafting the register, keeping source context visible, and assembling package evidence. It is the part that has traditionally been a project engineer with a spreadsheet and a week to spare. When SubPro finishes, the team has a complete, source-backed starting point to hand to whatever tracking process they already run.
That is why SubPro does not compete with a tracking tool. It feeds one. An empty tracker is a chore. A tracker loaded with a reviewed, source-backed register is a running start.
Take Division 23 00 00 Mechanical, HVAC, where the submittal list runs long across equipment and controls. SubPro handles the prep stage like this.
Rows for air handlers, pumps, and terminal units, each tied to its 23-section reference and source page.
A row for required mechanical coordination and shop drawings, flagged where trades overlap and a decision is needed.
Rows for the building controls and sequence-of-operations submittals, kept distinct so each is reviewed on its own.
The reviewed 23-division set exports as a source-backed register, ready to load into your approval and tracking workflow.
At the front, before tracking, approvals, and closeout. It turns the specifications into a reviewable first-pass log and package set, then hands that off to whatever your team uses to route, stamp, and track approvals.
Yes, and they work together. SubPro does not route or approve submittals. It prepares the log and package so your tracking tool starts from a complete, source-backed set instead of an empty register.
No. SubPro prepares a reviewable handoff before tracking and approval work. Your PM, PE, document control, and professional review processes stay in the loop for approvals and closeout.
Yes. Pilots start with a fit call and one spec set so the team can review output quality, timing, and data handling needs before scaling up.
The pages around this one, from the first pass to the files you get at the end.
How SubPro turns a first pass into a reviewable draft with source context.
How source-backed register prep keeps evidence visible.
How source checks and human review stay in the workflow.