Submittals and Transmittals
Get shop drawings, samples, and method statements formally approved before work proceeds, and keep a formal record of every document you issue.
Use this when: You need formal approval for a shop drawing, material sample, or method statement before building it — or you need a dated record that you issued documents to a client or vendor.
A submittal is something you send for approval before work proceeds — a shop drawing, a sample, product data, a method statement, or a mock-up. It moves through a numbered review workflow so everyone can see whose turn it is and what was decided. A transmittal is different: it is a formal cover record proving which documents (and which versions) you issued to whom, and why.
What Counts as a Submittal
On most contracts you cannot simply build from your own drawings — the consultant or client must approve your proposal first. TaameerPro keeps each of those approval requests as a numbered submittal on the project, with its files, its reviewer, and its decision in one place.
| Type | Typical example |
|---|---|
| Shop drawing | Your detailed fabrication or installation drawing, produced from the design drawings. |
| Material sample | A physical sample — tile, paint, ironmongery — submitted for selection or approval. |
| Product data | Manufacturer datasheets or certificates for a product you intend to use. |
| Method statement | How you plan to carry out a piece of work, submitted for review before starting. |
| Mock-up | A trial section of finished work, built for approval before repeating it everywhere. |
The Review Workflow
- 1
Draft the submittal
Create it on the project with a title, type, the files being submitted, and the date a decision is needed by.
- 2
Submit for review
Submitting moves it out of draft and starts the clock. Overdue submittals are flagged automatically once the required date passes.
- 3
Reviewer records a decision
The outcome is one of: approved, approved as noted (proceed, incorporating the comments), revise and resubmit, or rejected.
- 4
Revise and resubmit if asked
Choosing revise-and-resubmit creates a linked revision of the same submittal, so the whole history — Rev 0, Rev 1, Rev 2 — stays connected.
Do not build ahead of the decision
Work done against an unapproved submittal is work you may have to redo. Use the register to check the decision before the crew starts.
Ball-in-Court: Whose Turn Is It?
Every open submittal shows who the next action sits with — the contractor, the consultant, or the client. That single field ends the most common submittal argument on any project: 'we are waiting on you'. Filter the register by ball-in-court to see exactly what your side owes.
Transmittals: Proof of What You Issued
A transmittal is a formal cover record for documents you send out — to the client, a vendor, or anyone else. Each one records the recipient, the purpose (for approval, for information, for construction, or as-built), and the exact list of documents with the version each one had at the moment of issue.
Because the version labels are captured when the transmittal is created, a later revision of a drawing never changes the record of what was actually sent. A print-friendly view is available when you need a paper copy for the file.
Transmittal or just share the file?
Share files informally when it is routine. Create a transmittal when the issue has contractual weight — issued-for-construction sets, approval packages, or as-built handover sets.
What Clients See
Submittals marked client-visible appear read-only in the client portal, so the client can follow what is awaiting their own approval without calling your office.