New Change Order Task
Background: A change order will be use to make adjustments or Modifications to something that was already planned, stated or implemented in the existing contract
Starting November 20, 2024, we implemented a change by consolidating all change order tasks into a single milestone task in order to simplify the change order process..
The task will be named as Change Order (HCO/NCCO/ICO.
Installer Change Orders (ICOs) will have their own subtask
Homeowner Change Orders (HCOs) and No Cost Change Orders (NCCOs) will be combined into one subtask.
For HCOs and NCCOs, when you click the "Generate" button, a modal will appear, showing the required change order type along with the reason it was triggered.
Table of Content:
Automatic Change Order Creation Based on Product Rule Violation:
Instructions for how Installers can generate a Change Order (HCO/NCCO/ICO)
Consolidated Change Order Tasks
New Task will be named as “Change Order (HCO/NCCO/ICO)” consolidating all change order tasks into a single milestone task.
The Process for Editing the Project to generate the HCO is the same as for the ICO (You Only do this once)
If the “If Applicable” Text is not available, this means it is Required to be able to move forward
Homeowner Change Orders (HCO/NCCO) | Installer Change Order (ICO) |
|
|
How to check which Change Order document was generated?
To check wich NCCO/HCO/ICO Document was generated:
Step | Action | |
---|---|---|
1 |
| |
2 |
| |
3 |
|
Automatic Change Order Creation Based on Product Rule Discrepancy:
The change order task automatically checks if any product rule discrepancy has occurred during the process (The product rule discrepancy occurs when a pre-defined condition or requirement for a product is not met)
Step | Action | |
---|---|---|
1 |
|
|
2 |
|
|
3 |
|
How to Preview the Change Order Document Sample:
Step | Action | |
---|---|---|
1 |
|
|
2 |
|
|
Change Order Issues/Scenarios and Steps to Troubleshoot
Due to the recent consolidation of the New Change Order task, few issues came up affecting certain jobs. So this segment of the SOP will guide you on how to troubleshoot and resolve common issues encountered when dealing with rejected tasks involving the ICO (Installation Change Order) HCO (Homeowner Change Order) or NCCO (No Cost Change Order)
Task Rejection Not Displayed
System is not showing Both (NCCO and New Change Order) as generated in the History Tab
The System Displays Milestone Rejection but doesn’t show the Type of Task
No Cost Change Orders:
NCCO can be use to update the following: |
| ||
We will ONLY accept requests to update information if the request is coming from the Homeowner through:
|
Phone Call:
|
|
Please refer to the following article (Click Here) |
|
| ||
NCCO will not be applicable to update the Email Address since NCCO will be used only for required changes AFTER the contract has been signed)
|
| ||
Once the required information has been updated by support then The Sales Rep/Installer will need to use the NCCO Feature and generate a No Cost Change Order
| |||
Always ensure that if you modify the address, this one should match the address listed under ‘For Property Located At’, and NOT the one under “mailing address
|
Step 1 |
| |
Step 2 | |||
Step 3 | |||
Instructions for how installers can generate a Change Order (HCO/NCCO/ICO)
Step | Action | Reference | |
---|---|---|---|
1 |
|
| |
2 |
| ||
3 |
|
|