Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This should be considered a flexible guideline schedule with the cooperative aim of having a finished program about 2 weeks prior to the concert. Due dates in the above workflow are not hard deadlines.

Final Roster and Change Deadlines

Though the general workflow is considered a flexible, the 9-day deadline is firm.  9 days before your concert, the existing program draft will be considered final and go to press.  Any changes to roster or program after the 9-day mark will not appear in the final program.  

Making Corrections

  • Your ensemble team may choose who should be involved in the proofing process.  Have your point person distribute the proofs to your selected team, and collect edits from the team. 
  • Before sending corrections to the marketing designer, the point person should collate all the changes into a single document, and ensure that none of the changes contain conflicting information.  If there is a conflict, resolve the conflicting data internally before sending corrections. 
  • Whenever possible, an annotated PDF is the preferred method for receiving changes. You can use the markup tools provided in MacOS Preview to make clear changes throughout the proof.  A single change list in a Word document or the body of an email will also be accepted.  The changes must be collated into a single list.  Do not simply forward multiple change lists from multiple email addresses.
  • Please make every effort to send a single list of changes for every cycle.  Upon receiving changes, a new draft is frequently generated on a quick turnaround, so multiple changes coming in at different times results in a lot of excess work for everyone.