Detailed Explanation of Three Types of A3 Reports —— How to Write Proposal, Problem-Solving, and Status Report A3s

1. A3 Reports Are More Than Just "One Page"

Many quality professionals, when learning about A3 reports, often only encounter one template: background → current situation → root cause → countermeasures → verification. This template is indeed classic, but it is just a subset of A3 reports—Problem-Solving A3. In Toyota's practical application, A3 reports are categorized into at least three types based on different usage scenarios. Each type has distinct structures, focuses, and writing logic.

Not understanding this classification can lead to awkward situations such as "using a problem-solving template to write a project report and being criticized for being too verbose" or "using a proposal template to write a customer complaint analysis, resulting in insufficient space for the critical root cause section." This article will break down each of the three A3 types and provide writing points and example frameworks for each type.

2. Positioning and Structure of the Three A3 Types

1. Problem-Solving A3 (The Most Classic)

Applicable Scenario: Solving specific issues that have already occurred—such as a decline in production line yield, frequent equipment failures, or customer complaints.

Core Logic: The PDCA cycle embodied on one page.

Standard Structure (Seven Sections):

• Background/Purpose: The relationship between this issue and the company's goals/client needs
• Current Situation: Use data to illustrate the severity of the problem (trend charts, Pareto charts, stratification tables)
• Objective: SMART goals—by what time, what metric, from what level to what level
• Root Cause Analysis: 5Why or fishbone diagram, delving into process/standard/equipment levels
• Countermeasures: Short-term containment measures + long-term preventive measures, clearly specifying the Owner and completion date
• Effect Verification: Data comparison before and after the implementation of countermeasures
• Standardization/Horizontal Deployment: Update SOPs, control plans, and replicate to other workstations

Suggested Length Allocation: Root cause analysis and countermeasures should take up about 50% of the A3 report, as these are the core areas of focus for problem-solving A3s.

2. Proposal A3

Applicable Scenario: Proposing a new plan, new process, new investment, or change recommendation—such as suggesting the introduction of new equipment, changing the process route, or implementing a new management model.

Core Logic: From "problems in the current situation" to "value of the proposal" to "feasibility of implementation."

Standard Structure (Six Sections):

• Background/Purpose: What pain points or opportunities currently exist
• Current Situation Analysis: Quantitative explanation of the current approach's costs and issues
• Proposal Content: What is suggested and how it should be done
• Expected Outcomes: Estimation of benefits after implementation (quantified in terms of quality, cost, and efficiency)
• Implementation Plan: Milestones, resource requirements, risks, and responses
• Conclusion/Recommendation: What the decision-maker should approve

Key Differences: Proposal A3s do not require a root cause analysis section (since the problem hasn't occurred yet), but they need a more robust "expected outcomes" argument—this is the most critical part for decision-makers. Each data point must have a source, and it's not acceptable to write "expected to improve yield by 5%" based on a feeling.

3. Status Report A3 (Progress Report Type)

Applicable Scenario: Reporting project progress, annual quality goal achievement, audit nonconformity rectification status, etc., to management.

Core Logic: What was done in the past → current status → what needs to be done next.

Standard Structure (Five Sections):

• Goal/Plan Review: What goals and plans were initially set
• Current Progress: Actual completion status, indicated by green/yellow/red status
• Deviation Analysis: Reasons, impacts, and responses for unmet items
• Subsequent Plan: Next steps and required support
• Conclusion: Overall judgment—whether the project is on track and whether goals need to be adjusted

Key Differences: The focus is not on "deep root cause analysis" but on "information transparency and quick alignment." The red/yellow/green light method is the core tool of status report A3s, allowing managers to grasp the key points within 30 seconds.

3. Decision-Making for Choosing the Right A3 Type

In practice, the same team may need all three types of A3 reports:

Typical consequences of choosing the wrong type: Using a problem-solving A3 to write a status report, the leadership may feel it is "too deep, too slow"; using a status report A3 to write an improvement project, the improvement team may find "insufficient space for root cause analysis."

4. Writing Tips — Three Practical Checklists

Regardless of the type, a good A3 report has three common characteristics:

1. Hard Constraint of One Page. If you can't fit it on one page, it means you haven't thought it through—A3 doesn't limit the amount of information but forces you to distill the core logic. Supporting data and detailed attachments can be added separately.

2. Data-Driven, No Adjectives. Don't write "high defect rate," write "the defect rate for process A in March was 2.3%, 2.9 times the target value of 0.8%, ranking first in the plant's defect contribution, with a cost of approximately ¥15,000 per month."

3. Auditable Logic. The output of each section should naturally lead to the input of the next section. Current situation data should guide the direction of root cause analysis, root causes should guide targeted countermeasures, and countermeasures should guide verification metrics—forming a closed loop.

5. A Small Example: How to Write a Proposal A3

Assume that a long-standing issue of solder spatter in the welding process of an electronics factory has been affecting the appearance yield (current yield 92%, target 98%). The engineer plans to recommend changing the welding parameters and the protective gas mixture.

Example of Key Sections in a Proposal A3:

Current Situation Analysis Section: List the Pareto chart of appearance defects for the past three months—solder spatter accounts for 62% of total defects, with approximately 120 hours of rework per month, equivalent to a cost of about ¥15,000 per month.

Proposal Content Section: Clearly list—(1) Change the protective gas from pure CO₂ to 80% Ar + 20% CO₂; (2) Adjust the wire feed speed from 8m/min to 6.5m/min; (3) Add one gas mixer, with a budget of ¥8,000.

Expected Outcomes Section: Refer to industry data and preliminary small batch welding results—predict that the appearance yield can be improved from 92% to 97%, rework hours can decrease by 75%, and costs can be saved by about ¥11,000 per month. The investment payback period is approximately 22 days.

Such an A3 report allows managers to make decisions after reading it—whether to approve it or what additional information is needed.

6. Conclusion

Mastering the three types of A3 reports and their respective structural logics is essential to make A3 reports a true "communication tool" rather than a "form-filling task." Choosing the right type is more important than filling the content.

The value of an A3 report lies not in filling up one page but in selecting the right structure, explaining the logic clearly, and driving decision-making.

Knowledge code: 5.2.2

Version: v20260729

Author: Quality Think Tank The Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.