We often generate a single Prime Change Request which encompasses all the potential changes for a period of time (to ease the paperwork the Client must review). The method has been widely accepted and appreciated. On the Budget/Sub Change tab, we may list the same Vendor/Subcontractor more than once. Presently the system allow us to enter the next sequential number to each task for that Vendor (ie., 1,2,3); however, when saved it records each entry as the same change order number (ie., it would list each line as 1 even though there are 3 lines with unique numbers in the change order record Bud/Sub entry screen. We think others could use the Prime side to summarize all upcoming changes and keep paperwork to a minimum for their clients as well. Being able to assign Sub CO #'s and have them populate the Subcontract accordingly would make sense to all. It helps us to keep all the Budg/Sub entries tied to what the client is going to see on a progress bill. We found this most helpful, but we are presently having to give Subs ONE CO number for all the work so the database tracks it correctly - and that drives them crazy :-)
by: Pam G. | over a year ago | Project Management
Comments
Pam - you have the ability to assign each row to not only a row on the change order, but also a different change order # for each subcontractor. Just override the default that populates in the change order # column for that subcontractor.
We do things similarly. Multiple "mini" changes are proposed and accepted, but an official CO is not written until several "mini" change orders are approved. You should be able to enter "mini" change orders and roll them up into a large change order. Also, I would like to see the ability to update PO's on CO's in the same way that Subcontracts are updated with changes.