Approve Potential Change Order
Use Case
The project manager has asked that all potential change orders be reviewed and approved by him prior to becoming client change orders. The superintendent ensures all PCO updates have been made, then sends it to the project manager. The project manager receives it and after looking it over, approves it to be become the client change order status.
Some organizations may include an approval workflow at the PCO stage, before converting them to client change orders (CCOs). Approval workflows for PCOs are set up under Project Settings. You can then launch the approval process from the PCO record’s Details tab.
Ideas on Site
PCO approval may or may not be required within your organization. Some companies will use the PCO phase for getting formal internal approval, then use the CCO phase for finalizing the change order with the client.
Other companies may not require a formal approval process at the PCO stage. This will depend on what makes the most sense according to your company’s standard operating procedures.
How to Set Up Workflow Assignments for PCO’s
Workflow Assignments are made at the project level. They allow you to specify approval steps and the users/roles responsible to approve. When a new PCO is created, the appropriate employee is notified via email to review and approve or reject the PCO.
Workflow steps added at the Project Settings level cannot be edited in an individual PCO.
Step 2
Provide a step title with a threshold amount. This is the amount that will trigger the approval step.
Approval Process for PCO’s
With approval workflows set up, follow the steps below to approve a PCO.
Step 2
The Start approval process consists of three steps:
-
View assigned approval.
-
Add messsage (optional).
-
Attach supporting documentation (optional).
Click Start.
Access the following link to learn more: