Preliminary Design Review

A Preliminary Design Review (PDR) is a formal design gate review held after the conceptual design phase and before detailed design begins. PDR verifies that: system requirements are complete and baselined, the selected design concept is feasible and addresses all requirements, requirements have been allocated to subsystems, key risks have been identified and mitigation plans are in place, the design approach is technically sound, and the project can proceed to detailed design within cost and schedule. PDR is the last gate before significant engineering resources are committed to a specific design direction.

PDR artifacts typically include: baselined system requirements specification, concept of operations, system architecture block diagram, interface definitions, preliminary BOM with rough cost estimates, risk register with top 10 risks and mitigations, verification approach for each requirement, and a preliminary schedule for detailed design through DVT. The review board — typically senior engineers and program management — evaluates whether each artifact is sufficiently mature to support proceeding.

PDR is most valuable when teams resist the temptation to hold it prematurely. A PDR held with unresolved requirement conflicts, undefined interfaces, or unvalidated key technical assumptions creates a false gate — the paperwork passes but the underlying risks remain. The discipline is in surfacing and resolving (or explicitly accepting) all major uncertainties before PDR so the review is a genuine checkpoint, not a schedule milestone.