How to Document Scope Changes on a Construction Project and Control Their Impact

An undocumented change can become a deviation

On a construction project, changes can arise from a client request, a discrepancy in the drawings, an unforeseen ground condition, or a proposed improvement. The risk is not limited to modifying the work: it also arises when the decision is communicated in a piecemeal way, work proceeds before its impact is assessed, or not all affected teams are informed. This can make it harder to control costs and schedules, as well as lead to rework and disagreements about what was agreed.

To reduce these risks, treat each change as a traceable process, from the first notice through to closeout. The record does not replace the approvals required under the contract: it brings together the information needed to make a decision and document what was decided.

1. Record the request from the first notice

Every request should be entered in a single change log, even if it initially appears minor or has not yet been approved. The entry should identify who reported the change, when and where it occurred, and what work or cost item may be affected. It should also describe the finding or requirement and attach the available evidence, such as photographs, drawings, measurements, specifications, or related communications.

Recording the change close to where and when it is detected helps preserve details that could be lost in calls or informal conversations. If information is incomplete, the entry can state what is missing and who should obtain it, rather than presenting the request as a finalized decision.

2. Classify the request and assign responsibilities

Before calculating the consequences, identify the nature of the request. It may be a client request, an unforeseen condition, a design discrepancy, a proposed improvement, or the correction of nonconforming work. This classification guides the technical and contractual review, but does not by itself determine who will bear the cost: that depends on the agreements and documents applicable to the project.

Assign each request a person responsible for coordinating its assessment and a priority. The priority should reflect, for example, whether the change affects an upcoming activity, a critical task, or work that has already been carried out. This helps address urgent matters first without losing track of pending requests.

3. Assess the effects before authorizing the work

The assessment should describe what changes from the current solution and review at least four dimensions:

• Cost: work, materials, labor, equipment, subcontractors, and other items that may be affected. Distinguish estimates from amounts already quoted or confirmed.
• Schedule: task durations, dependencies, work sequence, and possible effects on milestones or critical activities.
• Technical and quality considerations: drawings, specifications, coordination between disciplines, inspections, and acceptance criteria that may need to be reviewed.
• Contractual requirements: approvals, notices, or documentation that the contract may require to formalize the change.

The analysis should also consider indirect consequences. For example, an adjustment to an installation may affect subsequent elements or other crews’ access. When the impact cannot yet be quantified precisely, state this explicitly, along with the assumptions used and the information still pending.

4. Obtain the appropriate approval and document it

Once the assessment is available, submit the request to the people authorized under the contract and internal procedure. Record the decision as approved, rejected, returned for clarification, or deferred. If approved, document the authorized scope, the agreed cost or its valuation method, the anticipated schedule impact, any applicable conditions, and who gave the approval.

Where required, formalize the change using the order, amendment, or document specified by the contract. A recorded request does not automatically constitute an approved modification, and an impact estimate does not necessarily constitute an accepted price. Keeping this distinction clear helps prevent different teams from interpreting the same communication as final authorization.

5. Manage urgent situations without losing traceability

Some situations may require a rapid response, for example, to address a technical contingency or prevent a critical activity from coming to a halt. If the contractual procedure and circumstances allow a provisional instruction, document who issued it, what work it authorizes, its limits, and which matters remain subject to approval or valuation.

Then complete the formal review and link the final decision to the original record. Urgency may change the sequence of tasks, but it should not erase the evidence or turn a limited authorization into broader approval than was actually given.

6. Update documents and communicate the current version

Once the change is approved, update the affected documents and communicate which version each team should use. Depending on the case, this may include drawings, specifications, the budget, schedule, work instructions, and subcontractor documentation. Identify the superseded versions to reduce the risk of someone carrying out work using outdated information.

The communication should reach those who need to act: project management and the site team, the technical office, the client where appropriate, designers, and affected subcontractors. Archiving the approval is not enough if the site instructions still describe the previous solution.

7. Compare approved work with completed work

Follow-up does not end with authorization. Record the progress of the change and compare actual costs with approved or anticipated costs, using consistent criteria to allocate expenses. If differences arise, document their cause and determine whether they require a new request or approval, in accordance with the contract and project procedure.

It is also useful to close each change once the work has been verified: confirm that the documentation has been updated, that related cost items have been identified, and that the final decision can be consulted alongside its supporting evidence. This closeout makes it easier to review what was approved, what was carried out, and how costs and schedules evolved.

What the change log should make possible

A useful system—digital or another controlled format—should make it easy for the team to consult:

• the identifier and status of each request;
• its origin, location, evidence, and responsible person;
• the technical, financial, and schedule assessment;
• the associated approvals and conditions;
• current documents and versions;
• the anticipated, approved, and recorded costs during execution;
• communications and change closeout.

The tool matters less than process discipline: there should be a clearly identified place to record, review, approve, and consult each decision, with defined responsibilities and access to current information.

The contract and jurisdiction define the procedure

The obligations for processing changes depend on the contract, the type of project, and the applicable jurisdiction. This workflow is therefore a management guideline, not a legal interpretation or a guarantee that an internal record will satisfy the formal requirements of a particular contract. Before carrying out or formalizing a modification with possible financial or contractual effects, review the applicable documents and, if necessary, obtain professional advice.