Change Order work rarely lives in one place. Project teams are constantly moving between conversations, CORs, progress tracking, and connected systems to understand what changed and where things stand.
September’s updates make that work a little easier. This month, Clearstory adds practical improvements across communication, reporting, project setup, and integrations, from CN messaging and WIP reporting to Procore imports and status visibility. Here’s what’s new:
September at a Glance
- CN Messaging: Message a trade partner, or just your own team, directly on a Change Notification.
- Move CORs Between Projects: Move a COR to a different project, with its line items, attachments, revisions, and history intact.
- Waived Stage for Voided CORs: Record a COR the contractor withdrew as a concession as Waived, not rejected.
- WIP Reporting for Received CORs: Track earned progress on the CORs you receive, not just the ones you send, and export any WIP view.
- Procore Project and Contract Import: Create a Clearstory project from a Procore project, and bulk-import Procore commitments as contracts.
- Procore Prime PCO and Commitment CO Status Sync (Beta): See Procore numbers and live statuses as columns in your COR Log.
- Foundation Integration (Beta): A new direct integration between Clearstory and Foundation Software, covering office and job linking, project mapping, field mappings, and pushing CORs
Message Directly Within Change Notifications
CN Messaging: A Messages tab and an Internal Messages tab on every Change Notification.
A Change Notification is where a GC puts a change in front of a trade partner to price or authorize. The new Messages tab is visible to everyone on the CN, so a trade partner can ask a scope question before responding and the GC can answer on the same page. GC teams also get an Internal Messages tab for coordinating internally on scope, next steps, and responses before communicating with the trade partner.
Both tabs support @mentions and attachments, the same way messaging works on CORs and T&M Tags. An @mention sends an in-app notification and an email, and CN threads appear in the Message Center with unread counts next to your COR and T&M threads. The question, the answer, and the backup stay attached to the change they are about.
Keep the COR Log Accurate
Move CORs Between Projects: Move a COR to another project in your company without rebuilding it.
CORs land on the wrong project. Work gets reassigned, a project gets split, someone picks the wrong job from the list. Until now the fix was to recreate the COR by hand or open a support ticket. Now an authorized user can move it. The COR keeps its line items, attachments, full revision chain, and message history, takes a new number from the destination project, and picks up that project's contract, rates, and permissions.
Waived Stage for Voided CORs: A fifth stage under Void for a COR the contractor voluntarily withdrew as a concession.
Waived Stage fixes a smaller, but consistent problem: not every voided COR was rejected. When a contractor drops a COR to keep a relationship healthy, the log can now say so. Waived is available on both Sent and Received logs.
Track Earned Progress on Both Sides of a COR
WIP Reporting for Received CORs: See % Complete and earned value on received CORs, per project in Contractor Insights and across your portfolio in Company Analytics.
WIP Report Export: Access PDF and Excel exports on every WIP report, matching your active filters and current view.
WIP reporting answers the question a COR status cannot: “How much of the open change order value has already been built?” For a specialty contractor, that is the gap between work in place and work approved to bill. For the GC, it is the same gap seen from the other side of the contract. WIP reporting now covers received CORs as well as sent ones, and each party records its own progress. An update on one side never changes the other side's numbers. Additionally, WIP reporting is available at the company level so that you can view all WIPs across your entire portfolio in one place.
Export sends the WIP view you already filtered straight to PDF or Excel for a progress meeting or monthly review, without rebuilding it in a spreadsheet.
Stand Up Procore Projects Without Re-Keying
Procore Single Project Import: A guided four-step wizard creates a Clearstory project from one Procore project and imports and links its vendors and contracts in the same pass.
Procore Bulk Contract Import: Select multiple Procore commitments on a mapped project and create the matching Clearstory contracts in one action from My Contractor Users. Already linked commitments are flagged and duplicates are skipped.
Prime PCO and Commitment CO Status Sync ( Beta): For CORs pushed to a Procore Change Event, the Prime PCO and Commitment CO numbers and their live statuses appear as COR Log columns, with a click-through to Procore.
Procore stays the system of record for the contract and budget, and Clearstory is where the change order work with trade partners happens. Now the project and its contracts come over once, and Procore status comes back to the COR Log, so nobody needs to check two systems to know where a change stands. Both imports match the CMiC imports that shipped in August. Status sync is available on request during Open Beta.
Also new this month
- Company-level Archived Project Filters: Company-level analytics reports now allow you to dynamically choose which Archived Projects you would like to view.
- Company-level Division Filters: Company-level analytics reports now have filtering for Divisions to easily allow you to filter to see the relevant subset of projects.
- Add Received COR from the COR Form: Building a COR and the trade partner's COR is not in Clearstory yet? Upload it from the same flow and link it without starting over.
- Agent Form Attachments: Clearstory's AI agents can read files already attached to a form, and attach files from the chat onto the form.
Less Rework, Better Visibility Across the Change Order Lifecycle
The common thread across September’s releases is reducing the amount of work project teams have to recreate, reconcile, or chase down as changes move forward. Conversations stay with the Change Notification, COR records are easier to keep accurate, WIP is visible on both sent and received work, and Procore status comes back into the COR Log. Together, those updates give teams a more complete view of where each change stands without adding another manual step to the process.
New to Clearstory? Request a demo to see the Change Order workflow end to end. Already a customer? Log in to try these updates, see Work in Place (WIP) Reporting for WIP details, or ask your Customer Success Manager about the Procore imports or the status sync in Open Beta. For more info, see the full knowledge base article here.
