Transmittal Purposes Reference
Purpose codes and values
| Code | Display name | Response required | Ack required | Contractual weight |
|---|---|---|---|---|
for_approval | For Approval | Yes — formal approval or rejection | Yes | Highest — formal acceptance/rejection of works |
for_information | For Information | No | Optional | Low — distribution record only |
for_review | For Review | Yes — comments expected | Yes | Medium — feedback record, not formal approval |
as_requested | As Requested | No | Yes | Medium — fulfils a formal request |
Purpose behaviour reference
for_approval
| Attribute | Details |
|---|---|
| Code | for_approval |
| Acknowledgement status triggers | On issue: pending_ack. On ack: acknowledged. |
| Workflow link recommended | Yes — link to the approval workflow instance |
| Document status update | Automatic when linked workflow completes: approved / approved_with_comments / rejected |
| Contractual notes | In most standard forms of contract (FIDIC, NEC, AS 4902), submission for approval is a formal contractual act. The transmittal number and issue date form part of the contract record. Keep the transmittal register as evidence of submission. |
for_information
| Attribute | Details |
|---|---|
| Code | for_information |
| Acknowledgement status | Optional — recipients can acknowledge but it is not required |
| Workflow link | Not applicable |
| Document status update | None |
| Contractual notes | Issued drawings and instructions distributed for information create a duty-to-read obligation. Although acknowledgement is not required, use Mail Distribution Rules to ensure the correct parties receive the transmittal. |
for_review
| Attribute | Details |
|---|---|
| Code | for_review |
| Acknowledgement status triggers | On issue: pending_ack. Ack required. |
| Response expected | Yes — comments or review notes (not a formal approve/reject) |
| Workflow link | Optional — can be linked to a Review step workflow |
| Document status update | None (document may move to Under Review separately) |
| Contractual notes | Review comments should be consolidated and actioned before the next revision is submitted For Approval. Maintain the transmittal record to evidence that comments were received. |
as_requested
| Attribute | Details |
|---|---|
| Code | as_requested |
| Acknowledgement status | Ack required — confirms the request has been fulfilled |
| RFI cross-reference | Include the originating RFI number in Remarks when issuing As Requested transmittals |
| Document status update | None |
| Contractual notes | As Requested transmittals typically fulfil an obligation created by an earlier RFI or formal request. Cross-reference the original RFI number to maintain the audit chain. |
Transmittal status values
| Status | Description |
|---|---|
draft | Created but not yet issued |
issued | Sent to recipients — acknowledgements pending |
acknowledged | All To recipients have acknowledged |
Related
- Transmittal Purposes Guide — when to use each purpose
- Acknowledgment Tracking — monitor receipt confirmation
- Creating a Transmittal — full transmittal creation guide