A document register is the continuing record of controlled documents and their current status. A transmittal is the formal record of one issue event: which documents and revisions were sent, to whom, when and for what purpose. The register describes the controlled collection; the transmittal proves a particular distribution.
A register answers, “What documents are controlled on this project?” A transmittal answers, “What exactly did we send on this occasion?” Good document control needs both views.
The difference in one example
Assume a project has 240 controlled drawings. The drawing register lists all 240 and identifies the current revision and status of each. On Friday, the design team issues 18 revised drawings to the contractor for construction. The transmittal records those 18 files, their revisions, the recipients, the issue date and the purpose of issue.
Next week the register may change again. The Friday transmittal should not. It remains evidence of that particular issue.
| Question | Document register | Transmittal |
|---|---|---|
| Scope | The controlled document population | One sent or received package |
| Changes over time | Continuously maintained | Fixed after formal issue |
| Main purpose | Status and revision control | Distribution and receipt evidence |
| Typical identifiers | Document number and revision | Transmittal number and issue date |
| Typical users | Document control, engineering, project controls | Sender, recipient, reviewers and contract administrators |
What a transmittal should record
- A unique transmittal number.
- Project, contract and package references.
- Sender and authorised recipients.
- Date and purpose of issue.
- Every included document number, title and revision.
- Required response or acknowledgement, where applicable.
- Any confidentiality, format or distribution notes required by procedure.
Why email alone is not the same thing
An email can carry files, but a normal message does not automatically create a reliable controlled issue record. Attachments may be replaced, forwarded without context or separated from the message. A formal transmittal gives the package a stable identity and makes the purpose of issue explicit.
Oracle's Aconex guidance treats transmittals as formal document exchanges that update the recipient's register and form part of the audit trail. Your organisation may use another system, but the underlying principle is the same.
How the register and transmittal work together
- Select the current approved revisions from the register.
- Assemble the issue package.
- Compare the selected register rows with the actual files.
- Create the transmittal from the verified package.
- Issue it to the authorised recipients.
- Record acknowledgement and any required response.
When Deliverable Preflight helps
Deliverable Preflight is useful between package assembly and formal issue. Export the relevant register rows to CSV or XLSX, compare them with the local delivery folder and resolve missing, unexpected or ambiguous files before the transmittal is sent. It does not send the transmittal or prove receipt.
A clean preflight reduces the chance that the transmittal and its attachment folder describe different packages.
View Deliverable Preflight in Microsoft Store →Related guides
See what an MDR should include and the document handover checklist.
Further reading
Questions people ask
Is a transmittal a document register?
No. A transmittal records one formal issue event, while a document register is the continuing index and status record for controlled documents.
Can email replace a transmittal?
Only if the agreed procedure explicitly treats it as the controlled issue record and captures the required package, recipient, revision and purpose information.
Should every file on a transmittal appear in the register?
Controlled deliverables normally should. Any exception should be understood and recorded under the project's document-control procedure.