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/Sharing and receiving through a client hub

    Process library · Engineering

    Sharing and receiving through a client hub

    Approved documents appear on the client’s hub, and the client gets a mail with a link. What the client has to send, they upload into the placeholder waiting for it, and it lands straight in a review in M-Files.

    See the flow HubShare and M-Files

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-31
    Sector
    Engineering
    Process
    Document delivery
    Starts with
    Approved document
    Result
    Reviewed answer
    Building blocks
    M-Files · HubShare · Engineering Pack
    Governance
    Audit trail · Version control
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Publish to the hub
    Project manager
    →
    2
    Notify the client
    Project manager
    →
    3
    Upload by the client
    Client
    →
    4
    Pick up
    Automatic
    →
    5
    Review what came in
    Reviewer
    →
    ✓
    Reviewed answer
    In shortRhythmFlowLifecycleBuilding blocksFAQ

    In short

    In this blueprint an engineering firm shares documents with its client through a hub (HubShare) connected to M-Files, instead of by mail. An approved revision is moved to publish and appears on the client’s hub; documents in review are never visible there. The project manager then sends a notification from the master document list: the client receives a mail that there are new documents on their hub, with a link. The other way round, documents the client must send wait as placeholders open for upload. The client uploads the file on the hub and fills in their own review number. M-Files picks it up, and a reviewer gets a task to check it: OK, or back to the client for a new upload. SoftAdvice built and documented the process.

    The moment

    Documents go both ways, and mail loses track of them

    The client mails its specification to three people. Two weeks later, nobody has checked it and two versions are in circulation.

    An engineering firm sends drawings and calculations to its client, and the client sends specifications and test procedures back. Both sides want to know what they have and what is still missing.

    By mail, attachments go to three people, versions cross each other, and a received specification sits in an inbox instead of in a review.

    • Only approved revisions on the hub
    • A mail with a link when there is something new
    • The client uploads into the waiting placeholder
    • Every received document goes into review
    The rhythm of an exchange

    What happens on the way out and on the way back

    Out: approve, publish, notify. Back: upload, pick up, review.

    After approval

    Publish

    The approved revision appears on the client’s hub.

    When a batch is ready

    Notify

    The client receives a mail with a link to the hub.

    When the client delivers

    Upload

    The client uploads into the placeholder that waits for it.

    Right after

    Review

    A reviewer gets a task: OK, or back for a new upload.

    The flow

    From approved document to reviewed answer, step by step

    People decide what to share and whether what came back is right. The hub and M-Files move the files and record every step in the history.

    Publish to the hub

    An approved revision is moved to publish and appears on the client’s hub. Documents in review stay hidden.

    Project manager

    Notify the client

    From the master document list, the project manager sends the notification: a mail that there are new documents on the hub, with a link.

    Project manager

    Upload by the client

    On the hub, the client opens a placeholder that is open for upload, adds the file and fills in their own review number.

    Client

    Pick up

    M-Files picks up the upload by itself, marks the document as added and sends a review task to the reviewer.

    Automatic

    Review what came in

    The reviewer marks the document OK, or sends it back to open for upload so the client can deliver a new version.

    Reviewer
    Lifecycle

    One route out, one route back

    What goes out is approved first. What comes in is reviewed first.

    Document to the client

    ApprovedHidden while in review
    PublishedOn the client’s hub
    Client notifiedMail with a link

    Document from the client

    Open for uploadPlaceholder waits
    AddedPicked up by M-Files
    Internal reviewReviewerOK or back
    Document OK
    A person decides before it can move onEnd of the route, kept with its history
    What changes for the team

    From attachments to a shared place

    The client always finds the latest approved revision, and what the client sends is checked before anyone builds on it.

    Before

    • Attachments to several people
    • Drafts sent by mistake
    • Client files stuck in an inbox
    • Nobody checks what came in

    Now

    • One hub per client
    • Only approved revisions shared
    • Uploads land in their placeholder
    • A review task for every received file
    Building blocks

    M-Files, HubShare and the Engineering Pack

    Configured and documented by SoftAdvice.

    Client hub with HubShare

    A secure place per client, connected to M-Files, for documents going out and coming in.

    Read more

    Placeholders open for upload

    What the client must send waits as a placeholder on the master document list.

    Read more

    Review workflow

    Every received document gets a review task, and every step is recorded.

    Read more

    Questions about this blueprint

    Does the client need an M-Files licence?

    No. The client works on the hub with their own login; M-Files stays your internal system.

    Which documents can the client upload?

    The ones you prepare as placeholders open for upload, for example specifications and test procedures. You decide this per document type.

    Can suppliers use the hub too?

    In this blueprint the hub serves the client. A route for suppliers can be set up the same way, with its own placeholders and review.

    Related

    All blueprintsFrom working copy to approved drawingFrom master document list to project overviewHubShare and M-Files
    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-28
    Selected documents
    Transmittal ready to send

    A transmittal ready to send by e-mail

    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.
    Audit trail
    M-Files
    Engineering Pack

    How do your clients get your drawings today?

    In a one-hour demo we publish a drawing to a client hub and receive a document back into review.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-31
    Engineering
    Document delivery
    Sharing and receiving through a client hub
    The moment
    The client mails its specification to three people. Two weeks later, nobody has checked it and two versions are in circulation.
    Approved revisions published to the client’s hub with a mail and a link; client uploads land in their placeholder and go into review.
    The flow
    1. 1
      Publish to the hub
      Project manager
    2. 2
      Notify the client
      Project manager
    3. 3
      Upload by the client
      Client
    4. 4
      Pick up
      Automatic
    5. 5
      Review what came in
      Reviewer
    Blueprint BP-31
    Sector
    Engineering
    Process
    Document delivery
    Starts with
    Approved document
    Result
    Reviewed answer
    Building blocks
    M-Files · HubShare · Engineering Pack
    Audit trail
    Version control
    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-customer-hub
    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