Skip to Content
  • Solutions

    Your challenge

    By challenge

    Start from the problem you have today.

    Solving document chaosFind every document by what it isRemoving manual workLet the system file and forwardEliminating audit stressEvery file audit-ready, every dayPreparing data for AIThe right version for AIAI across all your systemsOne governed knowledge layer

    Your sector

    By sector

    Blueprints for regulated sectors where documents carry liability.

    Read client cases →
    Accountancy & audit firmsPermanent files to e-signatureFinancial servicesKYC, contracts and client filesLegalMatters and deadlinesConstruction & engineeringDocument control and transmittalsManufacturingSpecs, quality and supplier filesPublic sectorRecords and compliance

    Your process

    By process

    One process, end to end.

    See the process library →
    Contract managementFrom first draft to renewalQuality management (QHSE)ISO, procedures and auditsPersonnel files (HR)Right access, right retention

    Free advice call

    Not sure where to start?

    Thirty minutes with a process architect. No obligation.

    Audit scoreHow audit-ready are you?Contract risk scoreHow big is your risk?

    Book a free advice call

  • Platforms
    M-Files

    One search bar for all your business information, with AI on your own documents.

    Why M-Files →
    M-Files AIAI on your own documentsCompare editionsWhich edition fits youM-Files HubshareSecure client portalM-Files MentNo-code document generationCompare M-FilesAgainst SharePoint, DocuWare, OpenText and more
    SharePoint +MacroView

    Mail and documents in SharePoint, managed as real case files.

    MacroView overview →
    SharePoint with SoftAdviceMicrosoft 365 as your document platformFiling from OutlookE-mail in the right file, in one moveAutomatic e-mail filingRules that file by themselvesAll MacroView featuresEvery feature on one pageMacroView or M-Files?An honest comparison
    Mindbreeze

    AI answers across all your systems, from trusted sources.

    Mindbreeze overview →
    Use casesSeven scenarios to start fromMindbreeze Insight WorkplaceAI agents and governed workflowsAgentic AIThe right context for every agentDeployment and securityCloud, hybrid or on premises
    dox42

    Automate every document, from any system.

    dox42 overview →
    dox42 with M-FilesGenerate straight into M-FilesPlan a dox42 demoSee it on your documentsAll integrationsERP, CRM, e-signing and more

    See it live.

    One hour, online, on your real use case.

    Plan an AI readiness talkFor AI across all your systemsMicrosoft 365M-Files and Microsoft, together

    Plan a demo

  • Approach

    How we work

    Process first. Technology second.

    Five steps from analysis to a working system, with one team end to end.

    See our approach →
    1. DiscoveryHalf-day session, advice within 10 days2. Discovery & designMap your processes and information3. Implementation & configurationBuild and configure your platform4. Integrations & customisationConnect and tailor to your systems5. Success servicesAdoption, support and growth

    AI governance

    AI you can defend

    Policies, controls and oversight for AI on your data.

    Governance framework →
    Shadow AI under controlWhat it is and how to contain itIs your data ready for Copilot?Check it before you switch it on

    Price request

    What does it cost?

    Transparent pricing per platform and per service.

    Price calculatorEstimate your licence costROI calculatorCalculate your savings

    Request a price

  • Knowledge

    Learn

    Knowledge Hub

    Learning, proof and what changes.

    Open the Knowledge Hub →
    BlogLong reads on information architectureWebinarsLearn it in an hourAnalyst reportsGartner and Forrester, no paywallUpdatesProduct news, translated into impact

    Regulation

    What the rules mean

    What each rule means for your documents.

    Regulation overview →
    PeppolMandatory in Belgium since 2026NIS2Cybersecurity duties for the mid-marketeIDAS 2The EU digital identity walletEU AI ActWhich obligations apply whenRetention periodsBelgium, the Netherlands and Luxembourg

    Free tools

    Answers in minutes

    Quick checks you can run today.

    SharePoint or M-Files?Take the 8-question quizRetention period lookupHow long to keep what

    AI Readiness Scan

    Is your data ready for AI?

    7 questions, your score out of 100 and concrete next steps.

    NewsletterOnce a month, in your language

    Start the scan

  • Cases
  • Who we are
  • Client zone
SoftAdvice - Proces & information architects
  • Plan a demo
  • Nederlands Nederlands (BE) English (US) Français (BE)
SoftAdvice - Proces & information architects
      • Solutions
      • Platforms
      • Approach
      • Knowledge
      • Cases
      • Who we are
      • Client zone
    • Nederlands Nederlands (BE) English (US) Français (BE)
    • Plan a demo

    Home/Process library/A transmittal ready to send by e-mail

    Process library · Engineering

    A 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

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-28
    Sector
    Engineering
    Process
    Document delivery
    Starts with
    Selected documents
    Result
    Transmittal ready to send
    Building blocks
    M-Files · Engineering Pack
    Governance
    Audit trail
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Select the documents
    Engineer
    →
    2
    Create the collection
    Automatic
    →
    3
    Render the transmittal
    Engineer
    →
    4
    Front page, zip and link
    Automatic
    →
    5
    Send by e-mail
    Engineer
    →
    ✓
    Transmittal ready to send
    In shortRhythmFlowLifecycleBuilding blocksFAQ

    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 moment

    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
    The rhythm of a delivery

    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.

    The flow

    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.

    Engineer

    Create the collection

    One command creates a transmittal collection with the selected documents, linked to the project. It starts as a draft.

    Automatic

    Render the transmittal

    When the collection is complete, the engineer moves it to render. M-Files generates the front page and the zip file.

    Engineer

    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.

    Automatic

    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.

    Engineer
    Lifecycle

    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

    DraftDocuments can still change
    Render transmittalStarted by the engineerComplete?
    RenderedLinked to its transmittal

    Transmittal document

    Front page and zipGenerated from the metadata
    Ready to sendWith a link for the client
    RecordedWith the project
    The engineer decides the batch is completeKept with the project and its history
    What changes for the team

    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
    Building blocks

    M-Files and the SoftAdvice Engineering Pack

    The same building blocks as the overview blueprint, configured and documented by SoftAdvice.

    Transmittals

    Collection, generated front page, zip file and link, recorded per project.

    Read more

    Client numbers as metadata

    The client’s document and revision numbers live on the document and appear on the front page.

    Read more

    Engineering Pack

    Placeholders, review per project and transmittals in one sector solution.

    Read more

    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.

    Related

    All blueprintsFrom project to transmittalPlaceholders generated from rulesTransmittalsEngineering Pack
    Related blueprints

    More from the process library

    All blueprints
    Engineering
    BP-14
    Project
    Transmittal

    From project to transmittal

    The client asks which revision they received. The answer is buried in an email from last month.
    Projects from your ERP or CRM, placeholders in one click, review per project phase and transmittals with a front page.
    Audit trail · Permissions
    M-Files
    ERP/CRM
    Engineering Pack
    Engineering
    BP-27
    Project
    Placeholders ready

    Placeholders generated from rules

    A new project starts. Each engineer creates and names their files their own way. At the end, three deliverables turn out to be missing.
    Every expected deliverable created in one go from placeholder sets: tagged, named, secured and in the review steps of its project.
    Audit trail · Permissions
    M-Files
    ERP/CRM
    Engineering Pack
    Engineering
    BP-29
    New project
    Project overview

    From master document list to project overview

    Progress meeting tomorrow. The client asks for the document list. Someone spends the evening updating a spreadsheet.
    Internal, client and supplier lists per project, every document a placeholder with a status from its workflow, one overview.
    Audit trail
    M-Files
    Engineering Pack

    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.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-28
    Engineering
    Document delivery
    A transmittal ready to send by e-mail
    The moment
    The client wants the documents for review today. Someone copies files into a folder, types a cover sheet and zips it all by hand.
    Selected documents become a transmittal: generated front page with client numbers, one zip file and a link, recorded with the project.
    The flow
    1. 1
      Select the documents
      Engineer
    2. 2
      Create the collection
      Automatic
    3. 3
      Render the transmittal
      Engineer
    4. 4
      Front page, zip and link
      Automatic
    5. 5
      Send by e-mail
      Engineer
    Blueprint BP-28
    Sector
    Engineering
    Process
    Document delivery
    Starts with
    Selected documents
    Result
    Transmittal ready to send
    Building blocks
    M-Files · Engineering Pack
    Audit trail
    Recognise this moment?
    Tell us about your own process. We look at it with you, without obligation.
    Discuss this processsoftadvice.eu/plan-a-callRead the full blueprintsoftadvice.eu/in-practice/engineering-transmittal-ready-to-send
    Blueprint from the SoftAdvice process library. Real process, described anonymously.
    Only M-Files Solution Partner in the BeNeLux · 100+ implementations since 2010
    See the flow

    SoftAdvice

    Process & information architects

    Partner of M-Files since 2010, and of MacroView and Mindbreeze, in Belgium, the Netherlands and Luxembourg.

    Otterstraat 199
    2300 Turnhout, Belgium
    info@softadvice.eu
    Belgium +32 2 895 06 00
    Netherlands +31 79 799 61 40
    Luxembourg +352 27 86 46 55

    LinkedIn

    Platforms

    • M-Files
    • SharePoint + MacroView
    • Mindbreeze

    Integrations

    • dox42
    • Penneo
    • Microsoft 365
    • All integrations

    Services

    • Discovery
    • Process consulting
    • Implementation
    • Integrations
    • Success services
    • AI governance

    Company

    • Who we are
    • Knowledge Hub
    • Newsletter
    • Contact

    Partners

    M-Files Solution PartnerSolution PartnerMacroViewMindbreezedox42

    Newsletter

    Once a month, in your language. Unsubscribe at any time.

    Subscribe

    Thank you. You will receive the next edition in your mailbox.

    © 2026 SoftAdvice BV. All rights reserved.

    PrivacyCookiesTerms

    We use cookies to provide you a better user experience on this website. Cookie Policy

    Only essentials I agree