The Change Order Management feature was one of the primary reasons for selecting Procore as our project management software. Unfortunately, our efforts implementing the Financial Management product line have not been as successful as we had hoped. To maximize utilization of this product line we purchased the Viewpoint Vista Connector. We recently wrapped up testing and concluded the connector will help eliminate redundancies and streamline our change order management process in leveraging the Prime Contract tool. Although this may sound like a step in the right direction the Prime Contract tool is in dire need of improvements. One those improvements include language modification to the owner change log and forms. Throughout Filanc’s change management training, end users have expressed great angst regarding Procore’s acronyms which has led to minimal buy-in and inefficiencies. Most end users in construction are familiar with owner changes referred to as an Owner Change Order (OCO) or Change Order (CO). In this case Procore uses the terminology Prime Contract Change Order (PCCO). This acronym is very similar to the Potential Change Order (PCO) request which is submitted to an owner. As you know similar acronyms may cause confusion creating problems and annoyance when the meaning is not understood nor embraced. It is difficult for end users to grasp and adopt Procore’s similar acronyms as it requires additional effort to differentiate the types of change order documentation. Procore and customers would benefit heavily if they would provide a feature allowing clients to modify the owner change order language to a terminology commonly used in the “construction” industry.

After issuing a Purchase Order in Procore, users need to be track the actual materials received onsite, preferably via the mobile app as this usually happens in the field. Would also like to have this available on web as well. Would like to have a check box for materials received, input for date received, input for quantity received, check box to indicate if material was delivered damaged or not. These fields need to be available in the Reports tool so users can run a report of materials that were not received that were included in a Purchase Order. Would also like to be able to capture a photo in the PO itself during the check in process for proper documentation. There are many times when materials come to the site and there are some items missing or damaged in transit.

In order to adhere to contractual obligations and get needed approvals on an owner invoice, we need to be able to spread the cost of an approved owner change order across multiple existing SOV line items.

Currently, if we manually spread a PCCO across line items, it affects the Original Contract Amount and doesn't show the Net Change by Change Order correctly in an invoice. But if we leave the SOV alone and add the PCCO line item in the invoice, it doesn't show the correct amounts for the updated SOV values (although it does show correctly the Net Change by Change Order).

In order for us to use the invoicing tool, we must be able to spread the dollar amount of approved change orders across existing SOV line items.

Currently, in order to send an RFQ to a vendor, the vendor MUST have a contract/commitment on the project. Then you can send the RFQ to a user who has 'standard' permissions on the commitments tool and more importantly has the ability to view the commitment. In some cases, I need to send an RFQ to a user/vendor that does NOT have a commitment on the project which is currently not possible. To work around this I have to send those vendors emails and then come back to the change event and enter their quotes. It would be much more efficient if I had the ability to send them RFQ's from the correlating change event.

Currently, there is no way to report on which Prime Contract is the source of Change Event markups. Clients with a large number of Change Events do not have a way to easily report on which have markup associated and where that markup is pulling from. The markup source for Change Events should be a data source that pulls into custom Change Event reporting.

Context: Alberici needed to delete a Prime Contract but were unable to do so since it was linked to multiple Change Events. The client needed to individually go through their Change Events to find the markup and remove it to delete the Prime Contract. As the number of Change Events increases over time, this will cause more time being spent which would be saved with a custom reporting option.