Managing Changes During Execution Without Losing Control

Managing Changes During Execution Without Losing Control

## Introduction: The Essence of Change in Projects Change is an integral part of any project's lifecycle. The need often arises due to unforeseen site conditions or a desire to improve project outcomes . However, the risk lies in the absence of an organized mechanism for handling these changes, which can lead to administrative chaos and unjustified additional costs. ## Summary Table: Change Control Matrix | Step | Description | Objective | | :--- | :--- | :--- | | Documentation | Recording the reason and description | Transparency | | Evaluation | Impact analysis (cost, duration, quality) | Informed decision-making | | Approval | Official authorization before execution | Budget and schedule control | | Update | Adjusting documents and plans | Aligning reality with design | ## Why Do Changes Occur? There are many reasons behind change requests, which can be summarized as follows : - Emergence of new stakeholder requirements. - Discovery of new site information not apparent during planning. - Presence of conflicts in engineering designs. - Unavailability of specific materials in the market. - Field suggestions to improve execution quality. Change itself is normal, but the flaw lies in executing changes without a documented decision . ## Structuring the Change Log To ensure control, a central log must be built for every change containing: 1. A precise description of the change. 2. The root cause and necessity. 3. Associated references (drawings, correspondence). 4. Comprehensive impact analysis on scope, quality, schedule, procurement, and costs. ## Separating Proposal from Executive Order A common administrative error is confusing "option study" with "approval for execution." The site team must realize that a request to study a change does not mean a green light to start . Approval authorities must be clearly defined, with the necessity of suspending works related to the change until an official decision is issued to prevent waste. ## Closing the Change Loop The change process does not end with execution; it begins the "update records" phase . Technical documents must be updated to match what was actually executed (As-Built). Periodic review of the change log is a powerful administrative tool for detecting delayed decisions and preventing the accumulation of work based on unconfirmed assumptions . ## Common Mistakes in Change Management - Verbal changes: Relying on promises without formal documentation. - Change accumulation: Failure to evaluate the impact of small changes that may aggregate to cause a significant effect. - Ignoring cumulative impact: Focusing only on direct cost without considering its impact on the schedule. ## Checklist for the Project Manager - [ ] Has the reason and description for every change been documented? - [ ] Has the financial and time impact been evaluated? - [ ] Has the approval decision been issued by the authorized entity? - [ ] Have affected works been suspended until approval? - [ ] Has the change log and project documentation been updated? ## What Does the Project Owner Learn? The project owner learns that discipline in documenting changes is the financial and time safety valve for the project, and that change does not mean chaos, but rather managing resources based on site developments. ## FAQs 1. Is every improvement proposal a change requiring approval? Yes, any change in scope requires evaluation and approval. 2. Who is responsible for updating the change log? It is an administrative responsibility under the supervision of the project manager or their delegate. 3. Does a simple change affect the schedule? Yes, accumulation is the greatest risk. 4. Does this guide replace engineering plans? No, this guide is advisory and is not a substitute for approved plans or the directions of engineers and competent authorities. ## Conclusion Effective change management enhances project success. At Merit Access, we support a methodological approach to documenting and managing processes, with the emphasis that this content is for advisory purposes only and does not replace specialized engineering consultations.