Configure Settings: Change Events
Objective
To configure advanced settings for the project's Change Events tool.
Background
If you have been granted the appropriate permissions, you can configure a variety of advanced settings for the project's Change Events tool.
Things to Consider
- Required User Permissions:
- 'Admin' level permissions on the project's Change Events tool.
- Additional Information:
- To learn more about the columns displaying in the Change Events tool, see these links:
- To enable the 'Sub Jobs' column, see Enable Sub Jobs on Projects for WBS.
- To enable the 'Production Qty' and 'Production UoM' columns, see Enable the Labour Productivity Cost Features for Project Financials.
- To enable the 'Non-Commitments' column, see How do I track non-commitment costs on a change event?
- For more information, see How do the Change Events tool's column display settings work?
- To learn more about the columns displaying in the Change Events tool, see these links:
Prerequisites
- Review this FAQ. See Can I enable the Change Events tool on my existing project?
- Add the Change Events tool to the project. See Add and Remove Project Tools
Steps
Follow these steps in these tasks to configure the settings for the Change Events tool:
- Enable and Disable the Column Display
- Maintain Budget Codes Across All Line Items in Sync
- Add Estimated Markup to All of the Change Events on a Project
- Set Attachment Settings
Configure the Budget ROM Settings - Prevent Budget Changes and Potential Variations on the Same Change Event Line Item
- Set User Permissions
Enable and Disable the Column Display
- Navigate to the project's Change Events tool.
- Click Configure Settings .
- Choose from these options to show or hide columns in the Change Events tool.
Note: The system turns all column displays on, by default. You can disable these columns by removing the tick. For a complete list of column's these settings affect, see How do the Change Event tool's column display settings work?- Display Revenue ROM, Latest Price, Latest Cost and Over/Under Columns
This checkbox turns the Revenue ROM columns ON and OFF. The default setting on new Procore projects is ON.- To enable the columns, place a tick in this checkbox.
- To disable the columns, remove the tick from this box.
Important
- If you choose to disable these columns from the Change Events tool, the 'Revenue ROM' column continues to be available in main contract variations. To learn more about the Revenue ROM columns, see Add Financial Markup Lines with Revenue ROM to Change Events.
- If you create a change event (see Create a Change Event) and select 'TBD' or 'In Scope' from the change event's Scope drop-down list, the 'Revenue ROM' field in the main contract variation shows £0. If you choose 'Out of Scope,' the field shows the latest cost.
- Display UoM, Revenue Qty, Revenue Unit Cost, ROM Unit Qty and ROM Unit Cost Columns
This tickbox turns the unit-based columns ON and OFF in the view page of a change event. The default setting for this tickbox is OFF.- To enable the columns, place a tick in this box.
- To disable the columns, remove the tick from this box.
Notes
- Removing the setting does NOT disable the columns when creating a change event. They are only hidden when viewing a change event.
- If your company is going to be creating change events from the Daywork Sheets tool, it is recommended that you enable this setting. If you do not, the summarised line item information from a Daywork Sheet will not be visible in a change event. See Create a Change Event from a Daywork Sheet.
- Display Revenue ROM, Latest Price, Latest Cost and Over/Under Columns
- Click Save.
Beta
Maintain Budget Codes Across All Line Items in Sync
Change event line items associated with variations will now be editable as long as the variation is also in an editable state. How are line items and budget codes updated across change objects?
When users update budget codes they will sync across linked change objects if those objects are also in an editable state.
- Navigate to the project's Change Events tool.
- Click Configure Settings .
- Check the box next to Maintain Budget Codes across all Line Items in sync.
- Click Save.
Note: This setting is NOT retroactive. Budget codes that were not matching between objects before enabling this setting will not automatically sync upon activation. Only budget codes changed after enabling this setting will sync between objects.
Set Attachment Settings
Tip
These settings can be turned ON and OFF on your project by a user with 'Admin' permission on the Change Events tool. When the configuration settings are enabled, the system automatically attaches any documentation from the last RFQ response to new main potential variations and new commitment variations when using the Bulk Actions menu to create variations.
- Navigate to the project's Change Events tool.
- Click Configure Settings .
- Choose from these options to include RFQ attachments in new variations:
- Copy attachments from RFQ response to Main PVs. Place a tick in this box to enable a setting that automatically includes the attachments from related RFQ response to a new main contract variations. See Create a Main Potential Variation from a Change Event.
- Copy attachments from RFQ responses to Commitment VARs. Place a tick in this box to enable a setting that automatically includes the attachments from related RFQ response to a new commitment variation. See Create a Commitment Variation from a Change Event.
- Click Save.
Limited Release
Configure the Budget ROM Settings
You can define the business logic that Procore users to automatically complete the 'Rough Order of Magnitude' value of a budget change. If the budget view assigned to a project includes the 'Budget ROM' column, the value is automatically populated in that project's budget when users create and edit budget changes. See Create Budget Changes).
- Navigate to the project's Change Events tool.
- Click Configure Settings .
- Scroll to the Budget ROM section.
- Choose Latest Cost, Latest Price or None from the following drop-down lists to define how the budget change feature handles the 'Scope' setting for a change event in your project's budget:
- Budget ROM for In Scope. This drop-down list applies your selected setting to changes that are marked 'In Scope'.
- Budget ROM for Out of Scope. This drop-down list applies your selected setting to changes that are marked 'Out of Scope'.
- Budget ROM for TBD Scope. This drop-down lists applies your selected setting to changes that are marked 'TBD' (to be determined).
- Click Save.
Tip
- The 'Budget ROM' amount in Procore can always be edited manually by project users.
- To learn how to add a 'Budget ROM' source column for your budget changes to a Procore budget view, see Add a 'Budget ROM' Column to a Budget View.
Beta
Prevent Budget Changes and Main Variations on the Same Change Event Line Item
This setting will only become available when your company account has Budget Changes turned 'ON'.
Turn this setting 'ON' to prevent Change Event line items from having both a revenue impact and budget impact. When this setting is turned 'ON', a Change Event Line Item cannot have a Budget Change and Main Contract Variation associated at the same time.
- Navigate to the project's Change Events tool.
- Click Configure Settings .
- Scroll to the Budget Changes section.
- Check the box next to Prevent Budget Changes and Potential Variations on the Same Change Event Line Item.
- Click Save.
Add Estimated Markup to All of the Change Events on a Project
Set User Permissions
- Navigate to the project's Change Events tool.
- Click the Configure Settings icon.
- Set the access permission level for the tool's users by clicking the icon in the desired column so a GREEN tick appears.
The colour-coded icons in the user permissions area denotes the user's access permission level to the tool. To learn more, see What are the default permission levels in Procore?
Icon Colour Header Column 3 GREEN The user has been granted this level of access permission to the tool. RED The user has NOT been granted this level of access permission to the tool. GREY The user is either (1) a Procore Administrator or, (2) has been granted access permission to the Procore tools on this project using a permission template (see What is a permissions template?). To change the user's access permission level, follow the steps in Manage Project Permissions Templates.