PDF submittal packages
Submittal packages come out as PDFs organized around the spec requirements, ready to open and review.
Submittal handoff output
Submittal handoff output for construction teams.
The document controller does not need another scavenger hunt. SubPro hands off PDF submittal packages plus an editable log and schedule in Excel, with every row carrying its source page and review flags.
Deliverables
Files built for handoff.
The goal is a practical package your team can inspect, edit, and move forward. SubPro keeps the log, schedule, submittal packages, and spec pages close together so review does not depend on memory, inbox archaeology, or scattered notes.
Here is what fast means in files. Once the log rows are approved, the folder simply appears: bound package PDFs, the working spreadsheets, the citations riding along. Nobody spends the following week merging cut sheets into covers, because that week no longer exists.
Submittal schedule XLSX
The schedule lands as an editable worksheet: what is due, when it needs to move, and who owns it.
Submittal log XLSX
The log export gives your PM, PE, or document control lead a working register they can review, mark up, and adapt to the rest of the project workflow.
Review context
Human review stays in charge.
SubPro does not turn construction judgment into an automatic send button. It prepares a cleaner handoff so the project team can verify the requirements before anything moves onward.
Source page context
Rows point back to the spec page that called for them, so reviewers can check why an item was included.
Review flags
Items that need a decision stay visible, including entries that may need product confirmation, package review, or project team judgment.
Editable by your team
The Excel files stay ordinary spreadsheets, so your team can clean them up, mark them up, and feed them into whatever process the company already runs.
Package output your team can inspect.
These sample package views show SubPro organizing transmittal details, product documentation, and PDF package context for review before handoff.
Structured transmittal
Package front matter is organized around project details, spec section, submittal type, dates, and distribution fields.
One transmittal per section
Every spec section gets its own cover with the same structure, so a reviewer never relearns the format between submittal packages.
The whole package, one PDF
A real 79-page assembly: cover up front, manufacturer product data behind it, ready for the reviewer to page through.
Worked example
One section, as a handoff set.
Take Section 22 00 00 Plumbing. Here is what lands in each deliverable for that section.
In the log XLSX
Rows for pipe, fixtures, valves, and water heater product data, each with its 22-section reference and source page.
In the schedule XLSX
The same items organized for timing, so long-lead fixtures surface before they hold up the job.
In the PDF package
Product data and safety data sheets assembled behind a cover for the plumbing submittals that are ready.
Flagged for review
Any fixture allowing a substitution stays flagged, so the team decides before the set is sent.
Submittal handoff output FAQ
What files does SubPro hand off?
A typical delivery: the assembled PDF submittal packages, a submittal schedule XLSX, and a submittal log XLSX, every row still carrying its source page and flags. Before a pilot starts you get the deliverable list in writing, down to the file names.
What is the difference between the log XLSX and the schedule XLSX?
The log XLSX is the working register of submittal obligations, one row per requirement with its spec page and status. The schedule XLSX organizes those items for timing and planning. The log answers what is required, the schedule answers when it needs to move.
What does the project team still review?
Your team reviews requirements, package fit, substitutions, compliance, final schedule decisions, and anything flagged before handoff. SubPro prepares the files, the team confirms them.
What inputs does SubPro use to build the handoff?
The work starts from the project specifications and project manuals, then uses available package evidence and your team's review expectations to shape the handoff files.
Related SubPro pages
Trace it back.
How the files in the handoff get built, step by step.
Submittal log software
The log these files come from, and how it stays editable.
Construction submittal software
Track status and revisions on every item until closeout signs off.
AI submittal software
The review gates each file clears before it reaches you.