KIER + Procore: Change Events
Department │ Operations
Internal Process and Standard Operating Procedure: Change Events
***KIER Construction requires all cost changes to be documented within 48 hours***
Background
A change event is any change that affects the original scope of a construction project. It can also be an event that causes a change to the project schedule or results in unexpected costs. In Procore, creating a change event provides your project's team members and stakeholders with the ability to prepare for a cost change before it becomes an actual cost.
EXAMPLE 1: CREATE A CHANGE EVENT TO ESTABLISH A CHANGE ORDER
A change event can come from many sources and is an event that establishes the change order process. Examples include:
- Accommodating an owner's request.
- Accounting for a design flaw.
- Addressing an unforeseen issue caused by a vague document or specification.
EXAMPLE 2: CREATE A CHANGE EVENT TO DOCUMENT A BACKCHARGE
A change event can also be used to document a project condition that resulted in a backcharge. The intent of a backcharge is to recover the unforeseen expenses incurred when performing corrective actions that a party was contractually obligated to perform.
To ensure that you have fully documented the conditions that resulted in the backcharge, you can create a change event. Common scenarios for documenting backcharges this way include:
- Repairing something that a subcontractor damaged.
- Cleaning up an area that the subcontractor was obligated to clean.
- Replacing defective materials provided by the subcontractor.
- Reinstalling an incorrect installation performed by a subcontractor.
- Bringing a neglected issue into compliance with safety regulations.
- Providing unforeseen equipment rental and use costs.
After a change event is created, you can then send a Request for Quote (RFQ) to your subcontractors. Subcontractors can then respond to RFQs (or a general contractor can enter a response to an RFQ on the subcontractor's behalf). Included in the RFQ response is all the required documentation related to the change event's potential cost and schedule impact. After your subcontractor's RFQs responses are reviewed, your project team has the information it needs to proceed with creating a Potential Change Order (PCO).
Things to Consider
- Required User Permissions:
- 'Standard' level permissions or higher on the project's Change Events tool.
- Limitations:
- A change event 'Number' is limited to a maximum of ten (1) characters.
-
Alternate ways to create change events:
- To learn how to use other Procore platforms and tools to create a change event, see Which Procore tools can I use to create a change event?
Steps
Create a New Change Event
- Choose from these options:
- Open the Project Tools menu and click the Create Circle
.

OR - Navigate to the project's Change Events tool. Then click the Create button.

- Open the Project Tools menu and click the Create Circle
- In the 'New Change Event' page, enter the following:
- Origin
Select the Procore tool and item from which your change event originates. - Change Event Number
Procore automatically assigns new numbers to change events in ascending sequential order. - Title
Enter a descriptive title for the change event. - Status: Select a status for the change event from the drop-down list
- Origin
|
Status |
Definition |
|
Closed |
This status indicates that the change event and all related items such as RFQs and change orders are complete |
|
Open |
(Procore’s Default) This status indicates the change event is open and Procore users are actively managing items related to the change event. For example, a budget modification, Potential Change Order (PCO), ROM, and/or Request for Quote (RFQ). |
|
Out for Pricing |
This indicates that RFQs have been requested. |
|
Pending |
This status indicates the change event is waiting to be reviewed. |
|
Pending Owner Approval |
This status indicates the change event is waiting to be reviewed by the owner. |
|
Pending PM Review |
This status indicates the change event is waiting to be reviewed by the project manager. |
|
Void |
This status indicates no change resulted from the change event. To view voided events, select Void or All (Include Void) from the Add Filters menu on the Change Events list page. |
- Scope
Select Out of Scope. - Expecting Revenue
Select YES or NO. If YES, select one of the options from the Line Item Revenue Source field. If NO, Revenue ROM amounts will be set to zero (0). - Line Item Revenue Source
Select one of the options from the list: Match with latest cost, No revenue expected, or Quantity x Unit Cost. - Type
Select one of the following from the drop-down menu:
|
Backcharge |
A Backcharge is an amount of money that a PM holds back from a subcontractor to recover any costs incurred due to the subcontractor performing incomplete or defective work. |
|
Internal |
Internal (IWO) means that KIER is paying for the change with an internal budget, internal contingency, or by back-charge from one subcontractor to another. |
|
Owner Change |
Owner is paying for the change and a PCO/PCCO will be formalized and sent to the Owner. |
|
Transfer |
A Transfer refers to a change in ownership for the performance of work. |
- Change Reason
Select a reason for the change from the drop-down menu:
|
Allowance |
An Allowance is an amount of money that has been set aside in a construction contract’s original sum to cover the costs of paying for known items that were not specified in detail in the contract. |
|
Backcharge |
A Backcharge is an amount of money that a PM holds back from a subcontractor to recover any costs incurred due to the subcontractor performing incomplete or defective work. |
|
Buyout |
Buyout refers to a cost for a commitment that was included in the original budget but was not bought out until after the handoff meeting with the Estimating Department or when a subcontractor is brought on to supplement another sub after default. |
|
Client Reason |
A Client Request refers to a change in the performance of work initiated by a request from the construction project’s client. |
|
Design Development |
Design Development |
|
Existing Condition |
An Existing Condition refers to a change that occurs where design plans must be modified due to existing conditions at the job site. |
|
Field Directive |
Field Directive instructs subcontractors to complete additional work, correct unacceptable work, provide clarification about the work, or perform emergency work. |
|
Internal Work Order |
Internal Work Order (IWO) means that KIER is paying for the change with an internal budget, internal contingency, or by back-charge from one subcontractor to another. |
|
Scope Gap |
The term scope gap refers to an instance where there is a gap in understanding of project expectations. It is a fundamental lack of clarity and understanding of project goals, deliverables, and expectations. |
|
Winter Conditions |
Winter conditions refer to specific budget line items added to accommodate increased fuel, material, and labor expenses related to activities during the coldest months of the year. Weather delay days, concrete blankets, fuel for heaters, hot water, chemical additives, tenting, etc. |
- Description
Describe the event that may result in a change in costs. - Attachments
Attach any relevant files. - Prime Contract (For Markup Estimates)
Select the contract containing the markup settings you want to use to calculate the markup on the Rough Order of Magnitude (ROM) values. Procore automatically selects the contract with the lowest number.

- Click Save.
Procore saves the new change event.
Add Change Event Line Items
- Navigate to the project's Change Events tool.
- Choose from these options:
- Click the Detail tab. Then find the change event to update and click Edit.

OR - Follow the steps in Create Change Events.
- Click the Detail tab. Then find the change event to update and click Edit.
- In the 'Edit Change Event' page, scroll to the 'Line Items' card.
- Choose from these options:
- To add one (1) new line item on the change event, click Add Line.
OR - To add line items in bulk using line items from all of the project's commitments in the 'Approved' status, click Add Lines for All Commitments.
OR - To import line items from a CSV file, see Import Change Event Line Items from a CSV File.

- To add one (1) new line item on the change event, click Add Line.
- Complete the line item data entry as follows:
- Budget Code
Select a budget code - Description
Enter a description for the line item. - Vendor
Select the vendor's company name from the drop-down menu. - Contract
Select the impacted purchase order or subcontract from the drop-down menu. See Create a Purchase Order or Create a Subcontract. - Qty
Enter a numeric value in this box to indicate the number of units that correspond to the unit of measurement that you specify. - UOM
Select a Unit of Measure (UOM) from the drop-down list. To learn about the default selections in this list, see Which units of measure are included in Procore's master list? and Add a Unit of Measure to the Unit of Measure Master List. - Unit Cost
Enter the monetary cost in this box to indicate the cost per unit of measurement. - Cost ROM
Enter a numeric estimation of the cost's Rough Order of Magnitude (ROM).- If you follow those steps to show the ROM value in the budget, and the change event line item ends up having no cost, you will need to zero out the ROM or close the change event to remove it from the budget
- Budget Code
- Click Update.
NOTE
If the budget code was not included on the project's original budget, a confirmation message appears for you to confirm that you want Procore to add these line items to the budget. Procore adds the new line item(s) to the project's budget and a question mark
appears next to each partial budget line item. To learn more, see What is a partial budget line item? and Add a Partial Budget Line Item.















The Funding tool is available as a limited release for Procore customers in the United States who have implemented the Procore for Owners point-of-view dictionary. To learn more, see 
