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

Prerequisites

Steps

Follow these steps in these tasks to configure the settings for the Change Events tool:

Enable and Disable the Column Display

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. 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 checkmark. 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 checkmark in this checkbox. 
      • To disable the columns, remove the checkmark 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 head 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 head 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 checkbox turns the unit-based columns ON and OFF in the view page of a change event. The default setting for this checkbox is OFF. 
      • To enable the columns, place a checkmark in this box.
      • To disable the columns, remove the checkmark 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.
  4. 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.

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. Check the box next to Maintain Budget Codes across all Line Items in sync.
  4. 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 head potential variations and new commitment variations when using the Bulk Actions menu to create variations.

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. Choose from these options to include RFQ attachments in new variations:
    • Copy attachments from RFQ response to Head PVs. Place a checkmark in this box to enable a setting that automatically includes the attachments from related RFQ response to a new head contract variations. See Create a Head Potential Variation from a Change Event. 
    • Copy attachments from RFQ responses to Commitment VARs. Place a checkmark 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.
  4. 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).

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. Scroll to the Budget ROM section. 
  4. 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:
    change-events-budget-rom-settings.png 
    • 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). 
  5. 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 Head 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 Head Contract Variation associated at the same time.

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. Scroll to the Budget Changes section. 
  4. Check the box next to Prevent Budget Changes and Potential Variations on the Same Change Event Line Item.
  5. Click Save.

Add Estimated Markup to All of the Change Events on a Project 

  1. Navigate to the project's Change Events tool.
  2. Click Configure Settings icons-settings-gear.png.
  3. Click Copy to Existing Change Events to copy the markup settings from the default Head Contract (This is the first Head Contract on your project when sorted by number then title).
  4. Click Confirm.
     NoteS 

Edit Financial Markup (Vertical) Estimate on a Change Event

Note: A Head Contract for Markup Estimates must be selected on a change event before markup can be edited on individual line items. See Add Estimated Markup to a Single Change Event.

  1. Navigate to the project's Change Events tool. 
  2. Locate the change event with the financial markup (vertical) to be edited and click its number to view the change event. 
  3. Click the value being edited in the markup section of the change event.
    2023-06-01_14-46-17.png
  4. Click Manual markup and enter a new markup amount.
    2023-06-01_14-52-55.png
  5. Changes are saved automatically once you click outside of the experience. 
 Important notes!
  • If you manually enter a markup value, it will no longer stay updated with the head contract's markup settings.

    • To reapply the contracted financial markup to the change event line items, the user must remove the current financial markup from the change event then complete the steps list here: Add Estimated Markup to a Single Change Event.

Creation of Head Contract Variations from Change Events with Edited Markup
  • When users create a Head Contract Variation from a change event with the edited financial markup, the Head Contract Variation will inherit the edited financial markup percentages entered on the change event.
  • Only vertical markup can be edited on a change event
  • There are some scenarios where edited financial markup in change events will not be able to pass to the Head Contract Variation due to complexity and the possibility of conflicting markup rules and logic. 
  • In the following scenarios, the user will have to edit the variation markup in the Head Contract Variation Schedule of Values.
    Note: Edited markups will remain in the change event, but the new Head Contract Variation will use the selected head contract markup rules
    • When multiple change events are used to create a variation.
    • When adding change event line items to an existing Head Contract Variation with markup logic already applied
    • Creating a new Head Contract Variation from a change event where the selected head contract conflicts with the change events 'Head Contract for Markup Estimates' field

 

Set User Permissions 

  1. Navigate to the project's Change Events tool.
  2. Click the Configure Settings icons-settings-gear.png icon.
  3. Set the access permission level for the tool's users by clicking the icon in the desired column so a GREEN checkmark 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-check.png GREEN The user has been granted this level of access permission to the tool.
    red-x.png RED The user has NOT been granted this level of access permission to the tool. 
    grey-x.png 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.

     

See Also