Transmittals (numbered document packages)

In construction and engineering, documents aren’t just sent — they’re issued: a numbered transmittal to a named recipient, for a stated purpose, entered in a register. "For construction" versus "for information" carries contractual weight, and when a dispute arrives the register is the answer to what did they have, and when did we send it. Email does the sending but keeps no register. FileDeck keeps the register.

FileDeck AI tier — Documents → Transmittals.

Issuing a transmittal

1. Select the documents (published ones only — the register must never name a document that wasn’t actually sendable).
2. Name the recipient and their email, choose the purpose — for information, for review & comment, for approval, for construction, as built (the list is filterable for house styles) — and optionally add a covering message.
3. Issue and email. The transmittal gets the next sequential number (TX-0001, TX-0002, … — format filterable), the register row is written, and the recipient receives one email listing every document with a signed download link.

Signed links mean the recipient needs no account on your site, no file has to squeeze through an email attachment limit, and every download they make still lands in the activity log attributed to that link. Links expire after 14 days by default (filedeck_transmittal_link_days).

The register

Each row freezes the document list as issued — titles at the moment of sending — because the register must describe what was sent even after documents are superseded or renamed. The register screen shows number, date, recipient, purpose, documents and issuer; Export register as CSV produces the artifact you hand to the contract administrator. Every issue is also written to the activity log.

What it deliberately is not

Not e-signatures, not a delivery-confirmation service, and not a workflow engine. If you need the recipient to confirm they read it, that’s acknowledgment tracking — the two compose.