kintone is a fully integrated social collaboration and customizable business application cloud platform that allows internal and external teams to solve business process inefficiencies through database and work flow-driven custom apps, communication and collaboration. kintone can be used for custom CRM, Project Mangement, SCM and much more.
Put review changes on the proof card for the assigned maker.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
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.
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.
Move revised creative proofs back to review with the next due date.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.
Email the original maker the proof version and fixes due next.
Your maker gets a rework email that names the reviewed proof and fixes due next.
Flag missing proof details on cards before review handoff.
Your proof cards show what reviewers need before brand review. Your team sees the current proof and any details still missing.
Bring the new proof and earlier fixes into one reviewer handoff.
Your reviewer can find the new proof beside the earlier version and the fixes still open, right on the task.
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.
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.
Check proof versions and reviewer details before each handoff.
Your team gets a clear review packet on the task, or a visible note about what the proof still needs before a reviewer can act.
Split proof feedback into fix tasks for the original maker.
Your maker gets clear fix subtasks tied to the proof the reviewer saw, so the next round starts with the right version.