Tags
Project, Proof, Section & Note

Proof Tags

Proof Tags can be used to promote proof status and categorization. A proof tag can be added to a single page in the Proof Review Interface, or multiple pages at once in Project Plan View.

While the Voting feature (displayed number of users who have applied the same Tag to the same element) is enabled for all Tag types, it is especially useful for polling at the Proof level. As an example, creative options could be internally polled as to which are shown to the customer.

Applying Proof Tags can also set the visibility of those proofs for other users. For example, only proofs tagged with "Legal Review" could be made visible at a different workflow step to reviewers from the Legal Dept.

In the Flat Plan of the Project Review Interface, proofs can be sorted by Proof Tag. Very helpful if you wish to quickly identify proofs tagged a certain way.

Let's take a look at the Proof Tags below:

Use Case Example

The design department within a marketing agency produces multiple creative options for each project. All options are internally reviewed, but only a select few are shown to the customer.

Business Case

• The designer uploads all creative proof options for internal review.
• Internal reviewers add their comments to the proofs and apply a "Like" proof tag to those they consider viable creative solutions.
• Once all internal input is gathered, the Creative Director decides which proof options to put in front of the customer and adds a "Customer Review" proof tag to them.
• When the proofs advance to the Customer Review workflow step, only proofs with the "Customer Review" proof tag are visible, while the others remain hidden.

Section Tags

Project proofs can be organized into Sections, which are simply groups comprised of one or more proofs. Section Tags make it simple to approve a section. As an alternative to approving individual proofs, a user can approve many proofs with just one Section Tag.

As an example, a "Legal Approved" Section Tag would plainly indicate to other departments that the proofs in that section have been vetted by the Legal Team.

Let's take a look at the Section Tags below:

Use Case Example

A marketing agency is creating web ads and banners to appear on multiple websites. There are design and content variations for each website, resulting in many proofs. The customer has multiple departments that will need to review the artwork.

• In Aproove, each set is contained within a separate section. The sections are named in accordance with the websites the ad/banner will be posted. Each section contains 3-4 proofs. 
  

Business Case

• The first review group in Aproove is the Marketing Dept. When a section reaches approval, the Marketing reviewer simply has to add a "Marketing Approved" Section tag to that section. The result is one section tag per section as opposed to a proof tag for each proof.
  
  
• In the same manner, the next review group and those to follow will indicate approval with a Section Tag for their respective department.
  
  
• Project managers and other stakeholders looking in on the project have a clear snapshot of review status by section.

Rotation Tool

Proofs such as mailers and packaging files get created the way they will get folded after print, which means some content might be displayed upside down or on the side when you are reviewing the proof.

Reviewers have access to the rotation tool, which enables them to rotate the proofs making it easier to read and markup during the review process. 

Transportation

Note Tags

Note Tags introduce a new way of managing annotation workflows. Note Tags cover multiple needs ranging from automated note identification to complex approval and decisions at a note level.

Note tags can automatically be applied when users make annotations, and permissions can be used at a project level to determine what note tags (if any) are available to the different users.

Note Tags can be added when a user creates an annotation note (automatically, manually, or both). Note Tags can also be made available or hidden at different step stages based on your workflow requirements.

We did not stop there! To enhance this feature even further, you can (optionally) request a user to explain the reason they chose a particular note tag. For example, if a user uses a note tag of "reject note," you may want an explanation of why they rejected the note.

Applying Note Tags can also set the visibility of the annotation notes for other users. For example, notes tagged with "Marketing" could be hidden from users on the "legal" team.

Note tags can also be sorted and filtered, allowing users to concentrate on specific notes tagged with a particular category. Finally, note tagging is available to users who want to generate reports for identifying trends, bottlenecks, or behavioral patterns in the review cycle based on note tags.

Note tags have a wide variety of uses across all business sectors. Below are two use case examples supported by short videos to show the behavior.

Use Case Example 1; (Video Above)
Annotation Notes Classification

Example; You have a weekly circular in a retail environment, and that circular has different categories of products on the page, eg., dairy, meat, grocery, and alcohol.

• You have a weekly circular in a retail environment, and that circular has different categories of products on the page, eg., dairy, meat, grocery, and alcohol.
  
  
• Different merchandisers are reviewing the page/s, and those merchandisers are responsible for different departments. In our example, we will use dairy.
  
  
• As our merchandiser marks up the dairy section on the page, the note automatically gets tagged with "Dairy" on the annotation note.
  
  
• Optionally, you can also allow permissions for the merchandiser to add other tags, but they can never remove the "dairy" tag.

Business Case

Anyone with permission can now "filter" on the note tags, for example, the line manager of the dairy section could opt only to see the notes created by the "dairy" merchandiser. This means they can ignore all the other annotation notes related to the different departments, which do not concern them.

Having the notes tagged allows for very detailed reporting at a very granular level based on the notes entered by different departments or teams.

Use Case Example 2; (Video Above)
Annotation Notes Review

• You want to allow specific user/s the ability to review the other reviewer's notes to either classify them (see classification example) or to make a decision on the note.
  
  
• The reviewer looks at the other reviewer's notes and decides to "accept note" or "reject note" the individual annotations.
  
  
• When the user adds the "reject note" tag, they have to fill out a reason why they rejected the comment, and without giving a reason, they cannot apply the "reject note" tag.

Business Case

• In this scenario, a checking mechanism is in place to validate the notes of the reviewers. This could be for numerous reasons such as compliance, legal check, or simply to ensure concise feedback to the artworker tasked to make the changes.
  
  
• Reporting can get invoked to analyze the level of note rejection or acceptance. This could be useful to identify problems in the workflow, to prompt training or spot trends.

Filter on your Note Tags (Video Below)

Another fantastic feature is the ability to filter on your note tags. This allows users to only see the annotation notes that are tagged with the criteria they require. Furthermore the administrator has the ability to hide notes tagged with certain criteria and only display them to selected users.