Capture and approve scope changes requested mid-project, rather than letting them proceed un-priced or unapproved. Complements the cross-cutting Change Order concept already in the lifecycle model.

Trigger

A scope change is requested by the customer or discovered in the field.

Owner

Project Manager

Participants

• Operations Manager

Inputs

• Change request.
• Current approved scope.

Steps

1. Document the requested change.
2. Price the change.
3. Route it for approval.
4. Update the plan and budget if approved.

Decision points

• Is the change approved? → If yes, loop back to Planning (or Installation, for minor changes); if no, document as declined.

Outputs

• Approved or declined change order.

Handoff

Lead Technician

Failure / exception path

A change proceeds in the field without an approved change order — the single biggest source of scope creep and margin loss; treated as a hard control point, not optional paperwork.

Related system objects

Future automation opportunity

Block marking any installed-equipment change as complete without a linked approved change order (already the Installation Documentation Standard’s future rule).

Required data

• Change requested date
• Priced change amount
• Approval decision and date
• Loop-back target stage