We're having some trouble surrounding our review and approval process, and I'm hoping to gain some insight from the community. We've been using document approvals (since you can do more reporting with those compared to proof approvals at the moment), but there's a lot of manual adding/removing of tasks by our Traffic team to accommodate for the reviewer's possible decisions. Our general workflow for artwork approval is below: 1. A Designer uploads the file, adds an Art Director and Editor to the document approval, then marks their task Complete. 2. The Editor and Art Director both have tasks to review the artwork, where they go into Documents and make their decision (Approved / Changes / Rejected), then mark their tasks complete. 3. Once both decisions have been made, a member of the Traffic team determines the next steps and manually adds tasks based on the document decisions. For example, if the Editor rejects the file and the Art Director chose Approved, then Traffic would add a task for the Designer to make updates and then for the Editor to review again. 4... This process repeats until the artwork is eventually fully approved, and many times it takes multiple rounds of review/approval before all the necessary changes have been made correctly. Our biggest problem with our current system is the level of involvement Traffic must have. Their team is small and short-staffed, and they can't spare all the extra time it takes to babysit document approvals when that process can (and should) be more automated. It's slowing down the progress of all of our projects. We're looking at changing to task approvals, since those decisions have an actual action-item tied to them. If a file is rejected, it would go back to the designer to make updates. If approved, the rest of the project can move forward. A couple of my concerns with using task approvals are: -there is no Changes (Approved with Changes) decision available -there doesn't seem to be the flexibility of more than one "if this then that" scenario. If the Editor has approved a file and the Art Director rejected it, the Editor doesn't need to see it again. From what I can tell, once the designer makes their changes and marks their task complete, there's no way to then omit the Editor stage of the approval process. We also want to avoid anyone having to click through many different pages to reach the file for review or to make their decision. Ideally we'd want a report that shows the name of the project, a link to the documents tab on the project, and a dropdown (or buttons?) with which to make the decision. We really like that document approvals let you make your decision directly on the document. Using task approvals would mean finding the document, then finding the actual task, then making a decision (too many steps). This was a really long post (sorry!) but if you have any suggestions or input, it would be greatly appreciated! What has your organization done for your review/revision processes? What worked and didn't work? The more info I have, the better. 🙂 Maddy Martin Fairway Independent Mortgage Corporation