First of all, when and why should a job definer create a Job Jackets file? There are no hard-and-fast rules for answering this question: If you want to, you can put Job Tickets for all of your print jobs in one great big Job Jackets file. However, here are some guidelines to indicate when you might want to have separate Job Jackets files.

• If you plan to create a number of print jobs that share the same Resources (such as colors, style sheets, trapping settings, color management settings, and page sizes), you might want to create one Job Jackets file for all of those print jobs. For example, if you’re a design firm that serves several different clients, each of which has its own visual identity, you might create one Job Jackets file for each client.
• If you are in charge of a design group and you’d like to make sure that every layout artist working on a particular project (such as a promotional campaign) uses the exact same Resources, you might want to create a Job Jackets file and Job Ticket template containing those Resources, and have all of the layout artists share that Job Jackets file.
• If you are an output provider and you have a particular press with particular requirements, you might create a Job Jackets file that captures that press’s requirements for your customers (and thus helps them to avoid exceeding those requirements). You might even be able to download a Job Jackets file containing a press’s requirements from the press manufacturer.

• Creating a Job Jackets file: Basic mode
• Creating a Job Jackets file: Advanced mode
• Adding Resources to a Job Jackets file: Advanced mode