Workflow Between Projects

[TaraMcKinnon]

We are onboarding an internal creative team. The work that they complete has a very specific process and workflow that requires their work to be done on a project. The work that they create is a process within a larger campaign project. Both projects require specific and different stakeholders to review the creative on both projects. Is there a way or does someone have a good workflow to eliminate the redundancy of having to apply feedback on the creative proof from the changes required on the campaign proof? 

Thank you! 

[Madalyn_Destafney]

Want to be sure I'm understanding - every asset has two identical proofs in a project living in same project but different approvers?

[TaraMcKinnon]

Not quite. We will have a creative project where the designers, copywriters, proofreaders and account managers will complete their tasks and proof reviews. We will then have a campaign project where the piece the creative team has created will be uploaded and reviewed by our analysts, strategy teams, execution ops teams and compliance. Each project has key details the stakeholders (proof reviewers) will leverage in order to make a decision on the proof. The creative team will create the concept, design and copy and review it internally for approval then pass it to the execution ops team who will route it and make a decision on it based on campaign criteria. If changes are required it will be passed back to the creative team to make changes...this is where the redundancy could occur. We don't want the strategy owner (the liaison between the two projects) to have to apply all of the callouts on the campaign proof to the creative proof. 

Hope this helps 

[Madalyn_Destafney]

Have you considered using proof workflows? Your proofs can start with your creative team (designer/proofer/whomever appropriate) can review, and if approved with no changes, then automatically goes to 2nd stage of your execution ops team for their review. If stage 1/creative team has changes, it goes back to proof owner to make those changes (these settings can be included in your proof workflow template).

If you have too much variance proof to proof of reviewers/approvers, you can create more than 1 proof workflow to use (choose which depending on the project) or you can set up a staged approval ad hoc when the proof owner uploads a proof and not use a workflow template.

[TaraMcKinnon]

Thank you for the suggestion. We do use proof workflows. Think of the internal creative agency as an outside agency that is using Workfront Proof. They have their own project with their own traffic coord and tasks. The above would require us to route on one project and unfortunately that would not work with this scenario.

[Madalyn_Destafney · Accepted solution]

What if once your creative team is good with their rounds, you move the proof to the campaign project? That way the owner is still on it, versions are kept if needed, and not having to duplicate efforts?