Concert Program Notes: What to Include and How to Write Them

Concert program notes are short written guides that tell the audience about the music they are about to hear. A good note gives the background of the piece and one or two things to listen for. Most notes run 250 to 400 words per piece. This guide covers what to include, how to write each note, a template you can copy, and how to organise rehearsals so the notes are ready on time.
TL;DR
- Program notes give background on the piece and tell the audience what to expect and what to listen for (Wikipedia: Concert program).
- Aim for 250 to 400 words per piece, built around one or two main themes (SFCM).
- Cover the composer, the context and the work itself. Give the listener something specific to hear.
- Write in your own words, in plain language, and edit more than once.
- Start early. Notes, bios and repertoire lists need planning time, and rehearsal materials need to be ready too.
Table of Contents
- What concert program notes are
- Who reads your notes
- What each note should include
- How to write a note, step by step
- A program notes template
- Planning the full program
- Keeping track of repertoire
- Rehearsal tracks for choirs and classrooms
- Our perspective
- Plan your concert materials with Stormusi
- FAQ
- Sources
What concert program notes are
Program notes are written guides that help an audience understand and enjoy the music at a concert. The Fort Collins Symphony describes them as a short essay or introduction to a piece. They usually cover the composer and the piece, and suggest things to listen for. They appear in the program book at the concert or are provided digitally beforehand.
According to the Wikipedia article on the concert program, notes serve two purposes. They give historical and background information. They also give the audience a sense of what to expect. The same article records that annotated programs began in Edinburgh and London in the 1840s. They were first used for chamber music concerts, notably by John Ella and his Musical Union, and became common at symphony concerts in the 1850s.
Notes also help the performer. A university research guide at Rider notes that writing them gives the performer a better understanding of the music, as cited in the same Wikipedia article. For students, that is a good reason to write the notes themselves.

Who reads your notes
The audience varies. A school concert has parents and grandparents. A community choir concert has friends and regulars. A recital has other musicians. The NFA Research Committee suggests adjusting your style for three types of reader:
- The enthusiastic novice.
- The reasonably well-educated music lover.
- The academic crowd.
Most school and community concerts are written for the first group. Write for them and the other two will still be served.
If you teach young children, the same rule applies at a smaller scale. Explain what a child can hear and notice, and leave out terms they do not know. Examples of this approach appear in music classes for young children, where music is introduced through listening and activity rather than theory.
What each note should include
Sources differ in detail, but they agree on the core. Use this as your checklist.
The composer
Give basic information on the creator. The Syracuse University Libraries guide lists this first. Include the composer's name and birth and death dates. The CSU Ohio research guide asks for these for every piece. Keep the biography short. Include only what helps the listener understand this piece.
The context
Say when and why the work was written. Mike Allsen's guide lists dates of composition and first performance, where and by whom it was first performed, and some composer biography. The Bard Conservatory adds scoring if it is not obvious, and brief information on publication.
The work itself
Describe how the piece relates to others in the same style or genre, as the Syracuse guide advises. Then describe the music. Say how it sounds and how it is built.
What to listen for
This is the part audiences use most. The NFA Research Committee says the note should give the reader something specific in the music to listen for. Its examples are a quotation of another work, a recurring motive, a basic form, the use of instrumentation, or a change in style. The Bard Conservatory suggests two or three particular things to listen for.
The ABRSM guide, cited in the research, says many programme notes follow three sections: a brief introduction to the composer, the work's historical context, and a description of the work.
How to write a note, step by step
- Listen first. Allsen advises experiencing the piece as an interested audience member would. Listen to a recording a few times rather than studying the score. He compares the writer to a good tour guide who lays out the overall form, describes the character of different parts and points out interesting features.
- Pick one or two themes. The San Francisco Conservatory of Music recommends selecting one or two main themes and organising the note around them. Think of the note as a narrative that tells an interesting story about the piece. Scattered details make a weak note.
- Talk it through. The NFA suggests recording yourself talking casually about each piece. Then transcribe the conversation and edit it until it is readable.
- Write plainly. The NFA advises nouns and verbs over adjectives and adverbs. Avoid jargon and the passive voice. A casual tone is fine, and it is acceptable to use "I".
- Define terms. Allsen advises defining technical terms. He also says to avoid specific key relationships that would mean nothing to most readers.
- Skip the play-by-play. The NFA warns against describing what happens throughout the piece, bar by bar.
- Edit repeatedly. Cut anything the listener cannot use while the music is playing.
What to leave out
The SFCM guide says notes usually do not include personal opinions, too much technical terminology, or overly casual or emotional language. It also warns against more personal anecdotes than information. The Bard Conservatory says notes should not read as reference entries.
Note that the NFA allows a casual tone and the SFCM warns against overly casual language. The two fit together if you keep the voice friendly and the content factual.
Use your own words
Some institutions have firm rules. The FIU Wertheim style guide requires notes in the writer's own words and forbids the use of AI or ChatGPT. The UVic style guide says notes that are not original thoughts must be cited. It also says you must get permission to reproduce text unless it is open-source or public domain. Check what your own school or venue requires before you copy any text.
A program notes template
Use this layout for each piece. The headings follow the UVic style guide, which puts the piece name and composer in bold. It also places notes after the complete list of repertoire.
| Part | What goes in it | Length guide |
|---|---|---|
| Heading | Full title, with movements if any, and composer with birth and death dates | One or two lines |
| Composer | Who they were, only what matters here | 1 to 3 sentences |
| Context | When and why it was written, first performance, scoring | 2 to 4 sentences |
| The music | Genre, style, shape of the piece | 3 to 5 sentences |
| Listen for | Two or three specific things | 2 to 3 sentences |
| Performers | Names of accompanists, soloists, narrators | As needed |
The whole note should land inside the 250 to 400 word range from SFCM. Short pieces can have shorter notes.
A short worked example
Here is the pattern in a sample note for a made-up piece. It is an illustration, not a real work.
"Harbour Lights", Jane Example (b. 1980)
Jane Example wrote this song for a school choir in her home town. It was first sung in the town hall by the choir that commissioned it. The piece is for three-part voices and piano. Listen for the piano figure in the opening bars. It returns in the last verse, played more slowly, as the harbour goes quiet.
The note names the writer, the setting and the scoring. It then gives one thing to hear. That is the whole structure.
Planning the full program
Notes are one part of a printed program. The FIU style guide says the front cover should show the program title, the featured artists, the date and time, and the venue name and address. The program page lists the repertoire. Notes come after it. FIU also says titles of larger works are italicised, smaller works go in quotation marks, and first citings are in bold.
Biographies take space too. UVic caps faculty and student biographies at 200 words and guest artists at 400 words. Ensemble biographies run 150 to 400 words. Combined biographical information for all performers should not exceed 800 words. These are one university's limits. Use them as a guide for your own page count.

School concerts
The NAfME post by Lori Schwartz Reichl recommends that school programs include notes with a brief composer biography, details of the work, historical and musical context, and a description of how the work will sound. It also suggests a performer interpretation, and biographies of any guest conductor or soloist.
The same post advises listing all accompanists, narrators and soloists. It suggests praising student achievements at county, state, regional, national or international events. It adds thanks to supporters, upcoming events and contact information. It also says to plan ahead and not expect a one-day turnaround.
Themed programs
If the whole program has a theme, you do not need a separate note for each piece. The Bard Conservatory says notes can be brief. For an integrated program, it says you can write one essay on the program as a whole.
Keeping track of repertoire
Program notes depend on a clear repertoire list. For a choir, band or school ensemble, the list changes through the term. Pieces are added, dropped or reordered. Keep one current list of titles, composers, movements and performers. Then write the notes from that list.
A tracking tool helps here. Repertoire Tracker in Stormusi Classroom is a Stormusi product for managing repertoire. For students who need help with their own program notes, Stormusi Composer supports sheet music creation using AI. Check your school or venue rules on AI first, as the FIU example above shows.
Rehearsal tracks for choirs and classrooms
Many readers who search for program notes also look for choral accompaniment tracks and classroom backing tracks. The two tasks connect. The tracks help you prepare the music, and your notes then describe what the audience will hear.
Types of tracks
Ascension Tracks lists four common types of pre-recorded tracks for choirs:
- Full accompaniment tracks: the whole band or orchestra without vocals.
- Vocal demonstration tracks: guide vocals for early rehearsals.
- Split tracks: one channel carries the music and the other carries the vocals.
- Multitracks or stems: individual parts you can adjust in playback software.
Alfred Music says a director who does not play piano can use publisher-made accompaniment tracks. The director can also record a pianist playing the parts on a phone.
Using tracks in rehearsal
The Ascension guide gives practical steps:
- Match the track to the choir's key and tempo before the first rehearsal.
- Teach the parts a cappella or with piano before using the track.
- Keep the track quieter than the choir.
- Use good speakers or a small PA, and connect by wire rather than Bluetooth.
- Label files by song title, key and version.
The S&S article on rehearsal tracks points out that a track is not neutral. Someone chose its tempo, rubato and breaths. Singers who learn with it learn those choices as if they were in the notation. Its remedies include offering more than one tempo, stating the reference pitch, and marking the track as a learning aid. It also suggests scheduling live accompaniment early enough to replace the track's habits.
This is useful when you write notes. If your performance differs from the recording, say so in the note. Do not describe the recording's tempo as the composer's.
Pop and jazz
Beth Morgan of The Creative Choir Leader says backing tracks suit pop, soul and jazz songs with a steady tempo, where a rhythm section would normally play. She says tracks can be customised by removing the piano part, so a live pianist is not replaced. She also says tracks cannot replace live musicians.
Classroom checks
GoldPass Music offers a checklist for preparing a track. Agree the song version, key and arrangement. Know the introduction and the student's entrance cue. Note any repeats, instrumental gaps or changed endings. Rehearse a short section first, and set a clear restart point.
Chamberlain Music says adjustable backing tracks give students a sense of balance, timing and musical context. It says teachers can build them in GarageBand, Logic or Cubase. It also suggests omitting prerecorded parts so students can play live with the rest.
Copyright
Check the rules before you share tracks with students. NAfME's copyright guidance covers the U.S. TEACH Act. It says rehearsal tracks may be created and distributed if the instructor controls distribution to only the students registered for the class. It also says a work that was not purchased should not be used. This is a United States rule. Australian teachers should check the licences that apply to their school or studio.
Our perspective
We build Stormusi for music teachers, studios and ensembles. Our products are made by educators for educators.
Program notes show a common problem in music teaching. The writing is small, but it depends on many other tasks. You need the repertoire list, the rehearsal schedule, the right recordings and the right parts for each student. When these sit in different places, the notes get written at the last minute.
We think the tools should sit under one login. Our products cover classroom tools, studio management, ensemble organisation, AI-supported sheet music creation and an in-browser lab for collaborative assignments. You pay only for the products you use. We do not charge per student, so a larger choir or class does not cost more.
For a concert, this means a teacher can track repertoire, prepare materials and write notes in one place. We recommend starting with the repertoire list. Everything else follows from it.
Stormusi
Plan your concert materials with Stormusi
Stormusi Classroom gives music teachers tools for the classroom. Stormusi has no per-student fees, and you pay for the products you use. You can start with the free tier options and add products as you need them. Discounts apply when you bundle several products.

To manage the pieces in your concert, open Repertoire Tracker. To see the full range of classroom tools, go to Stormusi Classroom. You can also learn about the whole suite on the Stormusi site.
FAQ
How long should program notes be?
SFCM recommends 250 to 400 words for each piece or set. The Bard Conservatory says notes can be quite brief. For a themed program, one essay on the whole program can replace separate notes.
What is the difference between program notes and a program?
The program is the whole printed document. It lists the repertoire and performers, and it can carry biographies and thanks. Program notes are the part of it that explains the music. FIU puts the repertoire on the program page and the notes after it.
Where can I find information for my notes?
Start with listening to the piece. Then use the score, the publisher's information and reputable references for dates and first performances. Cite anything that is not your own thought, and get permission before you reproduce text unless it is open-source or public domain, as UVic requires.
Should students write their own notes?
Yes, where the school allows it. Writing the note helps the performer understand the music better. Check your institution's rules on sources and AI tools first, because some, such as FIU, forbid them.
Can backing tracks replace a live accompanist?
They are a good tool when you have no accompanist or cannot play the accompaniment yourself. They cannot replace live musicians. Schedule live accompaniment before the concert so the choir does not learn the track's habits as the notation.
Sources
- Concert program, Wikipedia
- Classical Music Terms You Should Know, Fort Collins Symphony
- Writing Concert Program Notes, Mike Allsen
- Write Program Notes, Syracuse University Libraries
- Program Notes, San Francisco Conservatory of Music
- Writing program notes, NFA Research Committee
- Printed programs and bios, Bard Conservatory of Music
- What to Include, CSU Ohio research guide
- Style Guide, FIU Wertheim School of Music
- Concert Program style guide, UVic
- Get with the Program, NAfME
- Copyright Considerations for Music Educators, NAfME
- Tips for Rehearsing with Pre-Recorded Tracks, Ascension Tracks
- 10 Ways to Manage Choir Rehearsals, Alfred Music
- Using Customised Backing Tracks, The Creative Choir Leader
- Rehearsal tracks and their habits, S&S
- Singing With Accompaniment and Backing Tracks, GoldPass Music
- 5 Ways To Use Digital Tools To Enhance Musicianship, Chamberlain Music
