Struxen Docs

Submittal Review

Build the required-submittal register from the project specifications, then check each received submittal against the requirement it is supposed to satisfy

Submittal Review answers two questions at once: what does the spec require, and does what arrived actually meet it.

STRUX reads the project's specifications to build the register of required submittals, so an item the spec requires but nobody has submitted shows as Missing rather than being invisible. Each submittal that has arrived is compared requirement by requirement against the spec section that governs it.

This is a different surface from the Submittals register, which is where submittals are logged, routed, and formally responded to. Review is the check; Submittals is the record.

Build the register

The register starts empty. Press Re-scan specs in the header.

STRUX reads each specification section, extracts its submittal requirements, and writes a row per required item. Re-run it whenever new spec sections are added.

The register has no upload path of its own for specifications. Spec books are uploaded on the Documents page, where they are split on CSI section boundaries during processing. See Specifications.

Review what has arrived

Review all received runs the compliance check on every received submittal that has not been reviewed yet. The button is disabled, with the reason on hover, when nothing is waiting.

A review compares the submitted item against the requirements in its spec section and produces a determination plus a list of per-requirement results.

Reading the register

ColumnWhat it holds
Spec §The section that requires this item
Required submittalWhat the spec asks for
TypeProduct data, shop drawing, sample, and so on
ReceivedThe submittal number and date, or Missing
FindingsThe count of failing requirements, or None
DeterminationThe verdict

Determinations:

DeterminationMeaning
ApproveEvery requirement checked out
Approve as notedApproved with exceptions recorded
Revise & resubmitThe submitted item does not meet the spec
IncompleteRejected as insufficient to review
Not yet runReceived, review has not run
AwaitingRequired by the spec, nothing submitted

A row can also carry a Re-review badge. That is raised when a later drawing revision changed sheets the already-approved submittal covers, so the approval may no longer hold. See Revision.

Filters

The tabs above the table are All, Needs action, Missing, In review, As noted, and Approved, each with a live count. Alongside them are a discipline filter, built from the CSI divisions actually present in this project, and a search field that matches the spec section, the title, and the submittal number.

The counts and the rows come from the same filtered set, so a tab count never disagrees with what clicking it reveals.

The comparison viewer

Click any row to open the side-by-side comparison.

  • Requirements checked runs down the left. Each row names the requirement, what the spec asks for, and what the submittal actually said, with a pass, fail, or missing marker. Clicking one selects it.
  • Spec and Submittal panes sit side by side on the right, and both scroll to the requirement you selected, so you are looking at the same line in both documents.
  • The header summarises the run: how many requirements conform, how many are issues, and the determination.

For a required item nothing has been submitted against, the viewer says which spec section requires it and offers Upload submittal. STRUX compares it automatically once it arrives.

For a received item that has not been reviewed, the viewer says so and points you at Review all received.

Empty states, and what each one means

What it saysWhat it means
No required submittals yetThe scan has not been run. Press Re-scan specs.
No specifications foundThe project has no specifications to read. Upload the specs, or connect Autodesk Forma, then scan.
No submittal requirements foundSTRUX read the specifications and found no submittal requirements in them. Check that the right sections were uploaded.

These are distinct on purpose. An empty register because nothing was uploaded is a different problem from an empty register because the specs genuinely ask for nothing.

Troubleshooting

A submittal you uploaded is not in the register. The register is built from the specs, not from uploads. If the spec section that requires it has not been scanned, add the section and press Re-scan specs.

Findings is empty on a reviewed row. That row's requirements all passed.

Everything is disabled. You are on the shared demo project, which is read only.

The scan or the review will not start. Both are metered AI operations and stop at a zero credit balance. See Billing.

On this page