We find that contractors use the PCO (Potential Change Order) log for two main reasons:
- To assign a “bucket” to capture costs for work out of scope that is payable by the Owner
- To track costs missed in their estimates that they don’t want contaminating the cost report.
- We also see the assignment of PCOs for pending back-charges to a supplier or subcontractor
…each user uses this log a little differently!
At the request of a user, we recently added a function to our PCO log report which gives the user the ability to print only a portion of the PCOs in their log. We call it the “Do not print” feature. This feature is most beneficial to the contractor who wants to bring in their PCO log to a client, but not show the client what is being tracked “in house”.
So, for example, if your PCO log shows twenty-five (25) potential change orders on the list but one of them was set up to track the excavation of a dumpster pad you missed in the estimate and another code is to track the cost that you are back-charging your window installer, you can chose the “Do not print” option for these two PCOs. It’s easy to do, simply go into these two specific PCOs and click the “Do not print” button – your PCO log report will come out with only the PCOs you want to show, with the summation of the items adjusted to what shows on the printout.
This is just another example of the Runjob staff’s depth of on-the-job experience.