Make sure a change is documented and priced before it's built, not reconstructed afterward to justify what already happened.

Performed by

Project Manager

Used in processes

• Change Management

Governing standards

• Change Order Standard

Procedure

1. 1Document what is being added, removed, modified, or substituted.
2. 2Record the reason or origin category.
3. 3Assess impact to scope, labor, materials, subcontractor cost, price, schedule, and design.
4. 4Price the change.
5. 5Route for approval before affected work proceeds.
6. 6Update the project plan and budget once approved.

Decision / troubleshooting points

• Does the change affect contractual price or schedule? → Requires formal approval before work proceeds, no exceptions without a documented emergency.

Required evidence

• Change description
• Impact assessment
• Approval record with approver and timestamp
• Supporting documents or photos, where applicable

Completion criteria

Change order is approved or declined with every Change Order Standard field recorded, and the plan/budget reflect it.

Escalation

When: Work must proceed before formal approval can be completed — emergency only.

Involve: Operations Manager

Future system assistance

• Block marking related installation work complete without a linked approved change order.
• Calculate price impact from entered cost fields.
• Require the reason category from a controlled list.