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.
Use workflows again – in two formats
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.
Automated workflows as easy as 1-2-3
Build it
The user-friendly 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.
Send it
Once workflows are created, proofs can be sent by selecting one from the wizard options. You can send workflow proofs using either the Intake File Uploader or the GoProof extension for Adobe Creative Cloud.
Track it
The proof dashboard keeps track of all progress made along the workflow timeline, visually displaying which stages have been completed and where any important deadlines and potential bottlenecks are.
Customise the workflow
Collaborate efficiently
Set a proof deadline
Get 360° feedback on proof
Add privacy to proofs
Work smarter, not harder
Make comments private
On top of the whole workflow itself being made confidential (requiring a password to access it) now each comment 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.
Set a deadlines
Even if production is ahead of schedule, delays happen when content gets stuck in a department while everyone else is waiting on it.
Fix this issue in GoProof by setting each stage in the workflow with a deadline and a next action trigger. If a proof remains inactive, it can be pushed on to the next stage or be sent back for version changes.
By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Update your Cookie Preferences.