Approval Route Comparison

EMPB vs ISIR vs PPAP for Injection Molded Parts

EMPB, ISIR and PPAP should not be treated as a universal three-level approval hierarchy. The correct route depends on the customer-specified quality framework, submission form, required evidence and approval rules. Before preparing the package, confirm what the customer actually means by the requested term and which records must be submitted.

EMPB First-sample / approval reporting typically defined by VDA or customer-specific requirements.
ISIR Initial-sample inspection evidence whose exact scope is normally defined by the customer.
PPAP Formal production-part approval route with customer-defined submission requirements.
Approval Route Reference Customer Requirement First
EMPB ISIR and PPAP approval route comparison for injection molded parts based on customer-specific submission requirements
The requested acronym identifies the starting route; the actual evidence package is controlled by the applicable customer requirement.

Core rule: do not infer approval scope from the acronym alone. If the requirement is unclear, confirm the applicable standard, required form, submission level, approval owner and resubmission rules. Broader validation logic belongs in the injection mold validation and approval guide .

EMPB Scope

What Does EMPB Mean in a Customer Approval Process?

EMPB is commonly used for first-sample inspection and approval reporting in VDA or customer-specific quality environments. It can document conformity to the released drawing and agreed requirements, but the acronym alone does not define one universal submission package.

Typical Role

What an EMPB Route Commonly Establishes

  • Sample identity: link the submitted part, drawing revision and inspection basis to one controlled approval record.
  • Conformance evidence: record dimensional, material, visual or other required results in the applicable customer format.
  • Release status: support approval, conditional release or resubmission under the defined customer process.
Do Not Assume

What “EMPB” Does Not Define by Itself

  • It does not define one fixed global document list or universal approval depth.
  • It does not mean every customer uses the same form, portal or evidence package.
  • It should not be treated as a lower-level version of PPAP without checking the applicable customer requirement.
EMPB Rule

Confirm the governing requirement before preparing the package. Check the customer manual, specified form or portal, required evidence, approval owner and resubmission rules instead of relying on “EMPB” alone.

Authority reference: VDA Volume 2, Production Process and Product Approval (PPA), emphasizes agreement between the organization and customer on the applicable approval scope and documentation rather than relying on fixed submission levels. VDA QMC reference .
ISIR Scope

What Does ISIR Usually Cover in an Initial Sample Review?

ISIR commonly refers to an Initial Sample Inspection Report used to document whether submitted samples conform to defined drawing or customer requirements. In practice, the report may center on dimensional and sample evidence, but its exact contents are normally controlled by the customer’s own quality requirements.

01 · Identify

Controlled Sample Basis

Link the inspected sample to the correct part number, drawing revision, sample or cavity identity and applicable inspection scope.

02 · Inspect

Drawing-Linked Results

Record the dimensional or other required results using the customer’s defined format, characteristic list or inspection requirements.

03 · Confirm

Required Submission Scope

Verify whether the customer expects only an initial-sample report or additional approval records beyond the ISIR itself.

ISIR Boundary

Do not treat “ISIR” as a universal global submission level. The term may describe a customer-required initial-sample report, but the governing specification, required attachments, approval form and resubmission rules must still be confirmed for the individual program.

PPAP Scope

What Makes PPAP a Production-Part Approval Route?

PPAP is a formal production-part approval process used to show that engineering and customer requirements can be met through the defined manufacturing process under production conditions. The required submission still depends on the customer, submission level and applicable customer-specific requirements.

Production Evidence

What PPAP Adds Beyond a Sample Report

  • Process definition: evidence extends beyond the inspected sample to the manufacturing process used to produce it.
  • Control and measurement evidence: required process-control, measurement-system or capability records may form part of the submission.
  • Formal release: the package supports customer approval of the production part and its defined manufacturing conditions.
Scope Boundary

What This Comparison Page Should Not Rebuild

  • Do not reproduce the full PPAP element list or teach each PPAP record here.
  • Do not assume every customer requests the same submission level or identical submitted and retained evidence.
  • Do not use “PPAP” as a generic label for every supplier quality document requested before production.
Detailed PPAP

Once PPAP is confirmed as the required route, use the PPAP Level 3 document list for the customer-defined submitted and retained evidence requirements.

Authority reference: AIAG defines PPAP as the industry standard for the production part approval process, used to confirm that engineering design and specification requirements can be consistently met during an actual production run at production rates. AIAG PPAP reference .
Core Comparison Matrix

EMPB vs ISIR vs PPAP: Evidence and Approval Route Comparison

Use this matrix to compare the role of each route, not to rank them as fixed approval levels. The actual submission package must still follow the customer’s applicable standard, specified form, required evidence and approval instructions.

Decision Point EMPB ISIR PPAP
Primary Approval Question Do the submitted first samples and required records meet the customer’s defined approval basis? Do the inspected initial samples conform to the specified drawing or inspection requirements? Can the defined production process produce parts that satisfy engineering and customer requirements?
Typical Framework Often used in VDA-oriented or customer-specific first-sample approval processes. Usually a customer-defined initial-sample inspection or reporting requirement. AIAG-based production-part approval process with customer-specific requirements.
Sample Conformity Evidence Commonly includes controlled sample identity, drawing-linked results and other customer-required first-sample evidence. Commonly centered on measured initial-sample results and traceable inspection records. Includes dimensional or part-conformance evidence as part of a broader production approval package.
Process Evidence May be required depending on the governing customer approval process; do not assume one fixed scope. Not defined by the ISIR name alone; additional process evidence depends on customer requirements. Process-control, measurement-system or capability evidence may be required according to the submission level and customer.
Approval Record Customer-specific EMPB / first-sample report or approval format. Customer-defined ISIR form, inspection report or portal record. Formal customer submission and approval record under the required PPAP route.
Customer-Specific Override Always confirm the required VDA/customer form, evidence fields and release workflow. Always confirm the customer’s exact report scope, attachments and acceptance method. Always confirm submission level, customer-specific requirements and required submitted versus retained evidence.
Resubmission Trigger and scope depend on the customer’s approval rules and the nature of the change. Repeat or partial update depends on affected samples, characteristics and customer instructions. Resubmission depends on applicable PPAP and customer-specific change / notification requirements.
Read the Matrix This Way

Choose the route from the customer requirement, not from the acronym alone. If the project only needs traceable first-article measurement evidence, review the injection molding FAI report . If the customer has formally selected PPAP, use the dedicated PPAP document page rather than expanding the complete PPAP package here.

Customer Requirement Decoder

What Should You Confirm Before Choosing EMPB, ISIR or PPAP?

If the customer only writes “EMPB,” “ISIR” or “PPAP,” do not build the submission package from the acronym alone. Confirm the governing requirement, expected form, evidence scope and approval workflow before inspection or document preparation begins.

Check 01

Applicable Standard or Manual

Identify the named standard, customer manual or supplier quality requirement that controls the submission.

Check 02

Required Form or Template

Confirm whether the customer provides an EMPB form, ISIR sheet, PPAP format or proprietary portal template.

Check 03

Submission Level or Scope

Ask which records must be submitted, retained, uploaded or approved for this specific project.

Check 04

Sample and Cavity Scope

Confirm which samples, mold cavities or part variants must be represented in the approval evidence.

Check 05

Production-Run Expectation

Determine whether initial samples are enough or whether the customer expects production-representative process evidence.

Check 06

Approval Owner

Identify who reviews and releases the package: buyer, SQE, plant quality, engineering or another customer function.

Check 07

Portal and Naming Rules

Verify required upload location, document naming, revision coding and record-format rules before submission.

Check 08

Customer-Specific Evidence

Confirm any additional dimensional, material, functional, control or traceability records required beyond the named route.

Check 09

Resubmission Triggers

Ask which product, tooling, material, process or site changes require partial or full resubmission.

Decision Rule

The safest route is the one explicitly tied to the customer’s documented requirement. If the required form, submission scope or approval owner is unclear, clarify those points before building dimensional layouts, process records or portal packages.

Resubmission Triggers

What Changes Can Trigger EMPB, ISIR or PPAP Resubmission?

A change does not automatically mean a full resubmission. The correct response depends on what changed, which approved characteristics or process conditions may be affected, and what the customer’s approval rules require. Start with impact review, then define whether no update, a targeted update or a broader resubmission is needed.

Change Trigger What to Review Likely Action Key Boundary
Drawing or Specification Revision Identify affected dimensions, materials, functions or approval characteristics. Targeted or broader update depending on revision impact. Do not repeat unaffected evidence unless the customer requires it.
Tooling or Cavity Modification Review changed steel, geometry, cavity identity and affected molded characteristics. Partial / cavity-specific update may be sufficient. A local cavity repair does not automatically require a complete package rebuild.
Material or Approved Source Change Check whether material specification, performance or traceability basis changes. Impact review first; update evidence if affected. Customer notification or approval rules may control the scope.
Process, Equipment or Site Transfer Review whether approved manufacturing conditions, controls or production location have changed. Broader resubmission may be required when the approved process basis changes. Scope must follow the applicable customer-specific requirement.
Customer-Requested Reapproval Confirm the stated trigger, required format and evidence requested by the customer. Follow the defined customer submission scope. Customer instruction overrides generic route assumptions.
Resubmission Rule

Use change impact to define scope. Reconfirm the affected part, cavity, characteristic, material, process or site first; then apply the customer’s notification and approval requirement to decide whether the response is targeted, partial or full.

Supplier Evidence Review

What Should Buyers and SQEs Verify Before Accepting the Submission Route?

Before accepting a supplier’s claimed EMPB, ISIR or PPAP route, reviewers should confirm that the requirement source, submitted samples, inspection evidence, process evidence and release record all belong to the same controlled approval basis.

Requirement Source

Verify the customer manual, specified form, submission level or portal instruction that defines what the supplier is expected to submit.

Sample and Revision Identity

Confirm that the inspected part number, drawing revision, mold or cavity identity and sample source match the approval record.

Inspection Evidence

Check that dimensional, material, functional or other required results are traceable to the submitted samples and required characteristics.

Process Evidence When Required

If the route includes production-process approval, verify that the required process-control or capability records correspond to the approved manufacturing conditions.

Release and Open Issues

Confirm approval status, open deviations, conditional releases, missing records and any action that must be closed before the customer accepts the package.

Review Rule

Do not judge the package by document count alone. A stronger submission is one in which the customer requirement, sample identity, evidence and release decision can be traced without reconstructing the approval history manually.

Downloadable Engineering Reference

Download the EMPB / ISIR / PPAP Approval Comparison Sheet

This updated 4-page engineering reference helps buyers, SQEs and suppliers compare the three approval routes without treating them as a fixed hierarchy. Use it to clarify the required route, evidence scope and resubmission logic before the package is prepared.

  • Route comparison: EMPB, ISIR and PPAP compared by approval question, framework and evidence role.
  • Evidence matrix: sample conformity, process evidence, approval record and customer-specific override.
  • Requirement decoder: the key questions to confirm when the customer names an acronym but does not define the scope.
  • Resubmission matrix: drawing, tooling, material, process, site and customer-triggered change review.
  • Supplier review: requirement source, sample identity, inspection evidence, process evidence and release status.
  • Approval worksheet: a practical record for documenting route, evidence and open issues before submission.
Approval Route FAQ

EMPB, ISIR and PPAP Frequently Asked Questions

Are EMPB, ISIR and PPAP fixed approval levels?

No. They should not be treated as a universal three-level hierarchy. The actual submission scope depends on the applicable quality framework, customer-specific requirement, required form and approval instructions.

What should I do if the customer only writes “EMPB,” “ISIR” or “PPAP”?

Confirm the governing standard or customer manual, required form, submission scope, sample or cavity coverage, approval owner and resubmission rules before preparing the package.

Can EMPB or ISIR require process evidence as well as sample inspection?

Yes. Additional process or production evidence may be required when the customer’s approval procedure calls for it. The acronym alone does not determine the complete evidence package.

Does every drawing, tooling or material change require a full resubmission?

No. The change should first be assessed for impact. Customer rules then determine whether the response is a targeted update, partial resubmission or broader reapproval.

If the route is already defined and you need manufacturing support, review our injection molding production support and PPAP, FAI and quality documentation support .

Approval Scope Review

Confirm Your Approval-Document Scope Before Submission

Send the drawing and the customer’s quality requirement, checklist, form or portal instruction. We can help identify which submission route and supporting evidence need to be clarified before the package is prepared.

Confirm Your Approval-Document Scope

Include the customer requirement or submission instruction where available.