Approve a subcontract change order (SCO) with Sage Construction Management's workflow rules

You can approve a subcontract change order (SCO) when a workflow rule is in place.

Before approving an SCO:

• Verify that it is eligible for approval. Its Status must be Pending Submission or Pending, as only these two statuses can be routed for approval.

• The prime contract and the subcontract referenced on the SCO must already be Approved and have a status date.

• Make sure the SCO total and the project it belongs to match whatever value or project-specific limits are defined in the workflow rule.

To submit an SCO for approval:

1. Select Procurement > Subcontract Change Orders.

2. Select the SCO number.

3. Select Workflow Actions > Initiate to start the workflow rule.

   The rule’s first approver will see the SCO in their Pending queue. From this point forward, the SCO cannot be edited unless the rule is abandoned.

The assigned approver can then review the details and approve the SCO.

To approve an SCO:

1. Select Procurement > Subcontract Change Orders.

2. Select the SCO number.

3. Select Workflow Actions > Approve.

   If parallel approvals are configured, all approvers must complete their approvals before the status moves to Approved. If sequential approvals are configured, each approver is prompted in turn.

When the final approval is recorded, Sage Construction Management changes the SCO status to Approved and inserts the current date in the Status Date field. O Only approved SCOs with a status date will update the subcontract’s committed cost and appear in project analytics.

Key restrictions once a workflow rule is in force:

• The SCO cannot be edited unless the rule is abandoned.

• If the SCO has already been imported into a subcontractor invoice and approved there, the status/date are locked.

• If your firm has selected Do not allow Subcontracts or SCOs to be modified after Sub Invoices have been created, SCO items cannot be added or changed once an invoice exists.