Potential Change Orders
Potential Change Orders (PCOs) are the starting point of any budget or cost change. You can generate other change orders from a PCO. Link cost items to provide a connection back to the affected budget, contract, and supplier. However, cost items can also be created directly in the Cost Item tab and assigned to a PCO later.
In this article:
- Potential Change Order Tab Overview
- Create a Potential Change Order
- Edit Existing PCOs
- Generate Change Orders from a PCO
- Populate Pending Change Orders without an Open Subcontractor Change Order
- Create an Internal Budget Transfer from PCO
- Generate a Contract from a PCO
- Apply a Financial Markup to a PCO
- Export a PCO Report
- Related Articles
Potential Change Order Tab Overview
Select Add to create a PCO.
Select In Scope, Budget Only, Out of Scope, or Contingency to change the order's scope. When a change is budget-side only, simply do not add any values to the Estimated, Proposed, or Committed columns.
Type is an optional field if you’d like to number, track, or group change orders by their type.
Source Type and Source Ref are also optional, and you can use them to track or group based on the origin of the change.
Export allows you to export a PDF or CSV PCO report.
Column settings allow you to select the columns you wish to include in your view.
The view selector allows you to store and recall your preferred grouping or column visibility. See the Filter and Group article to learn more.
Select the PCO name to open the flyout panel. The
allows you to edit the name.
Select the More menu
to add cost items, duplicate, change status, and more.
Tip: You can create up to 100 cost items at once by choosing Batch create Cost Item.
Create a Potential Change Order
A PCO is the starting point for any change order. You can create it manually in the Change Order tool or create a PCO from an RFI, Issue, or Submittal Item.
To create a PCO:
Select the Change Order tool from the left navigation.
Select the PCO tab.
Click Add.
Enter a name for the PCO.
Set the Scope to In Scope, Budget Only, Out, or Contingency. The scope determines where the PCO appears in the budget and contract overview. You can also change the scope on the cost item level. Choose the scope from the available options:
- In Scope: Represents a cost-side change only, without affecting the budget.
- Budget Only: Indicates a budget-side change only, with no cost-side impact.
- Out of Scope: Refers to a budget-side change for items not included in the original scope. The owner will allocate extra budget through a PCO to cover the cost.
- Contingency: Denotes a change that is out of scope funded by transferring amounts from an existing contingency budget.
Tip: To learn more about scopes and how change orders populate in the budget and contract tables, see the Budget and Contract Tables article.Choose a PCO Type.
Choose a PCO Source Type. Available source types are:
- ASI: Architect's Supplemental Instruction
- CCD: Construction Change Directive
- INT: Internal
- ISSUE: Issue
- RFI: Request for Information
- RFP: Request for Proposal
- T&M: Time and Materials
Tip: You can deactivate the default types or add your own. See the PCO Source Types section in the Change Order Settings to learn more.Select or enter a Source Ref #. If the PCO is generated from an issue, you can select the issue. If the PCO is entered manually, you can enter any reference number.
To add a location to a PCO, use the Location field within the table. By doing this, you can filter and group to see a location-based view of changes. Project administrators configure locations within Build’s settings.
Now you can add more details to a PCO or generate a change order. Leaving a PCO as a draft will mean that any costs are not shown or used in calculations in the budget or contract overview. Setting the status to Open triggers those calculations, and the impact will be shown in the overview.
Create a Potential Change Order (PCO) from Project Management Workflows
It’s common for an Issue or RFI to incur a potential cost change. In such cases, Autodesk Build members can generate a Potential Change Order directly from the item. This streamlines the process and creates a connection between the workflows, reducing the risk of data loss and capturing the origin of the change order.
To work with this workflow, members need Full Control permission level for Cost Item and PCO in Cost Management.
Create a PCO from an RFI, Issue, or Submittal Item
From either a new or existing RFI, Issue, or Submittal item record:
Scroll to References and select Add reference.
Choose PCO.
In Add PCO Reference, select Create.
Fill in the PCO name and description, then select Create.
This information will populate the new PCO record within Cost Management, where it can be altered later.
Link Existing PCO(s) to an RFI, Issue, or Submittal Item
To link existing PCO(s) to project management items, follow the steps in the previous section, but instead of creating a PCO, choose the existing PCO(s) from the list and click Add PCO.
Within the RFI, Issue, or Submittal item list view in the Linked References column, select the PCO number to open the PCO in Cost Management. If the member does not have the correct permission level, this option will not be accessible.
An RFI is also shown in the Linked References section in the change order's details panel when:
- A PCO is linked to the RFI
- An RFQ, COR, OCO, or SCO is generated from the PCO
Learn more about the RFI workflow.
Create a PCO Through the Change Order Transfer (Collaborative PCO)
Collaborative PCO users with Collaborate permission can generate change order transfers, which are net-zero PCOs that move budget from one item to another without changing the total budget.
To create a change order transfer:
Go to the Change Order tool in Cost Management and select the PCO tab.
Click Change order transfer.
In Add change order transfer from Contract:
- If your company has only one associated supplier contract, the contract field will autopopulate.
- Use the Schedule of Values picker to select the SOV items for the transfer (only budget-associated SOV items are listed).
- Select From and To budgets to create the transfer.
Review the PCO preview showing the combination of positive and negative cost items:
- If budgets in From and To are linked to the same contract, positive and negative cost items are combined in the same PCO.
- If not, positive and negative cost items are placed in separate PCOs.
Click Add PCO.
Submit the change order transfer PCO through the normal PCO workflow. See Create a PCO as a Collaborative Access User for further instructions.
Create a PCO from Forecast Adjustment
You can create a PCO from forecast adjustment to request additional budget. This can be done when project administrator set revenue forecast.
To do so:
- Open th Budget tool in Cost Management.
- Click the blue triangle in the Budget Forecast Adjustments column in the Budget Forecast section of the table. Those are visible if revenue forecast is on. The bottom flyout opens.
- Click the More menu More menu next to the forecast adjustment. Tip: You can also batch create PCOs from forecast adjustments. To do so, check all the boxes next to forecast adjustments in the bottom flyout and click Generate PCO.
- Choose Generate PCO.
The Generate PCO window opens. You can generate from budget forecast adjustment, cost forecast adjustment, or both.
After the PCO is generated, you'll see changes in the Pending Owner Changes. If you generated from budget forecast adjustment, Budget Forecast Adjustment Qty is set to 0. As a result, Amount is also set to 0. Unit Cost is not changed. There are three activity logs after this procedure.
It's the similar rule for other options. If you generated PCO from cost forecast adjustment, you'll see changes in Cost Forecast Adjustment section and so on. If from both - you'll see changes in both places and there will be five activity logs.
Create a PCO as a Collaborative Access User
If you are a supplier with collaborative permissions and have been enabled by an administrator to create PCOs, you can submit a PCO.
To create a PCO as a Collaborative Access User, follow these steps:
Go to Change Order tool in the menu. Click Add.
Select the appropriate contract, and choose your budget. Confirm with the Add button.
Fill in the necessary fields and click Submit.
Your PCO is now proposed.
Note: If you click Save and Close instead of Submit, the PCO will be saved as a draft (with the status Pricing). You can edit the fields later by clicking the More menuand choosing Submit.
Edit Existing PCOs
After the PCO is created, you can add more or modify details. To do so:
Click the PCO name to open the details panel.
Add information to the applicable fields in the Details, Recipients, Scope of Work, and other sections, including:
- Name
- Description
- Cost Status (learn more about change order statuses)
- Schedule Change (impact of the PCO, as measured in the number of days the project schedule is changed)
Modify any previously defined fields if necessary.
Generate Change Orders from a PCO
You can generate CORs, OCOs, SCOs, and RFQs from a PCO. To do so, make sure that:
- The PCO's status is set as Open
- There is at least one cost item added
Then:
Click the More menu
next to the PCO.
If the scope of the PCO is:
- In Scope - click Cost Change and choose Generate RFQ or Generate SCO.
- Budget Only - click Budget Change to generate COR or OCO.
- Out of Scope or Contingency - click Budget Change to generate COR or OCO and Cost Change to generate RFQ or SCO.
Tip: To learn more about scopes and how change orders populate in the budget and contract tables, see the Budget and Contract Tables article.
The new change order generates and you’ll be moved to the suitable tab to continue the workflow.
How Data Flows When Generating Change Orders from PCO
When generating change orders from a PCO, data flows through specific fields at two levels:
- Change Order Level: Used for general descriptions and the overall scope of work, which applies to the entire change order and all associated trades.
- Cost Items Level: Used for detailed descriptions and scope of work specific to individual budget codes or trades.
Example scenarios:
Single PCO to OCO. If you generate one OCO from a single PCO:
- The PCO description is copied to the OCO.
- The scope is aggregated from the PCO and its cost items.
Multiple PCOs to OCO. If you generate one OCO from multiple PCOs:
- Descriptions from all PCOs are aggregated and copied to the OCO.
- Scopes from all PCOs and their cost items are aggregated and copied to the OCO.
This workflow reduces manual data entry and helps carry relevant details forward accurately to the appropriate levels. By following this process, you can maintain consistency and streamline the generation of change orders from PCOs.
Change Scope on Cost Item Level in Change Orders
You can edit the scope field for individual change order subitems. This may be helpful in cases where one or more cost items are a budget-only transaction for a particular change order, such as transferring from a noncontingency, allowance, or fee budget item. Scope options include:
- In Scope: Cost Side Change Only
- Budget Only: Budget Side Change Only
- Out of Scope: Budget and Cost Side and will be funded by extra budget
- Contingency: Budget and Cost Side and will be funded by transfer from an existing budget
Specific cost items can be excluded from the budget overview, even if the overall change order retains its original scope.
Populate Pending Change Orders without an Open Subcontractor Change Order
When a general contractor already knows the proposed price, they can populate pending change orders without creating an RFQ. To do so, enter a proposed value in the Proposed column on a cost item level when creating a PCO. The value is shown in the Pending Change Orders column in the Budget table.
Create an Internal Budget Transfer from PCO
Project administrators and members with both Budget and SCO full control permissions can create internal budget transfers directly from PCOs. This is useful when you need to move money from one budget item to another to pay for change orders without requiring extra approvals.
To create a budget transfer from a PCO:
Go to the Change Order tool and select the PCO tab.
You can create a budget transfer in several ways:
- From a PCO: Click the More menu
next to the PCO, click Budget change, and select Transfer budget.
- From multiple items: Select multiple PCOs or cost items, then click Transfer budget in the batch actions.
- From a PCO: Click the More menu
Then, in Internal budget transfer:
- Each selected cost item with a nonzero Committed value creates one transfer line.
- For positive Committed values (money allocated), the system automatically uses the cost item's linked budget in the To field.
- For negative Committed values (money being removed), the system automatically uses the cost item's linked budget in the From field.
- The Amount is automatically set to the absolute value of the Committed amount.
- A note is automatically added referencing the source cost item.
Click
to add more transfers, even those that are not linked to the cost items. Those transfers are separated in the table.
Click
to delete a transfer from the list.
You can use Copy to all "From" or Copy to all "To" buttons to quickly populate all transfer lines with the same budget.
Click Save to create one or more internal budget transfers.
You'll receive confirmation that the budget transfer was completed.
Generate a Contract from a PCO
Before generating a contract, make sure that:
- The PCO's status is set as Open
- There is at least one cost item added
Then:
Click the More menu
next to the PCO.
Choose Cost Change.
Click Generate Contract.
Enter Contract Code and Contract Name. If the foreign currency setting is enabled in your project, you'll see the Currency and Exchange Rate fields as well.
- Choose the currency for your new contract.
- Edit the exchange rate if needed. The default exchange rate is fetched from the settings.
Enter the committed value or copy it from the cost item. If the foreign currency setting is on, the
icon shows the converted value.
Click Generate.
Apply a Financial Markup to a PCO
You can create financial markup formulas to be added to change orders. An example of a financial markup is an add-on such as a bond, contingency, or fee. Before you can apply a financial markup, a project administrator must create the financial markup formula in the Change Order settings tab.
After the financial markup formula is created, you can apply it to PCOs. To do so:
- Switch to the Change Order tab in the Cost module.
- Select the PCO tab within the Change Order tab.
- Click the More menu
of the PCO that you want to add markup formula to.
- Go to Add Markup and select the financial markup formula to use.
Expand the PCO to see that the financial markup is added to the PCO.
If you see that your calculated markups are out of sync, select the line item and in the Apply Markup drop-down select the necessary markup from the list.
Export a PCO Report
You can export a PCO report that will contain all details or a minimum number of them. To do so:
Select the Change Order tool from the left navigation.
Switch to the PCO tab.
Click Export
.
Add the report title.
Choose one of the following:
- PDF Report – to export a report in a noneditable PDF format.
- Excel Report – to export a report in an editable Excel format.
Choose the report template:
- Current View - you can export a report from the current view, for example with applied filters.
- System Default Report – you can export a report with all default columns.
Choose whether you want to include the cost item information in the report. By deselecting this option, you can export a report only with the minimum details.
Add an optional message.
Click Run report.
You’ll receive the report by email. You can also find and download it from the Reports tool.
Reports for Collaborative Access Users
Users with collaborative access are able to export reports from change order tables (PCO/RFQ/COR/OCO/SCO).
For change order reports, cost items and their amounts, such as proposed amounts in RFQ reports, are displayed. However, budget codes and names are not included in these reports.