A transmittal log records more than the fact that files were emailed. It can show what was issued, to whom, at which revision and with what response. Reconciling that history before final submission helps the team distinguish a document that is current internally from the version the recipient actually reviewed.

Define the unit of reconciliation

Start with the final deliverable list and identify the document number or other stable identifier for each item. Record its intended final revision and status, then link the latest relevant transmittal and response. Keep package and recipient fields where one project has several parallel review routes.

Do not assume the transmittal date is the review date. Capture issue, receipt and response as separate events when the system provides them. This makes it easier to see whether a record is waiting on the sender, reviewer or another contributor.

Compare the four references

For each final item, compare the file identity, transmittal entry, recipient response and current register line. A useful reconciliation asks:

  • Did the transmittal include this exact document and revision?
  • Does the recorded response refer to the same issue?
  • Were comments addressed in a later revision?
  • Was the later revision formally resubmitted?
  • Is the register status supported by the recorded response?

Where a transmittal contains many attachments, preserve the attachment list or system export rather than relying on the email subject alone.

Resolve mismatches without erasing history

Suppose revision C is in the final folder, but the log shows the client last reviewed revision B. Record the mismatch and ask the document owner whether C needs formal submission. Do not copy B’s acceptance status to C merely because the change seems small.

If a response was entered against the wrong document, retain the correction reference and the reason. Where the client uses different status terminology, add a mapping note rather than changing the original wording in a way that hides it.

Issue a concise exception report

The closeout team usually needs the unresolved differences, not a second copy of every transmittal. List the affected document, evidence found, decision needed, owner and due date. Once resolved, record the supporting transmittal or response reference.

The log supports traceability. Whether a particular response constitutes acceptance, approval or release is determined by the contract and authorised project roles.