Documenting Project Change Orders

Su Subburaj
Su Subburaj
  • Updated

Many projects require at least on change order. This article provides guidance on how to document them during the course of your project.

 
The primary reasons for tracking a project change order are:
 
  1. Making sure your team is aware of the change
  2. Being able to separate the additional Devices from Tasks in the schedule/bill of materials

     

To accomplish these goals, we recommend adding information to a Device's  DescriptionInstallation Notes, or Part Number fields. All of these fields carry over to the Live Site after the Project is published and will be shown in the history of the Device. Adding information to the Part Number field has the added benefit of displaying in the Parts List. For instance, if you annotate the Part Number field, such as Cable 2 (CO #1), any Devices related to a Change Order will be easily identifiable in the Parts List. 
 
You can also create visual cues on a Plan to help communicate changes to your team members using features like Flags and Custom Device Colors. These cues can be seen by everyone in the office and Technicians in the field using SiteOwl Mobile. You'll want to communicate to your team the Custom Color being used for this purpose, if you choose to use it. 
 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.