Project Workflow

Designers should create a job folder using the template, so that all structure is intact CREATIVE/~ XXXXX JobName

Multiple concepts can be combined into a single file when only one page is being prepared, such as for a flyer or single ad. (Example: c1a-56843-v1-Results Interpretation Flyer.indd)
For projects that entail multiple pages or components, each layout file should contain only one concept. (Example: The Creative folder will have 2 files, c1a-56843-v1-Results Interpretation Flyer.indd and c2a-56843-v1-Results Interpretation Flyer.indd)
For projects with multiple concepts, create one presentation file for upload to seeker and passoff to the client. Take all individual PDFs and combine them into a "p" file. (Example: p1a-56843-v1-Results Interpretation Flyer.indd)
Before saving out our PDF, please be sure to go to File > File Info and fill in the File name with the name of the InDesign document. This helps us have a reference to the working file if the client ever saves the PDF with a different name and we need to reference the working file down the line. Please be mindful to keep this up-to-date each time a change is made
Once a PDF is made, confirm that the ‘Initial View’ properties are set to:
- Navigation Tab: Pages Panel & Page
- Page Layout: Single Page
- Magnification: Fit Page
- AT&T ONLY
  - Page Layout: Single Page Continuous
  - Magnification: Fit Page (unless a digital project, which is always 75%)
  - Open to Page: 1

Designers are expected to create a new version of a layout file whenever they receive feedback that changes the current file.
Never save over a previous version.
There is no need to append your initials. Simply change the letter to the next in the alphabet. (Example: Change file from c1a-56843-v1-Results Interpretation Flyer.indd to c1b-56843-v1-Results Interpretation Flyer.indd)
PDFs that are circulated internally for review should retain this naming structure.

Files will be updated to reflect that the client version has changed, going from v1 to v2 and the tracking code then returns to the letter a. (Example: Change file from c1c-56843-v1-Results Interpretation Flyer.indd to c1a-56843-v2-Results Interpretation Flyer.indd)
In instances where multiple single-paged concepts were created in one file, after selection of approved concepts, the layout files should be separated into distinct files
- 3 concepts were developed in a file labeled c1. Each distinct concept will now receive a unique tracking code in sequential order (e.g. c1, c2, c3).
All older versions are then moved to the Old Versions folder.

On creating final production files

Upon completion, several things can happen based on the type of project we are working on.

Move the final INDD file to the BUILD folder (Keep in mind to have the File Info up to date)
Create a final hires PDF using the Press Bleeds setting and adjusting if needed (for spreads). Preset can be found here: CREATIVE/TEMPLATES/Presets
Place PDF into the BUILD folder keeping the name the same.
Fill out the QA form and pass off to whoever is QAing the piece.
Once the QAer has approved this piece, they will:
- Change the version to -FIN- and move it to the FINAL folder
- Fill out the QA
- Upload the QA and the final Hires PDF with crops (or whatever type PDF is needed) to seeker

Move the last INDD file to CREATIVE > Old Layouts folder (Keep in mind to have the File Info up to date)
Package the file through our standard pre-flight process [1]
Keep Packaged file in the BUILD folder keeping the name the same. (This name will be the same as the file you just moved to Old Layouts)
Fill out the QA form and pass off to whoever is QAing the piece.
Once the QAer has approved this piece, they will:
- Change the version on the packaged file -FIN- and move it to the FINAL folder
- Fill out the QA
- Upload the QA and an Egnyte Link to seeker

Move the last INDD file to CREATIVE > Old Layouts folder (Keep in mind to have the File Info up to date)
Package the file through our standard pre-flight process, please name according to the Creative Portal [2] naming procedure
Keep Packaged file in the BUILD folder
Fill out the QA form and pass off to whoever is QAing the piece.
Once the QAer has approved this piece, they will:
- Notify the creative team or the AE that this is ready for a portal upload
- Move final packaged file to the FINAL folder
- Fill out the QA
- Follow the rest of the Creative Portal Upload procedure