Skip to documentation
Finance and AnalyticsFinance teamsProject managers

Change orders and variations

Document a scope change and approve its budget and contract impact.

Record why the agreed work changed

A change order records a formal variation: additional work, an omission or a changed specification. It keeps the reason, financial impact and reported time impact with the project. This optional feature is useful when an informal instruction would otherwise disappear into a revised budget. An RFI answer may explain the change, but does not replace approval of its cost.

Step-by-step walkthrough

  1. 01

    Describe the proposed change

    Create a draft for the project with the reason, scope, cost impact, time impact and supporting evidence.

  2. 02

    Submit for a decision

    Review the figures before submitting. The authorized reviewer approves or rejects; a rejected draft can be corrected and resubmitted.

  3. 03

    Check the downstream work

    After approval, inspect the budget and contract value. Update scheduling or purchasing separately where the change requires it.

Prepare and submit the variation

Open Change Orders or the project tab. Create a draft with project, title, description, justification, cost impact, time impact and supporting files. Review the signed amount carefully: additions and reductions have different effects. Submit for approval. The approver approves or rejects with a reason; rejected content can be revised and resubmitted. Draft or Submitted orders can be cancelled, but an approved variation has no ordinary undo or edit of its commercial content.

Review a change before applying it

Approval applies the cost delta to budget and contract value; project dates do not automatically move.

Understand exactly what approval changes

Approval applies the cost delta to both estimated project budget and contract value and stores the before-and-after figures. For example, a PKR 150,000 addition raises each by PKR 150,000. This is the application’s current rule; it does not model separate cost and selling-price deltas on the same variation. A reduction cannot make the budget negative.

Time impact is recorded, but approval does not automatically move the project or stage dates. Update Scheduling separately where required. Approval also does not buy material, create an outgoing payment or collect client money.

Share the approved decision

Only approved, client-visible change orders appear in the client portal. Review attachments before sharing. Internal sign-off still uses change-order approval permissions. If the record changed while you were reviewing, reload and compare the current figures before retrying; do not create another variation just because the first response was delayed.