Any marketer who has created or updated a catalog dreads the idea of ever doing it again. Yet, for many companies, producing product lists, seasonal catalogs, and other multi-page documents containing images, descriptions, part numbers, pricing, order forms, front and back covers, and indexes is a routine marketing chore.
It is hard enough to manage proofing workflow for a single page ad or a new piece of collateral. Multiply that by dozens if not hundreds of pages, and you have the “joys” of catalog proofing.
ProofHQ can transform this complicated process into “no big deal.”
Streamline catalog proofing with page-level workflow
ProofHQ lets users proof multi-part projects like catalogs at the page level. Here is how it works. The project manager separates the original catalog PDF into separate pages (or double page spreads if that is your preference), names the pages in a logical way and places each file in the same folder on the desktop. If the catalog can be divided into sections, users can create a sub-folder for each section for even more precise organization.
The project manager then uses the ProofHQ Desktop Uploader to push the entire catalog folder, including any sub-folders, into ProofHQ. The folder will be replicated in ProofHQ, and each catalog page becomes an individual proof. The implications of this page-level control are significant. Users no longer have to treat the catalog proof as one massive document that is sent to every reviewer. Members of the review team receive only the pages that are relevant to them and revisions only take place on the pages that require them.
Proofing flexibility improves efficiency
The flexibility of the proofing systems lets users set up and assign reviewing rights based on the requirements of the job. If every member of the review team needs to see each page, then the project manager can set up sharing in the uploader. If different members of the review team see different pages, then sharing should be set up after the proofs have been created. The review team receives e-mails with links to individual proofs. This structure allows teams to work with maximum efficiency and focus.
Each page has its own workflow
Because each page of the catalog is a separate proof, each can go through any number of revisions independent of other pages. The ability to quickly move among pages, make comments, view changes and otherwise manage the whole assembly at the page level represents an unprecedented improvement over manual catalog proofing.
Easy catalog navigation
Folder contents, that is, each catalog page, can easily be seen by clicking the Folder icon on the Proof Viewer. Here, both manager and client (which might be the department that “owns” the products in the catalog) can review and approve it page by page. This also gives a sense of how the catalog actually looks and feels to the end user, who would view it in a similar way.
Keeping track of page progress
Using dashboard controls, the project manager can track which page proofs have been approved and which are pending. Once a proof has final approval, the manager posts this decision on the central dashboard, and the finished design goes to production. What was once drudgery becomes leading-edge, technology-based marketing workflow.
