← Notes · · auto
Filling D4 When the Root Cause Is Still Unclear
What to actually write in D4 when your root cause investigation is still running, so the 8D keeps moving.
Most D4 sections we see are either blank or contain the phrase “under investigation”, written three weeks after the containment actions in D3 went in. The team has moved on. The containment is working. Nobody wants to go back and write something that might be wrong.
That hesitancy makes sense, but it causes problems. A D4 that stays empty or vague turns an 8D from a problem-solving record into a paper exercise. And when the same fault reappears six months later, nobody can tell whether the previous investigation got anywhere.
Here is what to actually do when D4 is due and the root cause is not yet confirmed.
What D4 Is Actually Asking For
D4 is not asking you to prove a root cause beyond all doubt. It is asking you to identify the most probable cause, supported by evidence, and to name the point in your process where the defect was able to escape to the customer.
Those are two distinct things. Root cause is the origin. Escape point is the gap in your detection. Both belong in D4.
If you are waiting until you have absolute certainty before writing anything, you are misreading what the section requires.
The Difference Between a Hypothesis and a Guess
When analysis is still running, the honest thing to do is state your working hypothesis clearly and say what evidence you have so far.
“We believe the cause is thermal expansion in the toolholder during the third shift, based on the pattern of non-conformances mapping to overnight runs. We are currently measuring spindle temperature over a full production cycle to confirm.”
That is a valid D4 entry. It tells anyone reading the report where the investigation stands. It names a mechanism. It describes the evidence. It is not a guess dressed up as a conclusion.
A guess would be: “Machine issue possibly.” Do not write that.
How to Structure D4 Mid-Investigation
When root cause is still being confirmed, split your D4 entry into three short sections.
Current hypothesis. One sentence. What you think caused the problem and why.
Supporting evidence. What you have already seen or measured that points toward this cause. Data, observations, test results, anything concrete.
Confirmation steps outstanding. What is still being done to either confirm or rule out the hypothesis. Include who is responsible and by when.
This keeps the report active and honest. It signals to whoever is reviewing the 8D that work is in progress, not stalled.
Why the Escape Point Matters as Much as the Root Cause
Teams often spend all their energy on the cause and barely mention the escape point. That is a mistake.
Even if you do not yet know exactly why the defect occurred, you usually know how it got through without being caught. Write that down. It is useful on its own and often leads you back toward the cause.
If a visual inspection missed 47 cracked housings, the escape point is the inspection step. The fact that it failed might be down to lighting, training, workload, or a gauge issue. Those are separate questions, but naming the escape point gives you somewhere to act before the root cause analysis is finished.
Containment in D3 often addresses the escape point temporarily. D4 should identify it properly so D5 and D6 can address it for good.
Keeping the 8D Moving
The mistake teams make is treating D4 as a gate. The report sits on someone’s desk, waiting for D4 to be “done” before anyone touches D5. That is not how the process is supposed to work.
D5 and D6 can begin on containment improvements and escape-point fixes before the root cause is fully confirmed. You do not have to wait.
What you should avoid is closing the 8D, or marking it complete, before D4 has a confirmed root cause and a verified escape point. An open, honest D4 is fine. A closed D4 with a wrong answer is not.
If your team is producing 8Ds regularly, it is worth having a standard template that separates hypothesis, evidence, and outstanding steps. The structured fault investigation tools in the diagnostics section are a reasonable starting point for building that discipline into your process.
And if the same problems keep cycling back through your 8D queue, that is usually a sign that D4 and D5 are not being written carefully enough. Running a quick calculation at losses.cadencestandard.com can help you put a number on what repeated escapes are costing, which tends to sharpen the team’s interest in getting the root cause right first time.