Project procedure

Currently management is reviewing our process to come up with a procedure for jobs over $5K(nearly everything) to ensure that things go smoothly. I believe they are doing this as a CYA type of thing in case a programming project goes awry and causes issues, which I completely understand. I even agree that a procedure would benefit all, in that it would bring consistency to the process and make estimation easier. That said, I've reviewed the proposed document and have several issues with wordings, and overall steps. Do any of you have a similar procedure, and if so, would you be allowed to share part or all of the document with me. I'd like to see how this procedure we are proposing stacks up with others, as well as help identify what pieces are irrelevant. To this point, the resource working on the project has been free to work in their own fashion. Most of all, I'd like to have a sound procedure which is congruent with others that are out there which doesn't cut corners, yet isn't so detailed that it hampers productivity. Any input is welcome.

Russ