What Is a 35% Design Review and Why It Matters
Industry standards for this phase vary significantly depending on the project delivery method, such as design-build versus traditional design-bid-build. While the 35% figure suggests a precise mathematical threshold, it acts more as a functional signal that the preliminary engineering is stable. At this stage, the design team has moved past sketches and has begun defining physical footprints, material specifications, and major system interfaces that dictate the project's long-term trajectory.
At a glance
| Feature | Status at 35% |
|---|---|
| Engineering | Conceptual to Preliminary |
| Cost Estimate | Class 3 or 4 |
| Scope | Defined but Flexible |
| Risk Profile | High Exposure |
What are the primary objectives of an early-stage engineering design review?
The primary objective is to align technical requirements with project constraints to prevent costly rework. At this stage, teams must verify that at least 80% of the project’s major equipment or structural components are identified and sized correctly, ensuring the design doesn't drift from the initial project charter.
How does a 35% design milestone differ from a 60% or 90% review?
A 35% review focuses on the "what" and "why," whereas 60% and 90% reviews shift toward the "how" and "how much." At 35%, engineers confirm the site layout or system architecture is viable. By 60%, the design documents must be fully coordinated between disciplines, such as ensuring mechanical ducts don't clash with structural steel beams. The 90% review is essentially a final quality check before issuing documents for permit or construction.
One notable nuance is that a 35% review often lacks complete specifications, relying instead on performance requirements. For example, a designer might specify a pump's required flow rate and head pressure without selecting a specific manufacturer or model. An exception occurs in fast-track projects where long-lead items, like custom transformers, are ordered before the 35% mark to avoid supply chain delays.
What specific documentation is typically required for this phase of project development?
The documentation package at this stage serves as a preliminary roadmap for all subsequent engineering efforts.
- Process Flow Diagrams: These initial schematics define the sequence of operations and identify major equipment loops.
- General Arrangement Drawings: These visual layouts establish the spatial footprint and physical boundaries for the major infrastructure.
- Equipment Lists: This preliminary inventory captures the primary assets, including their rough capacity and utility requirements.
- Material Selection Matrix: This document outlines the intended construction materials and their compatibility with the operating environment.
Who are the key stakeholders involved in evaluating a project at this level of completion?
Key participants include the project manager, lead engineers, the client’s representative, and the lead estimator. Many people assume the 35% review is primarily a technical exercise for engineers, but it is actually a financial and operational gate. If the client doesn't approve the conceptual direction at this point, the engineering team risks wasting thousands of hours on a design that will eventually be rejected for being too expensive or failing to meet the client's core operational objectives.
What criteria are used to determine if a design is sufficiently mature to pass this review?
Yes, a design is mature enough when all major site constraints are resolved and the primary system architecture is fixed. A project typically passes when 100% of the critical path components are identified, allowing for a cost estimate accuracy within a range of -15% to +30%.
How are budget and cost estimation refined during this stage of the design process?
Estimators convert the preliminary equipment list into a Class 3 or 4 estimate by applying historical unit costs to the identified scope.
| Item | Estimate Accuracy | Basis |
|---|---|---|
| Labor | +/- 30% | Industry averages |
| Materials | +/- 20% | Vendor quotes |
| Contingency | 20-25% | Risk assessment |
| Indirects | 15% | Historical data |
Use these figures to calculate the "design-to-budget" gap and adjust the scope before the design becomes too rigid to change.
What are the most common risks identified during an initial design assessment?
Initial assessments frequently uncover gaps between physical reality and theoretical design assumptions that could derail the project schedule.
- Utility Interferences: Existing underground lines often conflict with new foundations, requiring immediate rerouting or site layout adjustments.
- Soil Conditions: Unexpected geotechnical data can force a complete redesign of the foundation system, adding weeks to the timeline.
- Permitting Hurdles: Local zoning or environmental regulations may prohibit the planned footprint, necessitating a shift in the project's physical orientation.
- Supply Constraints: Long-lead items identified during this phase might have delivery schedules that exceed the planned construction window, requiring early procurement.
Mistakes to avoid
- Treating it as a final check. This review isn't for polishing details; it's for catching fundamental flaws in the project's direction before expensive work begins.
- Ignoring the budget baseline. Failing to reconcile the design with the cost estimate now leads to massive redesign efforts once the project reaches 60% completion.
- Underestimating stakeholder input. Skipping early feedback from end-users or maintenance teams creates technical debt that becomes difficult to fix later.
How does feedback gathered at this stage influence subsequent design iterations?
Feedback at 35% acts as a corrective lens, forcing the team to pivot before they invest in detailed modeling. If stakeholders identify a flaw in the facility workflow, the team can redraw the floor plan without discarding months of mechanical and electrical calculations. This early intervention prevents the "sunk cost fallacy," where teams persist with a flawed design simply because they have already spent significant time drafting it.
However, feedback isn't always a simple directive to change; it often requires a trade-off analysis. For instance, if an end-user requests a more complex automated control system, the team must evaluate how this impacts the budget and schedule immediately. The exception is when feedback contradicts safety codes, in which case the engineering requirements must override stakeholder preferences regardless of the cost or schedule impact.
Managing Expectations for Early Design
Focus your energy on identifying conflicting requirements and major physical constraints during this review. Catching these issues now prevents costly rework that often plagues projects once they move into the detailed engineering phase.