Bulk update change event status in Procore
Have you ever needed to move thirty change events out of pending, one at a time, on the last day of the month?
Procore has no native bulk status edit for change events. Here is what the tool actually supports, and how to change status across a project in one pass.
Procore has no true bulk status edit for change events. The list view allows inline edits on a handful of fields, and everything else means opening records one at a time, which is why month end turns into thirty rounds of the same four clicks. The shortest path that holds: pull every change event on the project into an Excel table, filter to the batch, fill the new status down, review, sync.
Pull every change event on the project into Excel
Open the Change Events tool in the Sandspit task pane and click Pull from Procore. One pull writes two sheets: one row per change event, and one row per line item. The status you are about to change is a dropdown column on the first sheet.
Watch out: a workbook is bound to one Procore project. A sweep across four jobs is four workbooks, each with its own pull and sync.
Filter the table to the batch
The sheet is a native Excel table, so use Excel. Filter the Status column to the value you are clearing, and narrow further by change type, reason, or date if you need to. The rows you can see are the rows that change.
Fill the new status down
Pick the new status from the dropdown in the first visible row and fill it down the filtered rows. Cells you change are highlighted against the value you pulled, and the task pane lists each changed row with before and after values.
Review the staged changes before they leave the sheet
Clear the filter and look at the Ready to sync list in the task pane. Status is a financial signal on a live job, and a bulk edit is exactly as fast at being wrong as it is at being right. Anything under Needs attention has a one-click fix.
Watch out: there is no single undo once records are written. Reversing a bad batch means another bulk edit back the other way, so the review list is the cheapest place to catch it.
Sync to Procore
Click Sync 30 changes to Procore. Only the fields that changed are sent, one change event per request, so one rejection does not stop the rest. If someone edited a change event in Procore since your pull, the task pane offers Refresh and merge before you sync.
Why this one hurts
Status is the field that gets touched most and batches worst. A change event moves through its lifecycle as pricing firms up, and the status has to follow. That is fine on one record. It is a different job at month end, when a project executive wants the pending column cleared and there are thirty events sitting in it.
The work is not hard. It is just thirty rounds of the same four clicks: open the record, change the field, save, go back. Nothing about the thirtieth one is more considered than the first.
What Procore supports natively
Procore’s bulk capabilities for change events are real but narrow, and none of them are status edits:
- CSV line item import. Adds new line items to a change event from the Schedule of Values template. An insert path, not an update path.
- Bulk commitment change order creation. Select line items across commitments and generate commitment change orders in one action from the line items view.
- Inline edits on the list view. A limited set of fields can be edited without opening the record. Useful, but it is still one row at a time.
So the honest answer to "can I bulk update status in Procore" is no, and the workaround people reach for is the export, edit, re-import loop. That loop is where the data goes stale, because the import cannot update what the export contained.
Frequently asked
Can you bulk update change event status natively in Procore?
Not as a true bulk edit. Procore’s Change Events list view supports inline editing on a limited set of fields, but most status changes are made by opening each change event individually. Procore’s bulk features for change events center on CSV line item imports and bulk commitment change order creation, both of which create records rather than edit the status of existing ones.
Does the CSV import let me change status on existing change events?
No. The Schedule of Values CSV template adds new line items to a change event. It is an insert path, not an update path, so it cannot move an existing change event from one status to another.
What permissions do I need?
Standard or Admin on the project’s Change Events tool. The Change Events tool in Sandspit is also turned on per company, so if it is not on your task pane home, ask support to enable it.
Can I update status across multiple projects at once?
Not in one sheet. A Sandspit workbook works with one Procore project at a time, and the pull brings in every change event on that project. For several projects, use one workbook per project and repeat the filter, fill, and sync.
What happens if a change event was edited in Procore while I was working?
Sandspit checks Procore for changes since your pull. If it finds any, it offers Refresh and merge, which brings Procore’s values into the sheet while keeping your unsynced edits. Where you and Procore changed the same field, the row shows a conflict and you choose which value to keep.
Procore Project Financials. Needs Standard or Admin on the Change Events tool. One project per workbook.
Step-by-step mechanics, every column, and every error message are in the documentation.
