Carry the notes on a rejected file into the related revision work.
Your creator gets the reviewer's requested changes and current draft together, so they can start the next revision without chasing files.
Your writers see changes requested in chat on the revision task they already use, with a link back to the review discussion.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Your editor gets a clear revision issue from comments on your draft page, with links back to the review.
Your writer sees requested changes on the assignment they already use, with the draft version and review close at hand.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Your maker sees the reviewed image or PDF and requested fixes on the linked assignment, with the right proof version in view.