Maintaining Design Objectives Through Delivery

Maintain design objectives through the management process

Design integrity is not limited to preserving an attractive rendering. It means keeping agreed program, functional, technical, operational, and performance objectives visible throughout delivery, then managing any proposed change to them. NCARB's PjM objective focuses on the process of communicating and monitoring design objectives through collaboration. The project manager should connect each important objective with a decision, responsible professional, measurable evidence, and review milestone.

Establish the approved objectives

At project definition and kickoff, identify the owner's priorities and the requirements used to evaluate design decisions. These may include capacity, adjacencies, accessibility, durability, operating cost, envelope performance, equipment function, sustainability, or an occupancy date. Distinguish an aspiration from an agreed measurable requirement. “Comfortable offices” needs clearer evaluation criteria if it is to guide mechanical and enclosure choices.

Record the approved program, requirements, assumptions, and relevant budget or schedule constraints. Identify who may approve a change and which stakeholders need to be consulted. A facilities manager can provide crucial maintenance requirements, but a preference expressed at a meeting may still need authorization from the designated owner representative. Preserve decisions so new staff and consultants can understand the approved basis.

Build a criteria and decision register

The table is an example, not a mandated set of objectives. Add revision dates, decision status, dependencies, and links to documents that implement the requirements. A register should be practical enough to use at meetings; a long list that nobody reviews will not protect design integrity.

Check continuity at phase gates

At SD, compare the concept with the approved program, site constraints, preliminary systems, and budget. At DD, verify that selected assemblies and engineering approaches still support the objectives. At CDs, check that drawings, schedules, specifications, and consultant information express those decisions consistently. During procurement and construction, evaluate substitutions and proposed changes against the same basis.

A phase approval does not freeze all design details, but it establishes a baseline for evaluating revisions. If a design objective changes, document why, obtain the applicable authorization, inform affected participants, and revise the relevant criteria and documents. Continuing to use the old criterion while changing the design creates an inconsistent record.

For example, a classroom program requires flexible furniture layouts and accessible circulation. A late built-in cabinet revision reduces those clearances. The manager should coordinate the program and accessibility review with the owner and responsible professional before accepting the revision. A lower construction price does not prove that the original functional objective is still met.

Evaluate value proposals and substitutions

A cost-reduction proposal should compare first cost, performance, maintenance, warranty, durability, appearance where relevant, procurement time, and coordination effort. Confirm that a proposed alternative satisfies required criteria and applicable law. Owner approval of lower cost does not waive code compliance or the architect's professional duty.

Assume an alternative finish saves $20,000 initially but requires an additional $3,000 in maintenance each year over an illustrative ten-year comparison. Undiscounted added maintenance totals $30,000, making the alternative $10,000 more expensive on that simplified basis. A full life-cycle comparison may also consider discounting, replacement, escalation, and residual value; do not present the simple example as a complete financial model. The management action is to disclose tradeoffs so the authorized owner can make an informed decision.

Coordinate changes across stakeholders

A proposed ceiling-height reduction can affect spatial quality, program, mechanical routing, lighting, acoustics, and accessibility or other code requirements. Identify all affected disciplines and owner users, assign evaluation, and document the accepted resolution. Do not let one discipline change a stated objective in isolation because it resolves its own clash.

Use meeting agendas and decision memos to frame choices. State the original objective, alternatives, evaluation evidence, cost and time effects, and decision needed. Record unresolved assumptions and a deadline tied to dependent work. After approval, verify the revision in every affected document. Communication is complete only when the decision has been understood and implemented, not merely when an email is sent.

Monitor construction and operational evidence

Submittal review, mock-ups, testing, and appropriate field observation can provide evidence of design conformance within the contracted services. Identify which criteria each process evaluates. A finish sample can show appearance but does not by itself verify structural performance or long-term durability. A permit approval does not prove that every owner operational objective has been achieved.

At closeout, preserve approved changes, test records, operating information, and unresolved items. B101's owner-requested operations meeting and any separately scoped POE can reveal whether expectations translated into usable performance. A POE finding should be analyzed with actual use, operating conditions, and the agreed evaluation method; a difference from a model does not automatically establish professional negligence.

Improve the next project

Capture recurring gaps in the lessons-learned process. If equipment-access conflicts appear repeatedly, improve the criteria register and coordination checklist. If substitution reviews overlooked maintenance, require that comparison earlier. Update standard details and specifications carefully rather than copying a project-specific solution into every project. Maintaining design integrity is a repeatable management process: establish objectives, communicate them, evaluate changes, obtain decisions, verify implementation, and learn from outcomes.

Reference: NCARB design-objective management scope.