Automated Proofing Workflows

AUTOMATED PROOFING WORKFLOWS

Easily create custom workflows that automatically pass proofs from one collaborator stage to the next using predefined triggers

SIT BACK AND WATCH THE MAGIC HAPPEN

Wouldn’t it be great if your processes take care of themselves?

That feeling of knowing everything is being done in line with company policy but without you having to jump in and tinker all the time. It’s so good.

Automated workflows in GoProof are just the ticket. They give you the toolset to build a timeline of stages for your proofs to follow, however simple or complex the journey needs to be.

When one collaborator stage review is over, the proof kicks automatically onto the next with rules and caveats managing the flow along each transfer, right until the proof reaches its final destination and is ready for changes or approval.

Automated workflows are a bit of magic to lighten your workload and embed compliance into your business processes.

HOW DO AUTOMATED WORKFLOWS WORK?

Automated workflows make difficult routing processes as easy as 1-2-3.

They’re a game-changer for group organisations of all sizes who have more complex needs when it comes to content approval. 

If you need to jump through some hoops, this is how you do it – with a smile on your face.

1: BUILD IT

The user-friendly Workflows configurator in GoProof helps you create your workflow, add as many stages as you want in a perfect sequential order and assign collaborator groups and individuals to review work each stage.

2: SEND IT

Once you have automated workflows created, proofs can be sent using a workflow by picking the one you want from the wizard options. You can send workflow proofs using either the Intake File Uploader or the GoProof extension for Adobe® Creative Cloud®.

3: TRACK IT

The powerful Proof Dashboard in GoProof keeps track of all progress made along the workflow timeline, visually displaying in quick-glance infographics which stages have been completed and where any important deadlines and potential bottlenecks are.

IT WON’T GET PUBLISHED UNTIL LEGAL HAS SEEN IT

Worrying about who needs to see content first, last or always is a thing of the past with automated workflows.

Each stage can be set up as a team, department, location, organisation or whatever you want. So if you need to make sure you get legal eyes on it after the sales team has thrown in their contribution, put legal after sales in the workflow and reduce the risk of exposure.

And if the North America HQ team has to choose from a list of campaign messages before the EMEA team sees it, allow them to comment on it first and give reasons why they went down their chosen route.

Open the door to structured, compliant flows of responsibility, creativity and total global collaboration.

USE WORKFLOWS AGAIN – IN TWO FORMATS

All custom workflows in GoProof are saved against your designated clients, so you can easily repeat them. You’ll save hours.

GoProof levels up further by saving the most recent version of that workflow and giving you the option to pick that one alongside the original.

So if a ton of collaborators joined or were removed from a workflow once it was out there, however it finished up can be the start of round two.

Simple but cool, right?

SENSITIVE COMMENTS? MAKE THEM PRIVATE

Sure, not all collaborators in a workflow can openly share their comments between the others. There are always some exceptions for sensitive commercial feedback.

On top of the whole workflow itself being made Confidential, so requiring a password to access it, each group can be made Private.

This means all comments, markups and threads that are created by private groups will be hidden from everyone except those in that group.

Fly under the radar, keep it on the down-low.

SET THE TEMPO USING DEADLINES

Content releases usually come with a ‘we need it by’ date.

Even if production is ahead of schedule, delays happen when content gets stuck in a department and can rot against the clock while everyone else is waiting to see it.

Easy to fix in GoProof. Set each stage in the workflow with a deadline and a next action trigger, so if it’s hanging around too long, it will push on to the next stage or be sent back for version changes.