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 Submissions & Review

Issue a Submission

Mark a compiled package as submitted and it becomes a permanent, numbered submission.

Six weeks after a package goes out, someone asks what was actually in it. If the answer lives in a folder of files that kept changing, you don't have one. Issuing a submission fixes that: the exact bytes you sent are kept forever.

What issuing does

On a submittal's page, Mark as submitted promotes the compile into a permanent submission. It is the header's green next step while the package is ready, and it sits in the header's More menu when the header is asking for something else first. Once a submission has gone out, it names the next one, such as Mark Rev 1 as submitted. The issued files can never change afterward, no matter how much you edit the submittal later. Every submission lands on the Submittal Log with its submitted date and review status.

Numbering runs Initial, Rev 1, Rev 2 (or Rev A, Rev B, depending on your submission naming setting), and each new submission continues the sequence automatically. See Submittal numbering.

Issue in one step

  1. Open the submittal. When the package is ready, the header's green is Mark as submitted. You can compile first to review the package, or skip straight to issuing. The Checks tab lists what a reviewer usually bounces; see Checks Before You Submit.
  2. Click Mark as submitted. With a reviewed compile ready, that compile is recorded as the submission. With no fresh compile, one click compiles, verifies, and issues in a single step.
  3. Confirm. The submission appears at the top of the Submissions tab and on the log.

If the package is short of documents its recipe requires, the confirmation warns you first rather than refusing, so a deliberate partial submission is still one click.

Walkthrough 6 steps · 0:47 video

  1. Issue a Submission, step 1: the screen with the control outlined
    Step 1 of 6 Open the submittal you are issuing. Its name labels every submission it issues.
  2. Issue a Submission, step 2: the screen with the control outlined
    Step 2 of 6 When the package is ready, the header's next step is Mark as submitted, or it waits in More while the header asks for something else. With no fresh compile, one click compiles, verifies, and issues.
  3. Issue a Submission, step 3: the screen with the control outlined
    Step 3 of 6 The confirm names any check still open. Confirm it, and the issued files can never change afterward.
  4. Issue a Submission, step 4: the screen with the control outlined
    Step 4 of 6 The Submissions tab keeps every submission and how its review went.
  5. Issue a Submission, step 5: the screen with the control outlined
    Step 5 of 6 The submission lands at the top of the list and on the log. View PDF opens exactly what was issued.
  6. Issue a Submission, step 6: the screen with the control outlined
    Step 6 of 6 Issued the wrong thing? Withdraw the latest submission before it goes out. Its snapshot is deleted and the number freed.

Preview what you issued

The header's Status, Submission, Sent and Expected back facts each open the latest submission on the Submissions tab. Every submission there opens in the same preview window the rest of the app uses, with a download beside it. Packages that include signed originals offer a complete-package download: the primary PDF, every untouched signed original, and a README. No more saving a file just to check what went out in Rev 2. The same row shows how the review went, and its arrow opens the full review record.

To hand the issued submission to the reviewing engineer, share it with an outside reviewer; the share always serves the latest issued submission.

Withdraw a submission that never went out

Issued the wrong thing? Withdraw the latest submission. Its snapshot is deleted and the number is freed, so the next submission is issued under the same label. Use it only for a package that was never actually sent; a package the reviewer has seen belongs on the record.

The next round

Issuing freezes the submission, not the submittal. The working submittal stays fully editable, so when the review comes back revise and resubmit, you answer the comments in the Comment Response Log, fix the documents, and issue the next submission from the same place.

Compile and issue are separate on purpose: compile as many times as you like while you review; only Mark as submitted creates a record.

← Previous Package Layouts Next → Submittal Log

Updated Oct 17, 2026

Can't find it? [email protected]