What is the purpose of writing program notes?
Program notes enhance your audience’s listening experience by providing meaningful context about your
pieces and their composers. They are a chance to share any particularly interesting information that may
add to their overall understanding and appreciation of what they’re about to hear. Incidentally, these are all
things you yourself should already know about your pieces—things without which you cannot truly ‘know’
or understand the repertoire you intend to perform. And lastly, this is an opportunity for you to develop the
essential skills of writing good program notes—something many of you will nd yourselves having to do again
in your future careers as professional musicians.
What makes a good program note?
Program notes are very much like pre-concert remarks in that they point out interesting and relevant facts
about your pieces in a concise, well-organized way that is engaging to read and easy to understand.
Components of eective program notes include:
• Historicalandsocialcontextforthepieceand/orcomposer
• DO include when and where the piece was written, and when and by whom it was rst performed (if
known).
• Example: Messiaen’s Quartet for the End of Time was written while the composer was being
held in a German prisoner-of-war camp during World War II. The quartet was rst performed on
January 15, 1941 by Messiaen and his fellow POWs.
• DO mention if the piece was written for a specic person, or inspired by (or in reaction to) a specic
thing or event.
• Example: Handel wrote his Dettingen Te Deum, HWV 283, to mark the victory of the British army
over the French at the Battle of Dettingen in the War of the Austrian Succession.
• Do NOT include biographical details for composers that are ‘household names,’ and devote the
valuable space instead to talking about the music itself.
• For composers that may not be as familiar to the audience, DO include a few lines of biographical
information.
• Interestingandrelevantthingstohelp“guide”yourlistenerthroughthepiece
• DO describe musical structures/patterns and/or unique instrumentation that may help listeners better
understand the piece, e.g. ground bass, da capo aria, rondo, fast-slow-fast movement scheme.
• Do NOT include technical terms like crescendo/diminuendo, forte/piano, sonata form, etc. unless
absolutely necessary.
• If you have to use them, DO assume that your readers will not be as musically literate as you or your
fellow music school peers, and do them the courtesy of explaininganytechnicaltermsinthe
simplestwaypossible. If you can’t dene a technical term in fewer than two sentences, leave it out
or nd another way of saying the same thing.
• Avoidmentioningspecickeysortonalities unless there is some direct relevance to the point
you’re making in your notes.
• Example: Do NOT just say, “The second movement is in the key of E major.” This matter-of-fact
statement is meaningless to most readers and contributes nothing to enhancing their listening
experience.
• Example: DO say, “In this aria, Bach chose the remote key of E-at minor to illustrate the
suering of Christ on the cross.” This helps your listener interpret the meaning of what they are
hearing.
• Properformattingandstyle
• Program notes should be engaging and concise, and kept to a minimum of 400 words, and a
maximum of 1000 words.
• Formatting-wise, a good strategy is starting with a few sentences that provide historical/social
context and biographical information, followed by pointing out some interesting and relevant
highlights about the piece.
• Highlighting one to three of the most interesting points about each piece or composer is
sucient. There will always be more to say than there is room to include, and that’s okay—
you’re not writing a comprehensive exam paper here.
• If there is too much information to present in one paragraph, separate these two components
(historical context and biography, and interesting highlights) into two paragraphs.