Critical Design Review (CDR)

A Critical Design Review (CDR) is the formal technical review that evaluates whether a system's detailed design documentation is complete, requirements-compliant, and mature enough to authorize the beginning of hardware fabrication, software coding, or production, and formally establishes the Product Baseline.

What is a Critical Design Review?

The CDR is the culminating design review in the DoD acquisition process, following the Preliminary Design Review. It demonstrates that the detailed design is fully defined, all requirements are traceable through analysis and test plans, interfaces are controlled, and the system can be built within the established cost and schedule. CDR success effectively closes the design phase and opens the fabrication, integration, and test phase.

CDR success criteria typically include: detailed design drawings and specifications complete for all hardware components, software detailed design documentation complete for all software items, all requirements verified through analysis, inspection, test, or demonstration (with verification methods documented in a Verification Cross-Reference Matrix), Technical Performance Measures at or above threshold values, no unresolved critical technical risks, build-to documentation complete, and the product baseline ready for government approval.

On large programs, CDR is conducted at the subsystem level first and then rolled up to a System-level CDR. Software-intensive programs may conduct a Software CDR (SWCDR) separately from the hardware CDR. After a successful CDR, the Product Baseline is approved and controlled through the configuration management process, and changes require formal Engineering Change Proposals.

Why the CDR matters for government contractors

CDR is one of the highest-stakes program events in defense contracting. A successful CDR authorizes the commitment of fabrication and production resources, which represent the majority of the program's cost. Entering fabrication without a complete, verified design is a primary driver of expensive rework and cost growth on DoD programs. The readiness of the CDR package directly affects the program's cost and schedule risk going forward.

Example

An Army combat vehicle prime contractor holds a system-level CDR after completing 14 subsystem CDRs over six months. The system CDR finds one open action item: the vehicle's cooling system thermal analysis shows a 3-degree margin against the maximum electronic bay temperature limit under desert conditions. The CDR board approves proceeding with fabrication while requiring resolution of the thermal margin issue through a test and analysis plan within 90 days. The engineering team closes the action item by adding a supplemental cooling duct, validated by environmental chamber testing.

Frequently Asked Questions

What documents must be complete for a CDR?

Required CDR documentation typically includes: engineering drawings (released at "production" or "approved for fabrication" status), Interface Control Documents (final), Software Design Documents, Verification Cross-Reference Matrix (mapping all requirements to verification methods), test plans, System Safety Analysis, and updated cost and schedule estimates. The specific documentation requirements are defined in the program's Systems Engineering Plan and the CDRL.

What is the Product Baseline and when is it established?

The Product Baseline documents the as-designed configuration of the system, the complete set of engineering documentation that defines what will be built. It is formally approved at or shortly after CDR completion. Changes to the Product Baseline after CDR require Class I ECPs approved by the Configuration Control Board and typically the government.

How long does a CDR typically take to conduct?

Subsystem CDRs may be conducted over one to two days. System-level CDRs for complex programs can extend over one to two weeks, covering multiple review boards, data packages, and action item resolution sessions. Total CDR preparation time (from design freeze to CDR completion) typically spans three to six months for major programs.

What is the risk of entering CDR before the design is truly complete?

Entering CDR with an immature design results in a high number of open action items, CDR failure, or program delay while the design matures. More seriously, if a contractor proceeds to fabrication without completing the CDR properly, design defects discovered during manufacturing cause expensive rework and schedule slips. Government program offices are increasingly scrutinizing CDR readiness criteria to prevent premature CDR completion.