# PCBA RMA Failure Analysis Report Template

> Source: https://netray.co/tools/pcba-rma-failure-analysis-report-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A structured report for returned boards: incoming condition, test results, root cause, containment and corrective action.

## Category

quality

## Industry

Electronics Manufacturing

## Audience

- Quality engineer
- Failure analysis engineer
- Customer quality manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Lakeshore Electronics Assembly

#### RMA number

**Key:** rma_no

**Type:** text

**Default:** RMA-26-0377

#### Customer

**Key:** customer

**Type:** text

**Default:** Northgate Controls

#### Assembly part number / revision

**Key:** assy_pn

**Type:** text

**Default:** PCBA-17730 Rev A

#### Serial number / date code

**Key:** serial

**Type:** text

**Default:** SN 38412 / DC 2541

#### Date received

**Key:** rcv_date

**Type:** date

**Default:** 2026-10-12

#### Report date

**Key:** report_date

**Type:** date

**Default:** 2026-10-20

#### Reported failure

**Key:** failure_mode

**Type:** textarea

**Default:** Unit intermittently resets after 20 minutes of operation in the field. No fault found at customer incoming test.

#### Analysis findings

**Key:** findings

**Type:** textarea

**Default:** Fault reproduced under thermal cycling from 20 C to 70 C. X-ray and cross-section of U5 BGA show a cracked solder joint at corner ball G1 with a thin intermetallic layer and head-in-pillow indication.

#### Root cause

**Key:** root_cause

**Type:** textarea

**Default:** Warpage of the BGA package at peak reflow temperature led to a head-in-pillow defect. The profile soak was marginal for the lot and the joint passed AOI because it is not visible from the top.

#### Cause category

**Key:** category

**Type:** select

**Options:**

- Assembly process
- Component
- PCB fabrication
- Design
- Handling / ESD
- Customer use / abuse
- No fault found

**Default:** Assembly process

#### Corrective and preventive action

**Key:** corrective

**Type:** textarea

**Default:** Reflow profile soak time extended and re-validated with thermocouples on a BGA. Added X-ray sampling for this part. Reviewed other lots built with the same profile.

#### Containment

**Key:** containment

**Type:** textarea

**Default:** Quarantined 85 units in finished goods. Sample X-ray found two suspect units, which were reworked. Customer notified of affected serial range.

**Blocks:**

#### Failure Analysis Report {{rma_no}}

**Body:** Company: {{company}}
Customer: {{customer}}
Assembly: {{assy_pn}}
Serial / date code: {{serial}}
Received: {{rcv_date}}   Report date: {{report_date}}

#### Reported failure

**Body:** {{failure_mode}}

#### Analysis steps performed

**Table:**

**Columns:**

- Step
- Method
- Result
- Evidence ref

**Rows:**

**0:** Incoming visual

**1:** Microscope, photos

**0:** Electrical verification

**1:** Functional test, ICT

**0:** Fault reproduction

**1:** Thermal, vibration or load

**0:** Non-destructive analysis

**1:** X-ray, thermal imaging

**0:** Destructive analysis

**1:** Cross-section, dye and pry

**0:** Material / records review

**1:** Traveler, lot, profile data

#### Findings

**Body:** {{findings}}

#### Root cause

**Body:** Category: {{category}}

{{root_cause}}

#### Containment

**Body:** {{containment}}

#### Corrective and preventive action

**Body:** {{corrective}}

#### Approvals

**Signatures:**

- Failure analysis engineer
- Quality manager
- Customer acknowledgement

**Notes:** Replace or extend with your customer's required format (for example 8D) when specified. Do not conclude root cause from visual inspection alone when the failure was intermittent; reproduce the fault first.

## Content

**Intro:** A returned board is the cheapest source of process knowledge you will ever get, but only if the analysis is documented. This report template guides the analysis from reported symptom to verified root cause and corrective action.

**Sections:**

#### How to use the template

**Body:** Complete the header and describe the failure exactly as reported. Work through the analysis table in order, starting with non-destructive steps so you do not destroy evidence. Write down findings with photos or X-ray images, then state the root cause and its category. Containment covers suspect inventory and customer notification, and corrective action covers the fix and its verification. Export to PDF or Word for the customer.

**Bullets:**

- Photograph the unit as received before touching it.
- Reproduce the fault before sectioning or reworking.
- Check traveler, lot and profile records for the serial number.
- Look for other units built under the same conditions.

#### The analysis logic

**Body:** The order matters. Visual and electrical checks come first, then non-destructive imaging such as X-ray and thermal camera, and only then destructive methods such as cross-section or dye and pry. Root cause means the underlying reason that allowed the defect to escape, not only the physical failure. In the example, a cracked BGA ball is the failure; warpage with a marginal profile is the cause; AOI blind spots on area array joints explain why it escaped.

#### Worked example

**Body:** A controller resets intermittently in the field. The lab reproduces the fault with thermal cycling, sees a cracked BGA corner joint on X-ray and confirms head-in-pillow in a cross-section. Records show the lot was built with a marginal soak profile. Containment quarantines stock and checks a sample by X-ray. The corrective action updates the profile, adds X-ray sampling and reviews other lots. The report closes the loop with the customer.

#### Common mistakes

**Body:** Teams often close an RMA as no fault found after one functional test, even though the failure was intermittent. Others stop at the physical symptom and never reach the process cause. Another mistake is skipping the review of other serials from the same lot; if one unit has the defect, others probably do too. Always tie corrective action to a measurable check.

**Cta:** If you want RMA findings linked to ERP lot and work order history automatically, we can build that traceability on your own infrastructure.

**Faq:**

#### What is the difference between an RMA report and an 8D?

**Answer:** An RMA failure analysis report documents the investigation of a returned unit. An 8D is a team-based problem solving format with defined disciplines including containment, root cause verification and prevention. Many customers require 8D for significant failures; this report can feed it.

#### How long should a failure analysis take?

**Answer:** Many customers expect an initial response within a few days and a full report within two to four weeks, depending on contract terms and complexity. Intermittent faults and destructive analysis can take longer.

#### What if no fault is found?

**Answer:** Record every test performed and the conditions. Try stress methods such as thermal cycling and vibration, review the customer environment and ask for application details. A no fault found conclusion is only credible if the analysis was thorough.

#### Should I rework a returned board?

**Answer:** Not before the analysis is complete. Rework destroys evidence. Once the root cause is verified and documented, follow the customer's instruction on repair, scrap or return.

## Search terms

rma failure analysis report template, pcba failure analysis report, returned board analysis template, customer return report electronics, 8d report pcb assembly, field failure analysis template, ems rma form, root cause analysis pcba

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json