Task completion based on proof decision -- Version control?

Hi ​@Kasey-Gagne , What I’ve seen in most cases, the cleanest and most scalable approach is to keep everything within the same task and use Workfront Proof’s versioning capabilities. Instead of creating new tasks for each round (R1, R2, etc.), teams typically upload new versions of the proof to the same task. This allows all feedback, decisions, and version history to remain in one place, making it much easier to manage and audit, while older versions are automatically locked.

From an automation perspective, task completion can be driven based on proof decisions (for example, Approved → complete task, Changes Required → move to the next step like another design round). This works best when the proof is attached at the task level, and routing can be handled either through native dependencies or more advanced logic using Fusion. While creating separate tasks for each round can provide clearer separation, it often leads to cluttered projects and added complexity in reporting and automation. As a result, most teams prefer a single-task approach combined with versioning and workflow automation to keep the process structured and traceable.

I’d suggest checking these documentations for automated proof workflows and Workfront’s versioning system.