Confirm the requirement
The paragraph that created the row is quoted beneath it, with its page number. A reviewer confirms the row is real in one read instead of a search.
SubPro keeps review flags and source checks on the row under review. Your PM sees the requirement, the page that created it, and the matched product data, then decides.
The paragraph that created the row is quoted beneath it, with its page number. A reviewer confirms the row is real in one read instead of a search.
A flagged row asks a specific question: which product, which or equal, whose selection. The reviewer answers it and the flag clears. Rows without a flag do not interrupt.
The manufacturer and product matched to the row sit beside it. If the data sheet is wrong for the specified assembly, the reviewer swaps it before anything binds.
Each row ends as ready, needs edit, or hold. Only ready rows move into the export, so the handoff never carries a row nobody looked at.
Thermal insulation is a short section with four kinds of submittal in it. Here is what the reviewer sees on each row, and the call that is theirs to make.
| Row in the log | What the reviewer sees | The call |
|---|---|---|
| Product data, board insulation | The paragraph in Section 07 21 00 that requires it, quoted with its page, and the matched data sheet. | Confirm the product matches the specified R-value and facing. Mark ready. |
| Substitution, where an equal is allowed | A flag on the row, because the spec section permits an or equal and someone has to choose. | Pick the product or keep the basis of design. The reviewer chooses, not the draft. |
| Fire-test and R-value reports | Test report rows with their source paragraphs, so conformance items are not lost among product data. | Check the report covers the assembly the drawings show. Hold if it does not. |
| Mockup, if the section calls for one | A question to the built-in chat returns the cited page. Either the requirement is there or it is not. | Add the row or close the question. Either way, the page is on record. |
Submittal review is where a PE or PM decides whether the log is right. Is this requirement real, is it assigned to the right party, does it need a substitution, is the product data sufficient. On most jobs that means bouncing between a spreadsheet, the project manual PDF, and a folder of cut sheets, rebuilding the picture for every row.
SubPro puts the evidence next to the decision. Each row shows its spec page and its matched product data in the same view, so the reviewer confirms the basis without leaving the row. When a question reaches past the row, the built-in chat pulls the relevant page from the project manual and cites it. It is the one place the reading is done for you, and the ruling is still yours.
None of this removes the reviewer. SubPro prepares the draft and surfaces the decisions. Your team confirms scope, product fit, timing, and the final call. To see the review pass on your own document first, order a Log Build. The drafted rows arrive with a report of which lines deserve your attention.
How the reading is bounded, and why every row is built to be checked by a person.
The document under review, defined from scratch: what a row is and what it tracks.
Where ready rows go next: a cover sheet, a PDF, and a dated record of the send.
It puts each draft row beside its spec page, its matched product data, and any flag. The reviewer confirms the requirement, rules on the flag, and marks the row ready or hold without reopening the project manual.
A flag marks a row that needs a person: a substitution, an owner selection, or a requirement written too loosely to act on. Flagged rows stay visible instead of blending into the log, so the reviewer clears them before the set counts as ready.
Yes. The built-in chat answers from the project documents and cites the page. A reviewer who wants to know whether Section 07 21 00 calls for a mockup asks, reads the cited page, and rules on the row.
No. Ready means your reviewer is satisfied the row matches the project manual and the submittal package behind it is complete. The architect's stamp action, from No Exceptions Taken to Revise and Resubmit, still comes from the design team.
A single fit call and a project manual from a live job. Your reviewer reads the drafted log, flags first. Nothing is decided until then.