The Preliminary Design Review (PDR) is a technical assessment that establishes the Allocated Baseline of a system to ensure a system is operationally effective. A PDR is conducted before the start of detailed design work and is the first opportunity for the Government to closely observe the Contractor’s hardware and software design. This review assesses the allocated design documented in subsystem product specifications for each configuration item in the system and ensures that each function, in the Functional Baseline, has been allocated to one or more system configuration items.
Definition: The Preliminary Design Review (PDR) is a review conducted to evaluate the progress, technical adequacy, and risk resolution of the selected design approach for one or more configuration items; to determine each design’s compatibility with the requirements for the configuration item; to evaluate the degree of definition and assess the technical risk associated with the selected manufacturing methods and processes; to establish the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment, facilities, software and personnel; and, as applicable, to evaluate the preliminary operational and support documents. – ISO/IEC/IEEE. 2009. Systems and Software Engineering – System and Software Engineering Vocabulary (SEVocab).
Purpose of the Preliminary Design Review (PDR)
The PDR establishes the allocated baseline (hardware, software, human/support systems) and underlying architectures to ensure that the system under review has a reasonable expectation of satisfying the requirements within the currently allocated budget and schedule.
Fact Sheet: Preliminary Design Review (PDR) Fact Sheet
When to conduct a Preliminary Design Review: 
The PDR should be conducted when the allocated baseline has been achieved, allowing the detailed design of hardware and software CIs to proceed. A rule of thumb is that 10 percent to 25 percent of product drawings and associated instructions should be complete and that 100 percent of all safety‐critical component (Critical Safety Items and Critical Application Items) drawings are complete.
The PDR should be conducted when all major design issues have been resolved and work can begin on detailed design. The PDR should address and resolve critical, system‐wide issues before detailed design begins. 
For complex systems, a PDR may be conducted incrementally for each configuration item. These incremental reviews lead to an overall system-level PDR. System-level performance is supported by compliance with Interface Control Documents, but not assured. Interface requirements make up each configuration item Allocated Specification.
Completion of the PDR should provide the following:
- An established system allocated baseline,
- An updated risk assessment for the Engineering, Manufacturing, and Development (EMD) Phase,
- An updated Cost Analysis Requirements Description (CARD) or CARD-like document based on the system allocated baseline,
- An updated program schedule including system and software critical path drivers, and
- An approved Life-Cycle Sustainment Plan (LCSP) updating program sustainment development efforts and schedules.
A successful PDR is predicated on the determination that the subsystem requirements, subsystem preliminary design, results of peer reviews, and plans for development, testing, and evaluation form a satisfactory basis for proceeding into detailed design and test procedure development. 
The Weapons System Acquisition Reform Act of 2009 directed the PDR to:
- PDRs before Milestone (MS) B is mandatory for all Major Defense Acquisition Programs (MDAP) and will be reflected in the Technology Development Strategy (TDS) to be approved by the MDA at MS A. Post-PDR assessments will be conducted in association with MS B preparations and will be formally considered by the Milestone Decision Authority (MDA) at the MS B certification review.
- The timing of PDRs for other than MDAPs will be approved by the DoD Component MDA when consistent with TDS or Acquisition Strategy objectives. When the PDR is conducted before MS B, a post-PDR assessment will be conducted in association with the MS B review and formally considered by the MDA at the MS B review. If the PDR is conducted after MS B, the MDA will conduct a post-PDR assessment at a time reflected in the approved acquisition strategy.
- PDR before MS B is now a statutory requirement for MDAPs. The post-PDR assessment will be conducted during the MS B review, and prior to the section 2366b certification by the MDA per title 10, Unites States Code.
Where a Preliminary Design Review (PDR) is conducted to ensure new technologies are mature enough to be integrated into a product subsystem to form its allocated baseline. A Critical Design Review (CDR) is focused on determining if a system can meet its stated performance requirements within cost, schedule, and risk.
- The Program Manager (PM) should conduct the PDR when all major design issues have been resolved and work can begin on the detailed design. The PDR should address and resolve critical, system-wide issues.
- IEEE 5288.2 “Standard for Technical Reviews and Audits on Defense Programs” is the standard for technical reviews and audits to be performed throughout the acquisition life cycle for the US Department of Defense (DoD) and other defense agencies. This standard guides the DoD and contractor on what is required during an SRR
- The PDR should be conducted when the allocated baseline has been achieved, allowing the detailed design of hardware and software configuration items to proceed. A rule of thumb is that 10 percent to 25 percent of product drawings and associated instructions should be complete and that 100 percent of all safety-critical component (Critical Safety Items and Critical Application Items) drawings are complete.
AcqLinks and References:
- Defense Acquisition Guidebook
-  Preliminary Design Review (PDR) Fact Sheet
- Preliminary Design Review Checklist – Jan 2015
- PDR Risk Assessment Checklist
- PDR Success/Exit Criteria Questions
- NAVAIR Instruction 4355.19D – Systems Engineering Technical Review
- OSD Guide to Best Practices Using Engineering Standards – April 2017