Skip to main content
All guides

Getting started

What is Submittal Kit Your First Project Search Everything The Dashboard Help and What's New Abbreviations We Understand

Projects & Schedule

Project Settings Schedule and Milestones

Equipment Register

Equipment Register Basics Import a BOM Equipment Documents

Parts & Library

The Parts Library Part Documents Find Datasheets The Document Library Search Inside Documents

Submittals

Create a Submittal Configure Sections Choose Equipment Scope Compile a Submittal Checks Before You Submit O&M Manuals Submittal Numbering Cover Pages Package Layouts

Submissions & Review

Issue a Submission Submittal Log Returned Reviews Comment Response Log Record an External Submittal Share with an outside reviewer

RFIs

RFI Basics RFI Log RFI Layouts

Field & QA

Punch Lists As-Built Redlines

Specifications & Scope

Upload Specifications Spec Check

Procurement & Change Orders

Quotes and Purchase Orders Coverage and Lead Times Change Orders Budget and SOV

Directory & Team

Firms & Contacts Team & Access Personnel & Certifications

Settings & Billing

Company Identity Library Vocabulary Billing and Plans

Integrations

Connect an Agent

Help Submittals

Checks Before You Submit

The Checks tab lists what a reviewer usually bounces, so you fix it before the package goes out.

A package that goes out with a missing datasheet or the wrong document on a part comes back a week later marked Revise and Resubmit. The Checks tab on every submittal lists those problems while you can still fix them.

Find it

Checks is the second tab on a submittal, after Contents. While something needs a look, the tab shows a △ and the count next to its name. With nothing to report, the tab has no count, and inside it reads "Nothing here a reviewer usually bounces."

Before the first submission, the line under the submittal's title can carry the count too, such as "2 checks on this package."

What it looks for

Before this goes out is a table with one row per problem. Each row leads with the kind of check, then says what a reviewer would see.

  • No document. An item in scope has no datasheet or other document selected.
  • Needs part. An item is still waiting for a part, so the compile leaves it out of the schedule and the product data.
  • Catalog number. The part's catalog number does not appear anywhere in its selected datasheet. Usually the right part has the wrong document.
  • Empty section. A section would print nothing but its own divider.
  • Spec demand. The linked spec section asks for something, such as wiring diagrams, that no section in the submittal carries. The row quotes the spec and names the article.
  • Lifecycle. The distributor lists a part as obsolete, end of life, or not recommended for new designs, with its suggested replacement when there is one.

Go to the item or Go to the section opens the Contents tab on the thing to fix. A Spec demand row is fixed by adding a section that carries what the spec asks for, in Configure sections. Fix the problem and the row leaves the table.

Walkthrough 6 steps · 0:37 video

  1. Checks Before You Submit, step 1: the screen with the control outlined
    Step 1 of 6 Open the submittal you are about to send.
  2. Checks Before You Submit, step 2: the screen with the control outlined
    Step 2 of 6 The Checks tab shows a count while something needs a look. Open it.
  3. Checks Before You Submit, step 3: the screen with the control outlined
    Step 3 of 6 Each row names the kind of check, then what a reviewer would see.
  4. Checks Before You Submit, step 4: the screen with the control outlined
    Step 4 of 6 A Spec demand row quotes the spec and names the article that asks for it.
  5. Checks Before You Submit, step 5: the screen with the control outlined
    Step 5 of 6 Acknowledge hides a row that is fine as it is. It comes back if the thing behind it changes.
  6. Checks Before You Submit, step 6: the screen with the control outlined
    Step 6 of 6 Go to the item opens the Contents tab on the thing to fix.

When a row is fine as it is

Some rows are deliberate, such as a section you want to print empty. Acknowledge hides that row. It comes back only if what it was about changes, such as a different part on the item or a new datasheet.

Checks never block a submission. Mark as submitted lists every open check in its confirmation, and the button reads Submit anyway while any remain.

Spec check

Under the table, the Spec check panel reads every datasheet against the submittal's spec section and answers one row per requirement. It says on its header line whether it has run and whether it is out of date, and Run starts it. See Spec Check.

Most rows clear in the Contents tab: see Equipment documents and Configure sections.

← Previous Compile a Submittal Next → O&M Manuals

Updated Oct 18, 2026

Can't find it? [email protected]