VegaUltimate

A Better Construction Change Order Process

The expensive part of change management is usually the gap between discovering changed work and documenting who approved what, when, for how much and with what schedule effect.

Capture the condition before the work disappears

Document the issue, location, date, relevant drawing or direction and the parties involved. A short factual record created promptly is more useful than a polished explanation written weeks later.

Price the same scope everyone is discussing

Define inclusions, exclusions, labor, material, subcontractor cost, markup and any schedule effect. If the scope is ambiguous, the approval will be ambiguous too.

Separate pending from approved

Pending changes matter to forecast risk, but they should not quietly become approved contract value. Keep the status visible and explicit.

Carry approval through the rest of the project

Once approved, update the appropriate budget, commitment, billing and schedule records. The signed document is not the end of the workflow.

Project review checklist

• Is changed work documented before it is covered? • Can the team distinguish requested, priced, submitted and approved status? • Are schedule effects discussed with cost effects? • Does approval update downstream project records?

Related guides and workflows

Create your VegaUltimate workspace · Explore the software