Currently, once a Potential Change Order (PCO) is executed, it can no longer be edited. This creates a limitation, as change orders often go through multiple rounds of review, clarification, and back-and-forth communication during the approval workflow. In many real project scenarios, additional cost items are identified after the PCO has already been accepted or executed.
At present, if a new cost item is added after the PCO has progressed to the Subcontract Change Order (SCO) stage, that cost item does not carry forward to the SCO. This results in incomplete records, manual workarounds, and potential discrepancies between the PCO and SCO values.
It would be highly beneficial to allow controlled editing of PCOs even after they are accepted or executed, such as adding or updating cost items, with proper version tracking or audit history. Any approved changes should automatically flow through to the corresponding SCO to ensure cost continuity, data accuracy, and alignment between commercial documentation across all stages of the change management process.
