← All methodology chapters

SIDM · PART V

Chapter

22

Chapter 22 — Project Decisions, Reviews, and Change Management

Decision, review, and change management ensure that stage progression has evidence, authority, and a traceable record. Project managers coordinate the…

Published Updated
Chapter 22 — Project Decisions, Reviews, and Change Management

Decision, review, and change management ensure that stage progression has evidence, authority, and a traceable record. Project managers coordinate the continuity of decisions; discipline leads confirm professional conditions; the commissioning party's authorized person decides objectives, scope, and commitments within their authority. Chapter 16 defines four stage-gate types; this chapter explains how decisions are made and controlled.

Preparing and Recording Reviews

Each review request should identify the object, version, reference basis, open decisions, and required participants. Materials include the Design Direction Definition or its reference, phase outputs, critical risks, alternatives, and supporting evidence. Participants should review their relevant conditions beforehand so that the meeting is more than a display of drawings.

Conclusions should be recorded distinctly as approved, approved subject to conditions, or returned. An approval defines what was accepted. Conditional approval defines restrictions, responsible roles, deadlines, and work allowed to continue. A return identifies causes, the required earlier step, and restart conditions. “Basically fine” or “looks acceptable” is not a valid authorization to manufacture or deliver when critical conditions remain unresolved.

Decision Authority and Risk Escalation

Set approval boundaries at project start for local specialist optimizations, cross-discipline changes, budget or schedule shifts, scope changes, and changes to core objectives. Local specialists may implement an adjustment directly only if the modification falls within authority and does not disturb approved goals or other domain conditions. Changes affecting actual use, safety, recognizable brand features, supply, quality, or delivery require input from affected roles.

Where a problem cannot be resolved under present authority, evidence conflicts, a critical professional requirement remains unconfirmed, or a risk may breach a commitment, the project manager escalates to the designated decision-maker. Escalation material should state the problem, impact, viable options, and specialist recommendations—not merely report time pressure. During escalation, specify what is paused and what can continue to prevent teams acting on incompatible assumptions.

The Change Workflow, from Request to Verification

Step Required action Evidence retained
Initiate Explain reason, object, version, and proposed change Change request and affected drawing/physical location
Analyze Check function, experience, brand, structure, process, supply, cost, schedule Impact analysis and affected disciplines
Compare Reframe the problem first and propose feasible alternatives Options and trade-off reasoning
Approve Confirm conditions and implementation scope under the appropriate authority Approval, specialist confirmation, documented decision
Release Synchronize CAD, drawings, standards, purchasing and site instructions Effective version and acknowledgment of receipt
Verify Inspect actual execution and closure of the original problem Recheck record and closure decision

Urgent circumstances may justify preauthorized protective or loss-limiting action while recording facts, responsibilities, and restrictions. Such action does not permanently substitute for formal approval of a change affecting a core objective. Address obsolete drawings, already purchased material, and already fabricated parts in the implementation plan—not only the updated digital document.

Problem Closure and Evidence-Based Rechecking

The issue register identifies location, type, impact, owner, action, target date, and closure evidence. Suggesting a fix is not closing a problem; an action must be implemented and rechecked against the applicable standard by the appropriate owner. Issues needing site observation or continuing use can move into a follow-up list, but current delivery acceptability, restrictions, and responsibility must remain clear.

Repeated problems should not be treated as unrelated workshop incidents. Investigate the governing rule, resources, and interface; where necessary, pass corrected practice to Chapter 25's standards process. Problems unresolved at project completion require explicit ownership and verification arrangements rather than disappearing through document archiving.

Version and Decision Records

Record dates, objects, versions, participants, evidence, disputes, conclusions, approval, and execution scope. Keep CAD, drawings, CMF, quality criteria, signage, and inspection instructions linked. Make the effective version accessible and clearly mark superseded versions. Production teams and external suppliers should confirm replacement of old execution instructions.

Convert consequential verbal decisions into written or graphical confirmation. Changing opinions within the commissioning party must be reconciled by its authorized representative; the design team should not select whichever opinion is easiest to implement. Preserve both specialist recommendations and final decisions where they differ so that later participants understand the limits of what was approved.

KEEP READING

Continue Exploring the Methodology

View all chapters →