Google Drive is Google's file sync app that lets you store all of your files online alongside your Google Docs documents, and keep them synced with all of your devices.
Flag conflicting proof revisions in creative review handoffs.
Keep proof reviews clear: your coordinator sees conflicting revisions on the issue and can choose which one belongs in review.
Link each ready creative proof to its pending review item.
Your reviewers can open the proof from the approval item, with the filename beside the link when a draft is ready.
Log proof decisions and route each task to its next owner.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Give the assigned maker one proof update with fixes and a deadline.
Your maker finds the next proof instructions on the proof item. The reviewed link, fixes, and deadline stay together.
Clarify which visual proof awaits the reviewer's decision.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
Sort incoming images into reviewer copies or named fix notes.
Your coordinator finds JPEGs ready to share in the review folder, with a clear note when a file needs fixing.
Return corrected proofs to reviewers after the final fix.
Your reviewer gets the corrected proof and completed fixes when the last correction is done, so the next decision does not sit in rework.
Reopen campaign review tasks with the replacement artwork proof.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.
Fill gaps in marked proofs before makers start their revisions.
Your makers find the marked PDF on their revision cards, with the reviewed version noted when a handoff missed the file.
Put review notes and the right proof on the maker's assignment.
Your maker sees the reviewed image or PDF and requested fixes on the linked assignment, with the right proof version in view.
Move rejected creative proofs to each maker's rework list with the reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Send rejected campaign proofs back to their makers with revision notes.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.