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/From working copy to approved drawing

    Process library · Engineering

    From working copy to approved drawing

    The engineer keeps working in the working copy. When a revision is ready, M-Files publishes it as a PDF with the next revision letter, sends it to the checker named on the drawing, and asks the approver for an electronic signature.

    See the flow Document control

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-30
    Sector
    Engineering
    Process
    Review and approval
    Starts with
    Working copy
    Result
    Approved revision
    Building blocks
    M-Files · Engineering Pack
    Governance
    Audit trail · Version control
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Create the working copy
    Engineer
    →
    2
    Name the reviewers
    Engineer
    →
    3
    Release a revision
    Automatic
    →
    4
    Check
    Checker
    →
    5
    Approve and sign
    Approver
    →
    ✓
    Approved revision
    In shortRhythmFlowLifecycleBuilding blocksFAQ

    In short

    In this blueprint an engineering firm keeps two records per drawing in M-Files: a working copy with the source file, and release copies for every revision. The engineer creates the drawing as a working copy in draft, linked to its placeholder and master document list; the name follows the naming convention. The reviewer and approver are filled in on the drawing, and the workflow sends its tasks to exactly those people. Moving the working copy to review publishes a release copy with the next revision letter, converted to PDF. The checker gets a review task; rejecting it sends the drawing back, completing it moves it to approval. The approver approves with an electronic signature, and the document status becomes OK. Every version stays in the history. SoftAdvice built and documented the process.

    The moment

    Which revision is the approved one?

    A drawing is sent to the client. It turns out to be revision A. Revision B was approved last week.

    A drawing changes many times before it is approved, and again after. Engineers need the source file to keep working; everyone else needs the approved PDF, with its revision letter.

    When both live in the same folder, a draft is sent as if it were approved, and nobody can show who checked revision B.

    • Working copy and release copies apart
    • Revision letters set by the system
    • Checker and approver named on the drawing
    • Approval with an electronic signature
    The rhythm of a drawing

    What happens from the first sketch to an approved revision

    The working copy moves at the pace of the engineer. Each revision moves at the pace of the review.

    While drafting

    Work and comment

    Versions, annotations, comments with colleagues tagged, track changes in Office.

    When a revision is ready

    Release

    A release copy with the next revision letter and a PDF.

    Within days

    Check

    The checker reviews the PDF and accepts or rejects.

    At approval

    Sign

    The approver signs electronically; the status becomes OK.

    The flow

    From working copy to approved revision, step by step

    People check and approve. M-Files numbers, converts, routes and records every step in the history.

    Create the working copy

    The engineer adds the drawing as a working copy, linked to its placeholder and master document list. It starts in draft and gets its name from the naming convention; mistakes in the metadata can still be fixed.

    Engineer

    Name the reviewers

    The checker and approver are filled in on the drawing. The workflow sends its tasks to exactly these people, so changing a name changes the route.

    Engineer

    Release a revision

    Moving the working copy to review publishes a release copy with the next revision letter, converted to PDF. The source file stays in the working copy.

    Automatic

    Check

    The checker gets a review task with a notification. Completing it moves the drawing to approval; rejecting it sends it back.

    Checker

    Approve and sign

    The approver approves with an electronic signature. The document status becomes OK, and the revision is the one everyone uses.

    Approver
    Lifecycle

    Two records per drawing

    The working copy keeps the source and the versions. Each release copy is one revision, with its PDF, its review and its signature.

    Working copy

    DraftSource file, versions
    Under reviewRelease copy published

    Release copy

    PDFNext revision letter
    ReviewCheckerAccept or reject
    ApproveApproverSignature
    ApprovedStatus OK
    A person decides before it can move onApproved, kept with its history
    What changes for the team

    From guessing the revision to knowing it

    Engineers keep working in one file, and everyone else sees only approved, numbered PDFs.

    Before

    • Drafts and approved drawings in one folder
    • Revision letters typed by hand
    • Review requested by mail
    • No proof of who approved

    Now

    • Working copy and release copies apart
    • Next revision letter by the system
    • Tasks for the people named on the drawing
    • Approval signed electronically
    Building blocks

    M-Files and the SoftAdvice Engineering Pack

    Configured and documented by SoftAdvice.

    Revisions and version control

    Every save is a version; every release is a revision with its own letter and PDF.

    Read more

    Review with electronic signature

    Tasks for the people named on the document, and a signature at approval.

    Read more

    Document control

    Naming convention, master document lists and document status in one model.

    Read more

    Questions about this blueprint

    Why a working copy and a release copy?

    So the engineer can keep working in the source file while a revision is in review. The release copy holds the PDF that is checked, approved and shared.

    Is the electronic signature legally binding?

    The approval signature records who approved and when, inside M-Files. For a legal signature towards the client, the transmittal that sends the documents is signed with an e-signature service.

    Can the client see drawings in review?

    No. A drawing in review is not shared. Only approved revisions go to the client.

    Related

    All blueprintsFrom master document list to project overviewA transmittal ready to send by e-mailDigital signatures
    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

    Who approved your last revision?

    In a one-hour demo we take a drawing from working copy to an approved, signed revision.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-30
    Engineering
    Review and approval
    From working copy to approved drawing
    The moment
    A drawing is sent to the client. It turns out to be revision A. Revision B was approved last week.
    Each revision released as a PDF with its own letter, checked by the person named on the drawing and approved with an e-signature.
    The flow
    1. 1
      Create the working copy
      Engineer
    2. 2
      Name the reviewers
      Engineer
    3. 3
      Release a revision
      Automatic
    4. 4
      Check
      Checker
    5. 5
      Approve and sign
      Approver
    Blueprint BP-30
    Sector
    Engineering
    Process
    Review and approval
    Starts with
    Working copy
    Result
    Approved revision
    Building blocks
    M-Files · 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-drawing-review-approval
    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