Submittals and transmittals

A submittal asks for review of a shop drawing, sample or product data before use. A transmittal is the cover record of documents issued to a recipient. An RFI asks a question. These are separate workflows and separate add-ons. For example, submit a tile sample for approval, then record the approved product sheet in a transmittal when issuing it to the site.

Open Submittals or the project tab. Create a draft with project, title, type, specification reference, due date, responsible reviewer or party, attachments and linked documents. Only drafts are editable. Submit the package, then use the review workflow to move it Under review and record Approved, Approved as noted, Revise and resubmit, or Rejected.

Read review notes even when approved as noted. Revise and resubmit creates a new linked draft revision; correct that revision and submit it instead of overwriting the reviewed record. Approved submittals cannot be deleted through the normal action.

1. 01

   Assemble one review package

   Create the draft with the project, submittal type, specification reference, reviewer, due date and supporting files. Check that the package is complete before submitting.

2. 02

   Submit and record review

   Submit the package and move it into review through the authorized controls. Record the decision and notes so the site knows whether it may use the proposed item.

3. 03

   Follow the decision

   For revise-and-resubmit, create the linked revision and correct it. For an approved package, read any conditions before using it. Make a transmittal separately when issuing document versions.

Ball in court identifies the party currently expected to act. Keep it aligned with the submission and review state, and check due dates and overdue items. A package marked with the consultant does not prove that they have reviewed it; the recorded review decision is the evidence. A rejected package and a request to revise are different outcomes—read the decision before preparing the next submission.

Open Transmittals, create the record, choose project and recipient type, enter recipient name and email where needed, and select documents with their version labels. Add the purpose and notes, then save and check the cover view or PDF. Version labels are captured at creation; later document revisions do not update the earlier transmittal.

A saved transmittal is an issue record, not proof that an email reached the recipient or that the recipient approved the content. Use your agreed delivery process and preserve the correct version references.

Client-visible submittals can be read in the assigned project portal when the features are available. The client does not perform the internal submittal review there. Do not assume a transmittal automatically publishes its documents to the portal; document sharing and approval rules still apply. See Documents.