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 deviation to effective CAPA

    Process library · Quality management

    From deviation to effective CAPA at a manufacturer

    A part fails inspection. The product is put on hold the same day, the cause is investigated, and the corrective action is only closed once a second person has seen proof that it was done and that it works.

    See a CAPA workflow in M-Files See the process

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-08
    Sector
    Quality management
    Process
    Quality and CAPA
    Starts with
    Deviation
    Result
    Effective CAPA
    Building blocks
    M-Files for Quality
    Governance
    Audit trail
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Record the event
    Quality control
    →
    2
    Contain
    Production
    →
    3
    Investigate and act
    CAPA owner
    →
    4
    Verify, validate, close
    Independent reviewer
    →
    ✓
    Effective CAPA
    In shortRhythmFlowProcessLifecycleBuilding blocksFAQ

    In short

    In this scenario a manufacturer records every deviation as a quality event in M-Files for Quality, linked to the product, the lot and the process. Containment, such as a product hold or quarantine, runs as its own record with its own verification, so it can close while the investigation continues. The corrective action (CAPA) follows a fixed lifecycle: assigned, carried out, verified by an independent reviewer, validated for effectiveness and closed with an electronic signature. A year later, the effectiveness is checked again. SoftAdvice sets up and documents the process.

    The moment

    A deviation is a race against the clock

    A batch is rejected. Again. Same root cause as last time.

    A manufacturer of technical components finds a part out of specification. Two things matter at once: the affected product must not leave the building, and the cause must be fixed so it does not happen again.

    With spreadsheets and e-mail, the hold is agreed in a corridor, the investigation lives in someone’s mailbox, and the action is closed without proof that it worked. That is exactly what an auditor looks for.

    • Nonconformances, complaints and supplier issues
    • Containment on its own timeline
    • Done is not the same as effective: two separate checks
    • Linked to product, lot and process
    The rhythm of quality

    What happens from the first hour to a year later

    A deviation has its own rhythm: act fast, investigate thoroughly, and check later that the fix really held.

    The first hour

    Record and contain

    The deviation is recorded with product and lot, and a containment action puts the product on hold.

    The first days

    Investigate

    Quality and production look for the root cause and decide whether a CAPA is needed.

    The following weeks

    Act and verify

    The owner carries out the action; an independent reviewer checks the evidence.

    At closure

    Validate and sign

    The reviewer confirms the action prevents recurrence and signs electronically.

    A year later

    Check effectiveness again

    M-Files brings the CAPA back for a second look, so a fix that faded is caught.

    The flow

    From quality event to closed CAPA, step by step

    Every step has an owner. M-Files routes the work, asks for evidence and keeps the audit trail.

    Record the event

    Quality control records the nonconformance in M-Files, linked to the product, lot and process. Complaints and supplier issues start the same way.

    Quality control

    Contain

    A containment record holds, segregates or quarantines the affected product. It is verified and closed on its own, while the investigation goes on.

    ProductionQuality

    Investigate and act

    The CAPA owner records the root cause and the planned actions. Documents that must change go into change control.

    CAPA owner

    Verify, validate, close

    An independent reviewer confirms the action was done, then that it works. Each step needs evidence and an electronic signature.

    Independent reviewer
    The process

    Watch the process run

    Every lane is a role. Follow the deviation from the shop floor to the signed CAPA, and see what M-Files does by itself.

    Quality control
    Production
    CAPA owner
    Independent reviewer
    M-Files
    Deviation found
    Record the nonconformance
    Link and notify
    Hold or quarantine
    CAPA needed?
    Closed as event
    Root cause and actions
    Verify and validate
    Evidence accepted?
    Close and plan the check
    CAPA closed
    YesNoYesNo
    Quality controlDeviation found

    A part fails the incoming or final inspection.

    Quality controlRecord the nonconformance

    Quality control creates the quality event in M-Files, with product, lot, process and severity. A photo or measurement report goes with it.

    M-FilesLink and notify

    M-Files links the event to the product and lot, and notifies quality and production that containment is needed.

    ProductionHold or quarantine

    Production puts the affected lot on hold. The containment record is verified and closed on its own timeline.

    Quality controlCAPA needed?

    Quality decides whether the cause needs a corrective action. A one-off deviation can be closed as an event.

    Quality controlClosed as event

    The event is closed with its disposition and stays available for trend analysis.

    CAPA ownerRoot cause and actions

    The CAPA owner records the root cause and carries out the actions. Documents that change go into change control.

    Independent reviewerVerify and validate

    The reviewer checks the evidence: was the action done as planned, and does it prevent recurrence?

    Independent reviewerEvidence accepted?

    If the evidence falls short, the CAPA goes back to its owner with a comment. If it holds, the reviewer signs electronically.

    M-FilesClose and plan the check

    M-Files closes the CAPA read-only and plans the effectiveness check a year later.

    M-FilesCAPA closed

    Event, containment, CAPA and evidence are linked in one trail for the next audit.

    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.

    • Record the nonconformance
    • Hold or quarantine
    • CAPA needed?
    • Root cause and actions
    • Verify and validate
    • Evidence accepted?
    M-Files

    What the technology carries

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

    • Link and notify
    • Close and plan the check
    Lifecycle

    Two records, two timelines, one trail

    Containment and CAPA each have their own lifecycle. The product can be released or scrapped while the root cause is still being investigated.

    Containment

    InitiatedLinked to event and lot
    In progressHold, segregate, quarantine
    ExecutedDisposition recorded
    VerificationIndependent reviewerEvidence
    Closed

    Corrective action (CAPA)

    NewFrom the quality event
    AssignedOwner and due date
    CompletedActions carried out
    VerificationWas it done as planned?Signature
    ValidationDoes it prevent recurrence?Signature
    ClosedEffectiveness check after a year
    Needs evidence and approval before it can move onClosed, read-only and kept in the audit trail
    What changes for the team

    From closing actions on trust to closing them on evidence

    Quality sees every open event and CAPA in one view, and nobody has to rebuild the story before an audit.

    Before

    • Holds agreed by word of mouth
    • CAPA list in a spreadsheet
    • Closed without proof that it worked
    • Nobody looks back a year later

    Now

    • Containment recorded and verified
    • Every CAPA linked to its event, product and lot
    • Verification and validation signed
    • Effectiveness checked again after a year
    Building blocks

    M-Files for Quality, set up for your process

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

    Quality events and CAPA

    Nonconformances, complaints, audit findings and supplier issues in one model, each linked to its CAPA.

    Read more

    Workflow with electronic signatures

    Each state has an owner; the steps that matter ask for evidence and a signature.

    Read more

    Product and process as metadata

    Every record carries product, lot and process, so trends per product or process are one view away.

    Read more

    Questions about this scenario

    Is this only for manufacturers?

    No. Any organisation that handles deviations, complaints or supplier issues can work this way, from machine building and food to services and regulated sectors such as medical devices.

    Does this make us compliant with ISO 9001?

    The solution supports the processes that ISO 9001 and sector standards such as ISO 13485 or IATF 16949 ask for, such as controlled CAPA, verified containment and audit trails. Compliance stays the responsibility of your organisation.

    Why separate verification and validation?

    Verification shows the action was carried out as planned. Validation shows it actually prevents the problem from coming back. Auditors ask for both.

    Can suppliers work in the system?

    Suppliers have no access to the vault. They are informed by e-mail when a supplier issue concerns them; your team records their answers.

    Related

    All scenariosFrom audit to closed findingFrom change to trained teamQuality managementStart with DiscoveryQHSE readiness score
    Related blueprints

    More from the process library

    All blueprints
    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
    Quality management
    BP-11
    Production
    Product file

    Product files without folders

    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.
    Audit trail · Version control
    M-Files
    M-Files for Quality

    How do you close a CAPA today?

    In a one-hour demo we show the CAPA workflow in M-Files, from deviation to validated action. Want to map your own process first? Discovery is the next step.

    Book a one-hour demo

    SoftAdvice
    Process library
    Blueprint BP-08
    Quality management
    Quality and CAPA
    From deviation to effective CAPA
    The moment
    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.
    The flow
    1. 1
      Record the event
      Quality control
    2. 2
      Contain
      Production
    3. 3
      Investigate and act
      CAPA owner
    4. 4
      Verify, validate, close
      Independent reviewer
    Blueprint BP-08
    Sector
    Quality management
    Process
    Quality and CAPA
    Starts with
    Deviation
    Result
    Effective CAPA
    Building blocks
    M-Files for Quality
    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/quality-deviation-to-capa
    Blueprint from the SoftAdvice process library. Real process, described anonymously.
    Only M-Files Solution Partner in the BeNeLux · 100+ implementations since 2010
    See a CAPA workflow 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