Project change control: linking design decisions to cost and time
Admin · 22 October 2026
Illustrative image. Photo by Daniel McCullough on Unsplash. Unsplash License.
A change request is rarely confined to the drawing on which it first appears. Moving an entrance can affect access, security, drainage and the construction sequence. Replacing equipment may alter supports, controls and maintenance arrangements. The management task is to identify those connections before the project commits to the change, then carry the decision consistently into design, procurement, cost reporting and delivery.
For a client project manager, a useful change process provides a dependable account of what is proposed, why it is needed and what the decision will authorise. It should support timely decisions without hiding uncertainty. A register full of requests does not achieve that on its own; the value comes from clear ownership, proportionate assessment and follow-through into the work.
Establish the reference being changed
Identify the approved requirement, scope or information affected by the proposal. Include relevant references and revisions so reviewers understand the starting position. Without that baseline, participants may disagree about whether the request introduces something new or merely explains an existing obligation. The actual appointments and contractual documents need appropriate review where that distinction has commercial consequences.
Describe the current arrangement in practical terms. What activity or function does it support, and who relies on it? This prevents the review from focusing only on the physical alteration. If a room becomes smaller, for example, the issue may concern equipment movement or staffing rather than area alone. The owner of the underlying requirement should participate in assessing the proposal.
Explain the reason and decision deadline
State the trigger for the request. It may be a changed operational need, new survey information, a supplier proposal or a coordination problem. Record the consequence of retaining the current arrangement as well as the expected benefit of changing it. That gives decision makers a meaningful comparison instead of a one-sided description of the preferred option.
Link the decision date to the work it affects. An order release or fabrication milestone may determine when the choice becomes difficult to reverse. Include time for the assessment and the formal communication of an approved decision. An urgent label is less useful than explaining which commitment is approaching and what happens if the answer arrives after it.
Assign an assessment owner
Name the person coordinating the assessment and identify the disciplines and packages that must contribute. The coordinator should collect the complete picture, not assume responsibility for every technical answer. Establish what each contributor needs to review and how their response will be recorded. This reduces the risk of several partial assessments being mistaken for a coordinated conclusion.
Check the interfaces deliberately. A designer may identify revised information, while the procurement team identifies an order already placed and the planner identifies a dependent handover. Each view matters. Ask contributors to distinguish confirmed effects from estimates and unresolved questions. The decision paper should preserve those differences rather than compress them into a single apparently certain number.
Compare credible alternatives
Where appropriate, examine more than the initial proposal. A different location, sequence or specification may address the underlying need with fewer consequences. Keep comparison boundaries consistent and include retaining the current arrangement where it remains feasible. Do not generate alternatives merely to fill a template; investigate options that could reasonably change the decision.
Consider a hypothetical occupier request for an additional meeting room after fit-out procurement begins. Options might involve a revised partition arrangement, adapting an existing room or managing demand differently. The project team needs the occupier to confirm the operational requirement while relevant specialists assess technical and delivery implications. The construction manager cannot decide the business priority simply by identifying the easiest alteration.
Connect cost and programme effects
Record cost movements against the relevant scope and explain their basis. Identify design work, procurement changes, installation consequences and other connected effects where applicable. A lower purchase price may be offset by redesign or rework. Commercial reviewers should establish the appropriate treatment under the actual arrangement and distinguish an internal estimate from an agreed adjustment.
Review time effects through the current programme rather than adding a general delay allowance without explanation. Identify the activities affected and the assumptions behind any proposed mitigation. An alternative sequence may create resource or access demands elsewhere. The planner and delivery team should assess those connections so the decision maker sees a coherent forecast rather than separate local promises.
Show uncertainty and conditions
If important evidence is missing, explain what cannot yet be established and what investigation would resolve it. The project may need a staged decision, such as authorising further design work before committing to the final change. Define that limited authority clearly. Approval to investigate should not be communicated as approval to manufacture or install.
Where a decision proceeds on an assumption, name the assumption and its owner. State when it must be checked and what will happen if it proves incorrect. This creates a practical control rather than a vague note that risk remains. The receiving team should understand which elements are settled and which are conditional.
Use the right authority
The Association for Project Management describes change control as capturing and evaluating proposed changes to an approved baseline before deciding their disposition. On a construction project, the relevant governance and contractual procedures determine who can approve a requirement, instruct work and agree commercial consequences. These may be different actions performed by different people.
Record the decision precisely, including scope, conditions and authority. Avoid language such as approved in principle without explaining what it permits. If another approval or instruction is required, identify it as an outstanding action. This protects the project from treating a useful management discussion as a complete authorisation when the formal steps remain unfinished.
Implement the decision across records
Identify the drawings, schedules, orders and planning records that require revision. Assign responsibility for each and track completion. Communicate through the project’s controlled channels so affected teams can identify current information. A change is not fully implemented because its status in the register has moved to approved; the people doing the work need the correct information and instruction.
Keep the relationship between the original request and subsequent revisions traceable. If the approved proposal changes during detailed development, assess whether the decision still covers the new position. Do not allow a broad initial approval to become an unrestricted permission for further scope movement. Significant departures should return through the appropriate review route.
Reconcile the outcome
At suitable intervals, reconcile approved changes with the current scope, forecast and commercial records. Check for requests counted twice, estimates still awaiting agreement and approved work not yet reflected in the programme. This makes reporting more dependable and helps leadership distinguish a proposal pipeline from commitments already made.
Review the causes of consequential changes after their effects are understood. Some reflect legitimate new needs; others reveal unclear requirements or late information. Use that evidence to improve future briefing and release decisions. The practical outcome of good change control is a project able to explain what changed, why it was authorised and how the decision reached the work and its supporting records.
Keep related requests connected
Several requests may arise from the same business decision. Give them a shared reference where useful and assess their combined effect. A layout change might generate separate entries for architecture, services and equipment, but leadership needs to understand the complete commitment. Conversely, one large request may need separate release points with different authorities. The register should support those relationships without counting the same scope twice. Check the grouping when a proposal is split, withdrawn or replaced so that the reported total continues to reflect the actual position.
