Review Module Issues/Automated Review process

My goal in using the review module is to have the following process:

1. A file is attached for review
2. A file is reviewed by creative and sent back for updates
3. Updates are made
4. Creative approves
5. Business reviews
6. Review approves

There does not seem to be a way to do this without sacrificing version history, widget compatibility, automation, and/or efficient assignment.

Review Module issues:

1. If you set someone up to review they will not receive a notification unless they have selected to receive notifications for “Date, Assignee, or Status is changed” on BOTH “tasks assigned to me or created by me” and “For other tasks I follow.” As you can imagine this is a selection the executives are loathe to choose.
2. Dashboards – There is no option to pull in reviews that are on a project level. Only on a task level.  You can get pending reviews for task level either through custom widget (which is tasks only) or “My pending reviews” but there is no project level widget for review.
3. Phone App – The phone app does not support “my pending reviews” for iphone, but it does for android. There is a laundry list of incongruences with the app beyond this.
4. You cannot automate a review process that goes through multiple reviews. That is to say you cannot have A create something attach it, then B review and approve, then it goes to C to approve.  You can either have a workload that continues to add and never takes away assignees, create a task structure and not preserve review history or file versions, and/or you can add new approvers.  Adding new approvers refreshes the approval, so all current approvers will have to go back into review and approve.  (Adding tasks is addressed in 5.)
5. Files do not share between tasks, so version control is extremely limited. Since you cannot set up dashboards to see reviews on a project level, storing files on a project level for review is problematic.  Storing it on a task level poses its own set of problems because each task could have a different version especially if you are going through different rounds of review (see issue 4), for example you have a creative review, then a business review.  Each round of review needs to approve, but if it is a different file, you have two files that either need to both have version control or one location, where you swap in and out approvers.  Alternatively you could have a workload setup, which does not push it to the next person, but rather requires each review to change the workload to add a person (or more) while keeping themselves attached to a file they have already approved, unless they are trained in removing themselves.