# FMEA Team Kickoff and Scope Template > Source: https://netray.co/tools/fmea-team-kickoff-scope-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A one-page planning document that fixes the FMEA scope, team, boundaries and rating scales before anyone writes a failure mode. ## Category quality ## Industry Manufacturing ## Audience - Quality engineer - Reliability engineer - Process engineer ## Tool **Kind:** template **Output:** document **Fields:** #### Company **Key:** company **Type:** text **Default:** Acme Precision Ltd #### FMEA type **Key:** fmea_type **Type:** select **Options:** - Process FMEA - Design FMEA - System FMEA - Supplemental FMEA-MSR **Default:** Process FMEA #### Subject (part, process or system) **Key:** subject **Type:** text **Default:** Aluminum housing, CNC machining line 3 #### Customer or program **Key:** customer **Type:** text **Default:** Hydraulic pump program #### Purpose of this FMEA **Key:** intent **Type:** textarea **Default:** Identify and reduce risk of dimensional and surface defects on the housing before PPAP submission. #### In scope **Key:** in_scope **Type:** textarea **Default:** Receiving inspection, OP10 to OP60 machining, washing, final inspection, packing. #### Out of scope **Key:** out_scope **Type:** textarea **Default:** Casting supplier process, customer assembly line. #### FMEA facilitator **Key:** leader **Type:** text **Default:** A. Rao, Quality Engineering #### Kickoff date **Key:** start **Type:** date **Default:** 2026-11-03 #### Draft complete by **Key:** due **Type:** date **Default:** 2026-11-24 #### Baseline or carry-over FMEA **Key:** baseline **Type:** text **Default:** PFMEA-0412 rev C (similar housing) **Blocks:** #### FMEA Kickoff and Scope **Body:** Company: {{company}} FMEA type: {{fmea_type}} Subject: {{subject}} Customer or program: {{customer}} Facilitator: {{leader}} #### 1. Purpose (why are we doing this) **Body:** {{intent}} #### 2. Scope and boundaries **Body:** In scope: {{in_scope}} Out of scope: {{out_scope}} Baseline or carry-over: {{baseline}} #### 3. Timing **Body:** Kickoff: {{start}} Draft complete: {{due}} #### 4. Cross-functional team **Table:** **Columns:** - Name - Function - Role - Meeting attendance **Rows:** **1:** Quality **2:** Facilitator **1:** Manufacturing engineering **2:** Process owner **1:** Production **2:** Operator voice **1:** Design or product engineering **2:** Requirements **1:** Maintenance **2:** Equipment **1:** Supplier quality **2:** Inputs #### 5. Inputs to collect before the first session **Table:** **Columns:** - Input - Owner - Due - Received **Rows:** **0:** Process flow diagram **0:** Drawings and special characteristics **0:** Customer requirements and CSRs **0:** Scrap, rework and complaint history **0:** Previous FMEAs and lessons learned **0:** Rating scales (S, O, D) and action rules #### 6. Agreed rules **Body:** Rating scales used: ______ Action threshold: ______ How often the team meets: ______ Who approves the final FMEA: ______ #### Approvals **Signatures:** - FMEA facilitator - Process owner - Quality manager **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the template **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### Is this the same as the FMEA form? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms fmea kickoff template, fmea scope template, fmea planning and preparation, fmea team charter, 5t fmea planning, pfmea scope definition, fmea project plan template, fmea boundary diagram scope --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json