HomeGlossaryEngineering Change Proposal (ECP)
Systems EngineeringECP

Engineering Change Proposal (ECP)

An Engineering Change Proposal (ECP) is the formal mechanism for proposing a change to an approved configuration baseline on a government contract, requiring evaluation and approval before implementation.

Quick answer

An Engineering Change Proposal (ECP) is the formal mechanism for proposing a change to an approved configuration baseline on a government contract, requiring evaluation and approval before implementation.


An Engineering Change Proposal (ECP) is the formal document used in government contracting to propose a modification to an approved configuration baseline, a change in the system's design, materials, software, or specifications, that must be evaluated and approved by the Configuration Control Board (and often the government) before it can be implemented.

What is an Engineering Change Proposal?

MIL-HDBK-61 and the program's Configuration Management Plan establish the ECP process. When a change is needed to the approved configuration, whether due to a technical problem discovered in testing, a new requirement, a material substitution, or a cost reduction opportunity, the originator prepares an ECP that describes the proposed change, its technical justification, and its impact on cost, schedule, performance, and interfaces.

ECPs are classified as Class I or Class II. Class I ECPs affect the form, fit, or function of the item and require formal government approval through the Configuration Control Board (CCB) before implementation. Class II ECPs are minor deviations that do not affect the items' performance requirements, interchangeability, or interfaces, and may be approved at the contractor level per approved CM plan delegation. The classification decision is made by the Configuration Manager based on the nature of the change.

An ECP package typically includes: a description of the existing configuration and the proposed change, the reason for the change (problem report, requirements change, design improvement), a technical analysis demonstrating the change meets requirements, manufacturing and quality plan changes, cost and schedule impact assessment, and a retrofit plan (what happens to units already built). Large ECPs on complex systems may require their own cost and schedule estimates, interface impact analyses, and safety assessments.

Why ECPs matter for government contractors

Unauthorized changes to an approved baseline, implementing a change without ECP approval, are a serious configuration management deficiency. Beyond audit risk, unauthorized changes can create fleet divergence where some units are built to different configurations, making maintenance and troubleshooting significantly more difficult. Proper ECP discipline protects both the contractor and the operational user.

Example

During production, a defense electronics contractor discovers that a critical integrated circuit has been discontinued by the manufacturer. A substitute part with comparable performance is available, but its pinout and footprint differ slightly. The contractor prepares a Class I ECP documenting the original part, the substitute, the technical equivalence analysis, updated drawings, and the manufacturing change plan. The government CCB reviews and approves the ECP. The contractor implements the change starting with the next production unit and documents the change-effective unit number in the production records.

Frequently Asked Questions

What is the difference between an ECP and a deviation or waiver?


An ECP proposes a permanent change to the approved configuration baseline. A deviation permits departure from a specified requirement before manufacturing, with the understanding that future items will conform. A waiver allows acceptance of a nonconforming item after manufacturing. Deviations and waivers are one-time exceptions; ECPs are permanent baseline changes.

How long does ECP approval take?


Timeline varies significantly by complexity and government workload. Simple Class I ECPs may be approved in two to four weeks. Complex ECPs affecting safety, interoperability, or Key Performance Parameters can take months, particularly when they require independent technical review or Congressional notification. Contractors should submit ECPs as early as possible to avoid production disruptions.

What is a Value Engineering Change Proposal (VECP)?


A VECP is a type of ECP proposed by the contractor specifically to reduce costs while maintaining required performance. If approved and implemented, the government shares in the cost savings according to the sharing formula in the contract. VECPs incentivize contractors to find innovative cost reduction opportunities throughout the production program.

Can a subcontractor submit an ECP?


Subcontractors propose changes to the prime contractor, who evaluates the impact on the system and submits the ECP to the government if a Class I change is involved. Subcontractors generally do not submit ECPs directly to the government unless their subcontract specifically authorizes direct access to the government CCB.

How Bidovate helps

Bidovate puts Engineering Change Proposal (ECP) to work inside your capture and proposal workflow.

Federal contracting

See Bidovate in action

Book a demo and we will show you the platform using your actual contract data.