Keep every submittal moving

DECK helps teams establish a practical workflow for each submittal:

DECK also helps connect submitted drawings and product data to the governing specification and contract document requirements.

Make status meaningful

"Open," "pending," and "closed" are not enough. A project team needs to know whether a submittal is waiting for a required attachment, a contractor response, architect input, engineering review, clarification of a potential substitution, or a revised package.

DECK is designed to make the next action visible, with clear ownership and context. That helps teams focus on the items that are actually at risk of delay.

Use AI without losing control

DECK can help reduce manual searching and comparison across construction documents. It does not replace qualified reviewer judgment. The reviewer remains responsible for verifying cited evidence and making the final approval, rejection, or other disposition. See the full review methodology in how to review shop drawings against specifications.

Learn more about how AI fits into review in How AI Helps General Contractors Review Submittals, or explore the AI-powered submittal review capabilities in detail.

DECK vs Procore for submittal management

Procore's submittal module tracks logs, workflows, and routing. It is effective for knowing that a submittal exists, where it is in the approval chain, and who has it. DECK adds the intelligence layer: it helps teams understand whether the submitted product or drawing actually meets the specification, surfaces evidence-backed potential issues, and preserves the reasoning behind each decision — not just the status.

DECK is designed to work alongside Procore, not replace it. Procore manages the shared project record; DECK helps teams make better decisions within that record.

DECK vs spreadsheets and email

Many teams still manage submittals with Excel logs and email threads. This works until it does not: lost attachments, unclear ownership, conflicting versions, and no way to trace why a decision was made three months later. DECK replaces the fragmented search-and-forward pattern with a structured workflow that connects every submittal to its source requirements, reviewer actions, and final disposition.

FAQ

At minimum, it should track the submittal identity, spec section, submission and required dates, revision, responsible parties, review status, comments, final disposition, and resubmittal history. Stronger workflows also retain the requirement source and rationale behind key decisions.

A submittal log is a register of project submittals, typically including item number, description, specification section, dates, parties, status, and disposition. It is useful, but it does not replace the underlying review, coordination, and decision workflow.