HomeAboutMusicBlogMentorship Contact

How to proofread your score so performers take it seriously

Ever wonder why some scores just instantly excite performers? I've seen firsthand how clean, intentional notation can make or break a new score. Here's the framework I use to proofread a score, shown on 2 real submissions for string quartet, so yours looks like a professional, published piece of music.

Saad HaddadBy Saad Haddad, composer

Here's the video this post comes from (26 minutes), or you can read it below.

  1. Start with a falcon view of the score
  2. All you need on the title page
  3. Put the inside pages in the right order
  4. Give the first page of music breathing room
  5. Get a handle on the instrumentation itself
  6. Go granular, one engraving parameter at a time

1. Start with a falcon view of the score

As a composer who's worked on commissions for the Kansas City Symphony and Ensemble Proton Bern, I've seen firsthand how clean, intentional notation can make or break a new musical score.

So I want to share the framework for how I look at scores, and show you exactly how I change real submissions from my subscribers.

Step 1 is when I open the score. I'm doing what's called a falcon view of the score. What that means is, does this score look like a professional, published piece of music?

Imagine you're a falcon looking at a score. Does it look like a piece of music from afar? Are there things clashing together? Are the systems separated well? Is there enough blank space in between the staffs? Is there too much blank space?

If you don't know what a publish-ready score looks like

It's very, very easy to find out. You can go on issuu.com, Boosey & Hawkes, Bärenreiter. There are all these websites that show modern contemporary classical music, and they have their scores available online completely for free.

So you can compare the instrumentation that you're writing for with that same exact instrumentation on any of those websites.

In step 2, there are 2 paths

The first path is that it passes the falcon view test and it looks like a publishable piece of music in that instrumentation. Then we start doing a granular look at each bar and seeing what kind of inconsistencies we can find.

The other path is that it doesn't look like it's at that standard yet. Then we have to see why, from a macro level.

The framework for how I look at a score
  1. 1
    A falcon view of the scoreWhen I open the score.
  2. ?
    Does this score look like a professional, published piece of music?Compare it with that same exact instrumentation on any of those websites.
  3. 2
    The first path: it passes the falcon view testA granular look at each bar, seeing what kind of inconsistencies we can find.
  4. 2
    The other path: it's not at that standard yetWe have to see why, from a macro level.

When a contest judge, a live performer, an ensemble or a conductor gets a first read of a score and it doesn't pass the falcon test, they're not going to take the piece seriously.

I hate to be the bearer of bad news here. I'm just the messenger. I've been on a lot of contest juries. I've seen what performers gravitate towards, what conductors gravitate towards.

If it doesn't pass the falcon test, they're not going to take a closer look at it.

If you're not sure what to look for in your own scores, don't worry. I've created a free engraving checklist to guide you through it.

2. All you need on the title page

The first submission was for string quartet, and I took a look at the title page first. It had the composer's name, the title of the piece and the date of composition.

The title of the piece was String Quartet. Normally we'd want to write the instrumentation too, something like 2 violins, viola and cello. But because the piece is called String Quartet, we don't need to do any of that.

So we know what the instrumentation is, we know the title, we know the name of the composer, and we know the date of composition. This composer also put the place of composition, which is totally fine as well, but that's extra information.

The title page on the second submission was perfect, because that's all you need: the title, then your instrumentation, your date and the composer's name.

Title Instrumentation Date Composer's name You don't need anything fancier than that

3. Put the inside pages in the right order

The next thing I look at in the falcon view is the inside pages of the piece.

On the first submission, there were a lot of good things. I saw some program notes, the title of the piece, some copyright notes. But they were all kind of jumbled in the wrong place.

I could tell this just from the falcon view. I hadn't even read a single word of this string quartet, and I was already getting a sense that it's not as professional as it could be.

How to fix it

This score had the copyright and the name of the composer at the top. That's not usually where it goes. At the very top, we write in the instrumentation. In this case, that's 2 violins, viola and cello.

The next part is going to be our performance notes, not our program notes. That's where we want to see all the information about what the instruments are physically doing differently in this piece than they would in a more traditional type of classical piece.

This composer had the techniques used on the bottom of a later page. We want those up a little bit higher, on the previous page.

Then we put our program notes. The program notes go at the bottom.

Jumbled in the wrong place
  • At the topThe copyright and the name of the composer
  • Program notes
  • Composer's notes
  • On the bottomThe techniques used

Not as professional as it could be

What we want to see
  • At the very topInstrumentation
  • The next partPerformance notes
  • At the bottomProgram notes

A quick snapshot of what this piece is about

Keep it simple

This score had a lot of information about each movement, which is all handy dandy. But the reality is most people would probably not read it, especially if they're doing a cursory review of the score.

So I'd try to keep it simple: the instrumentation, the performance notes that are most pertinent to this piece, and program notes that really help the contest judge, the performers, the conductor or the institution.

Anybody that has agency when it comes to performing a piece of music, we want to make sure they're getting a quick snapshot of what this piece is about.

This score had 3 pages of text. I'm pretty sure, without even reading it, that we can get it down to one page, or even one and a half pages.

These really important preface pages
Right now3 pages of text
We can get it down to1 page, or even 1 and a half

Program notes versus no program notes

I know there are people that argue for program notes versus no program notes. I think it's more and more important to have them.

You really want to show what your piece is about as soon as possible. That way somebody looking at your piece, whether it's a contest submission or a performer looking at a piece they want to play, can get a sense of it before even listening to it.

The piece just takes time to listen to, but it doesn't take much time to read a program note. Those are my 2 cents on that.

As for the performance notes, if your piece doesn't have any extraneous techniques, you don't really need that part. The second composer had certain abbreviations, symbols and general instructions, so it was really key to have all of those there.

4. Give the first page of music breathing room

From the falcon view, the first page of music on the first quartet actually looked not bad. Violin 1, violin 2, viola, cello: that was all done correctly. The bracketing was done correctly. All the clefs were done correctly. It had the title, the name of the composer and the movement number.

I'd also put a copyright at the very bottom. Does it really matter to have a copyright written there in this day and age? Not really, because people share scores freely all the time.

But it puts this nice little stamp there, and if it's missing, we kind of notice it. The copyright sign, the year, and then maybe the composer's name is really all you need in that center part.

The notes are squished together

I was still in the falcon view, and I could already see other issues. The notes were kind of squished together. There were 5 bars in the first system, another 5 bars in the second, and then 3 bars in the third.

So the note spacing was a little bit inconsistent, and it felt a little bit squished.

5 bars Squished 5 bars Squished 3 bars Breathing room

One way to fix that is just to move bars to the next system. You'll have to massage it.

In general, we want the notes not to be so stuck together. We want a little bit of breathing room. The third system was not bad in terms of the breathing room, but the first 2 systems needed a little bit of work.

The dynamics are going into the next staff

Another falcon view thing was the spacing in between some of the staves. It was kind of tight, and the way I know that is the dynamics were going into the next staves.

We want to put white space in between the staves in such a way that there's no colliding with the staff right below or above it.

We might even have to make the staff sizes maybe 15 to 20% smaller to accommodate these changes. That might screw up the entire rest of the score when you do that, but sometimes it's necessary. Or you might have to move one area up a little bit and another area down a little bit.

The espressivo really pops out at me

Espressivo is an indication that usually goes underneath the staff, and it's usually in italics. We want to put it next to the dynamic marking, in italics, all lowercase.

This composer had it above, with the first letter capitalized, and that's not really how it's done. It was even going into the second violin and the viola.

This composer had it above, first letter capitalized
Engraved by Verovio 6.4.1-fbe8f46 Espressivo
That's not really how it's done.
Next to the dynamic marking
Engraved by Verovio 6.4.1-fbe8f46 espressivo
Underneath the staff, in italics, all lowercase.

You might think, it just shows the performer what to do, they can read it. But it just doesn't have that falcon view look of professionalism that we want to go for when we're engraving a piece of music.

That was the end of my initial look at the score. If I was a contest judge or a live performer, I'd probably pass on this piece without even going through the rest of it.

That's not something I mean to be critical of. I'm just telling you exactly what I would do, or another performer would do, if they saw something like this. It's because it doesn't pass the falcon view.

5. Get a handle on the instrumentation itself

The second submission passed the falcon view, so I took a closer look at it. I pretend I'm somebody that is a violinist, because who cares about my opinion at the end of the day? It's about the live performers. It's about the contest judges. It's about institutions that want to play your music.

The very first thing we need to get a handle on is the instrumentation itself. I didn't love the instrumentation. It was violin, viola, cello and contrabass, and there are very, very few pieces written for this type of ensemble.

You're going to have a hard time programming that piece of music, because guess what? The string quartet configuration is usually violin 1, violin 2, viola and cello. That's the configuration 99% of the time.

Saad Haddad with the members of the Lydian Quartet
With the Lydian Quartet

If you want to add the contrabass for whatever reason, you can add the contrabass and it becomes a string quintet, which is also a common configuration.

What this piece was written for
ViolinViolaCelloContrabass

Very, very few pieces are written for this type of ensemble

String quartet
Violin 1Violin 2ViolaCello

The configuration 99% of the time

String quintet
Violin 1Violin 2ViolaCelloContrabass

Also a common configuration

Does it mean that it's going to be impossible to put on a program? No, not necessarily. But you do run the risk of creating a bit of difficulty, when this piece can probably, I'm going to say with 99% certainty, be reorchestrated for violin 1, violin 2, viola and cello.

This is kind of like the falcon descended down to 100 ft or something. I don't know anything about falcons. We're zooming in and trying to see what the viability of a piece like this is.

6. Go granular, one engraving parameter at a time

After we fix the falcon view, the white spacing, the number of bars per system, that espressivo marking, now is the time to get into the granular work.

On the first quartet, I looked at the first bit of music, in the cello line, and I noticed the bowing markings. Only in very rare instances do we actually put bowing markings in a piece for strings. The string players will normally put their own bowing markings on a typical piece of music.

On top of that, these bowing markings were incorrect. When you have a slur all over the bar, that means the bow direction stays the same. If you have a down bow and then an up bow, you're telling the performer to go down on the first 2 beats and then up on the next 2 beats, which is the opposite of the slur.

They're confusing. They're conflicting. Either we get rid of them entirely or we keep the slur, but they both can't stay there.

A down bow, an up bow and a slur all over the bar
Engraved by Verovio 6.4.1-fbe8f46 Espressivo
Down on the first 2 beats, up on the next 2, which is the opposite of the slur.
We keep the slur
Engraved by Verovio 6.4.1-fbe8f46 espressivo
The string players will normally put their own bowing markings.

See, I stopped there

I don't say, okay, let's look at all this other stuff and the dynamics clashing. No, we don't worry about that yet. We identified one issue.

Then I zoom out and see if I see this problem in any other parts of the piece. Measure 2 had the same problem with the down bow, up bow. So did the next area.

I'm focusing on just one engraving parameter. If I do them all, dynamics, pitches, rhythms, everything from bar to bar to bar, it's going to drive me nuts.

I want to do it one step at a time, so that I can keep track of the inconsistencies that I myself, as a composer, just do naturally.

And we want to get rid of that habit as well. If you're trying to get rid of multiple engraving habits in one go, your muscle memory is not going to remember that you have to fix those things.

We want it so that the next time you write a piece of music, it's already out of your system. You're not making those mistakes another time in a new piece.

Just one engraving parameter Go back to the first bar Find one issue Fix all of those One step at a time

When I see an engraving mistake, my eye says, are there any more like that in the rest of the score? Chances are if I made that mistake once before, I'll probably make it again.

Where are we crescendoing to?

Back on the first quartet, the next thing I noticed was hopefully a more obvious mistake: a collision between the pianissimo and the crescendo. We don't want any of that. We want to make sure we have a crescendo coming out of the pianissimo.

The next thing, which might be a little less obvious, is the hairpin. This might be a little bit controversial, but I see a lot of hairpins that don't have a dynamic marking in the center.

It's my belief that you should put a dynamic marking there, because it makes it that much clearer. That way the player knows where to crescendo to and then where to back off.

A hairpin with no dynamic marking in the center
Engraved by Verovio 6.4.1-fbe8f46 Espressivo
A crescendo to we don't know what.
With a dynamic marking in the center
Engraved by Verovio 6.4.1-fbe8f46 espressivo
The player knows where to crescendo to and then where to back off.

Let's say that's piano. It could easily have been a forte, and if it's a forte, this is a much different gesture than it would otherwise be. So we want to be really clear on what this is exactly.

Then I went through bar by bar and checked all the dynamics and the hairpins. In measure 3, there was a pianissimo and then a hairpin that was not aligned. Typically speaking, you want the hairpin to be perfectly in line with the dynamic marking.

Having both of these together is redundant

On the second quartet, there was a pizzicato with a tie over. A tie over just means that you're ringing out that pitch.

Next to it was l.v., which means exactly the same thing as that tie over. So we want to get rid of one of them. This is where we have to make a decision, but my vote would be to just get rid of the l.v.

Similar gestures, the same exact dynamics

In the third bar, the viola had a sforzando with a crescendo, which is kind of strange. Where do we go from there?

We had a clue in the cello line, which had a sforzando piano. Because that line is similar to the viola line, I put a piano right there. Now the gestures which are similar have the same exact dynamics.

It just has to be readable

We want to catch the more obvious things before catching the really specific things. A live performer especially is not someone that's going to be thinking of this in a grammatical kind of way, like it has to be completely perfect.

It just has to be readable, and something that performers can see has a professional touch to it. That way they'll take it a lot more seriously.

If you follow this process from the beginning to the end, you're going to have a publishable-ready score by the end of it. And it's going to give you that much more of a chance to get your piece selected in a contest, performed by a live musician, or even have outreach from an institution about a commissioning opportunity.

What to do next

Go back to the first bar of your own score, check it against my free engraving checklist, and see what other things you need to fix.

Keep reading

Orchestral score details that cost you the players' trustWhat the first page of your chamber music score says about youWhy performers pass on your solo pieces before playing a noteAll posts on scores and parts