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

Submittal Numbering

Set how submittals and manuals are numbered and named, and how long reviewers get.

Every GC wants numbers their way, and retyping them onto each cover invites the typo that derails a review thread. Set the format once under Settings > Numbering & review and every cover, transmittal, and file name follows it.

Name formats

Admins can set separate formats for submittal names and manual names, built from tokens that fill in from each package: type { in the field for the full list, with {project_no}, {title}, and {revision} among the workhorses. A [bracketed] part drops out entirely when its tokens are blank, so [ - Rev{revision}] appears only on a resubmittal. Leave a format blank to keep the default, and a live preview shows exactly how a sample submittal would read as you type. The result appears on the transmittal sheet, in the {submittal_number} cover token, and in the downloaded file name. A submittal's own Submittal # field, when filled in, always wins.

A submission naming convention (admin-set) controls how Rev 1, Rev 2 and so on read on the log, the transmittal, and every submission chip; the stored number never changes, only its label.

Walkthrough 4 steps · 0:29 video

  1. Submittal Numbering, step 1: the screen with the control outlined
    Step 1 of 4 Under Settings > Numbering & review, build the submittal name from tokens. Type { for the list.
  2. Submittal Numbering, step 2: the screen with the control outlined
    Step 2 of 4 The preview shows exactly how a sample submittal reads. The bracketed part appears only on a resubmittal.
  3. Submittal Numbering, step 3: the screen with the control outlined
    Step 3 of 4 The submission naming convention controls how Rev 1, Rev 2 and so on read on the log and transmittal.
  4. Submittal Numbering, step 4: the screen with the control outlined
    Step 4 of 4 Choose the page the Comment Response Log compiles on, Landscape or Portrait.

Type codes

Admins can give each submittal type a short code (PD, SD, OM) for the {submittal_type_code} token, custom types included. Codes are blank until you set them, because no two jobs abbreviate alike; bracket the token so an untyped code disappears cleanly. {submittal_type} prints the type spelled out instead.

Review turnaround

Admins can set a default turnaround in days. It drives the due and overdue math: submittal reviews and RFI responses past the window are flagged on their logs, and a new RFI gets its "response expected by" date the moment it's sent. Any single record can still be given, or cleared of, a date on its own page. See Returned reviews.

Comment Response Log

Choose the page the Comment Response Log compiles on: Landscape gives Comment and Response about half again the width, while Portrait matches the rest of the package with one record block per comment. The choice applies to every package carrying the section from the next compile on; already-issued submissions keep the page they were issued on.

Any team member can read this page and set the Comment Response Log layout; the name formats, type codes, and turnaround are admin-only.

← Previous O&M Manuals Next → Cover Pages

Updated Oct 10, 2026

Can't find it? [email protected]