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/Placeholders generated from rules

    Process library · Engineering

    Placeholders generated from rules

    Before the first drawing exists, the project already knows every document it will deliver. The project manager picks the placeholder sets; M-Files creates the empty documents in one go, with the right group, name, rights and review steps.

    See the flow Engineering Pack

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-27
    Sector
    Engineering
    Process
    Projects
    Starts with
    Project
    Result
    Placeholders ready
    Building blocks
    M-Files · ERP/CRM · Engineering Pack
    Governance
    Audit trail · Permissions
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Take over the project
    Automatic
    →
    2
    Choose the review steps
    Project manager
    →
    3
    Pick the placeholder sets
    Project manager
    →
    4
    Generate
    Automatic
    →
    5
    Fill the placeholder
    Engineer
    →
    6
    Into review
    Automatic
    →
    ✓
    Placeholders ready
    In shortRhythmFlowLifecycleBuilding blocksFAQ

    In short

    In this blueprint an engineering firm takes its projects from its project system into M-Files. Per project, the project manager decides which review steps apply, for example internal review, client review and final. Then they generate placeholders: empty documents that reserve a spot for every expected deliverable. A placeholder set, such as a set for safety documents, is chosen and generated, several times if needed. M-Files creates all placeholders in one go and tags each one with the project and a group numbering in three levels, names it by the naming convention, sets the rights, attaches the review workflow and publishes it, in the background. Engineers then drag their file onto the placeholder; it keeps the metadata, and the name follows the convention. SoftAdvice built and documented the process.

    The moment

    Every project delivers the same kinds of documents

    A new project starts. Each engineer creates and names their files their own way. At the end, three deliverables turn out to be missing.

    An engineering firm runs many projects at once. Each one delivers specifications, calculations, drawings and safety documents, grouped by a numbering the whole sector knows. And each client expects a slightly different review route.

    When every engineer creates and names files their own way, nobody can say which deliverables are still missing, and the same document exists under three names.

    • A reserved spot for every expected deliverable
    • Group numbering in three levels
    • Names built from the metadata
    • Only the review steps this project needs
    The rhythm of a project

    What happens from project start to the first upload

    The structure is set once, at the start. After that, engineers only add content.

    When the project arrives

    Project in M-Files

    The project comes from the project system, with client, manager and dates.

    At the kick-off

    Choose the review steps

    The project manager decides which review steps the documents of this project go through.

    Right after

    Generate the placeholders

    One or more placeholder sets are generated in one go, in the background.

    During the project

    Fill them

    Engineers drag their files onto the placeholders; the empty ones show what is still missing.

    The flow

    From project to ready placeholders, step by step

    Two decisions for the project manager, one gesture for the engineer. M-Files does the rest and records it in the history.

    Take over the project

    Projects come from the project system into M-Files, grouped by their state, with client, project manager, department and dates.

    Automatic

    Choose the review steps

    On the project, the project manager ticks the review steps that apply, for example internal review, client review and final.

    Project manager

    Pick the placeholder sets

    With the project selected, the project manager picks one or more placeholder sets, each with how many times it is needed, and presses generate.

    Project manager

    Generate

    M-Files creates every placeholder in one go: tagged with the project and the three group levels, named by the convention, with its rights, its review workflow, published. The team keeps working meanwhile.

    Automatic

    Fill the placeholder

    The engineer drags the file onto its placeholder and adds the client’s document and revision number. The name is built from the metadata.

    Engineer

    Into review

    The document starts in draft and only offers the review steps chosen for this project.

    Automatic
    Lifecycle

    From reserved spot to reviewed document

    A placeholder is a document from the first second. It only gets its content later, and then follows the review steps of its project.

    Deliverable

    PlaceholderEmpty, tagged and named
    DraftFile dropped in
    Internal reviewIf chosen for the projectReview
    Client reviewIf chosen for the projectReview
    FinalRevision recorded
    A person reviews; a revision update sends it back with a new revisionFinal, kept with its history
    What changes for the team

    From creating documents to filling them

    The project manager sees on day one what the project will deliver, and every day what is still missing.

    Before

    • Every engineer names files their own way
    • Missing deliverables found at the end
    • Group codes typed by hand
    • One review route for every client

    Now

    • Names built from the metadata
    • Empty placeholders show what is missing
    • Group levels set by the generator
    • Review steps chosen per project
    Building blocks

    M-Files and the SoftAdvice Engineering Pack

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

    Placeholder generator

    Placeholder sets defined once, generated per project in one click, in the background.

    Read more

    Projects from your project system

    Projects, clients and project managers come in from the system you already use.

    Read more

    Document control

    Naming convention, external document and revision numbers, and a review workflow per project.

    Read more

    Questions about this blueprint

    What exactly is a placeholder?

    An empty document created in advance for a deliverable you know will come. It already has its project, group, name, rights and workflow. You drop the real file onto it later.

    Who defines the placeholder sets?

    Your team, together with SoftAdvice, once. A set lists the documents a type of work always needs, with their groups. After that, generating is one click per project.

    Can a project skip review steps?

    Yes. The project manager chooses the steps per project, and the documents of that project only offer those steps.

    Related

    All blueprintsFrom project to transmittalA transmittal ready to sendDocument controlEngineering 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-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
    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 does your next project get its structure?

    In a one-hour demo we generate the placeholders of a project with you and fill the first one.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-27
    Engineering
    Projects
    Placeholders generated from rules
    The moment
    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.
    The flow
    1. 1
      Take over the project
      Automatic
    2. 2
      Choose the review steps
      Project manager
    3. 3
      Pick the placeholder sets
      Project manager
    4. 4
      Generate
      Automatic
    5. 5
      Fill the placeholder
      Engineer
    6. 6
      Into review
      Automatic
    Blueprint BP-27
    Sector
    Engineering
    Process
    Projects
    Starts with
    Project
    Result
    Placeholders ready
    Building blocks
    M-Files · ERP/CRM · Engineering Pack
    Audit trail
    Permissions
    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-placeholders-by-rules
    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