WhyTrace Plus Release Notes: Latest Features and Improvements
This page tracks what has shipped in WhyTrace Plus. Rather than a developer-focused changelog, the goal here is practical: what can you do now, and why did each addition get prioritized.
The features below are cumulative. If you created an account recently, all of these capabilities are already available.
AI-Guided 5 Whys
The 5 Whys method is straightforward in principle and difficult in practice. Investigators move too quickly through the "why" chain, stop at a symptom, or branch in directions that do not connect to actionable corrective measures. The most common failure mode is a final "why" that points to human error, with no further interrogation of the conditions that made that error likely.
WhyTrace Plus now guides the 5 Whys conversation rather than just providing a blank form. The AI asks follow-up questions when an answer is too vague or when the causal chain looks incomplete, and it flags when a stated cause is more likely a contributing factor than a root cause. The result is a cause chain that holds up under review — not just a completed template.
The session is conversational. Investigators respond in plain language; the system structures the cause tree as it progresses. At any point, the investigator can override the AI's framing or redirect the chain. The tool assists the thinking; it does not replace it.
Five RCA Frameworks
Different incident types require different investigation structures. A human-factors incident at a chemical facility and a quality escape in a machined parts operation share the methodology of root cause analysis but not the category structure that makes it useful.
WhyTrace Plus supports five frameworks:
4M (Man, Machine, Material, Method) is the entry-level manufacturing standard. It is fast to apply, broadly understood, and compatible with most quality management training. Teams already familiar with cause-and-effect diagrams can move directly into the tool without relearning a category structure.
5M1E (Man, Machine, Material, Method, Measurement, Environment) adds Measurement and Environment to the 4M base. The Measurement category catches gauge calibration issues, inspection gaps, and process monitoring failures that 4M investigations routinely miss. The Environment category covers workplace conditions — temperature, lighting, noise, layout — that are particularly relevant to human-factors incidents.
SHELL (Software, Hardware, Environment, Liveware, Liveware) is the aviation and high-reliability industries standard. The two Liveware categories — one for the individual, one for the individual's interactions with others — give SHELL precision for human-factors analysis that no manufacturing framework matches. EHS investigators working on incidents where the interaction between people is central to the cause chain will find SHELL the most structured tool available.
SRE (Site Reliability Engineering) postmortem format supports software and systems teams. The SRE framework treats incidents as system failures, not individual failures, and its category structure is built around service dependencies, failure modes, and detection gaps. For technology operations teams using WhyTrace Plus alongside standard postmortem practice, this framework integrates without translation.
Fault Tree Analysis (FTA) is the fifth framework, and it operates differently from the others. Where cause-and-effect frameworks build upward from causes to effects, FTA starts with the undesired top event and works backward through logical gates — AND, OR — to map the combinations of conditions that could produce it. FTA is the appropriate method for process safety analysis, risk assessment of potential failures, and any investigation where the question is not just "what happened" but "what else could produce this outcome." The implementation uses ReactFlow for the diagram (described below).
FTA Visualization with ReactFlow
Fault tree diagrams have traditionally been built in dedicated desktop software or drawn by hand. Both approaches create the same problem: the diagram is a separate artifact from the investigation record, maintained independently and often out of sync with the corrective action status.
WhyTrace Plus renders FTA diagrams using ReactFlow, which means the fault tree is interactive within the browser. Nodes can be added, restructured, and annotated during the investigation session. Logic gates are selectable from a palette. The tree updates in real time as the analysis develops.
For teams presenting findings to leadership or external auditors, the diagram exports as a PDF or image that communicates cause structure visually — which is consistently more effective than narrative descriptions for non-technical audiences.
QR Code Incident Reporting
One of the more consistent findings in near-miss research is that reporting friction directly suppresses submission volume. Workers who notice a hazard but face a multi-step reporting process on a shared terminal — or worse, a paper form that requires a supervisor signature before anything happens — simply do not report. The administrative burden lands hardest on the workers with the least administrative time.
QR codes eliminate the portal navigation problem. A QR code posted at a machine, entrance point, or storage area opens directly to a mobile reporting form. Workers scan, fill in what happened and where, and submit. The report is timestamped and linked to the location. The whole process takes under two minutes on a phone.
The reporting form is designed to be minimal: what happened, where, what hazard was present. Photo attachment is optional. No login is required from the submitting worker. Investigation assignment happens on the back end, not at the point of submission.
AI Interview
Collecting information from workers who were present during an incident is one of the harder parts of investigation practice. Written statements tend toward the brief and self-protective. Interviews conducted without a structured protocol produce useful information unevenly — some investigators ask follow-up questions instinctively; others do not.
The AI interview guides a structured conversation with an individual involved in or witnessing an incident. It asks about sequence of events, conditions at the time, what was expected versus what occurred, and what the individual understood to be normal practice. The questions are adaptive — the system follows up on vague answers and explores inconsistencies rather than moving to the next item on a fixed list.
Interview output is structured and saved to the investigation record. Multiple interview sessions can be linked to a single investigation, allowing the investigator to compare accounts and identify divergences. For investigations involving regulatory submissions or insurance reporting, the documented interview record satisfies evidentiary requirements that informal notes do not.
AI Quiz
Investigation methodology is a skill. Most workers who participate in investigations — as witnesses, as involved parties, or as assigned investigators — have not had formal training in root cause analysis. The result is that investigations often surface proximate causes and stop, or assign blame rather than identifying systemic conditions.
The AI quiz tests understanding of investigation concepts. Quiz sets are configurable by framework, difficulty level, and industry context. Questions cover cause-versus-contributing-factor distinctions, common 5 Whys failure modes, when to use FTA versus cause-and-effect methods, and how corrective actions should connect to identified root causes.
For EHS managers running annual training or onboarding new investigators, the quiz provides a documented record of methodology understanding. It is not a certification system — it does not replace formal training — but it is a practical way to identify gaps and to build shared vocabulary across investigation teams.
RAG Chat for Knowledge Retrieval
Every investigation draws on reference material: regulatory text, standard operating procedures, equipment manuals, historical investigation reports, industry incident databases. The standard practice is to search for relevant material manually, which is slow, incomplete, and inconsistently applied across different investigators.
RAG (Retrieval-Augmented Generation) chat queries your uploaded organizational knowledge — procedures, standards, past investigation records, training materials — against a current investigation question. An investigator working on a hydraulic system failure can ask what the maintenance SOP says about inspection intervals and receive a response drawn from the actual document, not a generic answer.
The knowledge base is populated by uploading PDFs and common text formats. The system makes documents findable and queryable during an investigation session, when manual document search is most disruptive.
Corrective Action Tracking
The part of most investigation processes that fails most visibly is corrective action follow-through. Actions are identified, assigned, and then lost — to job changes, competing priorities, unclear ownership, or simply no mechanism for tracking whether closure has occurred.
WhyTrace Plus links corrective actions to the investigation record where they originated. Each action carries an assigned owner, a due date, and a status. When an action is overdue, it is visible in the dashboard. When it is closed, the closure is timestamped and connected to the original cause finding.
This linkage matters for two reasons. First, it creates accountability without a separate tracking system. Second, it produces a closed-loop record: any future investigation into a recurrence can show whether the prior corrective action was actually implemented — the first question any auditor or regulator will ask.
PDF, Excel, and CSV Export
Investigation records need to leave the platform. They go to insurers, regulators, management review meetings, audit files, and quality management systems. The format requirements vary by destination.
All three export formats are included at every plan level:
PDF generates a formatted report suitable for submission to external parties or inclusion in audit documentation. The report includes the cause tree, investigation narrative, corrective action list, and metadata (date, investigator, affected location).
Excel exports structured data — causes, contributing factors, corrective actions, status fields — in a format that can be imported into existing tracking systems or analyzed across multiple investigations in a spreadsheet environment.
CSV provides flat-file output for integration with databases, business intelligence tools, or EHS management platforms that accept data imports.
Multi-Language Support
Investigation quality degrades when the investigation tool operates in a language that is not the investigator's primary language. Subtleties in cause description, precision in how contributing factors are characterized, and accuracy in documenting conditions at the time of the incident all depend on the investigator working in a language where they can be exact.
WhyTrace Plus supports multiple languages across the investigation interface, reporting forms, and AI functions. The QR code reporting form, the AI interview, and the AI quiz all operate in the selected language — not translated after the fact, but natively.
For multi-site organizations where investigation teams work in different languages, language settings are configurable at the workspace level without affecting how records are stored or reported centrally.
Everything above is available on the Free plan.
Three analyses per month, all five frameworks, full AI functions, QR reporting, and complete export options — no credit card required.
What Is Coming Next
The current development focus is cross-investigation trend analysis — querying patterns across a portfolio of investigations rather than reviewing records individually. Recurrence detection, cause category frequency, and corrective action effectiveness tracking are the primary capabilities in progress.
If you have workflow or integration requirements to flag, reach the team at support@whytrace.plus.
Related Resources
| Resource | Description | Best For |
|---|---|---|
| Getting Started with WhyTrace Plus | Step-by-step walkthrough from account creation to first exported report | New users activating features covered in this update |
| 5 Whys Analysis: Complete Guide | Full walkthrough of the 5 Whys method with examples from safety and manufacturing | Understanding the methodology behind the AI-guided 5 Whys feature |
| CAPA Management: Stop Losing Track of Corrective Actions | How to build a corrective action process that closes reliably | Getting the most from the corrective action tracking feature |
| RCA Framework Comparison: 4M vs 5M1E vs SHELL | When to use each framework and how they differ in practice | Choosing the right framework for your investigation type |
| QR Code Incident Reporting: How It Works | How QR-based reporting reduces submission friction and increases near-miss capture | Teams setting up QR reporting at worksites |
| WhyTrace Plus Pricing Guide | Full breakdown of Free, Pro, and Enterprise plans with exact feature and volume limits | Understanding plan options after reviewing the feature set |