Frequently Asked Questions
The PCO stage is not mandatory, but to proceed to a budget change order in Control, the CCO stage is required.
No. Issues can be used to record any valid project issue, so that they can be addressed appropriately.
A change order (contract variation) can be instigated in InEight Change but the managing of the change order’s completion takes place in the InEight Contract application.
If the CCO has already completed the approval process, you must modify the CCO Status drop-down to In review. This will mark the CCO in Control/Change as Revised and the CCO will be placed back into the approval workflow.
Yes, there is a limit in the integration between Change and Control as to how many issues can be associated to a CCO. Currently, users are able to execute a CCO with up to 250 line items.
Yes, when the InEight Document application is set up to integrate, supporting documents can be added from InEight Document directly to an issue or change order in InEight Change.
Yes. You can set pricing to update automatically under Project Settings > Change > Pricing Configuration or you can update the issue with the CCO pricing changes manually through the Actions menu.
See also:
The change record with all its details is sent to the Changes Register in Control for final approval by the person managing the Control budget.
See also: