Engineering Change Control
Quality & Inspection Standards
PRODUCTS CENTER
Get Custom Quote
PRODUCTS CENTER
Engineering Change Control Under GJB9001C
GJB9001C contains four distinct clauses addressing changes: Clause 6.3 (change planning), Clause 8.2.4 (changes to product/service requirements), Clause 8.3.6 (design and development changes), and Clause 8.5.6 (change control for production and service provision). Clause 8.3.6 requires organizations to identify, review, and control changes to products and services during design and development as well as subsequent changes, to ensure these changes do not adversely affect compliance with requirements.
For PCB manufacturers, engineering change control is the backbone of configuration management. Changes must be systematically identified, evaluated, approved, implemented, and verified — from initial customer requirement changes through production process optimizations and material substitutions. This guide provides a complete implementation roadmap covering the four change clauses, technical state change classification, ECR/ECO/ECN workflows, and audit preparation.
Engineering Summary
- GJB9001C contains four change clauses: 6.3, 8.2.4, 8.3.6, and 8.5.6 — each with distinct scope and requirements.
- Clause 8.3.6 (design changes) is most frequently applied for Gerber updates, stackup revisions, and material substitutions.
- Technical state changes are classified into Class I, II, and III under GJB 3206B — approval requirements escalate with impact level.
- Engineering changes that affect baselines become technical state changes and require customer consent.
- Standard change workflow: ECR (Request) → ECO (Review/Approval) → ECN (Notice/Execution).
- Key control points include version control, material transition management, trial production verification, and traceability.
1. What Auditors Check — A Quick Overview
| Audit Focus | What External Auditors Verify | Expected Evidence |
|---|---|---|
| Change Identification | Are design changes properly identified and documented? | Change requests, ECR/ECO records |
| Change Review & Evaluation | Are changes reviewed for impact on form, fit, function, reliability, safety, and cost? | Impact analysis reports, review minutes |
| Change Approval | Are changes approved by authorized personnel before implementation? | Approval signatures, authorization records |
| Customer Consent | Is customer consent obtained for changes affecting baselines or requirements? | Customer approval records, communication logs |
| Implementation & Tracking | Are changes properly implemented and tracked? | Updated documentation, revision history, MES records |
| Verification & Validation | Are verification activities conducted for significant changes? | Test reports, FAI records, validation records |
| Documented Information | Are records of changes, reviews, approvals, and actions retained? | Change control records, ECN files, configuration status accounting |
KEY INSIGHT:
Engineering change control is not optional — it is a mandatory requirement for all organizations in the military supply chain. Auditors will verify that changes are systematically controlled from identification through verification.
2. The Four "Change" Clauses in GJB9001C — Understanding the Differences
GJB9001C-2017 contains four distinct clauses addressing changes, each with different scope and requirements. Understanding which clause applies is essential for proper compliance.
| Clause | Scope | Description | PCB Application |
|---|---|---|---|
| 6.3 | Quality Management System | Changes to the QMS itself — organizational structure, processes, resources. Requires planned implementation considering purpose, consequences, system integrity, resources, and responsibilities. | Reorganizing the quality department, updating the document control system |
| 8.2.4 | Customer Requirements | Changes to product/service requirements — may originate from customer or organization. Requires review, documented information updates, and notification to all affected personnel. | Customer changes impedance requirement from 50Ω to 55Ω |
| 8.3.6 | Design & Development | Changes to design and development outputs throughout the lifecycle. Requires identification, review, control, and documented information. | Gerber file updates, stackup revisions, material substitutions |
| 8.5.6 | Production & Service | Changes during production and service provision. Requires review and control to ensure continued conformity. | Process parameter adjustments, equipment changes, inspection method updates |
3. Engineering Change vs. Technical State Change — Key Distinctions
Understanding the relationship between engineering changes and technical state changes is critical for GJB9001C compliance, as they are governed by different standards and have different approval pathways.
| Aspect | Engineering Change | Technical State Change |
|---|---|---|
| Definition | Permanent change to product technical state requiring baseline document updates | Change to formally approved technical state documentation within the product lifecycle |
| Scope | Broader — includes design, process, material, and documentation changes | Specifically addresses changes to baselines (functional, allocated, product) |
| Standard | Governed by GJB9001C Clauses 8.3.6 and 8.5.6 | Governed by GJB 3206A/B |
| Relationship | Engineering changes that affect baselines become technical state changes. All technical state changes are engineering changes, but not all engineering changes are technical state changes. | |
CRITICAL RULE:
When an engineering change affects functional, allocated, or product baselines, it must be controlled as a technical state change per GJB 3206 requirements.
4. Technical State Change Classification — Class I, II, and III
Under GJB 3206, technical state changes are classified into three categories based on impact level. Classification determines the approval authority and customer notification requirements.
4.1 Class I Changes (Major Changes)
Changes involving product functional and physical characteristics that affect reliability, safety, environmental adaptability, or performance after design finalization.
- PCB Examples: Material substitution (FR4 to high-frequency material), layer count change, impedance value change, surface finish change (ENIG to ENEPIG), critical dimension changes affecting fit or function
- Approval: Requires customer approval. For design-finalized products, Class I changes must be approved by the procuring party.
4.2 Class II Changes (General Changes)
General technical state changes that do not reach the impact level of Class I changes.
- PCB Examples: Minor material changes within approved families, process optimization not affecting electrical performance, non-critical dimensional adjustments, tolerance adjustments within specification limits
- Approval: For pre-design-finalization Class II changes, the contractor may self-approve and notify the customer; for post-design-finalization Class II changes, customer approval is required.
4.3 Class III Changes (Minor Changes)
Low-level technical changes that do not affect product quality or requirements fulfillment.
- PCB Examples: Errata corrections in documentation, drawing clarification, uniform annotation method updates, typographical corrections, non-technical clarifications
- Approval: Contractor may self-approve; no customer approval required.
5. The Six Principles of Technical State Change Control
GJB 3206B-2022 establishes six core principles for technical state change control that organizations must follow.
| Principle | Description | PCB Manufacturing Application |
|---|---|---|
| Classification Accuracy | Changes must be accurately classified according to definitions; classification cannot be arbitrarily changed | Properly classify PCB changes — don't downgrade a material substitution (Class I) to Class II to bypass approval |
| Sufficient Justification | Before submitting a change request, the proposing party must conduct comprehensive justification of necessity, correctness, and feasibility | Document why the PCB change is needed — cost reduction, supply chain issues, performance improvement — with supporting data |
| Test Verification | Verify the change plan through testing to confirm correctness, feasibility, and effectiveness | Conduct impedance testing, thermal cycling, or reliability testing to validate the change |
| Stakeholder Consensus | All affected departments and technical systems must have clear understanding and consensus on necessity and feasibility | Involve design, production, quality, procurement, and customer in the review process |
| Complete Approval | All affected technical state documents must be reviewed and approved according to defined responsibilities and procedures | Ensure all signatures are obtained — engineering manager, quality, customer (if required) |
| Full Implementation | All affected departments must implement and execute approved changes — including document updates, product realization, and supervision | Update Gerber files, fabrication drawings, BOMs, inspection criteria; train operators; verify first articles |
6. Engineering Change Control Process — The Seven Steps
The technical state change basic procedure consists of seven steps, from identifying the need through confirming completion.
| Step | Activity | PCB Example |
|---|---|---|
| 1 | Determine the Need — Any stakeholder may propose a change. Change category is generally determined by the contractor, with procuring party providing final confirmation if disagreements arise. | Customer requests impedance change; production identifies material availability issue; quality identifies reliability concern. |
| 2 | Submit Application — For Class I and II changes, prepare a change application document. Class III changes may proceed directly to a change notice. Application must have a unique identifier. | Submit ECR with change description, justification, impacted documents (Gerber, stackup, BOM), and supporting data. |
| 3 | Evaluate and Review — Different change categories require different review methods — meetings, counter-signatures, or hierarchical approval. Assess impact on product use, user requirements, schedule, cost, methods, and resources. | Cross-functional review involving design, production, quality, procurement, and cost control. Assess electrical performance risk, supply chain impact, process compatibility, and cost. |
| 4 | Approve and Decide — Approval is required before implementation. Approval authority depends on change classification: Class I (electrical/functional) → Chief Engineer; Class II (process) → Engineering Manager; Class III (documentation) → Supervising Engineer. | Obtain approval signature from appropriate authority. For Class I changes, obtain customer approval. |
| 5 | Prepare Change Notice — For Class I and II changes, prepare the change notice based on the approved application. For Class III changes, prepare directly according to established procedures. | Issue ECN with batch numbers, affected document list, and implementation instructions. |
| 6 | Implement the Change — Includes document updates (Gerber, drawings, BOMs with version control), material transition (parallel period ≤3 batches), trial production verification (first article → 50 pcs → functional testing → screening → sampling), and production switch. | Update Gerber files from V1.1 to V1.2; conduct trial run of 50 boards; perform impedance testing; update inspection criteria; verify first article. |
| 7 | Confirm Completion — Mark change batches with special labels; record change生效 serial number range in MES; compare DPPM for 3 batches before and after; analyze after-sales returns. | Label change batches with green ECN triangle mark; track quality metrics for 3 production batches; document effectiveness in closure report. |
7. PCB Manufacturing Change Scenarios — Practical Examples
7.1 Customer-Initiated Change
| Item | Description |
|---|---|
| Trigger | Customer requests impedance change from 50Ω to 55Ω |
| Change Class | Class I (affects electrical performance) |
| Required Actions | Submit ECR with impact analysis; obtain customer approval; update stackup and Gerber; conduct impedance verification testing; update fabrication drawing and inspection criteria |
| Documentation | Customer approval record, updated Gerber files, test reports, revised fabrication drawing |
7.2 Material Substitution Change
| Item | Description |
|---|---|
| Trigger | Original dielectric material discontinued by supplier |
| Change Class | Class I (material change affecting electrical and reliability characteristics) |
| Required Actions | Evaluate替代 material properties; conduct test verification (impedance, thermal cycling, CAF resistance); obtain customer consent; update BOM and material specifications; conduct FAI on first production batch |
| Documentation | Material qualification report, test verification records, customer approval, updated BOM, FAI report |
7.3 Process Optimization Change
| Item | Description |
|---|---|
| Trigger | Production proposes solder mask application process improvement |
| Change Class | Class II (process optimization not affecting form, fit, or function) |
| Required Actions | Conduct trial runs; verify solder mask adhesion and thickness; update process control documentation; notify customer of change |
| Documentation | Trial run records, verification test reports, updated process documents, customer notification |
7.4 Documentation Correction
| Item | Description |
|---|---|
| Trigger | Typographical error found in fabrication drawing notes |
| Change Class | Class III (no impact on product quality) |
| Required Actions | Correct the drawing; update revision; distribute updated document |
| Documentation | Updated fabrication drawing, revision history entry |
8. ECR, ECO, and ECN — Understanding the Three Documents
In PCB manufacturing, engineering changes are typically managed through three interconnected documents that form a complete workflow.
| Document | Full Name | Purpose | Stage |
|---|---|---|---|
| ECR | Engineering Change Request | "I want to change" — documents the change need, justification, and initial impact assessment | Initiation |
| ECO | Engineering Change Order | "Can we change and how" — documents the review, evaluation, and approval decision | Review & Approval |
| ECN | Engineering Change Notice | "Everyone follows the new standard" — communicates approved changes and implementation instructions | Implementation |
PROCESS FLOW:
ECR (Request) → ECO (Review/Approval) → ECN (Notice/Execution)
9. Key Control Points in PCB Engineering Change Management
9.1 Version Control
- Gerber files must be versioned (e.g., V1.1 → V1.2)
- All related documents must be updated consistently (Gerber, fabrication drawing, assembly drawing, BOM, test specifications)
- Old versions must be clearly identified and archived to prevent
9.2 Material Transition Management
- New and old part numbers may have parallel periods (typically ≤3 production batches)
- Consider in-transit purchased materials, work-in-progress semi-finished products, warehouse inventory, and already-shipped products
- Clearly define cut-off dates and disposal methods for old version materials
9.3 Trial Production Verification
- First article confirmation → small batch (50 pcs) → functional testing → environmental stress screening → shipment sampling
- First Article Inspection (FAI) per GJB 908 requirements
- Double inspection for first month after change implementation
9.4 Traceability
- Change batches marked with special labels (e.g., green ECN triangle mark)
- MES system records change serial number range
- Retain old version stencils for 3 months for reference
9.5 Emergency Change Process
- For line-stopping changes, require counter-signature within 2 hours (red ECN expedited process)
- Emergency changes still require subsequent formal documentation and approval
10. Change Control Documentation Requirements
Under GJB9001C Clause 8.3.6, organizations must retain documented information for all design and development changes.
| Required Documentation | Description |
|---|---|
| Design and development changes | Records of what was changed and why |
| Review results | Records of change reviews, including participants and decisions |
| Change authorization | Records of who approved the change |
| Actions taken to prevent adverse effects | Records of measures implemented to mitigate risks |
Additional requirements:
- Track implementation of design changes
- Conduct system analysis and verification for important design changes
- Follow prescribed approval procedures
- Design changes must comply with GJB 3206 technical state management requirements
- Computer software changes must comply with GJB 5235 software configuration management requirements
11. Common Audit Findings and How to Avoid Them
| Finding | Why It Happens | How to Avoid |
|---|---|---|
| "Changes not identified or documented" | Changes made informally without proper request documentation | Require ECR for all changes, no exceptions |
| "No impact analysis performed" | Changes implemented without assessing consequences | Mandate impact analysis as part of every ECR |
| "Changes implemented without approval" | Bypassing approval process to save time | Enforce "no approval, no implementation" rule |
| "Customer consent not obtained" | Not recognizing when changes affect baselines | Train staff on baseline identification and customer approval requirements |
| "Incomplete review records" | Reviews conducted but not documented | Use standardized review forms and retain meeting minutes |
| "Verification not performed" | Assuming change is safe without testing | Require test verification for all Class I and Class II changes |
| "Documentation not updated" | Change implemented but documents not revised | Include document update as a mandatory step in change implementation |
| "No traceability of implementation" | Unable to identify which products received the change | Implement batch marking and MES tracking systems |
12. Frequently Asked Questions
What is the difference between Clause 8.3.6 and Clause 8.5.6?
Clause 8.3.6 applies to design and development changes — changes to design outputs such as Gerber files, stackups, and specifications. Clause 8.5.6 applies to production and service provision changes — changes during manufacturing such as process parameters, equipment, and inspection methods.
When does an engineering change become a technical state change?
When an engineering change affects functional, allocated, or product baselines, it becomes a technical state change and must be controlled per GJB 3206 requirements.
What changes require customer approval?
Class I technical state changes and Class II changes after design finalization require customer approval. Any change affecting baselines also requires customer consent.
What is the difference between ECR, ECO, and ECN?
ECR (Engineering Change Request) initiates the change. ECO (Engineering Change Order) documents the review and approval decision. ECN (Engineering Change Notice) communicates approved changes for implementation.
How should change verification be conducted?
Change verification should be based on the change's impact. For significant changes, conduct system analysis and verification. For technical state changes, use test verification per GJB 3206 requirements.
What documented information must be retained for changes?
Organizations must retain records of: the change itself, review results, change authorization, and actions taken to prevent adverse effects.
Can Class III changes be implemented without approval?
Class III changes still require approval — just with lower-level authorization. They do not require customer approval but must follow established internal procedures.
How should change implementation be tracked?
Organizations must track implementation of design changes. For PCB manufacturing, this includes batch marking, MES system tracking, and post-change quality monitoring.
Related Standards & Topics
PCB Manufacturing for Military and Aerospace Programs
UltroNiu Electronics Group provides PCB and PCBA manufacturing services under GJB9001C-compliant engineering change control. Contact our engineering team for program-specific change management requirements.
Request Engineering ReviewReferences: GJB9001C-2017 Clauses 6.3, 8.2.4, 8.3.6, 8.5.6 (Central Military Commission Equipment Development Department); GJB 3206B-2022 Technical State Management; GJB 3206A-2010 Technical State Management. Technical state change classification and six principles sourced from GJB 3206B-2022. Change control procedures and PCB manufacturing examples based on industry best practices for military and aerospace PCB manufacturing. Courtesy of UltroNiu Engineering Knowledge Center.
Get Custom Quote
PRODUCTS CENTER
World-class PCB & PCBA manufacturer focused on high-frequency and high-reliability boards for defense, aerospace, automotive and industrial electronics.
You can unsubscribe at any time with a single click.
Copyright © 2025 UltroNiu Electronics Group All Rights reserved.