jpol

We find time and time again we wonder why a job was rejected. May I suggest some sort of field that comes up if the "Rejected" status is selected allowing a user to input a note of why the job was lost. This way, if you go back to a project wondering, you can see a reference and possibly a trend.

I know we want to get all jobs, but sometimes it's inevitible that we loose some. We just want to keep track of why.

Thanks!

slemay

Good idea.

TouchToBegin

Originally Posted by jpol

We find time and time again we wonder why a job was rejected. May I suggest some sort of field that comes up if the "Rejected" status is selected allowing a user to input a note of why the job was lost. This way, if you go back to a project wondering, you can see a reference and possibly a trend. I know we want to get all jobs, but sometimes it's inevitible that we loose some. We just want to keep track of why. Thanks!

You could always add that to the Scope Of Work under project information.

__________________
Boy do I feel like a tool.

jpol

True... I guess I was thinking that we actually use the scope of work for all projects as we require the client to sign off so if anything changes, we have a legitiment change order. I really didn't want to alter the scope of work in case they came back to us later on down the road... I could just restore the archive and pick back up where I left off. It has happend in the past.