Texas Quality Assurance – Quality Management Simplified

Managing a quality management system involves more than maintaining procedures and preparing for audits. Quality managers regularly face decisions about corrective actions, training records, supplier approval, and the level of documentation needed to maintain effective controls. In Episode 5, Kyle Chambers and Caleb Adcock address seven common QMS questions that arise in their work with clients. Quality professionals regularly face questions about corrective actions, training documentation, supplier approvals, and maintaining effective processes. In Episode 5, Kyle Chambers and Caleb Adcock address seven common QMS questions they frequently receive from clients. The discussion begins with two related concerns: Does every nonconformity need a CAPA? and Can one CAPA address multiple audit findings? Not every nonconformity requires formal corrective action, as isolated issues may only require correction and documentation. However, recurring problems or identifiable trends may justify a more thorough investigation. Multiple findings can also be addressed through a single CAPA when they share a common root cause, provided the corrective action addresses the underlying problem and includes verification of its effectiveness. The conversation then turns to employee competence and purchasing controls, beginning with Is a signed training sheet enough? A training record may demonstrate attendance or awareness, but technical responsibilities often require additional evidence of competence through testing, observation, or practical demonstrations. The appropriate documentation depends on the training's purpose and the employee's responsibilities. This distinction between documented approval and demonstrated capability also applies to Does an approved supplier mean an approved purchase? Supplier approval should establish the specific products or services a supplier is authorized to provide, rather than automatically approving every potential purchase. Transactions outside that scope may require additional evaluation, conditional approval, or documented exceptions to maintain appropriate purchasing controls. Another common question involves document control: We revised the procedure. Have we fixed the problem? Updating a procedure does not necessarily resolve the original issue, particularly when affected employees have not been informed of the change or trained on their revised responsibilities. Kyle and Caleb explain why organizations should consider the impact of procedural changes, communicate revisions effectively, and confirm that the updated process is understood and implemented. Depending on the circumstances, significant changes may also require additional controls, such as formal corrective action or management of change. The discussion then addresses What should management review actually produce? Rather than serving as a meeting held solely to satisfy audit requirements, management reviews should result in documented decisions, assigned responsibilities, actionable improvements, and follow-up on previously established objectives. The final question, What should the quality manager do between audits?, brings these topics together by emphasizing ongoing oversight rather than periodic preparation. Kyle and Caleb recommend maintaining a regular schedule for reviewing nonconformities, corrective actions, training records, calibration, maintenance, and supplier performance. They also highlight the importance of spending time on the production floor, communicating with employees, and identifying concerns before they develop into larger problems. Throughout the episode, the central message remains consistent: an effective quality management system should support daily operations without creating unnecessary administrative work. By maintaining practical controls, meaningful documentation, and consistent oversight, organizations can improve their processes throughout the year rather than waiting until the next audit.

A revised procedure can show that a team completed a corrective action, but it cannot prove the problem will stay fixed. In Episode 4, Kyle Chambers and Caleb Adcock examine that gap through corrective action effectiveness. Revisiting the Rivian recall discussed in the previous episode, they consider what should happen after a manufacturer changes an automated check. The central question is whether that change addresses the cause and whether similar equipment could share the same weakness. That broader review starts with root cause analysis that looks beyond the person who made the mistake. Kyle and Caleb caution against treating retraining as the automatic answer or creating a separate exception for every customer problem. Instead, they recommend examining the process and reviewing similar equipment or programs for the same failure mode. Someone outside the project can help challenge assumptions that the people closest to the work may overlook. Once the team implements a change, verification of effectiveness requires evidence from subsequent work. The hosts describe keeping corrective actions in a complete-pending-verification status while comparable jobs pass through the revised process. Smaller shops may review several relevant jobs, while larger operations may have enough data to compare defect rates. An internal or external audit can also provide an independent review, particularly when the change concerns training or management processes. Those follow-up checks extend to the inspections themselves, including automated checks. Observing an inspector and independently checking the same work can reveal gaps that paperwork misses. Kyle and Caleb recommend applying the same scrutiny to automation rather than assuming repeatability guarantees a reliable result. Their approach to corrective action effectiveness is to implement the fix promptly, then allow evidence to support closure.

A failed calibration check can turn a routine inspection into a much bigger problem. Once a measuring tool proves unreliable, the next step is figuring out which parts it checked and whether any have already shipped. In Episode 3, Kyle Chambers and Caleb Adcock use a reported Rivian recall to explore how traceability helps manufacturers identify affected products and respond to quality concerns. Although they don't know the details of Rivian's internal controls, the example leads to a practical question: could another shop narrow down a similar problem? The discussion connects that question to a simple practice: recording the specific tool used for each inspection. When inspection records link a device to a job, the team has a clearer starting point for investigating a failed tool. Daily spot checks can provide another useful reference by helping establish when the device last worked correctly. Together, those practices can make it easier to identify potentially affected work and assess what needs further inspection. Kyle and Caleb also explain why effective controls depend on people staying involved in the process. Spending time on the shop floor gives quality managers opportunities to learn from operators, observe inspections, and notice gaps that routine work can make easy to overlook. That same curiosity matters when reviewing automation, because a system may repeat its programmed process without recognizing a blind spot. The conversation considers where additional verification can help and why another perspective may reveal something the original check missed. Throughout the episode, the focus stays on choosing controls that make sense for the product and the consequences of failure. That includes involving engineering when reviewing measurement errors and tolerances, as well as creating a workplace where people can raise concerns without hesitation. Kyle and Caleb bring those ideas back to a straightforward priority: get it right, get it on time, then get it on budget.

Using AI for Compliance and Audit Readiness Kyle recently saw an ad for an AI compliance tool that promised to assess an organization’s ISO 9001:2026 readiness. It caught our attention. A tool that reviews documentation and identifies possible gaps could save quality professionals considerable time. Caleb dug into the idea. The more we explored it, the more we questioned how much of the assessment depended on AI’s own interpretations. Having someone approve the final result sounded reassuring, but it raised another question: how thoroughly would that person verify the work? That distinction matters when an assessment could influence your understanding of audit readiness. We strongly recommend having an experienced quality manager review the results, often with support from a skilled, certified auditor. The review needs someone who understands the requirements, your evidence, and how your business actually operates. Where AI Compliance Tools Add Value We love AI. Saving time and energy is central to our company mission, and AI can help with both. It can organize information, research a topic, compare documents, and prepare drafts faster than we could do those tasks manually. We think of it as having a team of efficient entry-level researchers and writers. They can produce useful work quickly, but their work still needs direction and review from someone with experience. That is the role we recommend for AI compliance tools: assistance with research, review, and writing. AI-assisted compliance can help you investigate possible gaps and prepare documentation. We would not treat its output as a final determination that your quality system conforms to its requirements. Document Approval Needs a Human Touch A procedure can read well and still describe something your employees cannot reasonably do. It might assign responsibility to the wrong person or overlook an important detail about your process. We see similar problems with human-written drafts. A consultant can prepare a procedure, but your team needs to check whether it fits the business. Document approval should represent that review. Skimming a draft and clicking approve does not establish that its instructions are correct or workable. The same applies when approving an AI-generated assessment. An experienced reviewer brings context that may never appear in the uploaded documents. That human touch helps connect what the paperwork says with what actually happens. AI Hallucinations Require Careful Checking Our concern with AI hallucinations includes errors hidden inside otherwise reasonable text. One unsupported sentence can change a procedure’s meaning without making the whole document look obviously wrong. If later work builds on that sentence, the mistake can spread. A confident explanation may make it harder to notice. That is why review needs to go beyond presentation. Check the evidence, assumptions, and conclusions. Include that checking time when deciding whether the tool actually reduces your workload. AI vs Automation: Different Expectations AI vs automation is another important distinction. A predefined workflow that generates and emails a PDF follows planned logic. An AI assessment adds interpretation that someone needs to evaluate. We prefer giving AI manageable tasks with results we can check. In software development, that means testing a requested function and checking that unrelated functions still work. The same principle applies to compliance work: define the task, review the output, and keep an experienced person responsible for the decision. AI compliance tools can save time and energy. Their greatest value comes when capable people use them to support their work—and bring the experience needed to verify the results. The post Episode 2: Using AI for Compliance and Audit Readiness #QualityMatters2.0 appeared first on Texas Quality Assurance - Quality Management Simplified.

AI can save you time, but what happens when you can't explain how it reached an answer? That's a problem in any quality system. It's also where we think the AI hype needs a little reality check. In Episode 1, Kyle Chambers and Caleb Adcock return after a long break, share an update on the TQA app, and get into where AI may actually help quality teams. The biggest theme is simple: use AI as a tool, not an authority. If a report, calculation, or recommendation matters, you still need to verify the source. You should also understand how the system produced the result. The same applies to audits and inspections. An experienced auditor notices context, inconsistencies, and shop-floor details that a yes-or-no system can miss. There's also a people side to this. Automating every easy task may save time today. But it can remove work that helps newer employees build judgment and experience. We also discuss customer-data separation, software permissions, and why AI should start with narrow, useful jobs before it reaches critical decisions. AI is moving fast, but quality still depends on traceability, experience, and someone willing to check the work.

In the latest mini-episode of Caleb's Corner, we dove into a crucial topic every quality professional faces: When do you keep tweaking your system, and when is it time for a total overhaul? This fundamental concept, often described as Iterative Design vs. Radical Redesign, isn’t just for software developers; it's highly applicable across all areas of Quality Management Systems (QMS). The Heart of Iterative Design As the Quality Software Manager at Texas Quality Assurance (TQA), much of my work revolves around our TQA Cloud platform, which helps clients manage everything from calibration and maintenance to employee training and document control. In developing the next version of our app—which will offer a smoother, more integrated experience—I face constant decisions on whether to improve existing features incrementally or scrap and rebuild entire modules. Iterative Design is the practice of making small, controlled adjustments to improve a system continuously. This approach: * Allows for measurable, incremental improvements * Provides lower risk since changes are smaller and easier to reverse * Helps maintain system stability while adapting to new requirements * Encourages continuous improvement, a core principle of ISO 9001 and other quality standards In many cases, iterative design is the safest and most effective way to evolve a QMS software platform or any quality management process. The Necessity of Radical Redesign However, there are times when no amount of tweaking will get you where you need to be. This is where Radical Redesign becomes necessary. Sometimes, your approach is fundamentally flawed for the goals you're trying to achieve. Signs it's time for a full rebuild include: * Legacy systems that cannot integrate with modern tools * Process flows that no longer reflect your organization's actual operations * Compliance gaps that cannot be closed with minor adjustments * User frustration due to convoluted or outdated interfaces In these cases, starting fresh allows you to rethink your processes, design for today's needs, and set a stronger foundation for future growth. Balancing the Two in Quality Management In the world of quality management consulting, we frequently help clients evaluate their systems through this very lens. Whether we're advising on ISO 9001 compliance, API Q1 certification, or customizing TQA Cloud for a new client, the same question applies: Is this a tweak or a rebuild? By regularly assessing your QMS and leveraging both iterative design and radical redesign when appropriate, you can ensure your systems are not only compliant but also practical, scalable, and truly supportive of your business objectives. Let Texas Quality Assurance Help You Decide Struggling to determine whether your quality system needs a few small adjustments or a complete redesign? Texas Quality Assurance can help. With decades of experience in quality management systems, compliance, and software solutions, we guide companies just like yours through these critical decisions every day. #QualityMatters, #CalebsCorner, #QualityManagement, #QMS, #ISO9001, #APIQ1, #ContinuousImprovement, #IterativeDesign, #RadicalRedesign, #TexasQualityAssurance, #TQACloud Call us today at (281) 756-7316 or email [email protected] to schedule a consultation.

When you think of innovation in manufacturing, do you picture automation, robotics, or AI-driven workflows? In this episode, Cy Rankin challenges that notion by sharing a counterintuitive truth: sometimes, the most innovative thing you can do is make your business boring—in all the right ways. Cy leads Texas Stress, a Houston-based company that specializes in welding stress relief services. He was recently invited to speak at the American Welding Society Convention in The Woodlands. His presentation, rather than dazzling with futuristic trends, focused on one core principle: master the basics and execute consistently. Cy argues that the foundation of true innovation lies in business fundamentals: things like repeatable processes, clear responsibilities, reliable timelines, and straightforward expectations. These “boring” elements are often dismissed, but they’re exactly what allow a company to scale, maintain customer satisfaction, and stay compliant with standards like ISO 9001. Whether you’re a quality professional, an operations leader, or someone who just wants your business to run better, this episode is packed with real-world insight. Key Takeaways 1. Make Business Predictable Cy explains that predictability is a feature, not a flaw. By keeping operations consistent and minimizing chaos, you earn trust from your team and clients alike. 2. Quality Management Is Not Paperwork The episode highlights how quality management systems aren’t about red tape—they’re about results. Proper documentation and training are tools to build confidence, reduce errors, and ensure long-term reliability. 3. Speak the Language of Simplicity Cy’s approach to presenting at a major industry event? Keep it simple. Speak clearly. Focus on what people actually do, not just what looks good in a PowerPoint. This applies equally to leadership and quality strategy. 4. Innovation Doesn’t Mean Chaos While innovation often gets tied to disruption, Cy reminds us that innovation can also mean refining what already works—especially in industries like welding where reliability is king. About the Guest Cy Rankin is a leader at Texas Stress, a company known for its expertise in heat treatment and welding stress relief. With deep industry knowledge and a passion for practical quality solutions, Cy bridges the gap between shop floor execution and executive vision. Resources & Mentions * Texas Stress Official Site * American Welding Society * AWS Summit on LinkedIn * AWS Summit Speakers

Understanding the Climate Change Amendment in ISO 9001 In Episode 216 of #QualityMatters, we explore the climate change amendment, a concise yet impactful update to ISO 9001 that compels organizations to identify and address climate-related risks within their quality management systems. This climate change amendment—just two lines of text—requires companies to determine whether climate change is an issue and to integrate relevant controls into their existing processes. Why ISO 9001 Amendment Matters Now ISO 9001 has long embraced risk-based thinking, but until recently, “environmental” considerations focused on product conformity and resource usage. The new ISO 9001 amendment explicitly brings climate risk into scope, aligning quality management with global sustainability goals. By articulating climate change as an “interested party” requirement, the amendment extends the standard’s reach into environmental stewardship without creating a separate ISO document. Exact Wording of the Two-Line Update The amendment reads: * The organization shall determine whether climate change is an issue that can affect its quality management system. * Where such issues are identified, the organization shall plan and implement actions to address these climate-related risks and opportunities. Though minimal, this language integrates seamlessly into Clauses 4 and 6 of ISO 9001:2015, reinforcing the risk-based framework and ensuring that climate considerations become an embedded part of continual improvement. Practical Interpretation: Determining Climate-Related Risks “Determine whether climate change is an issue” may sound broad, but organizations can ground this in real-world examples. For instance: * Manufacturers assess supply-chain vulnerabilities due to extreme weather events. * Service providers evaluate energy-use efficiency and carbon footprint in daily operations. * Agricultural operations might switch from diesel-based to biofuel-based equipment or adopt no-till practices to reduce greenhouse gas emissions. By mapping these risks in a dedicated section of the risk register, companies demonstrate compliance with the climate change amendment and strengthen overall process resilience. IAF Guidance: What Auditors Need to Know Shortly after publication, the International Accreditation Forum (IAF guidance) issued a complementary document outlining how auditors should verify compliance: * Evidence gathering: Auditors must review documented risk assessments and climate-related action plans. * Scope expansion: Interviews with process owners should probe climate mitigation measures alongside traditional quality controls. * Audit time allocation: Expect an additional 30–60 minutes to cover climate topics thoroughly. This IAF guidance ensures consistent treatment across certification bodies, preventing arbitrary interpretations and audit surprises. Adapting Your Audit Planning Incorporating the amendment into audit planning involves: * Pre-audit review of climate-risk registers and related meeting minutes. * Schedule adjustment to include climate-specific interviews and process walk-throughs. * Auditor training on environmental metrics and carbon accounting fundamentals.

Welcome to the very first episode of Caleb’s Corner, part of the #QualityMatters podcast! If you're a welder, inspector, or anyone curious about stepping into the welding inspection world, this episode is your step-by-step, real-world guide on how to become a Certified Welding Inspector (CWI). Based on Caleb’s personal journey — from welding school to earning his CWI certification, and later moving into software development — this episode breaks down everything you need to know that most official guides don’t tell you. You’ll hear practical, boots-on-the-ground advice that will save you time, money, and frustration. Why Become a Certified Welding Inspector? Many welders realize early that staying on the shop floor or crawling through tight spaces forever isn’t a sustainable long-term plan. A CWI certification opens doors to inspections, NDT (non-destructive testing), and higher-paying quality roles, while building on your welding foundation. Understand the Process (and Why It's Hard) Becoming a CWI isn’t easy. The AWS CWI exam is intentionally challenging, and it should be — you're certifying yourself as an expert. Expect to study extensively in these three main areas: * Code Book Navigation (ex: AWS D1.1, API 1104, etc.) * General Welding Knowledge (safety, welding processes, NDT methods, metallurgy) * Practical Inspection Skills (actual weld evaluation and measurements) The exam isn't just about memorizing answers — it's about learning how to read, interpret, and apply complex standards accurately. AWS intentionally mixes topics to test your comprehension, not your memory. Choose a Solid Prep Course The prep course is critical. Caleb highly recommends Real Educational Services (or similar reputable prep programs). These courses walk you through the code books and show you where to tab important sections. They provide practice exams that simulate the actual AWS exam format. They offer real-world tips on navigating tricky AWS wording and test traps. They help clarify differences between similar concepts like welder qualification vs procedure qualification. Pro tip: Schedule your AWS exam as close as possible to your prep course — ideally within one week, but no longer than one month after the course, to retain fresh knowledge. Commit to a Study Schedule Caleb studied for 2 hours per night for about 3 months before taking the prep course, followed by focused practice right up to the exam. Plan to review every section you’re weak in (TIG welding, NDT, safety, etc.). Use your prep course study materials to guide your self-study. Focus on reading comprehension — not just memorization. Practice navigating the actual code book under time pressure. Master Reading Comprehension This skill is crucial. The AWS exam is designed to trip you up with fine distinctions. You need to fully read every question before attempting to answer. Pay attention to footnotes, exceptions, and definitions. Double-check whether the question refers to procedure qualification or welder qualification. Build speed while maintaining accuracy. Tip: While reading your prep materials, pause frequently and quiz yourself: “Do I really understand this paragraph?” Know What the Exam Looks Like The exam consists of three parts: * Code Book Portion: Code-specific problem solving. * General Knowledge: Broad welding & inspection topics.

Quality Matters Episode 215: What’s the Real Cost of Poor Quality? In this episode of the #QualityMatters podcast, Kyle and Caleb dive deep into a topic that touches every business, from manufacturing to customer service—the true cost of poor quality. But this isn't your typical lecture on scrap and rework. The guys bring stories, perspectives, and real-world relevance to the table—from customer loyalty and personal tech decisions, to school choice and workforce skills, to the vital role of culture in shaping quality outcomes. When Customer Experience Drives a Brand Switch Caleb kicks off the episode with a personal story that many of us can relate to: a frustrating experience with a major cell phone manufacturer that ultimately led him to switch to Apple. This wasn’t just about technical specs or flashy features—it was about how quality (or the lack of it) is perceived by customers. When something breaks or a system doesn’t work as promised, customers don’t just lose patience—they lose trust. "It wasn’t the cost of the broken phone. It was the cost of lost time and support that pushed me to change brands." – Caleb This example underscores a key theme: poor quality isn't always measured in dollars—it’s often paid for in loyalty, reputation, and long-term business. Kyle's Thoughts on Education, Trades & the Future of Quality Shifting gears, Kyle reflects on education choices for his sons—particularly the value of vocational training and skilled trades. In a world that’s heavily focused on four-year degrees, Kyle advocates for alternative education paths that equip young people with tangible skills—and the ability to contribute meaningfully in quality-centric roles from day one. "We’ve got to stop thinking a good education only happens in a classroom. It happens in a shop, at a lathe, with a wrench in your hand." This discussion challenges us to rethink how we prepare the next generation for quality-focused careers, and how education directly impacts organizational quality from the ground up. Scrap, Rework & the Obvious Costs Of course, no episode about poor quality would be complete without touching on the more visible costs—scrap, rework, waste, and lost production time. The hosts break down how these issues creep into operations and why they are symptoms, not the root cause. Caleb reminds us that you can’t fix culture with corrective actions alone, and that lasting change must address both processes and people. Culture: The Real Root of Quality What ties all these topics together? Culture. The heart of the episode rests in the idea that quality begins with people, and the culture that leaders build around them. A culture that values continuous improvement, feedback, and pride in workmanship is the only true long-term solution to preventing quality failures—whether they happen on the shop floor or in customer support. QualityMatters, #CostOfPoorQuality, #CustomerExperience, #TradeEducation, #QualityCulture, #ManufacturingMatters, #LeadershipDevelopment, #ContinuousImprovement