Import a change event log into Procore with Copilot or Claude
Have you ever retyped an eighty-line buyout log into Procore change events, one line at a time?
Hand your own hold, buyout, or PCO log to Copilot or Claude, let it fill the change event sheet, review what it flagged, and sync.
To import a change event log into Procore, open the Sandspit extension in Excel and use Create Change Events. Click Guide so Copilot or Claude can read how the sheet works, ask it to turn your log into change event lines using the project’s codes on Picklists, then review what it flagged and sync. Every line with the same number lands on one change event.
Put your log in the workbook
Paste or copy your hold log, buyout log, or PCO log onto its own sheet in the workbook, in whatever format your team already uses. Open the Sandspit extension, choose Create Change Events, and stay on the Bulk Import tab.
Open the Guide for your AI
Click Guide in the pane. Sandspit adds the Create Change Event Guide sheet. Its For AI assistants section tells Copilot or Claude how Change Event Import works: one row per line item, the same Change Event Number on every line of an event, and codes chosen from the Picklists sheet.
Note: the guide tells the assistant to flag ambiguous vendor and cost code matches, leave unknown amounts blank, and stop at the draft unless you ask it to sync.
Ask Copilot or Claude to map the log
Ask your assistant to read the guide and Picklists, then turn your log into rows on Change Event Import, one row per line, with one change event number for the package. For example: “Read the Create Change Event Guide and Picklists. Turn Buyout Log into change event 210, one row per line. Flag anything you can’t match.”
Review what it flagged
Fix anything the assistant flagged, such as a line with no cost code, by picking from the Budget Code or Vendor dropdown. Then read the lines in the pane: each change event shows as CE 210 · 16 line items with every line’s budget code, vendor, and Cost ROM. Anything that doesn’t match the project shows under Needs attention with a fix.
Sync the change event
Click Sync 1 change to Procore. The change event is created with all its line items, Sync Status reads Synced on every row, and the Procore Link column fills in.
Why logs don’t paste straight in
Every team keeps its log differently: trade names instead of budget codes, sub nicknames instead of directory names, one tab per package. Mapping eighty lines of that onto Procore’s fields by hand is the slow part, and it’s exactly the part an assistant is good at.
Who does what
- Your assistant maps. It reads the guide and Picklists and fills Change Event Import.
- Sandspit checks. Budget codes, vendors, numbers, and amounts are validated against the project.
- You decide. Nothing reaches Procore until you review the lines and click Sync.
Frequently asked
How do I import a change event log into Procore from Excel?
Put the log in the workbook, open Create Change Events, and click Guide. Ask Copilot or Claude to map the log onto Change Event Import using the guide and Picklists, review the rows, and sync. Rows with the same Change Event Number become one change event.
Does Sandspit use AI to read my log?
Not on this path. Your own Copilot or Claude in Excel does the mapping, and Sandspit validates the rows against the project before anything is sent. For PDFs, photos, CSVs, or spreadsheets of T&M, the AI Extraction tab is the built-in route.
Do I need Copilot or Claude?
No. You can paste or type the rows yourself. An assistant helps when the log is long or in a format that doesn’t line up with the import columns.
Can one change event have eighty lines?
Yes. Put the same Change Event Number on every row that belongs to it. A buyout spread across many cost codes becomes one change event with a line per code.
Can I add a line for every commitment on the job?
Yes. Open Quick actions, choose Lines from commitments, pick a change event number and the contracts, and click Add lines to sheet. Each line gets its budget code, vendor, and contract. Amounts are left blank for you to fill in.
What permission do I need?
Standard or Admin on the project’s Change Events tool.
Procore Project Financials. Needs Standard or Admin on the Change Events tool. Your own Copilot or Claude in Excel does the mapping; Sandspit validates the rows before sync.
Step-by-step mechanics, every column, and every error message are in the documentation.
0:50 Pull Procore data into Excel for custom reports
Have you ever rebuilt the same cost report from a fresh Procore export every Monday morning?
0:32 Compare a Procore budget to last month’s snapshot in Excel
Have you ever exported the Procore budget at month end, pasted it beside last month’s, and remapped the columns just to see what moved?