{"id":1779,"date":"2026-11-10T00:00:47","date_gmt":"2026-11-10T00:00:47","guid":{"rendered":"https:\/\/mestric.com\/upravljanje-neskladnosti-8d\/"},"modified":"2026-11-10T00:00:49","modified_gmt":"2026-11-10T00:00:49","slug":"upravljanje-neskladnosti-8d","status":"publish","type":"post","link":"https:\/\/mestric.com\/sl\/upravljanje-neskladnosti-8d\/","title":{"rendered":"Managing non-conformities with 8D: a guide for plants"},"content":{"rendered":"<\/p>\n<p>The 8D method manages a non-conformity as a team project with eight disciplines. You contain the problem for the customer first. Then you find and verify the root cause, apply a permanent fix, check that it works and spread the learning. <a href=\"https:\/\/asq.org\/quality-resources\/eight-disciplines-8d\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ASQ describes 8D<\/a> as a structured approach for identifying, correcting and eliminating problems. This guide walks through each discipline as a plant team would use it, with the evidence and records that make an 8D report hold up with a customer.<\/p>\n<div data-blg-cta=\"after_tldr\" data-blg-cta-layout=\"banner\" style=\"margin:28px 0;font-family:-apple-system, BlinkMacSystemFont, &apos;Segoe UI&apos;, Roboto, Helvetica, Arial, sans-serif\">\n<div style=\"border-radius:26px;padding:min(22px,3.2vw);background:radial-gradient(circle at 100% 0%,#e3eeec 0 150px,rgba(255,255,255,0) 151px),radial-gradient(circle at 0% 100%,#e3eeec 0 130px,rgba(255,255,255,0) 131px),linear-gradient(180deg,#edf3f2 0%,#f6f9f9 100%)\">\n<div style=\"background:#ffffff;border-radius:18px;overflow:hidden\">\n<div style=\"padding:34px 30px;text-align:center\">\n<div style=\"margin:0 0 18px\"><span style=\"display:inline-block;max-width:100%;border-radius:999px;padding:6px 13px;font-size:12px;font-weight:800;letter-spacing:0.1em;text-transform:uppercase;line-height:1.3;background:#669f94;color:#ffffff\">Mestric<\/span><\/div>\n<div style=\"font-size:26px;font-weight:800;line-height:1.2;letter-spacing:-0.01em;color:#1f2937;margin:0\">Spot Quality Issues in Real Time<\/div>\n<div style=\"width:56px;height:6px;border-radius:3px;background:#669f94;margin:12px 0 14px;margin-left:auto;margin-right:auto\"><\/div>\n<div style=\"font-size:15px;line-height:1.55;color:#64748b;margin:0 0 24px;max-width:44em;margin-left:auto;margin-right:auto\">Mestric connects with manufacturing equipment to track quality parameters and production performance, helping teams make informed decisions.<\/div>\n<p><a href=\"https:\/\/mestric.com\/sl\/\" style=\"display:inline-flex;align-items:center;gap:9px;border-radius:10px;font-weight:700;font-size:15px;text-decoration:none;padding:13px 22px 13px 26px;background:#669f94;color:#ffffff\">Explore Mestric<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<h2 id=\"tldr\" tabindex=\"-1\">TL;DR<\/h2>\n<ul>\n<li>Use 8D when the root cause is not obvious, several functions are affected, or a customer complaint, recall or serious quality deviation is on the table.<\/li>\n<li>Contain first (D3), then analyse. Sorting and rework protect the customer for now, but they do not stop the problem returning.<\/li>\n<li>Verify the root cause with data instead of settling on the cause the team likes best, and also ask where the defect escaped detection.<\/li>\n<li>Close the loop: measure effectiveness against a baseline, standardise the fix across similar products and record lessons learned.<\/li>\n<li>Customer deadlines for 8D differ from one customer to the next. Read the supplier manual of each customer you ship to.<\/li>\n<\/ul>\n<h2 id=\"table-of-contents\" tabindex=\"-1\">Vsebina<\/h2>\n<ul>\n<li><a href=\"#when-to-use-8d-for-a-non-conformity\">When to use 8D for a non-conformity<\/a><\/li>\n<li><a href=\"#the-eight-disciplines-at-a-glance\">The eight disciplines at a glance<\/a><\/li>\n<li><a href=\"#d1-build-the-team\">D1: build the team<\/a><\/li>\n<li><a href=\"#d2-describe-the-problem-in-numbers\">D2: describe the problem in numbers<\/a><\/li>\n<li><a href=\"#d3-contain-the-problem-for-the-customer\">D3: contain the problem for the customer<\/a><\/li>\n<li><a href=\"#d4-find-and-verify-the-root-cause\">D4: find and verify the root cause<\/a><\/li>\n<li><a href=\"#d5-and-d6-choose-implement-and-prove-the-fix\">D5 and D6: choose, implement and prove the fix<\/a><\/li>\n<li><a href=\"#d7-prevent-recurrence\">D7: prevent recurrence<\/a><\/li>\n<li><a href=\"#d8-close-the-report-and-recognise-the-team\">D8: close the report and recognise the team<\/a><\/li>\n<li><a href=\"#customer-and-slovenian-context\">Customer and Slovenian context<\/a><\/li>\n<li><a href=\"#see-8d-data-in-a-real-production-setting\">See 8D data in a real production setting<\/a><\/li>\n<li><a href=\"#faq\">Pogosto zastavljena vpra\u0161anja<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ul>\n<h2 id=\"when-to-use-8d-for-a-non-conformity\" tabindex=\"-1\">When to use 8D for a non-conformity<\/h2>\n<p>Not every deviation needs eight disciplines. A one-off scratch with a clear cause is better handled with a quick correction and a note in your quality system. ASQ says 8D is particularly suitable when the <a href=\"https:\/\/asq.org\/quality-resources\/eight-disciplines-8d\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">root cause is not apparent, several functions are affected, or there is a customer complaint, recall or significant quality deviation<\/a>.<\/p>\n<p>A practical trigger list for a plant:<\/p>\n<ul>\n<li>a customer complaint or a customer-issued 8D request;<\/li>\n<li>a defect that repeats after a first correction;<\/li>\n<li>a non-conformity that crosses departments, for example a supplier material issue that shows up on the final line;<\/li>\n<li>a safety or regulatory risk linked to the product;<\/li>\n<li>a scrap or rework rate that has moved well beyond its normal range with no clear reason.<\/li>\n<\/ul>\n<p>Some organisations add a D0 step before the team starts. <a href=\"https:\/\/support.minitab.com\/en-us\/engage\/help-and-how-to\/tools\/forms\/types-of-forms\/process-improvement\/8d-methodology\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Minitab says D0<\/a> should decide whether 8D is appropriate, gather data and feedback, and prepare the investigation before the team is assembled. In practice, D0 is where the quality engineer pulls the first numbers: how many parts, which batches, which machines, which shifts.<\/p>\n<h2 id=\"the-eight-disciplines-at-a-glance\" tabindex=\"-1\">The eight disciplines at a glance<\/h2>\n<p>ASQ lists the core disciplines as follows, with D0 as an optional planning step.<\/p>\n<table>\n<thead>\n<tr>\n<th>Discipline<\/th>\n<th>What it answers<\/th>\n<th>Typical output<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>D0<\/td>\n<td>Is 8D the right tool, and what do we know already?<\/td>\n<td>Decision, first data, emergency actions<\/td>\n<\/tr>\n<tr>\n<td>D1<\/td>\n<td>Who works on it?<\/td>\n<td>Named team, leader, champion<\/td>\n<\/tr>\n<tr>\n<td>D2<\/td>\n<td>What exactly is wrong?<\/td>\n<td>Quantified problem statement<\/td>\n<\/tr>\n<tr>\n<td>D3<\/td>\n<td>How do we protect the customer now?<\/td>\n<td>Interim containment<\/td>\n<\/tr>\n<tr>\n<td>D4<\/td>\n<td>Why did it happen and why was it not detected?<\/td>\n<td>Verified root causes<\/td>\n<\/tr>\n<tr>\n<td>D5<\/td>\n<td>What permanent action fixes it?<\/td>\n<td>Chosen and verified corrective actions<\/td>\n<\/tr>\n<tr>\n<td>D6<\/td>\n<td>Did the fix work?<\/td>\n<td>Implementation and effectiveness evidence<\/td>\n<\/tr>\n<tr>\n<td>D7<\/td>\n<td>How do we stop it and similar problems recurring?<\/td>\n<td>Updated procedures, FMEA, standards<\/td>\n<\/tr>\n<tr>\n<td>D8<\/td>\n<td>How do we close and learn?<\/td>\n<td>Sign-off, lessons learned, recognition<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"d1-build-the-team\" tabindex=\"-1\">D1: build the team<\/h2>\n<p>A good 8D team has people who know the product and the process. <a href=\"https:\/\/support.minitab.com\/en-us\/engage\/help-and-how-to\/tools\/forms\/types-of-forms\/process-improvement\/8d-methodology\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Minitab states that D1<\/a> needs a cross-functional team with the skills, technical expertise, availability and authority to address the problem, plus a named project leader and champion.<\/p>\n<p>Size matters too. One large manufacturer\u2019s <a href=\"https:\/\/www.vestas.com\/content\/dam\/vestas-com\/global\/en\/about\/partnering\/documents\/8D%20supplier%20guideline.pdf.coredownload.inline.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">supplier guideline<\/a> recommends trained team members, a leader, core and invited participants, and a team of at least 3 and at most 10 people.<\/p>\n<p>For a typical plant, the core team looks like this:<\/p>\n<ul>\n<li>a team leader, usually from quality or production;<\/li>\n<li>a process owner or shift supervisor who knows what happens on the line;<\/li>\n<li>a maintenance or automation engineer;<\/li>\n<li>a representative from the department that found the problem;<\/li>\n<li>invited specialists, such as purchasing or design, when the analysis points their way.<\/li>\n<\/ul>\n<p>Give the leader the authority to stop a batch or to request a machine slot. An 8D team without that authority stalls at D3.<\/p>\n<h2 id=\"d2-describe-the-problem-in-numbers\" tabindex=\"-1\">D2: describe the problem in numbers<\/h2>\n<p>A vague problem statement produces a vague investigation. ASQ recommends describing the problem in quantifiable terms with 5W2H: <a href=\"https:\/\/asq.org\/quality-resources\/eight-disciplines-8d\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">who, what, where, when, why, how and how many<\/a>, supported by evidence.<\/p>\n<p>One automotive supplier specification adds useful detail: the <a href=\"https:\/\/suppliermanual.veoneer.biz\/sites\/veoneer-portal\/files\/SupplierDocumentLibrary\/SQPS\/SQPS-063.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">D2 description should separate the customer perspective from the technical problem<\/a>, compare the desired and actual condition, quantify the issue and use drawings, graphs, sketches or photographs.<\/p>\n<p>Compare two statements:<\/p>\n<ul>\n<li>Weak: \u2018Housings are cracking.\u2019<\/li>\n<li>Strong: \u2018Customer reports crack at the mounting boss on housings from lot 4417, found at their incoming inspection. 38 of 500 inspected parts affected. Drawing requires no cracks. Photos attached.\u2019<\/li>\n<\/ul>\n<p>The strong version lets you check every other lot and shift against the same description. It also tells you where to look in D4.<\/p>\n<p>This is where machine data helps most. If your downtime, scrap and parameter data is captured automatically per machine and shift, the \u2018when\u2019 and \u2018how many\u2019 of 5W2H come from records, not from memory. Our guide on <a href=\"https:\/\/mestric.com\/sl\/manufacturing-quality-control-tips-enhance-product-quality\/\" target=\"_blank\" rel=\"noopener\">manufacturing quality control tips<\/a> covers the data you should have at hand.<\/p>\n<h2 id=\"d3-contain-the-problem-for-the-customer\" tabindex=\"-1\">D3: contain the problem for the customer<\/h2>\n<p>Containment answers one question: how do we make sure no more bad product reaches the customer while we investigate? The <a href=\"https:\/\/sp-i.org\/downloads\/SPI%208D%20RCCA%20Guidebook.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">SPI 8D guidebook<\/a> says D3 must identify, isolate and correct nonconforming product, data or output so it cannot escape to the customer. Possible actions include replacement, repair, rework, sorting, extra inspection, recall and segregation of supplier or sub-tier material.<\/p>\n<p>The same guidebook draws a clear line between containment and corrective action. Sorting, repair and rework protect the customer temporarily, but they do not eliminate recurrence. That is why D3 never replaces D4 and D5.<\/p>\n<p>Good containment practice, taken from a supplier specification that sets it out in detail:<\/p>\n<ul>\n<li><a href=\"https:\/\/suppliermanual.veoneer.biz\/sites\/veoneer-portal\/files\/SupplierDocumentLibrary\/SQPS\/SQPS-063.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">start quickly and have management verify it<\/a>;<\/li>\n<li>give operators written instructions for sorting or rework, and keep training records;<\/li>\n<li>evaluate the containment itself with FMEA or another risk tool, so it does not create a secondary problem such as handling damage or a mix-up.<\/li>\n<\/ul>\n<p>Check three places for suspect stock: your own work in progress, finished goods and warehouse, and product in transit or at the customer. Record quantities for each, with lot numbers and dates.<\/p>\n<h2 id=\"d4-find-and-verify-the-root-cause\" tabindex=\"-1\">D4: find and verify the root cause<\/h2>\n<p>D4 is where most 8D reports are weak. Teams brainstorm and then write down the first plausible cause. ASQ recommends <a href=\"https:\/\/asq.org\/quality-resources\/eight-disciplines-8d\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">verifying causes rather than merely brainstorming them<\/a>, and names 5 Whys and cause-and-effect diagrams as useful tools.<\/p>\n<h3 id=\"look-for-two-causes-not-one\" tabindex=\"-1\">Look for two causes, not one<\/h3>\n<p>A useful framing comes from the <a href=\"https:\/\/media3.bsh-group.com\/Documents\/20646126_Instruction-8D-Report-cn.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">BSH 8D instructions<\/a>. They distinguish four types of cause: technical occurrence, technical non-detection, managerial occurrence and managerial non-detection. In other words, ask why the defect was made, why your controls did not catch it, and what in your management system allowed both.<\/p>\n<p>A worked example. A bore diameter drifts out of tolerance on a CNC machine.<\/p>\n<ol>\n<li>Technical occurrence: tool wear passed the limit because the tool-change interval was set by the part count, not by measured wear.<\/li>\n<li>Technical non-detection: the in-process check sampled one part per shift, and the drift happened between samples.<\/li>\n<li>Managerial occurrence: the tool-life limit was never revised after the material supplier changed.<\/li>\n<li>Managerial non-detection: the control plan was not reviewed after the change.<\/li>\n<\/ol>\n<p>Fixing only the first leaves three gaps open.<\/p>\n<h3 id=\"tools-that-work-together\" tabindex=\"-1\">Tools that work together<\/h3>\n<ul>\n<li><strong>Pareto analysis<\/strong> shows which defect type, machine or shift accounts for most of the problem. See our guide to <a href=\"https:\/\/mestric.com\/sl\/pareto-analiza-proizvodnja\/\" target=\"_blank\" rel=\"noopener\">Pareto analysis in production<\/a>.<\/li>\n<li><strong>Ishikawa diagram<\/strong> structures the possible causes by category.<\/li>\n<li><strong>5 Whys<\/strong> drills into the most likely branch. <a href=\"https:\/\/sp-i.org\/downloads\/SPI%208D%20RCCA%20Guidebook.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">SPI notes<\/a> that the chain runs from root cause through contributing causes to the direct cause and the problem, and that it need not stop at exactly five questions. Our walkthrough of the <a href=\"https:\/\/mestric.com\/sl\/5-why-analiza\/\" target=\"_blank\" rel=\"noopener\">5 Whys with data verification<\/a> shows how to run it in a short session.<\/li>\n<\/ul>\n<p>A 2024 peer-reviewed case study from Slovakia reports that <a href=\"https:\/\/reference-global.com\/download\/article\/10.2478\/czoto-2024-0045.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">combining Pareto, Ishikawa and 5 Whys<\/a> produced more favourable outputs and a synergistic process in its investigation.<\/p>\n<h3 id=\"verify-before-you-move-on\" tabindex=\"-1\">Verify before you move on<\/h3>\n<p>Verification means you can switch the cause on and off. Run the process with the suspected cause present and the defect appears. Remove it and the defect disappears. If you cannot test it directly, compare good and bad lots on the suspected variable using recorded data. Downtime and stoppage records are often the quickest evidence; our article on <a href=\"https:\/\/mestric.com\/sl\/analiza-vzrokov-zastojev\/\" target=\"_blank\" rel=\"noopener\">downtime cause analysis<\/a> shows how to close a first root cause analysis within one shift.<\/p>\n<h2 id=\"d5-and-d6-choose-implement-and-prove-the-fix\" tabindex=\"-1\">D5 and D6: choose, implement and prove the fix<\/h2>\n<h3 id=\"d5-select-permanent-corrective-actions\" tabindex=\"-1\">D5: select permanent corrective actions<\/h3>\n<p>The SPI guidebook sets out what a sound corrective action looks like. It must address verified root and contributing causes, be practical and SMART, carry an implementation or effectiveness date, remain sustainable, avoid creating new nonconformities and be reviewed.<\/p>\n<p>Compare options by what they remove. A poka-yoke fixture that makes the wrong assembly impossible beats an extra line in the work instruction. A tool-wear-based change trigger beats a reminder to operators.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/mestric.com\/wp-content\/uploads\/2026\/11\/1794107040059_Worker-fitting-a-component-into-a-poka-yoke-fixture.jpeg\" alt=\"Worker fitting a component into a poka-yoke fixture\"><\/p>\n<h3 id=\"d6-implement-and-check-effectiveness\" tabindex=\"-1\">D6: implement and check effectiveness<\/h3>\n<p>SPI says D6 requires implementation as defined, confirmation of the process, and effectiveness measured against a baseline or prior performance. If the action is ineffective, the team returns to D4. Containment may be removed progressively, and only after effectiveness is demonstrated.<\/p>\n<p>A supplier e-learning manual recommends <a href=\"https:\/\/www.mahle.com\/media\/global\/purchasing\/supplier-portal\/8d-e-learning\/manual_8d-process_en-ex.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">two checks after implementation<\/a>: a quick provocation test, and a longer-term check such as process capability or failure analysis. Containment comes off only when the action is effective.<\/p>\n<p>A simple effectiveness record:<\/p>\n<table>\n<thead>\n<tr>\n<th>Item<\/th>\n<th>Example entry<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Baseline<\/td>\n<td>7.6% scrap on the bore operation over the previous 8 weeks<\/td>\n<\/tr>\n<tr>\n<td>Action<\/td>\n<td>Tool change triggered by measured wear<\/td>\n<\/tr>\n<tr>\n<td>Owner and due date<\/td>\n<td>Process engineer, week 47<\/td>\n<\/tr>\n<tr>\n<td>Validation method<\/td>\n<td>Capability study on 125 consecutive parts, then weekly scrap trend<\/td>\n<\/tr>\n<tr>\n<td>Result<\/td>\n<td>OK \/ Not OK<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The action, owner, due date, actual date, validation method, effective date and OK\/Not OK result are the fields that <a href=\"https:\/\/assets.danfoss.com\/documents\/latest\/402826\/AH492546037856en-000101.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">one manufacturer\u2019s 8D form<\/a> records for D5 and D6. Use the same fields and nobody has to ask what \u2018done\u2019 meant.<\/p>\n<p>If your rework rate is the main symptom, our article on <a href=\"https:\/\/mestric.com\/sl\/zmanjsanje-predelav\/\" target=\"_blank\" rel=\"noopener\">cutting rework with RCA, SPC and a pilot<\/a> gives a practical way to test a fix on one line first.<\/p>\n<h2 id=\"d7-prevent-recurrence\" tabindex=\"-1\">D7: prevent recurrence<\/h2>\n<p>D7 is the discipline most often skipped under time pressure. ASQ defines it as modifying management systems, operating systems, practices and procedures so that the problem and similar problems do not recur.<\/p>\n<p>A D7 checklist:<\/p>\n<ul>\n<li>Standardise the verified action across relevant products and processes. The Danfoss form asks you to <a href=\"https:\/\/assets.danfoss.com\/documents\/latest\/402826\/AH492546037856en-000101.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">record whether design, system or process FMEAs were updated<\/a>.<\/li>\n<li>Update the control plan, work instructions and training material.<\/li>\n<li>Look at similar products, lines and suppliers. A UK industry guide says D7 should <a href=\"https:\/\/constructioninnovationhub.org.uk\/media\/mopp5btt\/9-cpqp-8-disciplines-final.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">document lessons learned, store records in a common data environment and apply the learning across affected products<\/a>.<\/li>\n<li>Verify that the preventive action is actually in use, with an audit a few weeks later.<\/li>\n<\/ul>\n<p>The same logic applies along the whole chain, from your material suppliers to your customers. A good primer on <a href=\"https:\/\/offthegroundmarketing.com\/blog\/aerospace-manufacturing-supply-chain-basics\" target=\"_blank\" rel=\"noopener\">aerospace manufacturing supply chain basics<\/a> shows why a defect cause in one tier has to be checked across comparable parts and partners.<\/p>\n<p>When the lesson concerns complaints in general, our article on <a href=\"https:\/\/mestric.com\/sl\/zmanjsanje-reklamacij\/\" target=\"_blank\" rel=\"noopener\">cutting complaints with FMEA pilots<\/a> shows how to feed 8D findings into your FMEA.<\/p>\n<h2 id=\"d8-close-the-report-and-recognise-the-team\" tabindex=\"-1\">D8: close the report and recognise the team<\/h2>\n<p>Danfoss defines D8 as sign-off and celebration. It includes lessons learned, how results will be shared, an approval decision, and the date, function and name or signature of the approver. The Construction Innovation Hub guide adds that you should <a href=\"https:\/\/constructioninnovationhub.org.uk\/media\/mopp5btt\/9-cpqp-8-disciplines-final.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">list contributors, recognise significant contributions where appropriate and close formally<\/a>, with the customer\u2019s signature where one is required.<\/p>\n<p>Recognition is not decoration. Operators and technicians who gave honest data in D2 and D4 are the reason the next 8D is faster. Name them in the report.<\/p>\n<h2 id=\"customer-and-slovenian-context\" tabindex=\"-1\">Customer and Slovenian context<\/h2>\n<p>No general Slovenian law prescribes 8D. It is a customer and industry practice. A Slovenian plastics manufacturer, for example, reports using <a href=\"https:\/\/www.tomplast.si\/sl\/celovita-ponudba\/kakovost\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">structured 8D together with Ishikawa and 5 Why<\/a> as part of preventive process control and continual quality improvement.<\/p>\n<p>What does bind you are the requirements of each customer. Examples from published supplier manuals:<\/p>\n<ul>\n<li>One automotive customer says suppliers should <a href=\"https:\/\/suppliermanual.veoneer.biz\/en\/supplier-lifecycle\/supplier-management\/complaint-reporting-and-resolution\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">respond using 8D for disciplines 1 to 3, then report corrective actions for disciplines 4 and 5<\/a>, unless agreed otherwise, with D6 to D8 reported later according to its timing model.<\/li>\n<li>A Czech metal-parts customer requires <a href=\"https:\/\/www.pressmetal.cz\/wp-content\/uploads\/2025\/07\/DP-06.01.01-ISMM-PM-Supplier-Quality-Requirements-r8_merged.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">D3 within 24 hours, D5 within 5 working days and D8 within 20 working days<\/a>, with deliveries supervised until corrective action is resolved and each complaint considered in the PFMEA revision.<\/li>\n<\/ul>\n<p>These deadlines apply to those customers\u2019 suppliers only. Keep a table of each customer\u2019s 8D deadlines and formats where the quality team can see it, so the clock is known on the day a complaint arrives.<\/p>\n<blockquote>\n<h2 id=\"our-perspective\" tabindex=\"-1\">Our perspective<\/h2>\n<p>We see the same pattern in most plants. The 8D method itself is sound. What slows it down is data. D2 needs numbers, D4 needs evidence, and D6 needs a baseline. When these are collected by hand from paper logs, the team spends the first week reconstructing what happened.<\/p>\n<p>That is the problem Mestric\u2122 is designed to solve. Our MES connects to your machines and collects performance, downtime and quality data automatically. A team can open the shift and machine history on day one, quantify the problem, and test cause hypotheses against recorded data instead of opinions. Live KPI dashboards help show whether a corrective action is holding, which is exactly what D6 asks for.<\/p>\n<p>Our approach is simple: capture the data once, at the machine, and let every 8D, Pareto chart and 5 Whys session start from the same facts.<\/p>\n<p><em>Andra\u017e<\/em><\/p>\n<\/blockquote>\n<h2 id=\"see-8d-data-in-a-real-production-setting\" tabindex=\"-1\">See 8D data in a real production setting<\/h2>\n<p>If your 8D reports take longer than your customer allows, the bottleneck is usually evidence. Mestric\u2122 MES is designed to give production managers real-time KPIs, downtime and quality parameters from connected machines, with AI-powered optimisation tools on top. You can see it working in a real production environment through our demo presentation.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/mestric.com\/wp-content\/uploads\/2026\/09\/1771068359718_mestric.jpg\" alt=\"Mestric\"><\/p>\n<p>Learn more about <a href=\"https:\/\/mestric.com\/sl\/o-resitvi\/\" target=\"_blank\" rel=\"noopener\">Mestric\u2122 MES<\/a> and how a demo is organised for your plant.<\/p>\n<h2 id=\"faq\" tabindex=\"-1\">Pogosto zastavljena vpra\u0161anja<\/h2>\n<h3 id=\"what-is-the-difference-between-8d-and-a-simple-corrective-action\" tabindex=\"-1\">What is the difference between 8D and a simple corrective action?<\/h3>\n<p>A simple corrective action fixes a known, local cause. 8D adds a team, a quantified problem statement, containment for the customer, verified root causes, an effectiveness check and a recurrence-prevention step. Use it when the cause is unclear, several functions are involved or a customer is waiting for a formal answer.<\/p>\n<h3 id=\"how-many-people-should-be-on-an-8d-team\" tabindex=\"-1\">How many people should be on an 8D team?<\/h3>\n<p>There is no universal number. One large manufacturer\u2019s supplier guideline specifies at least 3 and at most 10 people, with a named leader and core and invited participants. What matters most is that the team covers product and process knowledge and has the authority to act.<\/p>\n<h3 id=\"is-8d-required-by-law-in-slovenia\" tabindex=\"-1\">Is 8D required by law in Slovenia?<\/h3>\n<p>No general rule requires it. 8D is usually a customer requirement, so deadlines and report formats are set by each customer\u2019s supplier quality manual. Check the manual of every customer you supply before the next complaint arrives.<\/p>\n<h3 id=\"when-can-containment-be-removed\" tabindex=\"-1\">When can containment be removed?<\/h3>\n<p>Only after the corrective action has been shown to work. Measure effectiveness against the baseline, and withdraw containment progressively. If the action proves ineffective, return to D4 and re-examine the root cause.<\/p>\n<h2 id=\"sources\" tabindex=\"-1\">Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/asq.org\/quality-resources\/eight-disciplines-8d\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ASQ: What is 8D? Eight Disciplines Problem Solving Process<\/a><\/li>\n<li><a href=\"https:\/\/support.minitab.com\/en-us\/engage\/help-and-how-to\/tools\/forms\/types-of-forms\/process-improvement\/8d-methodology\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Minitab Engage: 8D Methodology<\/a><\/li>\n<li><a href=\"https:\/\/www.vestas.com\/content\/dam\/vestas-com\/global\/en\/about\/partnering\/documents\/8D%20supplier%20guideline.pdf.coredownload.inline.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Vestas: 8D supplier guideline<\/a><\/li>\n<li><a href=\"https:\/\/suppliermanual.veoneer.biz\/sites\/veoneer-portal\/files\/SupplierDocumentLibrary\/SQPS\/SQPS-063.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Veoneer: Supplier Quality Process Specification<\/a><\/li>\n<li><a href=\"https:\/\/sp-i.org\/downloads\/SPI%208D%20RCCA%20Guidebook.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">SPI: 8D RCCA Problem Solving Guidebook<\/a><\/li>\n<li><a href=\"https:\/\/media3.bsh-group.com\/Documents\/20646126_Instruction-8D-Report-cn.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">BSH: 8D-Report instruction<\/a><\/li>\n<li><a href=\"https:\/\/reference-global.com\/download\/article\/10.2478\/czoto-2024-0045.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Process improvement using selected quality management tools (2024)<\/a><\/li>\n<li><a href=\"https:\/\/www.mahle.com\/media\/global\/purchasing\/supplier-portal\/8d-e-learning\/manual_8d-process_en-ex.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Mahle: 8D process manual<\/a><\/li>\n<li><a href=\"https:\/\/assets.danfoss.com\/documents\/latest\/402826\/AH492546037856en-000101.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Danfoss: 8D Problem Solving Documentation<\/a><\/li>\n<li><a href=\"https:\/\/constructioninnovationhub.org.uk\/media\/mopp5btt\/9-cpqp-8-disciplines-final.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Construction Innovation Hub: Toolset Guideline 9<\/a><\/li>\n<li><a href=\"https:\/\/www.tomplast.si\/sl\/celovita-ponudba\/kakovost\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Tomplast: Kakovost podjetja<\/a><\/li>\n<li><a href=\"https:\/\/suppliermanual.veoneer.biz\/en\/supplier-lifecycle\/supplier-management\/complaint-reporting-and-resolution\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Veoneer: Complaint Reporting and Resolution<\/a><\/li>\n<li><a href=\"https:\/\/www.pressmetal.cz\/wp-content\/uploads\/2025\/07\/DP-06.01.01-ISMM-PM-Supplier-Quality-Requirements-r8_merged.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">PressMetal: Supplier Quality Requirements<\/a><\/li>\n<\/ul>\n<h2 id=\"recommended\" tabindex=\"-1\">Priporo\u010deno<\/h2>\n<ul>\n<li><a href=\"https:\/\/mestric.com\/sl\/obvladovanje-neskladnosti\/\" target=\"_blank\" rel=\"noopener\">Reduce Defect Recurrence in 90 Days With Nonconformity Management<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/sl\/meje-nadzora-spc\/\" target=\"_blank\" rel=\"noopener\">SPC control limits: how to set, read and review them<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/sl\/upravljanje-reklamacij-v-proizvodnji\/\" target=\"_blank\" rel=\"noopener\">Manufacturing Complaints: Use MES Data to Cut Issues in 30 to 90 Days<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/sl\/upravljanje-zastojev-v-realnem-casu\/\" target=\"_blank\" rel=\"noopener\">Real-time downtime management in manufacturing<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>How to manage a non-conformity with the 8D method: the disciplines D0 to D8, who to put on the team, how to contain, verify causes and close the report.<\/p>","protected":false},"author":1,"featured_media":1780,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1779","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-learn"],"acf":[],"_links":{"self":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1779","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/comments?post=1779"}],"version-history":[{"count":1,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1779\/revisions"}],"predecessor-version":[{"id":1782,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1779\/revisions\/1782"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media\/1780"}],"wp:attachment":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media?parent=1779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/categories?post=1779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/tags?post=1779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}