Process · General Industry
System design freeze
The point in a system's development after which its hardware design, interfaces and bill of materials change only through formal change control, so that validation, certification and production preparation work on a stable design.
- Also known as
- Hardware design freeze
- Type
- Process
- Domain
- General Industry, Programme jargon
Overview
A system design freeze is the milestone at which the design of a whole system, its boards, mechanics, interfaces and parts list, stops changing freely. It usually follows the first engineering builds, once the main problems have been fixed, and comes before the design validation build. After it, every change is raised, assessed and approved before it is made.
How it works
Before the freeze, the team agrees what is in the design: board revisions, mechanical drawings, the bill of materials with its approved sources, the firmware version needed for validation, and the interface control documents. These are baselined in the configuration management system.
After the freeze, a change request is needed for any change. The request states the reason, the parts affected and the effect on cost, schedule, validation and certification. A change board approves or rejects it. Approved changes are made in a new controlled revision, and the validation plan is updated to cover them.
Software and firmware often keep changing after the hardware freeze, under their own release control, as long as they stay within the frozen interfaces.
Examples
- A controller's boards frozen at their second revision before the design validation build.
- A late connector change after the freeze raised as a change request and approved with an added test.
- A medical monitor whose frozen design is the one submitted for certification.
- A system whose hardware is frozen while its application software continues to be released.
Why it matters
Validation and certification take time and money, and a test result only counts for the design that was tested. Freezing the design means the results of design validation and certification apply to what will be built. It also lets purchasing order long-lead parts and the factory prepare its tooling. System architects, systems engineers, programme managers and configuration managers run the freeze.
In the system lifecycle it sits at the end of design, before design validation, and later changes go through change control into sustaining releases.
It matters most to: Configuration Management Engineer, Hardware Program Manager, System Hardware Architect, Systems Engineer
Common confusions
- Not the same as an RTL or chip design freeze
- A chip team's design freeze stops changes to one chip's RTL and layout before tape-out. A system design freeze covers the whole system: boards, mechanics, interfaces and the parts list.
- Not the same as a hard freeze
- A hard freeze allows no change at all. After a system design freeze, changes are still possible, but only through formal change control.
Sources
- The role of design freeze in product development (ICED 05) (opens in a new tab), Delft University of Technology research portal, 2026-11-10
- Design freeze sequencing using Bayesian network framework (opens in a new tab), Industrial Management & Data Systems (Emerald), 2026-11-10
- Engineering change analysis during ongoing product development (ICED 07) (opens in a new tab), Technical University of Munich research portal, 2026-11-10
Related terms
Part of the General Industry glossary, with every term in the topic and the lifecycles, tools and standards that use them.
Where it appears on the Hub
Used on 7 pages of the Hub. In each group, the pages that mention it most come first.
Lifecycle stages and gates
Suggest an improvement
Suggest an improvement to this entry
A clearer definition, an example, a correction or a source an editor can check. Editors review every suggestion before the entry changes.
Last reviewed . Written by The Semiconductor Hub editorial team. The full glossary