If you don’t guide design early, you usually pay for it later in change orders, delays, and field fixes.
I’d sum up the article like this: design management is how I keep design tied to the owner’s requirements, scope, budget, schedule, code needs, buildability, and handoff needs from day one through turnover. The main point is simple: design decisions made early shape cost, timing, and jobsite results long before construction starts.
Here’s the article in plain English:
A few facts from the article show why this matters:
| Area | When I manage design early | When I step in late |
|---|---|---|
| Cost | Budget checks happen during design | Redesign starts after bids come in high |
| Schedule | Permits and long-lead items are planned sooner | Delays stack up through late approvals |
| Field work | Build issues are reviewed before construction | Conflicts show up during installation |
| Risk | Open issues are logged and resolved earlier | Change orders and disputes become more likely |
If I had to reduce the whole piece to one idea, it would be this: the owner cannot sit out the design phase and still expect cost, schedule, and project goals to stay in line.
Good design management starts with clear owner governance: defined roles, decision rights, and escalation paths. But those controls only work when everyone knows who owns each call.
The Owner's Project Manager (OPM) coordinates the owner, design consultants, and builder, and helps keep decisions buildable. The Design Manager leads the preconstruction design effort and makes sure the design stays aligned with cost, schedule, and constructability needs. The Executive Sponsor controls major budget thresholds and makes final calls on schedule and risk. User stakeholders define functional requirements and performance goals, so their priorities need to be set early and tracked the whole way through. On Design-Build and Progressive Design-Build projects, the builder leads design, which makes owner oversight even more important. [1]
Unclear accountability leads to missed decisions and rework. The simplest way to clear that up is with a RACI matrix. [1]
| Activity | Owner | Architect/Engineer | GC/CM | Trade Partners |
|---|---|---|---|---|
| Requirements Definition | Accountable | Responsible | Consulted | Informed |
| BIM Coordination | Informed | Responsible | Accountable | Responsible |
| Estimating/Budgeting | Accountable | Consulted | Responsible | Consulted |
| Constructability Reviews | Informed | Consulted | Accountable | Responsible |
| Permitting Support | Responsible | Responsible | Consulted | Informed |
| Document Control | Informed | Responsible | Responsible | Informed |
| Change Approvals | Accountable | Consulted | Responsible | Informed |
R = Responsible, A = Accountable, C = Consulted, I = Informed
This kind of matrix does one simple but important job: it shows who decides, who does the work, who gives input, and who just needs updates. That cuts down on the back-and-forth that slows teams down.
Once responsibilities are set, the owner needs formal gates to lock each phase before the next one begins. Stage-gate approvals help stop scope drift and reduce late redesign. Each gate should freeze the current phase before work moves ahead. [1]
| Approval Gate | Key Deliverables | Decision Authority |
|---|---|---|
| Concept/Feasibility | Economic/financial feasibility, strategic alignment | Owner Executive / Investment Board |
| Schematic Design | Site plan, massing, preliminary budget | Owner Project Manager |
| Design Development | Systems selection (MEP), material specs, 3D models | Design Manager / Owner Rep |
| Construction Documents | Final permit set, definitive cost estimate | Owner Executive / Lead Stakeholder |
The gates are only part of it. Owners also need set thresholds for change approvals. Minor design tweaks below a defined limit can be approved by the Design Manager. Changes above that level should move up to the OPM. Anything that affects the total project budget or schedule should go to the Executive Sponsor. [1]
Technical conflicts need the same kind of structure. Say end-users push for a feature, but the budget lead says it falls outside scope. If there is no clear escalation path, that issue can sit there and hold up procurement or delay permitting. A decision log helps keep things moving by recording the decision, approver, date, and contract basis. Without that record, teams tend to reopen the same issues and lose time. [1]
With roles and gates in place, the next move is building a repeatable workflow from OPR through turnover.
Design Management Workflow: From OPR to Turnover
The owner's workflow carries those roles and approval gates through each design phase. It starts with the OPR and moves step by step from concept to turnover.
The OPR is the owner's design baseline. Before any designer begins schematic work, the owner needs a written set of goals that covers budget, schedule, performance criteria, user needs, and operational needs. On regulated or specialized projects - cleanrooms, labs, and data centers - it may also spell out redundancy needs, environmental controls, and compliance targets.
The OPR should come out of a facilitated workshop that brings together the owner, designer, and facilities team. As Bob Morris, Commissioning Manager, notes:
"A successful Commissioning Process delivery really depends upon a clear, concise, and comprehensive OPR document." [2]
After the OPR is approved, the team develops schematic plans. The owner then checks those plans against the OPR before the design gets locked in and sets the initial cost baseline before moving ahead. Keep the OPR active through design, construction, and occupancy. It becomes the point of reference for design development and budget checks.
Use design development to approve the Basis of Design, review constructability, and set freeze points that support procurement and permitting. Approving the BOD at this stage gives the team a clear explanation of how the design will meet the OPR. Freeze milestones lock in parts of the design early enough to cut down on late-stage disruptions [1].
As the project moves into construction documents, the focus shifts to drawing completeness and permit readiness. Identify long-lead items early so the team can order them before they turn into schedule bottlenecks. An early long-lead review helps avoid procurement delays. Do not move past the CD gate until the drawings are complete enough for permit submission and the cost estimate reflects the full scope. Once the documents are permit-ready, attention shifts to RFIs, change control, and field alignment.
Design management does not stop when construction starts. The owner's team needs to stay on top of RFIs, design-related change orders, and field conditions that do not match the drawings. Use a decision log to keep RFIs and clarifications in check. Log each RFI, clarification, and decision with the approver, date, and contract basis.
As Kabri Lehrman-Schmid, Superintendent & Project Leader at Hensel Phelps, says:
"Design managers are constantly tracking the exchange of information in all different mediums while maintaining a clear trail of decision-making that ties back to the contract and owner requirements." [1]
Before substantial completion, confirm that as-builts, O&M manuals, and digital records are in the required format. Commission the systems with the team that designed them, and make sure facility staff are trained directly by project experts [3]. That final owner check confirms operational readiness before handoff. Those turnover checks depend on the document control and coordination tools covered next.
Once the owner sets the workflow and approval gates, the next step is simple: keep every design decision tied to budget, schedule, and scope. That sounds obvious, but projects often drift when those checks aren't built into the day-to-day process.
Budget control is a rolling estimate process. As the design shifts, the cost picture has to shift with it. If a spec changes or a system gets upgraded, that move should be checked against the current budget before it gets approved and locked in.
Value engineering is about cutting cost without hurting performance, operability, or code compliance. Done right, it's not cheapening the project. It's finding a better path to the same result.
The difference between a loose process and a controlled one is pretty stark:
| Uncontrolled Design Changes | Controlled Design Management | |
|---|---|---|
| Owner Response | Reactive; navigating multiple consultants for answers | Proactive; single point of contact for design and construction impacts |
| Cost Impact | High risk of costly redesigns and material waste | Value engineering opportunities identified early |
| Schedule Impact | Delays from uncoordinated approvals or permit re-submissions | Accelerated permitting through early design-construction alignment |
| Risk Level | High; misalignment between design and field reality | Low; constructability issues identified in preconstruction |
Owners should require a Common Data Environment (CDE). In plain English, that means one record set everyone works from for drawings, models, RFIs, submittals, and approvals. Without that, teams can end up using different drawing versions, and that's when rework starts creeping in. It also gets messy fast when people try to figure out what was approved, by whom, and on what date.
Before design development starts, owners should also set a few ground rules:
The CDE and decision log back up the owner's decision rights already set in the RACI. That link matters. It connects approval gates straight to the document record, so decisions don't float around in email threads or meeting notes. Clash detection then helps spot conflicts between MEP, structural, and electrical systems before anyone breaks ground.
| Tool Category | Primary Function | Impact on Project Outcomes |
|---|---|---|
| 3D Modeling / BIM | Visualizing design and identifying constructability issues early | Reduces field rework; improves trade coordination |
| Document Control Platforms | Managing distribution, version control, and approval workflows | Ensures all teams use current data; provides audit trail |
| Clash Detection Software | Identifying coordination clashes between design systems | Prevents costly on-site modifications and schedule delays |
| Decision Logs | Recording stakeholder input and contractual alignment | Minimizes disputes; ensures owner requirements are met |
With the CDE in place, teams can use the same record set for RFIs, submittals, and risk reviews.
Document control by itself isn't enough. It only works if open issues are reviewed on a fixed cadence.
Recurring risk workshops give teams a place to sort out timing, sequence, and scope before problems hit the field. The right mix of people should be in the room: owners, end-users, and construction leads. That way, practical conflicts across user needs, design intent, and construction planning can be spotted early instead of turning into change requests later.
On a fast-track infrastructure project, the original plan for a new electrical duct bank would have added two years to the schedule. Early coordination let the team keep the existing duct bank in place during construction, avoiding a two-year delay. [1]
That's the day-to-day value of early constructability review.
Once governance, roles, and controls are in place, the next test is simple: do they help teams make better day-to-day calls?
Owner routines are often the line between a controlled project and a messy one. Weekly design review meetings keep architects, engineers, and construction leads lined up on open issues before those issues snowball. Stage-gate reviews should stop design moves that get ahead of budget approval. Those checkpoints give owners real leverage.
Put plainly, these routines make design review a delivery tool, not just another status meeting.
A lab project cut ductwork by nearly 30% by reworking the layout during design [1]. That kind of result doesn't happen by luck. It comes from disciplined owner-led review. In this case, it came from disciplined value engineering at design milestones.
It also helps to track RFI age by discipline. That's a simple way to spot stalled decisions before they hit the schedule. Keep decisions in one log as well, so open issues don't slow procurement or force redesign.
The biggest gains tend to show up when these habits aren't one-offs. They need to become repeatable across the owner's portfolio.
Repeatable delivery takes an internal design-management capability, not ad hoc coordination.
That usually means having the right people in-house or on retainer: Owner's Project Managers, Design Managers, Estimators, Schedulers, MEP Specialists, and Commissioning Leaders. Each role solves a different problem. MEP specialists catch coordination conflicts before clash detection does. Commissioning leaders keep operability in the design from day one. Together, these roles help owners apply the same controls across multiple projects.
On larger projects, owner rep support can also tighten bid review and change-order control.
Design management isn't something owners can hand off entirely to outside consultants. The owner sets the requirements, controls the budget, and remains accountable for delivery. That means staying in the driver's seat through the design phase. When owner-led discipline is built into the way a program runs, owners get tighter cost control, fewer surprises in the field, and projects that deliver what was promised.
An owner should start design management at the outset of the project, ideally early in the design phase. That gives the team a clear way to guide decisions, keep the design tied to project goals, and handle risks before they turn into bigger problems.
Owner-side design reviews should involve the design management team, including the design integration manager, design consultants, and key stakeholders.
The owner’s representatives should review the design with a close eye on operational functionality, life-cycle costs, and program compliance.
Design management cuts down on change orders by tracking and sharing design decisions as they happen. That keeps the design tied to project goals instead of drifting over time.
It also helps teams spot issues early, when they're still easier and cheaper to deal with. As a result, teams can look at impacts on cost, schedule, and constructability before those issues turn into changes during execution.
