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.
Tie your creative decision to the proof version you reviewed.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Route rejected artwork back to its designer with your review reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Send rejected artwork back to its maker with your review notes.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.
Put revised artwork back in the review queue with its version clear.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.
Send the maker the reviewed artwork and requested fixes by email.
Your maker gets a rework email that names the reviewed proof and fixes due next.
Show which proof needs a creative decision and by when.
Your proof cards show what reviewers need before brand review. Your team sees the current proof and any details still missing.
Put revised artwork and prior fixes together for your review.
Your reviewer can find the new proof beside the earlier version and the fixes still open, right on the task.
Show which visual proof needs your creative decision.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
Reopen your artwork review task with the replacement proof.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.
Put the current visual proof and decision question in one task.
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.
Send requested visual changes to the original maker as separate tasks.
Your maker gets clear fix subtasks tied to the proof the reviewer saw, so the next round starts with the right version.
Carry your requested visual changes to 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.