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/Product files without folders

    Process library · Quality management

    Product files that build themselves at a manufacturer

    A customer or an auditor asks for the full history of one serial number. Instead of opening folders, the quality manager selects the product and the serial number, and M-Files shows every record that belongs to it.

    See product files in M-Files See the process

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-11
    Sector
    Quality management
    Process
    Quality and CAPA
    Starts with
    Production
    Result
    Product file
    Building blocks
    M-Files for Quality
    Governance
    Audit trail · Version control
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Define the product
    Engineering
    →
    2
    Tag every document
    Author
    →
    3
    Record production
    Manufacturing
    →
    4
    Retrieve
    Quality
    →
    ✓
    Product file
    In shortRhythmFlowProcessTraceabilityBuilding blocksFAQ

    In short

    In this scenario a manufacturer anchors every document and record to a product in M-Files for Quality. A document category marks whether a document belongs to the design file, the technical file with the released specifications, or the production history. Production records also carry the serial or lot number. The three files are not folders but views that assemble themselves from this metadata, so they are always complete and current. Quality events, changes and risks are linked to the same product. SoftAdvice sets up and documents the configuration.

    The moment

    Three files per product, and they must always be complete

    A customer reports a problem with one serial number. The file is scattered across design, production and quality.

    Customers, certification bodies and regulators want to see how a product was designed, which specifications applied and how each unit or lot was made. In practice the same document often belongs in more than one file.

    With folders, documents are copied, versions drift apart, and building the history of one serial number for a complaint or an audit takes days.

    • Design file: plans, reviews, tests
    • Technical file: released specifications
    • Production history per serial or lot
    • Linked to quality events and changes
    The rhythm of a product

    What happens from design to the last unit shipped

    The product sets the rhythm. Every document added along the way lands in the right file by its metadata.

    During design

    Build the design file

    Plans, reviews and test reports are tagged as design and linked to the product.

    At release

    Release the technical file

    Released specifications and instructions form the technical file of the product family.

    Every lot

    Record production

    Production records carry the lot or serial number and build the production history.

    Every change

    Keep the files current

    A change to the product updates the technical file at once; history stays visible.

    Every question

    Show it in minutes

    Pick a product and a serial number; the file is there.

    The flow

    From product to audit-ready file, step by step

    The work is in tagging documents well when they are created. M-Files does the rest.

    Define the product

    Engineering creates the product with model, product family, intended use and the standards that apply.

    Engineering

    Tag every document

    Each controlled document gets the product and a document category: design, technical file or production. The category stays the same for the whole lifecycle.

    Author

    Record production

    Manufacturing adds production records with the serial or lot numbers from a controlled list.

    Manufacturing

    Retrieve

    Quality opens the design, technical or production view for a product or serial number, with every linked event and change.

    Quality
    The process

    Watch the process run

    Every lane is a role. Follow one product from its definition to a customer question about a serial number, and see what M-Files does by itself.

    Engineering
    Author
    Production
    M-Files
    Quality
    New product
    Define the product
    Tag document with category
    Show in the right file
    Record lot or serial number
    Add to production history
    Customer asks about a serial
    Open the three files
    Answered
    EngineeringNew product

    A new product or product family is developed.

    EngineeringDefine the product

    Engineering creates the product with model, product family, intended use and the standards that apply.

    AuthorTag document with category

    Each plan, test report or specification gets the product and a category: design, technical file or production.

    M-FilesShow in the right file

    The document appears in the design or technical file view by itself. Only released versions enter the technical file.

    ProductionRecord lot or serial number

    Production adds its records with the serial or lot numbers from a controlled list.

    M-FilesAdd to production history

    Each record joins the production history of that serial or lot, next to the design and technical file of the product.

    QualityCustomer asks about a serial

    A complaint or an audit asks how one unit was made.

    QualityOpen the three files

    Quality picks the product and the serial number and sees design, technical file, production history and every linked event or change.

    QualityAnswered

    The answer is ready in minutes, with the evidence attached.

    StartTaskDecisionDone by M-FilesEnd
    Process first, then the tools

    First understand. Then improve. Only then automate.

    We design the process and its decisions first. Only then do we let the software carry the routine.

    Where people decide

    Judgement stays with your team

    These steps need knowledge of the client, the product or the risk, so a person owns them.

    • Define the product
    • Tag document with category
    • Record lot or serial number
    • Customer asks about a serial
    • Open the three files
    M-Files

    What the technology carries

    These steps run by themselves, and every action is logged.

    • Show in the right file
    • Add to production history
    Traceability

    One product, every record linked

    Everything hangs on the product. Follow the chain from design to a single unit, and from there to any issue or change.

    From design to unit

    ProductModel, family, intended use
    Design filePlans, reviews, tests
    Technical fileReleased specificationsReleased only
    Production historyPer serial or lot
    Quality events and changesLinked to the same product
    Only released, effective documents appear hereEvery link stays in the audit trail
    Source and view

    The records are controlled. The file is a view.

    Every specification, drawing, test report and production record is a controlled record with its own version, approval and history. That is the source the auditor relies on.

    The design file, technical file and production history are not copies of those records. They are views that M-Files assembles from the metadata, so a record lives in one place and still appears in every file it belongs to. Change the record, and every file shows the new version.

    • Controlled record: versioned, approved, signed
    • File: a view built from metadata
    • No copies, so no versions drifting apart
    • In medtech: DHF, DMR and DHR
    What changes for the team

    From copying documents into folders to files that are always complete

    Quality spends audit days answering questions, not collecting paper.

    Before

    • The same document copied into three folders
    • Versions drift apart
    • Serial numbers in a separate spreadsheet
    • Days to rebuild the history of one unit

    Now

    • One document, shown in every file it belongs to
    • Always the effective version
    • Serial and lot numbers as metadata
    • The history of a unit in one view
    Building blocks

    M-Files for Quality, set up for your products

    The quality solution from M-Files, configured and documented by SoftAdvice.

    Product and process as master data

    Every document, event, risk and change is linked to a product, a process or both.

    Read more

    Views instead of folders

    The three files are views built from metadata, so one document can appear in several files.

    Read more

    Controlled lifecycle

    Only approved, effective documents enter the technical file; every version stays in the history.

    Read more

    Questions about this scenario

    Which sectors is this for?

    Any manufacturer that has to trace products by serial or lot number: machine building, metal and plastics, electronics, food and packaging, and regulated sectors such as medical devices, where these files are called DHF, DMR and DHR.

    Does M-Files run our design control workflow?

    The standard configuration assembles the design file from tagged documents. Design inputs, outputs, reviews and transfer as separate workflow objects are not part of it; we look at what you need in the implementation.

    Can we link to our ERP or PLM system?

    Yes. Product data and serial or lot numbers can come from ERP or PLM, so they are not typed twice. The scope is set during discovery.

    Cloud or on-premises?

    Both. The solution runs as an M-Files Cloud vault in Microsoft Azure or on your own servers, depending on your validation approach and IT policy.

    Related

    All scenariosFrom deviation to effective CAPAFrom change to trained teamQuality managementStart with DiscoveryM-Files with ERP and CRM
    Related blueprints

    More from the process library

    All blueprints
    Quality management
    BP-08
    Deviation
    Effective CAPA

    From deviation to effective CAPA

    A batch is rejected. Again. Same root cause as last time.
    Containment the same day, root cause, and a CAPA closed only after verification and validation.
    Audit trail
    M-Files
    M-Files for Quality
    Quality management
    BP-09
    Audit plan
    Closed finding

    From audit plan to closed finding

    The certification audit is next week. Last year’s findings are still open. Nobody knows who owns them.
    Internal, supplier and certification audits in one plan, every finding linked to its follow-up.
    Audit trail · Permissions
    M-Files
    M-Files for Quality
    Quality management
    BP-10
    Change request
    Trained team

    From change request to trained team

    A procedure has changed. On the shop floor, the old version is still pinned to the wall.
    A change assessed and approved, one effective version, and training that follows the document.
    Audit trail · Version control
    M-Files
    M-Files for Quality

    How long does it take to trace one serial number?

    In a one-hour demo we show how product files assemble themselves in M-Files. Want to map your own files first? Discovery is the next step.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-11
    Quality management
    Quality and CAPA
    Product files without folders
    The moment
    A customer reports a problem with one serial number. The file is scattered across design, production and quality.
    Design file, technical file and production history assembled from metadata, per product and serial or lot number.
    The flow
    1. 1
      Define the product
      Engineering
    2. 2
      Tag every document
      Author
    3. 3
      Record production
      Manufacturing
    4. 4
      Retrieve
      Quality
    Blueprint BP-11
    Sector
    Quality management
    Process
    Quality and CAPA
    Starts with
    Production
    Result
    Product file
    Building blocks
    M-Files for Quality
    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/quality-product-file-per-serial-number
    Blueprint from the SoftAdvice process library. Real process, described anonymously.
    Only M-Files Solution Partner in the BeNeLux · 100+ implementations since 2010
    See product files in M-Files

    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