Yes. If you are a Procore Administrator or if you have 'Admin' permissions on the project's Admin tool, your company's Procore Administrator (or a user with 'Admin' level permissions on the Project Admin tool) can enable the Change Events tool. However, before enabling the tool, it is important to follow the steps below:
- Step 1: Check to See if Any Variations Exist on the Project
- Step 2: Request to Run the Variation Migration Process
- Step 3: Run the Variation Migration Process (This step is performed for you by Procore)
- Step 4: Enable the Change Events Tool
Step 1: Check to See if Any Variations Exist on the Project
Before enabling the Change Events tool, determine if any variations have been created on the project. To view a list of variations on a project, follow these steps: View Variations.
- If variations have NOT been created on the project, you can skip steps 2 and 3 below and proceed with Step 4: Enable the Change Events Tool.
- If variations have been created on the project, you must complete Step 2: Request to Run the Variation Migration Process below.
Step 2: Request to Run the Variation Migration Process
If you discover that your users have already created variations on the project, your company's Procore Administrator or a user with 'Admin' level permissions on the project's Admin tool must send an email to your company's Procore point of contact requesting to run Procore's variation migration process on your project.
The purpose of the migration process is:
- To create a new change event for every Head Contract Potential Variation (PV) that exists.
- To create new line items in each new change event for each line item on every Head Contract PV.
- The variation migration process is best suited for clients who have configured the two (2)-tier variation setting on the Head Contracts tool. See What are the different variation tiers in Project Financials?
- It is less common for clients to configure the three (3)-tier variation tier setting on the Head Contracts tool. However, most Procore clients who choose to configure three (3) tier (or more tiers) typically decide to leave the project's Change Events tool disabled on their projects.
Step 3: Run the Variation Migration Process
This step is performed for you by Procore. Your Procore point of contact will notify you when the migration process is complete.
Step 4: Enable the Change Events Tool
- Update your default permission templates. See What are the default project permissions templates in Procore? and Manage Project Permissions Templates.
- To send a Request for Quote (RFQ) to your collaborators, you must provide those collaborator(s) with 'Standard' level permissions on the project's Commitments tool.
- To provide one of your employees with the ability to create a change event (For example, a Foreman or Site manager), those employees will need to be granted 'Standard' level permissions on the project's Change Events tool.
- Procore also recommends that you consider providing any appropriate employees with 'Admin' level permissions on the project's Change Events tools.
BETATo allow your project collaborators to submit variations, see (Beta) Allow Collaborators to Submit Site-initiated Variations.
- Enable the tool on Procore's standard project template so the Change Events tool is turned ON in your company's new projects by default. See Edit a Project Template and Add and Remove Project Tools.