Skip to content

Document transmittal in engineering: fields, workflow and template

A document transmittal is the formal record of each delivery of technical documents between companies on an engineering project. This guide explains what a transmittal is for, which fields it needs, how the round trip with vendors and EPCs works and how an EDMS automates it. In Brazil the same record is called a GRD, guia de remessa de documentos.

Short answer

A document transmittal is the record of a formal delivery of technical documents between two parties on a project. It lists each document sent with its number, revision and purpose, identifies sender, recipient and date, and proves that a given revision was delivered. In Brazil it is called a GRD, short for guia de remessa de documentos.

What is a document transmittal?

A document transmittal records one formal delivery of technical documents. Every time a design contractor sends drawings to the owner, a vendor delivers equipment documentation or the owner returns commented documents, a transmittal records what went, to whom, when and why.

The transmittal is not the technical document. It is the cover of the delivery. One delivery may include one document or three hundred, but it always has one transmittal with its own number. That number is what lets you answer, months later, questions like “did revision C of the datasheet reach the manufacturer before the purchase order?”.

Transmittals are part of the document control that underpins engineering document management. They work with two other artefacts: the master document register, which receives the date and status of each delivery, and revision control, which defines which revision may be sent.

What is a transmittal for?

  • Proof of delivery. The transmittal shows that a specific revision was delivered on a specific date. In schedule or scope disputes, it is the evidence.
  • Traceability. Every revision of every document is linked to the transmittals it travelled on, out and back.
  • Progress measurement and payment. Many contracts measure engineering progress by documents issued for approval or approved. The transmittal is the proof.
  • Response-time control. With the send date and the contractual review period, document control knows which responses are overdue.
  • Distribution. The transmittal defines who receives each document and in which format.

Which fields should a transmittal have?

No international standard defines the form. The fields below appear in most engineering projects:

Header

  • Transmittal number, unique and sequential per sender and project.
  • Project or contract.
  • Sender and recipient, with company and person or department.
  • Issue date.
  • Purpose: for approval, for review and comment, for information, for construction, as built.
  • Response due date, where applicable.
  • Delivery method: EDMS, owner’s platform, media or paper.

Document list

  • Document number, following the project numbering system.
  • Title.
  • Revision.
  • Number of sheets or files.
  • Format, whether PDF, native or paper, and number of copies, if any.
  • Purpose per document, when it differs from the overall purpose.

Closing

  • Remarks.
  • Acknowledgement of receipt: date, name and, where the contract requires it, signature.

How does the transmittal workflow run with vendors and EPCs?

On an industrial project, transmittals make the round trip between three kinds of party: the asset owner, the EPC or design contractor, and the equipment vendors. A typical flow:

  1. Issue. The designer or vendor prepares the revision, completes the internal check and issues an outgoing transmittal marked “for approval”.
  2. Receipt. The owner’s document control checks the transmittal: numbers, revisions, readable files, complete sheets. Deliveries with errors are returned without review.
  3. Review. The owner’s disciplines comment within the contractual period.
  4. Return. The owner issues a return transmittal with a return code per document and the comments.
  5. Next revision. The designer incorporates comments, issues the next revision and opens a new transmittal.
  6. Final issue. Once approved, the document is issued for construction or fabrication and, at the end, as built.

In an EPC chain, the same vendor document can travel on two transmittals: vendor to EPC, then EPC to owner. That is why the transmittal must carry both the project number and the vendor’s original number.

What return codes do transmittals use?

Return codes are not set by any standard. Each owner defines its own in the document control procedure. In practice, most projects use a variation of this set:

Example codeMeaningWhat happens next
1 or AApprovedThe document can proceed to construction or fabrication
2 or BApproved with commentsWork may proceed; comments go into the next revision
3 or CRejectedNot to be used; needs a new revision and a new submission
4 or DFor information, not reviewedFiled as received, with no technical opinion

Some companies add codes such as “cancelled” or “superseded”. What matters is one return code per document and revision, and that the register receives it.

On projects that follow ISO 19650 the logic is similar but lives inside the common data environment (CDE). The UK BIM Framework guidance says the CDE must let each information container move between states and record who made each transition and when. A suitability status such as “suitable for review and comment” takes over part of what a paper transmittal used to do.

Transmittal template

Use this structure as a starting point. The header appears once per transmittal; the document table has one row per document.

Header: Transmittal no. TR-P123-ABC-0047 · Project P123 · From: Designer ABC · To: Owner document control · Date: 14 Oct 2026 · Purpose: for approval · Response due: 10 working days.

ItemDocument numberTitleRev.SheetsFormatPurposeReturn codeReturn date
1P123-U200-ME-DE-0012Pump house layoutB2PDF + nativeFor approvalFilled in by ownerFilled in by owner
2P123-U200-ME-FD-0003Pump P-201 datasheetA1PDFFor comment
3P123-U200-EL-LI-0001Electrical load list04PDF + XLSXFor information

Numbers and titles above are fictitious examples.

How should a transmittal be checked on receipt?

The receipt check is the filter that stops a delivery error from becoming a design error. The receiving document controller, for each transmittal:

  1. Checks the header. Transmittal number in sequence, right project, right recipient, purpose filled in.
  2. Checks each line against the files. Number and revision on the transmittal match the title block and the file name.
  3. Checks the register. The revision sent is the next one expected; no skipped revisions, no documents outside scope.
  4. Checks legibility. Files open, sheets are complete, format is as agreed.
  5. Logs receipt. The receipt date starts the review clock.
  6. Returns what fails. Faulty deliveries go back with the reason and no technical review; the designer corrects and resends.

It looks like paperwork, but this check is what keeps the register reliable. A document logged at the wrong revision on receipt contaminates every control after it.

Paper, email or EDMS transmittals: what changes?

AspectPaper or spreadsheetEmailEDMS
NumberingManualManualAutomatic
Document listTypedTyped, loose attachmentsBuilt from the documents
Revision checkVisualVisualSystem compares with the current revision
Proof of receiptSignatureRead receipt, if anyUser and date record
Register updateRetypedRetypedAutomatic on send and return
History searchFolders and physical archiveSeveral people’s mailboxesQuery by document or transmittal

Email is still useful to announce that a transmittal has been issued. The problem starts when email becomes the control itself: attachments scatter across several mailboxes and nobody can rebuild what was sent on each date.

How does an EDMS automate transmittals?

In a spreadsheet, the transmittal is typed, numbered and checked by hand. In an EDMS, it is generated from the documents themselves:

  • Automatic numbering, unique per project and sender.
  • Document list built by the system, reading number, title and revision from attributes, with no retyping.
  • Blocking invalid sends, such as a revision not yet approved internally or a document already superseded.
  • Return recording with code and comments per document, which updates the status in the register.
  • Due-date alerts for overdue responses.
  • Full history of each revision and every transmittal it travelled on.

Each platform handles transmittals in its own way, so check the vendor’s documentation for what is standard and what needs configuration. The platforms 29docs works with are described based on what each vendor publishes. 29docs does not sell licences: its independent consulting helps choose the tool and design the workflow, and the Greendocs implementation service configures transmittals, the register and approval workflows in the system.

Transmittals on Brazilian projects: the GRD

International EPCs and vendors working for Brazilian owners will meet the transmittal under its local name, GRD. The concept is the same, but a few habits are worth knowing:

  • The GRD number is quoted everywhere. Registers, return letters and progress reports refer to GRD numbers, so keep your own transmittal number and the client’s GRD number side by side.
  • Return GRDs are formal documents. The owner’s response usually comes as a “GRD de retorno” listing a return code per document, not as loose comments.
  • Owner standards define the document number. In Brazilian oil and gas, documents delivered to Petrobras follow standard N-1710 for numbering, so the transmittal must carry the N-1710 number. See the document numbering guide.
  • Portuguese titles are common. Agree early whether titles are bilingual and which language is the reference.

Which transmittal mistakes come up most?

  • No purpose stated. Without “for approval” or “for information”, the recipient does not know whether to review.
  • Wrong revision on the transmittal. The file is revision C, the transmittal says B. A receipt check catches it.
  • One transmittal for several projects. It mixes deadlines, progress measurement and recipients.
  • Returns outside the transmittal. Comments sent in a loose email do not update the register.
  • Files outside the system. When the transmittal lives in one folder and the files in another, proof of delivery weakens.

In industries with many equipment vendors, such as oil and gas and mining, these mistakes multiply with document volume. A sound transmittal process is what lets a project close out vendor documentation without gaps.

Updated on .

Frequently asked questions

What is the difference between a transmittal and a submittal?

In construction, a submittal is usually a package the contractor sends for the designer's or owner's approval, such as shop drawings or product data. A transmittal is the cover record of any formal delivery, whatever its purpose. A submittal often travels under a transmittal.

What is a GRD?

GRD stands for guia de remessa de documentos, the Brazilian name for a document transmittal. If you work with Brazilian owners or EPCs, you will see GRD numbers on cover sheets, registers and return letters.

Does a transmittal need a signature?

It depends on the contract. Paper transmittals used to carry a signed receipt. In an EDMS, the send record, date and receiving user serve that purpose, as long as the system keeps the history.

Can I send documents by email without a transmittal?

You can, but you lose proof of what was sent, at which revision and for what purpose. Email can carry the transmittal; it does not replace it. Without it, the master document register has no source for the status of each revision.

Ready for your next audit?

A 30-minute conversation. No pitch. We want to understand your document reality before talking about any solution.

We reply within 1 business day. Your data is never shared.