{"id":9393,"date":"2024-10-31T12:37:34","date_gmt":"2024-10-31T12:37:34","guid":{"rendered":"https:\/\/amtivo.com\/us\/?post_type=resources-filter&#038;p=9393"},"modified":"2025-10-24T13:59:31","modified_gmt":"2025-10-24T12:59:31","slug":"root-cause-analysis-and-systemic-corrective-actions","status":"publish","type":"resources-filter","link":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/","title":{"rendered":"Root Cause Analysis and Systemic Corrective Actions"},"content":{"rendered":"<p><strong>All ISO-based standards require defined steps to rectify nonconformances, including the following:<\/strong><\/p>\r\n<ul>\r\n\t<li>Containment, interim actions and related activities necessary for control of nonconforming outputs<\/li>\r\n\t<li>Root cause analysis, methodology used, analysis and results<\/li>\r\n\t<li>Implementation of systemic corrective actions, including consideration of the impact on similar processes and products<\/li>\r\n\t<li>Verification of the effectiveness of implemented corrective actions<\/li>\r\n\t<li>Reviewing and, where necessary, updating the appropriate documented information (e.g. PFMEA, control plan, work instructions, procedures, etc.)<\/li>\r\n<\/ul>\r\n<h2>Definitions<\/h2>\r\n<p>Here are some important definitions:<\/p>\r\n<ul>\r\n\t<li><strong>Correction:<\/strong> defined as \u201cAction to eliminate a detected nonconformity\u201d<\/li>\r\n\t<li><strong>Corrective Action:<\/strong> defined as \u201cAction to eliminate the systemic cause of a detected nonconformity\u201d<\/li>\r\n<\/ul>\r\n<h2>Root Cause<\/h2>\r\n<p>Root cause analysis is a logic-based methodology to determine what, how and why an event or failure happened.<\/p>\r\n<p>Effective root cause should:<\/p>\r\n<ul>\r\n\t<li>Identify the specific underlying situations or events<\/li>\r\n\t<li>Something(s) that can be reasonably identified<\/li>\r\n\t<li>Be fixable by Top Management<\/li>\r\n\t<li>Identify something that can be prevented at a systemic level.<\/li>\r\n<\/ul>\r\n<h2>Nonconformance Statements<\/h2>\r\n<p>When we write a nonconformance, identifying the process that failed within the system helps drive efforts towards systemic analysis and actions.<\/p>\r\n<p>If the nonconformance isn\u2019t geared towards the process, corrective actions may not be systemic in nature.<\/p>\r\n<p>Clear nonconformance statements are the first step.<\/p>\r\n<p>Citing the specific evidence found during the audit doesn\u2019t typically belong in the nonconformance statement; list that under the evidence.<\/p>\r\n<h2>Three Distinct Parts of an NC<\/h2>\r\n<p>Let\u2019s look at a couple of examples to show the three distinct parts of a nonconformance:<\/p>\r\n<ul>\r\n\t<li>Nonconformance Statement<\/li>\r\n\t<li>Requirement<\/li>\r\n\t<li>Evidence<\/li>\r\n<\/ul>\r\n<p>Here are some Nonconformance Statement examples that could be reworded:<\/p>\r\n<p><strong>Example 1:<\/strong> Work instructions #48A, #56C and #93F are all missing information.<\/p>\r\n<p><em><strong>Better:<\/strong> The process to maintain work instructions is not effective.<\/em><\/p>\r\n<p><strong>Example 2:<\/strong> Preventive maintenance records are missing for Machine #582.<\/p>\r\n<p><em><strong>Better:<\/strong> The maintenance process is not entirely effective.<\/em><\/p>\r\n<p><strong>Example 3:<\/strong> The control plan and router for PN 23-5901485 have different inspection frequencies for measuring O.D. grind.<\/p>\r\n<p><em><strong>Better:<\/strong> The quality planning process is not effective in all areas.<\/em><\/p>\r\n<p><strong>Nonconformance Statement:<\/strong> The maintenance process is not entirely effective.<\/p>\r\n<p><strong>Requirement:<\/strong> IATF 8.5.1.5, The organization shall develop, implement and maintain a documented total production maintenance system. At a minimum, the system shall include the following\u2026h) use of preventive maintenance methods.<\/p>\r\n<p><strong>Evidence:<\/strong> Preventive maintenance records are missing for Machine #582.<\/p>\r\n<p><strong>Nonconformance Statement:<\/strong> The quality planning process is not effective in all areas.<\/p>\r\n<p><strong>Requirement:<\/strong> ISO 9001, 8.5.1c: The organization shall implement production and service under controlled conditions. Controlled conditions shall include, as applicable: c) the implementation of monitoring and measurement activities and appropriate states to verify that criteria for control of processes or outputs&#8230; have been met.<\/p>\r\n<p><strong>Evidence:<\/strong> The control plan and router for PN 23-5901485 have different inspection frequencies for O.D. grind.<\/p>\r\n<h2>Process<\/h2>\r\n<p>Amtivo does not dictate what methodology our customers use; we do however, require them to submit the results of their analysis along with the finalized root cause(s).<\/p>\r\n<p>This should be submitted along with the completed F-3000 NCR form, or their own corrective action form that contains the same information.<\/p>\r\n<p>F-3000 Nonconformance Report<\/p>\r\n<p>Customers may utilize their own corrective action format, as long as it contains all four required fields on page 2 of the ASR form F-3000:<\/p>\r\n<ul>\r\n\t<li>Correction<\/li>\r\n\t<li>Root cause analysis<\/li>\r\n\t<li>Corrective action<\/li>\r\n\t<li>Verification<\/li>\r\n<\/ul>\r\n<p>It\u2019s helpful if they reference their form on our F-3000.<\/p>\r\n<p>Corrective action submissions for all audits (except Stage 1) against all standards must include the following:<\/p>\r\n<ul>\r\n\t<li>F-3000 Nonconformance Report, or the customers equivalent<\/li>\r\n\t<li>Evidence of correction<\/li>\r\n\t<li>Root cause methodology and results, with a final root cause statement<\/li>\r\n\t<li>Corrective action plan that addresses the identified root cause<\/li>\r\n\t<li>Effectiveness verification showing the root cause has been eliminated or mitigated<\/li>\r\n<\/ul>\r\n<p>Let\u2019s review each of these items in more detail.<\/p>\r\n<h2>Correction<\/h2>\r\n<p>Consider correction the \u201cband-aid\u201d or short term action to immediately fix what was identified.<\/p>\r\n<p>Customers must submit evidence of correction when a nonconformance is issued.<\/p>\r\n<ul>\r\n\t<li>For example, if the auditor writes a nonconformance because there\u2019s a vital step missing from a work instruction, the correction would be to update the work instruction.<\/li>\r\n\t<li>If the auditor identifies that there\u2019s a mismatch between two documents, the customer would update both documents with the correct information.<\/li>\r\n<\/ul>\r\n<p>Depending on the severity of the nonconformance, correction may also require the containment of product in-house, sorting \/ inspection, rework \/ repair and notification to the customer.<\/p>\r\n<h2>Root Cause Analysis<\/h2>\r\n<p>Many companies shine when determining the root cause for a defective part but struggle with performing it for a process.<\/p>\r\n<p>Solid root cause analysis can be painful as the truth becomes apparent. No one wants to admit there was a failure in their system, or there was something they \u201cforgot\u201d as part of the planning process.<\/p>\r\n<p>There are several methods available to help identify what went wrong, why it occurred and\/or what allowed the situation to exist.<\/p>\r\n<p>For all standards, ASR requires the customers to submit their root cause analysis, methodology and results (See F-3000 NCR Form).<\/p>\r\n<p><strong>Root Cause Analysis<\/strong><\/p>\r\n<p>This is the most important step in the corrective action process because when done properly, it identifies the gap in the system to prevent recurrence.<\/p>\r\n<p>Root cause analysis and methodologies might include (but are not limited to):<\/p>\r\n<ul>\r\n\t<li>5-Why<\/li>\r\n\t<li>Fishbone Diagram<\/li>\r\n\t<li>Is\/Is Not<\/li>\r\n\t<li>Brainstorming<\/li>\r\n\t<li>Pareto chart<\/li>\r\n\t<li>Flowcharting<\/li>\r\n<\/ul>\r\n<p>Root Cause Analysis should answer the questions \u201cwhy,\u201d \u201chow\u201d and \u201cwhat\u201d<\/p>\r\n<ul>\r\n\t<li>Why did \/ didn\u2019t that happen?<\/li>\r\n\t<li>How did that happen?<\/li>\r\n\t<li>Why wasn\u2019t it detected?<\/li>\r\n\t<li>What would stop it from happening again?<\/li>\r\n<\/ul>\r\n<p>Going back to an earlier example of a work instruction missing a vital step, review the following examples of root cause and see which ones you think are valid.<\/p>\r\n<p>Nonconformance Statement, written at the system level: The process to maintain work instructions is not effective in all areas.<\/p>\r\n<p><strong>Possible Root Causes:<\/strong><\/p>\r\n<ol>\r\n\t<li>The work instruction didn\u2019t contain all the steps.<\/li>\r\n\t<li>The employee responsible didn\u2019t understand the requirements.<\/li>\r\n\t<li>The operators didn\u2019t tell us it was wrong.<\/li>\r\n\t<li>The prior process engineer wrote it but he has since been fired.<\/li>\r\n\t<li>We forgot to include it.<\/li>\r\n<\/ol>\r\n<p>Did you think any of these were valid? Did any of these statements address the failure at a systemic level?<\/p>\r\n<p>The answer is no!<\/p>\r\n<p>Let\u2019s review each one with a bit more discussion.<\/p>\r\n<p><strong>1. The work instruction didn\u2019t contain all the steps.<\/strong><\/p>\r\n<p>This is merely a restatement of the nonconformance statement.<\/p>\r\n<p><strong>2. The employee responsible didn\u2019t understand the requirements.<\/strong><\/p>\r\n<p>This might be a starting point, but the next question should be \u201cwhy\u201d \u2013 why didn\u2019t the employee understand the requirements? This may lead to additional questions related to training \/ training effectiveness, documentation of job responsibilities and definition of competency requirements.<\/p>\r\n<p><strong>3. The operators didn\u2019t tell us it was wrong.<\/strong><\/p>\r\n<p>Blaming the employee is invalid 99.9% of the time, unless there is evidence of blatant disregard or deliberate tampering.<\/p>\r\n<p><strong>4. The prior process engineer wrote it but he has since been fired.<\/strong><\/p>\r\n<p>Blaming an individual doesn\u2019t identify the systemic gap.<\/p>\r\n<p><strong>5. We forgot to include it.<\/strong><\/p>\r\n<p>On a very rare occasion, this might be a valid statement, but only if there is evidence that everything else was reviewed and rejected as a potential contributor to the situation.<\/p>\r\n<p>Many customers us the 5-Why methodology to analyze potential gaps in a process.<\/p>\r\n<p>This method starts with the nonconformance statement, then keeps asking \u201cwhy\u201d with each answer until the systemic failure is identified.<\/p>\r\n<p>Let\u2019s look at a few more examples of unacceptable root cause statements and additional questions that could be asked as starting points for a 5-Why:<\/p>\r\n<p><strong>The machine malfunctioned.<\/strong><\/p>\r\n<p>This doesn\u2019t answer the question of \u201cwhy\u201d the equipment malfunctioned. What caused the machine to stop working correctly? Was it a preventable situation? Has the machine ever malfunctioned that way before? If so, why?<\/p>\r\n<p><strong>Our previous auditor didn\u2019t find it.<\/strong><\/p>\r\n<p>Blaming the auditor for not identifying doesn\u2019t answer the questions of \u201cwhy\u201d the situation existed!<\/p>\r\n<p><strong>It was done by a new employee<\/strong><\/p>\r\n<p>Was the employee trained? If not, that\u2019s a good starting point: Why wasn\u2019t the employee trained? If so, was that training verified as effective? If not, there\u2019s another starting point: Why wasn\u2019t the effectiveness of training verified?<\/p>\r\n<p>Let\u2019s look at a simple example of a 5-Why analysis for that nonconformance statement: The process to maintain work instructions is not effective in all areas.<\/p>\r\n<p><strong>Why?<\/strong> Posted work instruction is missing a critical step.<\/p>\r\n<p><strong>Why?<\/strong> Step was added to the process as a result of a continual improvement.<\/p>\r\n<p><strong>Why wasn\u2019t the work instruction updated?<\/strong> The quality engineer implemented the change using an approved internal deviation. When the deviation expired, the work instruction was never updated to permanently implement the change.<\/p>\r\n<p><strong>Why wasn\u2019t the work instruction updated?<\/strong> No formal requirement in the change control process to trigger a review for possible document updates from approved internal deviations.<\/p>\r\n<p>Now we have a root cause that is actionable at the system level!<\/p>\r\n<h2>Corrective Action<\/h2>\r\n<p>The purpose of corrective action is to prevent recurrence by updating the system in some way.<\/p>\r\n<p>It\u2019s uncommon for the corrective action to be identical to the correction taken to fix the immediate issue.<\/p>\r\n<p>In our work instruction example, we identified the following root cause: No formal requirement in the change control process to review for possible document updates from approved internal deviations.<\/p>\r\n<p>This sounds like updates are required to their change control process.<\/p>\r\n<p>This might include a procedure, process flow, checklist, turtle, work instructions, job responsibilities or other system-level documents to effectively implement that change.<\/p>\r\n<p>When reviewing corrective action plans and evidence of implementation, be sure that the actions actually address the identified root cause.<\/p>\r\n<p>For example, if the root cause states: \u201cThere is no formal process to validate tools\u201d the corrective actions should include something about tool validation, e.g. a new or updated Buy-Off procedure, a change to the APQP process or Launch form, something like that.<\/p>\r\n<p><strong>Corrective Action Impact<\/strong><\/p>\r\n<p>The customer\u2019s corrective action should include an assessment of similar parts and\/or processes to ensure that the same symptom that was identified as part of the original nonconformance doesn\u2019t exist elsewhere in the system.<\/p>\r\n<p>Some people call this a \u201cread\u2013across\u201d<\/p>\r\n<h2>Verification<\/h2>\r\n<p>Once the customer has implemented their systemic action plans, they need to verify the effectiveness of their actions.<\/p>\r\n<p>This doesn\u2019t mean verification that the actions were taken.<\/p>\r\n<p>This means they have monitored the situation to determine that the actions they took have truly prevented recurrence.<\/p>\r\n<p>This might involve a special internal audit, an update to their layered process audits or monitoring of data that demonstrates the system changes will prevent the situation from occurring again.<\/p>\r\n<p>In some cases, the customer may realize their actions were not far reaching enough and revise their action plans.<\/p>\r\n<h2>Reviewing Corrective Actions<\/h2>\r\n<p>Once the customer has submitted their corrective actions, the auditor will evaluate the following:<\/p>\r\n<ul>\r\n\t<li>Is there evidence of correction? Was correction applied to similar situations?<\/li>\r\n\t<li>Does the root cause apply to the system and not just the specific evidence cited?<\/li>\r\n\t<li>Do action plans address the systemic root cause?<\/li>\r\n\t<li>Does the submitted evidence show an update to the system?<\/li>\r\n\t<li>Do the system updates consider similar parts or processes when applicable?<\/li>\r\n\t<li>Is there a solid verification plan for effectiveness and not just implementation?<\/li>\r\n<\/ul>\r\n<p>&nbsp;<\/p>\r\n<p>If you cannot answer yes to all these questions, push back and ask for more information.<\/p>\r\n<h2>In Summary<\/h2>\r\n<p>By writing clear nonconformance statements supported by a documented requirement and objective evidence, we identify opportunities to strengthen their management systems.<\/p>\r\n<p>When customers perform valid root cause analysis, they identify the systemic gap in their management system that allowed a nonconforming situation to exist. Performing corrective actions to close that gap will prevent a recurrence of that situation.<\/p>\r\n<p>Verification ensures that the corrective action process is executed robustly.<\/p>","protected":false},"excerpt":{"rendered":"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.","protected":false},"author":24,"featured_media":9396,"template":"","resource":[23],"resource-tag":[36],"class_list":["post-9393","resources-filter","type-resources-filter","status-publish","has-post-thumbnail","hentry","resource-insights","resource-tag-iso"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Root Cause Analysis and Systemic Corrective Actions - Amtivo<\/title>\n<meta name=\"description\" content=\"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Root Cause Analysis and Systemic Corrective Actions\" \/>\n<meta property=\"og:description\" content=\"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/\" \/>\n<meta property=\"og:site_name\" content=\"Amtivo US\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-24T12:59:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2024\/10\/root-cause-analysis-min.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"802\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2025\/04\/testimonialImage-placeholder.jpg\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minutes\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Root Cause Analysis and Systemic Corrective Actions - Amtivo","description":"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/","og_locale":"en_US","og_type":"article","og_title":"Root Cause Analysis and Systemic Corrective Actions","og_description":"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.","og_url":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/","og_site_name":"Amtivo US","article_modified_time":"2025-10-24T12:59:31+00:00","og_image":[{"width":1200,"height":802,"url":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2024\/10\/root-cause-analysis-min.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_image":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2025\/04\/testimonialImage-placeholder.jpg","twitter_misc":{"Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/","url":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/","name":"Root Cause Analysis and Systemic Corrective Actions - Amtivo","isPartOf":{"@id":"https:\/\/amtivo.com\/us\/#website"},"primaryImageOfPage":{"@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/#primaryimage"},"image":{"@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/#primaryimage"},"thumbnailUrl":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2024\/10\/root-cause-analysis-min.jpg","datePublished":"2024-10-31T12:37:34+00:00","dateModified":"2025-10-24T12:59:31+00:00","description":"Discover how to use root cause analysis and systemic corrective actions to help ensure compliance with global standards.","breadcrumb":{"@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/#primaryimage","url":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2024\/10\/root-cause-analysis-min.jpg","contentUrl":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2024\/10\/root-cause-analysis-min.jpg","width":1200,"height":802,"caption":"root cause analysis"},{"@type":"BreadcrumbList","@id":"https:\/\/amtivo.com\/us\/resources\/insights\/root-cause-analysis-and-systemic-corrective-actions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/amtivo.com\/us\/"},{"@type":"ListItem","position":2,"name":"Resources","item":"https:\/\/amtivo.com\/us\/all-resources\/"},{"@type":"ListItem","position":3,"name":"Insights","item":"https:\/\/amtivo.com\/us\/resources\/insights\/"},{"@type":"ListItem","position":4,"name":"Root Cause Analysis and Systemic Corrective Actions"}]},{"@type":"WebSite","@id":"https:\/\/amtivo.com\/us\/#website","url":"https:\/\/amtivo.com\/us\/","name":"Amtivo","description":"","publisher":{"@id":"https:\/\/amtivo.com\/us\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/amtivo.com\/us\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/amtivo.com\/us\/#organization","name":"Amtivo","url":"https:\/\/amtivo.com\/us\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/amtivo.com\/us\/#\/schema\/logo\/image\/","url":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2025\/09\/cropped-Amtivo-US-Registered-logo-XXL_Cobalt-Logo-Stacked-copy-2.png","contentUrl":"https:\/\/amtivo.com\/us\/wp-content\/uploads\/sites\/18\/2025\/09\/cropped-Amtivo-US-Registered-logo-XXL_Cobalt-Logo-Stacked-copy-2.png","width":2557,"height":2121,"caption":"Amtivo"},"image":{"@id":"https:\/\/amtivo.com\/us\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resources-filter\/9393","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resources-filter"}],"about":[{"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/types\/resources-filter"}],"author":[{"embeddable":true,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/users\/24"}],"version-history":[{"count":1,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resources-filter\/9393\/revisions"}],"predecessor-version":[{"id":12663,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resources-filter\/9393\/revisions\/12663"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/media\/9396"}],"wp:attachment":[{"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/media?parent=9393"}],"wp:term":[{"taxonomy":"resource","embeddable":true,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resource?post=9393"},{"taxonomy":"resource-tag","embeddable":true,"href":"https:\/\/amtivo.com\/us\/wp-json\/wp\/v2\/resource-tag?post=9393"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}