Construction 101 for Software Engineers: Transmittals
Q: What is a Transmittal in construction?
In construction, a transmittal (aka “letter of transmittal” or “transmittal document”) is a document that shows what, when, and to whom items (e.g. files, documents, samples) were sent.
Q: What does a Transmittal look like?
Q: Why are Transmittals needed?
Transmittals establish a clear paper trail of documents during a construction project. Having a documented flow of information is important for understanding and managing liability over time, especially in the event of a lawsuit.
Transmittals are less popular now because email is typically sufficient. However, documents that are more likely to have legal implications (e.g. contracts) will often have a Transmittal letter associated with them.
Q: Who uses Transmittals?
Transmittals are sent to everyone involved in a project, including Owners, Project managers, Architects, Engineers, local agencies, and Inspectors. Generally, they are sent and received by people who handle documents.
Q: When are Transmittals sent?
Transmittals can be sent at any stage during a construction project.
Q: How are Transmittals sent out?
Transmittals are either sent via the software a construction company uses, or mailed via a postal service. Transmittals don’t necessarily require a response from the recipient.
Q: What information do Transmittals typically include?
A Transmittal typically includes the following information:
| Information | Category | Description |
|---|---|---|
| Attachments | Reference | Any attachments (e.g. contracts, drawings) associated with the Transmittal. |
| Due Date | Date | The date the Transmittal is due. |
| Issue Reasons | Metadata | A list of reasons the Transmittal was issued (e.g. “Issued for Approval"). |
| Number | Metadata | The number of the Transmittal, used for internal reference. |
| Recipient(s) | Stakeholder | The intended recipients of the Transmittal. |
| Required Actions | Metadata | A list of actions required by the recipient in response to the Transmittal ("Approve By"). |
| Sender | Stakeholder | The individual that sent the Transmittal. |
| Sent Date | Date | The date the Transmittal was sent. |
| Status | Metadata | The status of the Transmittal (e.g. outstanding). |
| Subject | Metadata | The title or subject of the Transmittal. |
Note, Agave API includes all of the above fields in its data model for Transmittals.
Q: What systems does Agave integrate with for Transmittals?
Agave currently supports reading Transmittals from Aconex. We plan to add other systems, including CMiC and Procore in the near future.
If there’s any Source System you would like us to expedite for Transmittals, feel free to email us at api-support@agaveapi.com.
Q: How are Transmittals different from Submittals?
- Purpose: Submittals are product info and samples submitted to the Design team for approval before materials are purchased/installed on a project. A Transmittal may include a Submittal for proof that it was sent, but the latter usually stands on its own.
- Timing: a Submittal is generally sent earlier on in a construction project, whereas a Transmittal can be sent at any stage.
- Response: a Transmittal does not always require a response, whereas a Submittal always requires a response from the Design team.
Are you working to read and write Transmittals data to multiple construction systems? Use Agave because we unify those data models and save you weeks of work.