Job Jackets serve two main purposes:

• To allow a job definer to create detailed specifications for Print and Web layouts.
• To allow a layout artist to create projects and layouts from those specifications, share the specifications with other layout artists, and verify that a layout follows its specifications.

Job Jackets were created because producing a layout and successfully sending it to output can be a complex task.

For example, consider some of the difficulties that have plagued creators of print layouts. Different presses have different capabilities, and modern page layout applications must be versatile enough to support all of those capabilities. Consequently, any number of things can go wrong, especially when you include the inevitable possibility of simple human error. Just to provide a few examples:

• A layout artist may use colors or imported graphics that cannot be reproduced accurately on the target press.
• A document that has been budgeted at 100 pages may be sent to output with a length of 112 pages.
• A project may be sent to the output device without its required graphic files or fonts.
• A layout with small text in a spot color may be sent to a four-color press, resulting in text that is unreadable.
• Color management settings may be configured incorrectly for the output device, leading to unexpected results.

Large and complex print jobs provide even more opportunities for error, and the cost of such errors becomes much greater. Job Jackets prevent unprintable or incorrectly constructed jobs from being constructed in the first place.

• What are Job Jackets?
• The structure of Job Jackets
• Sample Job Jackets workflow