I am looking for the best work flow or process for Change Orders.
Let’s say I have an “As-Sold” revision then 4 change orders and 1 change notice.
Day 2; Change Order 2 and Change Notice 1 are approved by the client.
Day 15; Change Order 3 is approved by the client.
Day 21; Change Order 1 and 4 are rejected by the client.
How do we keep this straight in the revisions as what revisions to “Compare”.
Sorry this is a year plus after the fact. For our work flow, that is an unrealistic way to manage changes.
In a large project, you could have multiple changes waiting for approval and receive approval/disapproved out of “order”. Change Notices are easily managed in the order they are created but Change Orders may have to go through several client approvals before you get your answer.
Believe me, if I could keep them in order of creation I would.
I do appreciate the feed back and we do look for more efficient ways for our processes.
We are having a HUGE issue with this. We have multiple change orders that are all in different states and have a very hard time keeping the current Job correct. DTools needs to add a feature where there is a current job and the job has individual children (pending CO’s) that when they get approved, they get shot over to the current running project. The current way of doing change orders is a complete mess…