Getting Started with WhyTrace Plus: Your First AI Analysis in 10 Minutes
Most root cause analysis tools come with a learning curve that compounds the problem they're supposed to solve. You're already dealing with a fresh incident, documentation pressure from your QMS or safety program, and a team waiting for answers. The last thing you need is three hours of setup and a training course before you can run your first investigation.
WhyTrace Plus was built around a different premise: the tool should guide you through the analysis, not require you to already know how to use it. This walkthrough shows you exactly what happens from the moment you create a free account to the point where your first investigation is documented and ready to share — a process that takes most users under 10 minutes.
Before You Start: What WhyTrace Plus Actually Does
WhyTrace Plus is an AI-guided root cause analysis platform. It supports five investigation frameworks — 4M, 5M1E, SHELL, SRE, and Custom — plus 5 Whys analysis and fault tree analysis (FTA). The AI component does three things that matter in practice:
It guides the analysis in real time. Rather than presenting a blank form, the AI interviews you about the incident and suggests cause branches based on your responses. This keeps investigations consistent across different investigators and experience levels.
It asks clarifying questions you might skip. An experienced investigator might naturally probe deeper into certain cause categories; a less experienced one might not know what questions to ask. The AI interview function handles this systematically, regardless of who is running the session.
It drafts reports from the investigation data. Once the cause chain is documented, WhyTrace Plus can generate a structured report — formatted for sharing with management, attaching to a CAPA record, or distributing via QR code to the team.
The free plan gives you three analyses per month, ten reports per month, and ten AI queries — enough to run real investigations before you commit to anything.
Ready to follow along? Create your free account at whytrace.plus — no credit card, no installation.
Step 1: Create Your Account (2 Minutes)
Go to whytrace.plus and select the free plan. You'll need an email address and a password. There is no installation, no browser extension, and no approval process — the account is active immediately.
The free plan starts you with:
- 3 analyses per month
- 10 reports per month
- 10 AI queries
That's enough capacity to run real investigations on actual incidents, not just toy examples. If you're evaluating the tool for your team, three analyses across meaningful incidents will give you a clear picture of how it fits your workflow.
Once you're logged in, you'll see the main dashboard. The primary action from here is creating a new analysis.
Step 2: Create a New Analysis (1 Minute)
Click New Analysis from the dashboard. You'll be asked to provide basic incident information:
- Incident title — keep it specific. "Laceration to right hand, Line 3, March 4" is more useful than "safety incident."
- Date and time — when the incident occurred, not when you're documenting it.
- Location — site, department, or equipment as specific as you have.
- Brief description — one or two sentences describing what happened.
This initial information does two things: it anchors the analysis to a specific event (preventing scope drift later), and it gives the AI enough context to provide relevant guidance in the next steps.
One practical note: specificity in the problem statement pays off throughout the entire analysis. A vague description produces generic AI suggestions. A specific, factual description of what happened, where, and under what conditions produces cause hypotheses that actually apply to your situation.
Step 3: Choose Your Analysis Framework (30 Seconds)
WhyTrace Plus supports five frameworks. The right choice depends on your industry and the type of incident:
| Framework | Best For | |-----------|----------| | 4M (Man, Machine, Material, Method) | Manufacturing defects, equipment failures | | 5M1E (+ Measurement, Environment) | Quality investigations, production incidents | | SHELL (Software, Hardware, Environment, Liveware, Liveware) | Aviation, healthcare, human factors incidents | | SRE (Site Reliability Engineering model) | IT incidents, system outages, service failures | | Custom | Mixed environments or non-standard cause categories |
If you're running a 5 Whys rather than a framework-based analysis, that option is also available from this screen. The 5 Whys path follows the same general flow — AI interview, cause chain documentation, report generation — but structures output as a sequential why-chain rather than a category diagram.
For most manufacturing or construction safety incidents, 5M1E covers the full range of cause categories you'll want to explore. For IT operations teams, SRE maps directly to the categories your team already uses.
Step 4: Run the AI Interview (3–5 Minutes)
This is the core of the WhyTrace Plus experience and where the AI earns its place in the process.
After selecting your framework, the AI interview begins. The system asks targeted questions about the incident based on the framework categories and the description you provided. For a 5M1E analysis of a manufacturing incident, you might see questions like:
- "Was the operator trained on the specific procedure involved in this task? When was training last completed?"
- "Were maintenance records current for the equipment involved? What was the last service date?"
- "Was the procedure being followed as written at the time of the incident? Were any deviations observed?"
Answer each question with what you actually know. If something is unknown, say so — unknown factors are legitimate findings that may warrant further investigation. Don't guess to fill in blanks.
As you answer, the AI populates cause branches in the analysis tree. You can see the structure building in real time in the ReactFlow visualization panel on the right side of the screen. This visual representation of the cause chain is one of the more immediately useful features — it makes it easy to spot where branches are shallow (possible missed causes) versus where the chain is fully developed.
The AI quiz feature is available during this stage as well. If you want to test your understanding of a specific cause category or framework element, the quiz generates scenario-based questions that help calibrate whether you're applying the methodology correctly. This is particularly useful if you're new to a specific framework or if you're training a team member.
Two things to watch for during the interview:
First, resist the urge to accept the first plausible cause the AI surfaces. The interview is designed to probe further. Answer each follow-up question before concluding that a branch is complete.
Second, if the AI's suggested cause doesn't match what you actually observed at the site, override it. The AI is working from your description and general patterns; you have direct knowledge of the incident. The tool is a guide, not an authority.
Step 5: Review and Edit the Cause Tree (1–2 Minutes)
Once the AI interview is complete, you'll see the full cause tree in the ReactFlow visualization. This is an interactive diagram — you can:
- Add causes manually to any branch where you have information the interview didn't capture
- Remove causes that don't apply to your specific situation
- Edit cause text to use the exact terminology your organization uses
- Reposition nodes to improve readability before generating the report
Spend a minute reviewing the tree with the original incident in mind. Ask whether the complete cause chain — from the immediate event back to the root cause — is logically coherent. If any branch leads to "human error" or "operator mistake" as a terminal node, push further: that's a symptom, not a root cause. What in the system, procedure, training, or design made that error possible?
The FTA (fault tree analysis) mode is available at this stage if you want to switch to a formal Boolean logic representation of the cause structure. This is most relevant for complex incidents with multiple contributing factors or for environments where FTA is a regulatory or procedural requirement.
Step 6: Generate and Share the Report (1 Minute)
With the cause tree finalized, click Generate Report. WhyTrace Plus produces a structured document that includes:
- Incident summary (from your initial input)
- Full cause tree diagram
- Root cause identification
- Corrective action fields (you fill these in)
- Investigation metadata (date, framework used, analyst)
The report can be exported as a PDF or shared via QR code. The QR code feature is worth highlighting: it generates a link to the report that anyone with a smartphone can scan, making it practical for posting at the incident site, attaching to equipment, or including in a toolbox talk without requiring recipients to have a WhyTrace Plus account.
For CAPA documentation under ISO 9001 or ISO 45001, the report format provides the audit trail auditors expect: a documented path from incident to root cause to corrective action, with evidence at each step.
What the Free Plan Gets You
Here's a clear picture of what's available without paying anything:
| Feature | Free Plan | |---------|-----------| | Analyses per month | 3 | | Reports per month | 10 | | AI queries | 10 | | Frameworks | All 5 (4M, 5M1E, SHELL, SRE, Custom) | | 5 Whys analysis | Included | | Fault tree analysis (FTA) | Included | | ReactFlow visualization | Included | | QR reporting | Included | | AI interview | Included | | AI quiz | Included | | RAG chat | Included |
The free tier is not a crippled demo. It supports the full feature set at a volume appropriate for a small team or an individual evaluating the tool. Three analyses per month is enough to cover a typical safety incident load at a single site.
The Pro plan at ¥980/month expands capacity to 50 analyses, 100 reports, and 100 AI queries per month — appropriate for teams running investigations at scale or sites with higher incident volumes.
Common First-Use Questions
Do I need to know the 5 Whys methodology before using WhyTrace Plus?
No. The AI interview guides you through the questioning process. Understanding the methodology helps you interpret the results, but the tool does not assume prior expertise. The AI quiz can help you build that understanding as you work.
Can I use this for quality investigations, not just safety?
Yes. The framework selection — particularly 4M, 5M1E, and Custom — maps directly to quality investigation methodology used in ISO 9001 environments. Many teams use WhyTrace Plus for both safety incidents and nonconformity investigations within the same account.
Can multiple people collaborate on an analysis?
The AI interview is typically run by one investigator, but the cause tree can be reviewed and edited by anyone with access to the analysis. Reports can be shared via link or QR code.
What about data security?
WhyTrace Plus is a cloud-based platform. If your organization has restrictions on cloud processing of incident data, review your data handling policies before uploading sensitive information. For most B2B environments, cloud-based investigation tools are standard practice.
Can I run the RAG chat during an investigation?
Yes. The RAG (retrieval-augmented generation) chat lets you query a knowledge base during the investigation — useful for referencing regulatory requirements, framework guidance, or organizational standards while the analysis is in progress rather than switching to another tab.
After the Analysis: Where to Go Next
The first investigation is the starting point, not the destination. Over time, a body of investigation records becomes a strategic asset: patterns in root causes across incidents, evidence for systemic improvements, and documented due diligence for regulatory audits.
A few habits that pay off from the first analysis:
Be specific in corrective actions. The report includes fields for corrective actions, but the tool cannot write these for you — it doesn't know your organizational responsibilities or constraints. A corrective action should specify what will change, who owns it, and when it will be verified complete.
Use consistent terminology. When multiple people run investigations in the same account, agree on standard terminology for common cause categories. This makes trend analysis across investigations meaningful.
Set a follow-up reminder. The corrective actions from an investigation are only valuable if someone checks whether they were implemented. A 30-day or 60-day follow-up to verify completion is a standard part of any CAPA process — but it requires someone to actually do it.
Start your first analysis free. WhyTrace Plus is free to start — three analyses per month, all features included, no credit card required.
Create your free account | See pricing
Related Resources
| Resource | Description | Best For | |----------|-------------|----------| | 5 Whys Complete Guide | Comprehensive methodology overview with examples and templates | Understanding the 5 Whys framework before your first analysis | | How to Do a 5 Whys Analysis | Step-by-step walkthrough of running a 5 Whys correctly | Teams new to structured investigation methodology | | Best RCA Software in 2026 | Comparison of seven RCA tools with honest assessment of trade-offs | Evaluating WhyTrace Plus against alternatives | | AI in Root Cause Analysis | How AI is changing investigation methodology and what to trust | Understanding what the AI in WhyTrace Plus actually does | | RCA Framework Comparison: 4M vs 5M1E vs SHELL | Choosing the right framework for your industry and incident type | Selecting the correct framework during setup |