Home/Process library/A transmittal ready to send by e-mail
Process library · EngineeringA transmittal ready to send by e-mail
The engineer selects the documents for the client. M-Files bundles them, renders a front page with every document and revision, makes one zip file and a link, and records it all with the project. What is left is one e-mail.
See the flow Transmittals in M-Files
In short
In this blueprint an engineering firm sends documents to its client as a transmittal. The engineer selects the documents in the project, for example the ones in client review, and creates a transmittal collection with one command. The collection starts as a draft, so documents can still be added or removed. When it is complete, the engineer renders the transmittal: M-Files generates a front page from the metadata, with the project, the transmittal, the issue date, the recipient and every document with the client’s document and revision number, plus an acknowledgement of receipt to sign and return. It also packs the documents into one zip file and creates a link the client can open. The transmittal is recorded with the project, ready to send by e-mail. SoftAdvice built and documented the process.
The client must know exactly what they received
The client wants the documents for review today. Someone copies files into a folder, types a cover sheet and zips it all by hand.
In engineering, documents go to the client in batches, for review or for approval. The client works with its own document and revision numbers, and wants a list of what is in the batch, signed for receipt.
By hand, someone copies the files into a folder, types a cover sheet in Word, zips it and attaches it to a mail. Months later, nobody can say which revision went out in which batch.
- Select the documents, nothing else to prepare
- A front page generated from the metadata
- One zip file and one link for the client
- Recorded per project and revision
What happens from selection to the client’s inbox
A transmittal takes minutes instead of an afternoon, and its record stays with the project.
When a batch is ready
Select
The engineer selects the documents in the project and creates the transmittal collection.
Before rendering
Check
The collection is a draft: documents can still be added or removed.
One click
Render
Front page, zip file and link are made and recorded with the project.
Then
Send and sign
The transmittal goes out by e-mail; the client signs the front page for receipt and returns it.
From selected documents to a transmittal ready to send, step by step
The engineer chooses what goes out. M-Files builds the package and keeps the record.
Select the documents
In the project view, the engineer selects the documents for the client, for example all documents in client review.
Create the collection
One command creates a transmittal collection with the selected documents, linked to the project. It starts as a draft.
Render the transmittal
When the collection is complete, the engineer moves it to render. M-Files generates the front page and the zip file.
Front page, zip and link
The front page lists project, transmittal, issue date, recipient and every document with the client’s document and revision number, with lines to sign for receipt. A link lets the client open the transmittal.
Send by e-mail
The transmittal is ready: front page, zip file and link go to the client in one e-mail, and the transmittal stays recorded with the project.
Two records: the collection and the transmittal
The collection says what was selected. The transmittal document says what was sent, as a front page and a zip file.
Transmittal collection
Transmittal document
From building packages to sending them
Engineers no longer copy, type and zip. And when the client asks which revision they received, the answer is in the project.
Before
- Files copied into a folder
- Cover sheet typed in Word
- Client numbers looked up by hand
- No record of what went out
Now
- Select and create in one command
- Front page generated from the metadata
- Client numbers on the front page
- Every transmittal recorded with the project
M-Files and the SoftAdvice Engineering Pack
The same building blocks as the overview blueprint, configured and documented by SoftAdvice.
Client numbers as metadata
The client’s document and revision numbers live on the document and appear on the front page.
Questions about this blueprint
Does M-Files send the e-mail itself?
In this blueprint the transmittal is made ready and the engineer sends it, so they keep control over the message to the client. Sending it from the workflow is possible too.
What is on the front page?
Project, transmittal, issue date, recipient and the list of documents with the client’s document and revision number, plus lines to sign for receipt. The layout follows your own template.
Can we see later what a client received?
Yes. Every transmittal is linked to its project and to the documents it contained, so you can look up what went out, when and in which revision.
How long does your next transmittal take?
In a one-hour demo we build a transmittal with you, from selection to front page and zip file.
