GoVisually Academy

Steps

1. 1
   Have the spec in your Knowledge Base.

   • Upload it as a Product spec document. PDF, Excel and CSV all work.
   • Wait until it has finished extracting.
2. 2
   Attach the spec at upload.

   • In Upload files and folders, open Product spec (optional) next to the file.
   • Choose the spec for this product.
   • GoVisually may show "Suggested: … — matched on code …". This is only a suggestion; you choose.
   • Click Upload.
3. 3
   Run the check.

   • Open the proof's AI tab and click Run playbook.
   • Click Run on a playbook that includes the product spec check.
   • If your project runs playbooks automatically on upload, this happens for you.
4. 4
   Open the results. When the scan finishes, open it and choose the Product spec tab.
5. 5
   Read the checklist.

   • The summary shows how many values were checked and how many rows were checked in total.
   • Sections with a mismatch open first. Each mismatched row shows the Specification value beside the Artwork value.
6. 6
   Place it on the proof.

   • Click Place on proof. The canvas zooms to that value and opens a draft comment with the fix.
   • Check the comment, then Post it.
7. 7
   Decide.

   • The check compares; you decide what is right.
   • If the spec itself is out of date, update the spec, not the artwork.

Don't miss

• "No specification attached" means nothing was compared. It is not a clean result.
• Choose Set product spec from the proof's menu, then run the playbook again.
• "Check did not run" means the playbook doesn't include the product spec check.
• Add it to the playbook.
• The check reads the PDF's live text.
• If fonts are outlined or the page is flattened, values can't be confirmed.
• Upload a PDF exported with live text.
• It compares the artwork with the spec. It doesn't check:
• spelling, layout or barcode scannability;
• whether one language on the pack agrees with another.

You're done when

• You've read every mismatch in the Product spec tab.
• Each one has a comment on the proof.