Hi, Rob - I'm not sure if you're referring to the number of tasks involved in producing large page count projects, or the proof approval process, but in any case, for the tasks, you could create "buckets" of tasks for each section of the catalogue to help break it down. for example, you could have a parent task such as "Introduction pages" and within that, all the necessary tasks required to produce. the only caution there is that if you have tasks with identical names (ex. "Create first proof") for each section, whoever is assigned to those won't be able to differentiate which one is due on which date. they would have a bunch of tasks of the identical name but with potentially different due dates. i suggest you name according to the section ("Create Introduction pages first proof", "Create Section 1 first proof", "Create Section 2 first proof", etc.) i'm told there is no limit to the number of pages you can upload in a proof, but you could treat the pages in a similar way so that you upload sections of pages for the proofs. i would discourage you from opening separate projects for sections/spreads as that will likely cause confusion and lack of overall project visibility, expenses, etc. i hope this helps. Tracy Brunet Costco Wholesale Canada
