WhyTrace Plus Complete Guide: From Reporting to Knowledge Management
Most teams that adopt a new SaaS tool use somewhere between 20 and 40 percent of its features in the first month. They solve the immediate problem, and the rest stays unexplored. For an investigation platform, the features left untouched are often the ones that turn incident records into organizational knowledge — which is where the long-term value lives.
This guide covers the full scope of what WhyTrace Plus can do, from the first analysis to the knowledge management layer. If you're already using it for the 5 Whys and nothing else, there's a good chance you're leaving the most useful parts untouched.
The Platform Architecture: How the Pieces Connect
WhyTrace Plus is built around a core investigation loop: define a problem, run a structured analysis, document the cause chain, assign corrective actions, generate a report. That's what most users encounter first. But the platform has three distinct layers:
Layer 1 — Analysis tools. The AI-guided 5 Whys, five frameworks (4M, 5M1E, SHELL, SRE, Custom), and fault tree analysis. This is where investigations happen.
Layer 2 — AI assistance. The AI interview, AI quiz, and RAG chat — running alongside investigations to guide methodology and surface relevant knowledge.
Layer 3 — Output and knowledge management. Reports, QR sharing, corrective action tracking, and PDF/Excel/CSV exports. This is where investigations become organizational assets.
Most users master Layer 1 quickly. Layers 2 and 3 are where the compounding value lives.
Layer 1: The Analysis Tools
Five Investigation Frameworks
The framework you choose determines the category structure of your cause tree. WhyTrace Plus supports five:
| Framework | Primary Use | |-----------|-------------| | 4M (Man, Machine, Material, Method) | Manufacturing defects, equipment failures | | 5M1E (adds Measurement, Environment) | Quality investigations, production incidents | | SHELL (Software, Hardware, Environment, Liveware x2) | Aviation, healthcare, human factors | | SRE (Site Reliability Engineering) | IT incidents, system outages | | Custom | Non-standard categories or mixed environments |
Choosing the right framework is not just a formality. The category structure drives the AI's interview questions — a 4M analysis of the same incident will produce different questions, and potentially surface different causes, than a 5M1E analysis. For manufacturing quality events, 5M1E is the default because it adds measurement variation and environmental conditions. For IT incidents, SRE maps directly to the language your engineers already use. For human factors events in healthcare or aviation, SHELL's treatment of the human-human interface (Liveware-Liveware) handles categories the other frameworks don't cover.
The Custom framework is underused. If your organization has cause categories that don't map cleanly to the four named options — or if your CAPA templates require specific terminology — Custom lets you define the structure from scratch.
5 Whys Analysis
The 5 Whys path produces a sequential cause chain rather than a category-based tree — the right choice for simpler incidents, for teams less familiar with structured frameworks, or when a quick investigation is more appropriate than a comprehensive one.
The AI interview operates in 5 Whys mode the same way it does in framework mode: asking follow-up questions based on each answer, populating the chain as you go, and pushing back when a chain has stopped at a symptom. You can also start with a 5 Whys and upgrade to a framework analysis if the investigation reveals more complexity than initially apparent.
Fault Tree Analysis (FTA)
FTA takes a top-down, Boolean logic approach: rather than asking "why did this happen?" iteratively, it maps all combinations of events that could produce the undesired outcome. It's standard in aerospace, nuclear, and process safety environments because it handles multiple simultaneous failure modes explicitly.
In WhyTrace Plus, the ReactFlow visualization renders the fault tree with AND/OR gate logic. FTA is most valuable for complex incidents with multiple interacting failure paths, or when a regulator or auditor requires evidence that all failure combinations were analyzed. For most day-to-day investigations, the 5 Whys or a framework analysis is faster and sufficient.
ReactFlow Cause Tree Visualization
Every analysis produces an interactive cause tree in ReactFlow — a visual graph of the cause chain from the immediate event back to the root. It's an editable workspace, not just a display.
During the investigation, the tree gives you an immediate read on where the analysis is shallow: a branch ending after one level is a flag that the investigation either stopped early or genuinely has nothing there. After the AI interview, you can add, remove, or edit any node directly. Repositioning nodes for readability before report generation is worth a minute — a clear tree is easier to explain in a management review than a default-layout tangle.
Layer 2: AI Assistance Tools
AI Interview
The AI interview is the engine of the analysis. It's not a chatbot that answers your questions — it's the other direction: the AI asks you questions about the incident, systematically covering each cause category or why-step based on your answers.
This matters for two reasons. First, it produces consistent investigations regardless of who runs them — an experienced investigator probes certain categories naturally; a newer one may not know what to ask. The AI applies the same systematic coverage to both. Second, it prevents premature closure: the AI continues probing within each category until you've confirmed or ruled out that branch, rather than accepting the first plausible cause.
The interview adapts to your answers. If you say the operator wasn't trained on the specific procedure, the next questions focus on the training program — not equipment maintenance. It's contextual questioning, not a fixed script.
AI Quiz
The AI quiz generates scenario-based questions relevant to the framework you're using, the analysis stage, and the incident type. It's most useful for training new investigators — identifying gaps in framework understanding before they affect real analyses — and for calibrating experienced investigators applying an unfamiliar framework. For an EHS manager running a SHELL analysis for the first time, a few quiz questions confirm whether the cause categories are being applied correctly.
The quiz doesn't affect the investigation record. It runs alongside the analysis as a learning layer.
RAG Chat
RAG chat is the platform's knowledge query layer. During an investigation — or between them — you can query the knowledge base for regulatory requirements, framework guidance, organizational standards, or past investigation summaries.
Out of the box, the RAG chat surfaces framework guidance, methodology best practices, and general regulatory context. As your organization's investigation records accumulate, those records join the knowledge base — meaning you can query past analyses to find similar incidents, identify recurring causes, or check how a previous failure of the same type was resolved.
A team with six months of analyses in the platform can ask "what root causes have appeared most often in equipment failure investigations this year?" and get an answer drawn from their own records. That kind of pattern recognition — done manually across spreadsheets or PDFs — is the work that usually doesn't happen.
Layer 3: Output and Knowledge Management
Report Generation
Reports are generated from the completed cause tree and investigation metadata: incident summary, full cause tree diagram, root cause identification, and structured corrective action fields. The format meets the documentation standards expected in ISO 9001, ISO 45001, and OSHA investigation contexts — a complete audit trail from incident to root cause to planned action.
One thing worth using well: the corrective action fields. The platform provides the structure; you provide the substance. A corrective action should specify what will change, who owns it, and when it will be verified complete. "Retrain operators" is a placeholder. The report's value depends on the specificity of what goes into those fields.
QR Code Reporting
Every generated report can be shared via QR code. The code links to the live report — accessible without a WhyTrace Plus account — and can be printed, posted at the incident site, attached to equipment, or included in a toolbox talk handout.
For a manufacturing incident, posting the QR code at the site of the event lets anyone scan to see what the investigation found and what corrective actions are in progress — no safety meeting attendance required, no intranet access needed. It's also a visible signal that investigations lead to documented outcomes, which changes how incident reporting is perceived on the floor.
Corrective Action Tracking
The platform tracks corrective actions from assignment through verification. Each action carries an owner, a due date, and a completion status. Open actions are visible in the dashboard, making it straightforward to monitor which investigations have pending corrective actions and which are closed out.
Corrective action tracking is where many CAPA processes quietly fail: the investigation is documented, the actions are assigned, and nothing happens until the next audit. Keeping status visible at the investigation record level — rather than in a separate spreadsheet — reduces the gap between assignment and follow-through.
Export Options
Completed analyses and reports export as PDF, Excel, or CSV. PDF suits regulatory submissions and management presentations. Excel and CSV give quality and EHS teams the data for trend analysis — aggregating cause types, incident categories, and corrective action timelines. The CSV export is particularly useful for importing investigation data into a separate CAPA or quality management system without re-entry.
See the full platform in action. WhyTrace Plus is free to start — three analyses per month, all features included, no credit card required.
Create your free account | See pricing
Plan Capabilities Reference
| | Free | Pro (¥980/mo) | Enterprise (¥4,980/mo) | |--|------|----------------|------------------------| | Analyses/month | 3 | 50 | Unlimited | | Reports/month | 10 | 100 | Unlimited | | AI queries | 10 | 100 | Unlimited | | All frameworks + FTA | Included | Included | Included | | AI interview + quiz + RAG | Included | Included | Included | | QR reporting + exports | Included | Included | Included | | Custom frameworks | — | — | Included | | API access | — | — | Included |
The free plan runs the full platform — not a stripped preview. Three analyses on real incidents will tell you more about fit than any demo.
Getting the Most From the Platform
Use the RAG chat between investigations. A monthly query of past records to surface recurring cause patterns is a lightweight input to a continuous improvement program.
Set achievable corrective action due dates. A realistic timeline that closes on time is better than an ambitious date left perpetually overdue.
Agree on terminology early. When investigators describe the same cause differently — "procedure not followed" vs. "SOP deviation" — pattern detection becomes noise. A short shared list of common cause terms pays off quickly.
Export on a schedule if you use a separate CAPA system. The CSV export is most useful as a recurring workflow item, not an audit-driven scramble.
Related Resources
| Resource | Description | Best For | |----------|-------------|----------| | Getting Started with WhyTrace Plus | Step-by-step walkthrough of your first AI-guided analysis | New users running their first investigation | | 5 Whys Complete Guide | Methodology overview with examples and templates | Understanding the 5 Whys before using the platform | | Best RCA Software in 2026 | Comparison of seven RCA tools with trade-off analysis | Evaluating WhyTrace Plus against alternatives | | AI in Root Cause Analysis | How AI is changing investigation methodology | Understanding what the AI in WhyTrace Plus actually does | | How to Do a 5 Whys Analysis | Practical step-by-step walkthrough with common pitfalls | Teams new to structured investigation methodology |