Requirement
The submittal item, package, or review obligation pulled from the project specifications.
A submittal log is the list of everything the specs make you submit: who owes it, when it is due, what has been reviewed, and what is still waiting on somebody. Every late material order on a job traces back to a row that was not on it.
The first log draft should preserve enough context to review each row. SubPro focuses on getting that first pass into a form your team can inspect before it moves into tracking.
The submittal item, package, or review obligation pulled from the project specifications.
The section, page, or surrounding note that explains why the row belongs in the project log.
The visible flag, owner, due date, or note that helps the project team decide the next step.
SubPro turns the concept into reviewable rows with source context, not just a blank spreadsheet.
Rows are prepared for project review, cleanup, and handoff rather than left as disconnected notes.
The reviewer can inspect the source page behind the row and decide whether it belongs.
Before a single product ships, the specifications spell out what has to be submitted and approved: product data, shop drawings, samples, test reports, and certifications. The submittal log is the master list that turns those scattered requirements, spread across dozens of CSI sections, into one tracked set of obligations the whole team can see.
A log that is just a list of names does not help much. A useful log preserves enough context to review each row: which specification section it came from, what type of submittal it is, who is responsible, and whether it still needs a decision. That context is what lets a reviewer trust the list instead of re-reading the manual to check it.
The first draft matters most. It sets the starting scope for review, responsibility, schedule planning, and package preparation. A row missed in the first pass becomes a submittal nobody chased until the material was already late. Getting the first draft complete and source-backed is exactly the work SubPro takes on.
Take Section 09 51 00 Acoustical Ceilings, a section on most commercial jobs. Its submittals article turns into several tracked rows.
Manufacturer data for the acoustical panels, logged with the 09 51 00 reference and the spec page it came from.
Product data for the grid and hangers, a separate row so the reviewer can confirm each component.
A samples row, flagged as an architect or owner decision, so the selection is not lost inside the list.
The required test or compliance report, tracked with a status so it is chased before install, not after.
A submittal log is a construction project list that tracks required submittals such as product data, shop drawings, samples, and test reports, along with the responsible party, review status, due dates, and notes. It is the master list that turns scattered specification requirements into one tracked set of obligations.
A useful row carries the requirement, its CSI section, the submittal type, the responsible party, the source specification page, the review status, and a due date or note. The source reference is what lets a reviewer confirm the row belongs.
Teams use the terms differently, and in practice both usually refer to the organized project list used to track required submittals and review progress. Some teams call the full source-backed list a register and a working slice of it a log.
Usually a project engineer, submittal coordinator, or document control lead. SubPro prepares the reviewable first draft from the spec set so that person starts from real rows with source context instead of a blank sheet.
These pages show how SubPro turns the log concept into practical project output.
How SubPro turns spec books into a first-pass log.
How SubPro supports a reviewable draft and editable handoff.
How review flags and source checks stay visible.