Simplified Change Order Process

The simplified change order process lets you generate Owner Change Orders (OCOs) and Supplier Change Orders (SCOs) directly in their final status, bypassing intermediate statuses and approval workflows. This streamlines workflows for teams that don't need multi-step review processes.

With the simplified process enabled:

• OCOs are generated directly in the Approved status
• SCOs are generated directly in the Sent status

In this article:

• Enable the Simplified Change Order Process
• Primary User Roles
  • Default Settings by Role
• Generate Approved OCOs
• Generate Sent SCOs
• Behavior Notes
• Role-Based Defaults
  • Supplier as Primary User
  • Owner as Primary User
• Related Articles

Enable the Simplified Change Order Process

Project administrators can enable the simplified process through Project Process settings. The available options depend on your company's role in the project.

To enable the simplified change order process:

1. Select the Settings tool from the left navigation.
2. Switch to the General tab.
3. Go to Project Process and click Edit.
4. Navigate through the wizard to Upstream change order or Downstream change order.
5. Enable the desired toggle:
   • Simplified Owner Change Order Process
   • Simplified Supplier Change Order Process
6. Click Save.

Primary User Roles

Your company's role in the project determines which simplified process options are available and their default settings. When setting up Project Process, select your company's role:

• Main Contractor: Traditional general contractor role managing both upstream (owner) and downstream (supplier) workflows.
• Owner: Project owner role that typically receives change orders rather than creating them.
• Supplier: Subcontractor or supplier role working primarily with downstream workflows.

Default Settings by Role

Generate Approved OCOs

When the Simplified Owner Change Order Process is enabled, OCOs are generated directly in the Approved status. This bypasses the typical Draft → Open → Submitted → Approved workflow.

You can generate approved OCOs from:

• PCO (Potential Change Order)
• COR (Change Order Request)

To generate an approved OCO:

1. Select the Change Order tool from the left navigation.
2. Select the PCO or COR tab.
3. Select one or more PCOs with cost items.
4. Click the More menu next to the item.
5. Click Budget Change and choose Generate OCO.
6. Complete the generation dialog and click Generate.

The OCO is created directly in Approved status. A confirmation message appears: "OCO generated in the Approved status." You can proceed to generate SCOs or set the OCO as Executed.

Generate Sent SCOs

When the Simplified Supplier Change Order Process is enabled, SCOs are generated directly in the Sent status. This bypasses the typical Draft → Open → Sent workflow.

You can generate sent SCOs from:

• PCO (Potential Change Order)
• RFQ (Request for Quotation)
• COR (Change Order Request)
• OCO (Owner Change Order)
• Cost Item

To generate a sent SCO:

1. Select the Change Order tool from the left navigation.
2. Select the appropriate tab (PCO, RFQ, COR, OCO, or Cost Item).
3. Select one or more PCOs with cost items.
4. Click the More menu next to the item.
5. Click Cost Change (or Generate for Cost Items) and choose Generate SCO.
6. Complete the generation dialog and click Generate.

The SCO is created directly in Sent status. A confirmation message appears: "SCO generated in the Sent status." You can proceed to set the SCO as Executed.

Behavior Notes

When you generate change orders with the simplified process:

• Approval workflows are bypassed: Even if approval workflows are configured, they don't run for simplified generation.
• Required fields aren't validated: Required fields remain empty when the change order is created. The Set as Executed action is disabled until all required fields are filled in.
• Compliance requirements aren't checked (SCO only): Compliance requirements remain noncompliant when the SCO is created. The Set as Executed action is disabled until compliance requirements are met.
• Status actions remain available: The generated change order works like any regular approved OCO or sent SCO. You can revert to previous statuses if needed.

Role-Based Defaults

When you select a primary user role, the system applies default settings for custom terms and company setup. You can also manually configure custom terms in Additional Terms.

Supplier as Primary User

Owner as Primary User

Related Articles

• Project Process Settings
• CORs, OCOs, and SCOs
• Change Order Statuses
• Approval Workflows
• Compliance Requirements