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.
Keep reviewer marks tied to the right maker task and proof.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Keep creative review tasks clear on proof versions and due dates.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Flag blocked proof reviews before the team routes them to clients.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Keep proof handoffs clear when creative files change.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Keep approval tasks tied to the current proof revision.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Keep proof handoffs tied to the right revision and maker.
Your maker gets a clear fix list tied to the PDF revision reviewers saw, so the next round starts with the right changes.
Spot proof access problems before they hold up creative reviews.
Your approval task shows whether the reviewer can open the current proof before the due date, with a request for a corrected link when needed.
Keep changed proofs visible before a review decision moves forward.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
Keep rejected asset feedback tied to the right design revision.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Keep proof decisions clear across your creative team's handoffs.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Keep rejected creative proofs assigned to their makers for rework.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.
Keep revised proof handoffs clear for the review team.
Your reviewer can find the new proof beside the earlier version and the fixes still open, right on the task.