FMEA Team Kickoff and Scope Template
Most FMEAs go wrong in the first meeting, not the last. This kickoff template forces the team to agree on purpose, boundaries, people, inputs and rules before any failure modes are brainstormed.
Fill in
FMEA Team Kickoff and Scope Template
FMEA Kickoff and Scope
Company: Acme Precision Ltd FMEA type: Process FMEA Subject: Aluminum housing, CNC machining line 3 Customer or program: Hydraulic pump program Facilitator: A. Rao, Quality Engineering
1. Purpose (why are we doing this)
Identify and reduce risk of dimensional and surface defects on the housing before PPAP submission.
2. Scope and boundaries
In scope: Receiving inspection, OP10 to OP60 machining, washing, final inspection, packing.
Out of scope: Casting supplier process, customer assembly line.
Baseline or carry-over: PFMEA-0412 rev C (similar housing)
3. Timing
Kickoff: 2026-11-03 Draft complete: 2026-11-24
4. Cross-functional team
| Name | Function | Role | Meeting attendance |
|---|---|---|---|
| Quality | Facilitator | ||
| Manufacturing engineering | Process owner | ||
| Production | Operator voice | ||
| Design or product engineering | Requirements | ||
| Maintenance | Equipment | ||
| Supplier quality | Inputs |
5. Inputs to collect before the first session
| Input | Owner | Due | Received |
|---|---|---|---|
| Process flow diagram | |||
| Drawings and special characteristics | |||
| Customer requirements and CSRs | |||
| Scrap, rework and complaint history | |||
| Previous FMEAs and lessons learned | |||
| Rating scales (S, O, D) and action rules |
6. Agreed rules
Rating scales used: ______ Action threshold: ______ How often the team meets: ______ Who approves the final FMEA: ______
Approvals
Planning and preparation is the first step in the AIAG-VDA FMEA method, often summarized as the 5Ts: intent, timing, team, task and tools. Adapt this page to your own procedure.
Want FMEA inputs pulled from your ERP?
We can assemble scrap, NCR and routing history into a pre-FMEA package. Optional, the template works on its own.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill the header fields, then print or export the document and complete the tables in your kickoff meeting. The facilitator owns the document and circulates it to every team member. Keep the scope statement specific: name the operations or the system boundary, not just the part number. Anything you list as out of scope should have an owner elsewhere, such as the supplier or the customer.
- Write the purpose as a risk you want to reduce
- List real operation numbers in scope
- Name a person for each input, not a department
- Store the signed page with the FMEA
Why planning matters
The AIAG-VDA FMEA handbook starts with planning and preparation because an FMEA without a clear scope turns into a never-finished wish list. Intent says why, timing says when, team says who, task says what and tools says how. Defining these early prevents the two classic failures: an FMEA written by one engineer alone, and an FMEA that spans the whole plant and is never completed.
Choosing the team
A useful PFMEA team has the process owner, an operator or setup person who runs the process, quality, maintenance and, where relevant, design and supplier quality. Five to seven people is typical. People who know the process daily find causes that engineers miss. Record attendance because customers and auditors often ask who contributed.
Common mistakes
Do not skip the baseline question: a carry-over FMEA from a similar part saves days, but only if the team reviews what changed. Do not leave rating scales undefined, since two teams scoring the same failure differently makes the results incomparable. Do not let the kickoff date slip without updating the draft deadline.
Frequently Asked Questions
Is this the same as the FMEA form?
No. This is the planning page that comes before the FMEA worksheet itself. It records scope, team, timing and rules so the worksheet work stays focused and defensible in audits.
What are the 5Ts?
Intent, timing, team, task and tools. They are the planning questions in the AIAG-VDA method: why the FMEA is done, when it must finish, who participates, what is analyzed and which methods and forms are used.
Do I need one kickoff per FMEA?
Yes for new FMEAs. For a revision of an existing FMEA, a shorter kickoff that records what changed and who reviews it is usually enough, as long as the scope statement is updated.
Who should sign it?
Typically the facilitator, the process or design owner and the quality manager. Follow your own quality procedure and any customer-specific requirements if they differ.
If your FMEA inputs live across ERP routings, NCRs and scrap history, Netray can pull them into one prepared package. Ask for a short review.
Related Tools
FMEA Failure Mode Brainstorm Worksheet
Capture process steps, functions, failure modes, effects and causes in one structured table before you score severity, occurrence and detection.
Quality & InspectionFMEA Recommended Actions Tracker Worksheet
Track each FMEA action with owner, due date, status and before-and-after ratings, with RPN and RPN reduction calculated automatically.
Quality & InspectionFMEA Lessons Learned and Carry-Over Review Template
A structured document to capture what escaped, why the FMEA missed it and which lines and controls need updating.
Quality & InspectionFMEA RPN and Risk Reduction Calculator
Compare RPN before and after an action and see how much each rating contributes to the reduction.
More Quality & Inspection tools
See all- Cpk Confidence Interval Calculator
- Pp Ppk Process Performance Calculator
- DPMO and Sigma Level Calculator
- X-bar and R Control Chart Limits Worksheet
- Control Chart Constants Table (A2, D3, D4, d2, c4)
- P Chart Control Limits Calculator
- Defect Pareto Analysis Worksheet
- DMAIC Project Charter Template
- SIPOC Diagram Template