Change Documentation: Authorization Protocols, Tracking, and Record-Keeping
How architects and project teams document, authorize, track, and maintain records of changes during construction, from formal change orders through configuration management systems.
Why Change Documentation Can Make or Break a Project
Changes happen on every construction project. Every single one. That is not the problem. The problem is what happens when those changes are poorly documented, verbally approved, or tracked inconsistently.
On the ARE, you need to understand the full lifecycle of a construction change: who can authorize it, what documentation is required, how it gets tracked through resolution, and why record-keeping matters long after the project closes out. This goes beyond knowing that change orders exist. You need to evaluate when documentation protocols have been followed correctly and when they have broken down.
The architect plays a specific role in this process. Under AIA General Conditions, the architect prepares Change Orders and Construction Change Directives and may authorize minor changes in the Work. That signature on a change order is not just a formality. It keeps the architect connected to the evolving project scope, which directly affects the ability to determine whether the contractor's work conforms to the contract documents.
When change documentation fails, the consequences cascade: disputed costs, schedule delays, litigation, and broken professional relationships. Strong authorization protocols and tracking systems prevent these outcomes by creating a clear, defensible paper trail from the moment a change is identified through final resolution.
Want to track your progress and access more study tools?
Create a free account