©2023 Michael Norris

A set of plug-ins for Sibelius that check your scores for common notation and layout issues.




Click here to download the complete set of plugins

Individual plugin downloads

(MN) CHECK LAYOUT plugin v 1.6


  • Locate the downloaded folder, and the files within called MNCheckLayout.plg, MNCheckRhythmicNotation.plg, MNCheckAccidentals.plg and MNClearCommentsAndColours.plg. These are the plug-in files themselves.
  • Go to your Sibelius Application Data folder
    • on Windows, this is C:\Users\username\AppData\Roaming\Avid\Sibelius\ (or \Sibelius 7\)
    • on Mac, go to the Finder, and choose Go→Go To Folder… and enter: ~/Library/Application Support/Avid/Sibelius/
  • If you see a folder called 'Plugins', open it — if not, create it (make sure you spell it exactly, including the capital P), then open it.
  • If you see a folder called 'Proof-reading', open it — if not, create it, then open it.
  • IMPORTANT: this is case-sensitive, so it must be spelled exactly as written, including the capital P.
  • Drag the plug-in files to the 'Proof-reading' folder. Mac users may need to hold down the option key in order to copy it, rather than making an alias.


One of the most common errors in music notation is poor rhythmic notation, especially when notes or rests ‘hide’ a beat, or when the beaming is incorrect. These issues can be very offputting for performers, and can lead to problems in rehearsal and performance. This plugin was created to help composers ensure that their scores meet these professional expectations by checking over the selected music for incorrectly notated rhythms. If it finds an issue, it will add a comment and highlight the offending note(s)/rest(s). The comment tells you what is wrong and how to fix it. (NB: the plugin does not fix the error—the user must correct it.)

The following common rhythmic notation issues will be found and flagged:

• Notes 'hiding' a beat (with common exceptions)
• Tied notes that can be 'condensed' into a single note
• Rests that can be 'condensed' into a single rest
• Bar rests entered manually
• Notes not beamed together
• Notes incorrectly beamed together


This plug-in for the Sibelius music notation software checks your score for 60 different layout, notation and instrumentation problems.

If the plug-in finds what it thinks is an issue, it will add a comment and highlight the offending note(s)/rest(s)/object(s). The comment tells you what is wrong and how to fix it. (NB: the plugin does not fix the error—the user must correct it.)

The plug-in does not check for rhythmic notation problems or opportunities for improving accidental spelling — you can use the 'partner' plugins, Check Rhythmic Notation and Check Accidental Spelling for these.

If you wish to clear all the comments and highlighting, use the accompanying ‘(MN) Clear Comments and Colours” plug-in.

In the dialog box that opens when you choose the plug-in, you can select which issues you want to check your score for, from the following list:


Spacing and layout
⁃ Check staff spacing: Checks that the space between staves is between 6–9mm. As this is only a recommended value, you can turn this off in special cases.
⁃ Check system spacing: Checks that the space between systems is between 12–16mm. As this is only a recommended value, you can turn this off in special cases.
⁃ Check staff size: Checks that the staff size is not too large or too small. Recommended sizes are: 1) solos and single-staff duos: 5.9–6.5mm; 2) trios or duo with grand staff: 5.6–6.5mm; 3) 4 staves: 5.3–5.9mm; 4) 5+ staves: 4.4–5.0mm
⁃ Check margins: Checks that the margins are 15mm or smaller. As this is only a recommended value, you can turn this off in special cases. ⁃ Check barline width: Checks that the barline width is between 1–1.6mm.
⁃ Check beam thickness: Checks that the beam thickness is between 0.45–0.5mm.
⁃ Check bar spacing: Checks for systems that contain considerably more or fewer bars than the average. It is impossible for Sibelius plug-ins to reliably tell when the music is too spaced out or too cramped, so you may need to ignore these warnings.
⁃ Check fermatas: For music with more than 2 staves, checks to see whether there is one part that has a fermata, but the other parts don’t (which would be expected)

Staff names and order:
⁃ Staff names (solo works): Checks that the staff names are hidden for solo works.
⁃ Staff names (ensemble): For ensembles of less than 6 players, checks that the first system staff names are full, but after that, are not shown. There are some situations in which you might need to show them, however, so this could be turned off.
⁃ Duplicate staff names: Checks whether two staves have been given identical names (e.g. 'Violin' and 'Violin'), or one staff is numbered and one is not (e.g. 'Violin I' and 'Violin')
⁃ Grand staff order: For sextets and smaller, checks that grand staff instruments are at the bottom.
⁃ Special ensemble order: Checks the correct order for some specific non-orchestral ensembles (wind quintet & brass quintet)
⁃ Brace on single staff: Single staves should not have a brace on them, but they are sometimes erroneously added by Sibelius (e.g. the vibraphone) and should be manually removed.
⁃ Check system text staves: Checks that system text, such as tempo markings, are shown above the correct staves on the score (i.e. above the top and above the string section only). There are some variances in practice here, so you could ignore this warning.

Font and text placement:
⁃ Check tuplets font: The default Sibelius tuplet font of 'Opus Text Std' or 'Helsinki Text Std' is quite heavy for tuplet text; this plugin suggests changing it to Times New Roman italic. This is a question of style, and can be ignored or turned off.
⁃ Check dynamics font: Checks that dynamics have been entered with the correct font.
⁃ Check styled text: Checks for markings that should not be italicised (e.g. pizz., arco, etc) or bold
⁃ Check dynamics location: Checks that dynamics appear below the staff. As there are sometimes good reasons for dynamics to appear above the staff, this could be ignored.
⁃ Check Expression location: Checks that Expression text appears below the staff. Text appearing above the staff should generally be Technique text.
⁃ Check Technique location: Checks that Technique text appears above the staff. As there are sometimes good reasons for Technique text to appear below the staff, this could be ignored.
⁃ Check text misplaced: Checks for text that has been placed a long way from the note it is attached to, which may indicate it has been attached to the wrong staff, which could affect the parts.
⁃ Instrument change on note: Checks for an instrument change warning being put above the last note of the previous instrument, rather than afterwards ⁃ Check straight quotes: Checks for text objects that include a ‘straight’ quote, and suggest that it should be made curly — see

Common text errors:
⁃ Check misspellings: Checks for common misspellings of text (e.g. 'col lengo'), as well as incorrect use of fullstops (e.g. 'arco.')
⁃ Check lowercase text: Checks text that should be lowercase (e.g. 'pizz', etc) is indeed lowercase
⁃ Check tempo capital: Checks to see if a tempo marking begins with a capital letter (it should do), or if a tempo change (rit/accel) starts with a lowercase letter (it should do)
⁃ Check space at start: Checks to see if there is a space character or other non-alphanumeric character at the start of a text string.
⁃ Check abbreviations: Checks for text that is commonly abbreviated (e.g. 'con sordino')
⁃ Check Expression text: Checks for text objects that should be in Expression text (e.g. 'cresc.')
⁃ Check Tempo text: Checks for text objects that appear to be tempo markings, but are not in Tempo text.
⁃ Check ‘trem.’ markings: Checks for explicit ‘trem.’ or ‘tremolo’ text objects, which should instead just be indicated with the three-stroke tremolo marking from the Keypad.
⁃ Check redundant dynamics: Checks for dynamic markings that have recently already been set (e.g. pp occurring 2 bars after pp was already marked). There are some situations where this might be helpful, so could be ignored.
⁃ Check incorrect symbols: Checks that symbols such as fermatas have been entered using the keypad, not using the symbol palette

Special Instrument Notations:
⁃ Check mute markings: Checks for unnecessary mute indications when the instrument is already muted/unmuted (i.e. no duplications)
⁃ Check arco/pizz.: Checks arco/pizz./col legno markings to ensure no duplications
⁃ Check tasto/pont.: Checks tasto/pont/ord markings to ensure no duplications. It can differentiate between, say, 'sul pont.' and 'poco sul pont.'
⁃ Check tremolos: Checks that no more than 3 strokes have been used to indicate an unmeasured tremolo. Also, for pitched percussion, checks that tremolos have been written as 'single tremolos' rather than 'double tremolos'.
⁃ Check correct clefs: Checks common orchestral instruments for incorrect use of clefs (e.g. alto clef in the cello)
⁃ Check 8va/8ba etc.: Checks incorrect use of 8va/8vb, e.g. 8va in bass clef
⁃ Check harmonics: Checks that a) artificial harmonics have been entered using the correct interval of a perfect fourth and b) natural harmonics have been entered at a position where a natural harmonic exists. Note that there are some instances, such as double-stops with a stopped note and a natural harmonic, that look like artificial harmonics but have different intervals in them. Therefore the composer may ignore these warnings if they are confident in their string writing.
⁃ Check pizz issues: Checks that pizz. notes have not been written with staccato articulations, which is generally not recommended, or that the duration of pizz notes are not too long
⁃ Check ‘tutti’/‘div.’ etc: Checks that the correct way of marking tutti, a 2 and div have been used on orchestral scores
⁃ Check piano stretches: When writing for piano, checks that the chords in each hand are within a tenth.

General errors:
⁃ Check slur issues: Checks for a number of issues relating to the use of slurs:
a) Slurs that begin at the end or middle of a tied note.
b) Slurs that end at the beginning or middle of a tied note. (For very long tied notes, this warning could be ignored)
c) Slurs that end on the same note as another slur starts. (There are a number of situations where this warning can be ignored)
d) Repeated notes under a slur (unless they have a tenuto or staccato articulation).
e) Accented notes under a slur. (If a diaphragm accent or accent during continuous bowing is intended, this warning can be ignored).
⁃ Check appoggiaturas: Checks for appoggiaturas, which are sometimes incorrectly used instead of grace notes.
⁃ Check flipped stems: Checks for manually flipped stems for non-cross staff notes, which are almost never needed.
⁃ Check mid-tie accidental: Checks for tied notes with an accidental rearticulated in the middle of the tie.
⁃ Note tied to another pitch: Checks for a tied note with the tie going to a note of a different pitch.
⁃ Check pickup bar rests: Checks for pickup bars with different lengths in different parts, or the incorrect length given.
⁃ Staccato on dotted note: Checks for incorrect use of staccato on a note with an augmentation dot, which is almost always incorrect (or at least contradictory)
⁃ Check transposing score: Checks that, if you are using transposing instruments, you have switched the Transposed Score function switched on (as it is recommended that the final score is transposed)
⁃ Check key signature: Checks for key signatures with more than 6 sharps or flats (which can usually be enharmonically rewritten), and for key signatures that are only in effect for less than 16 bars (where accidentals might be more appropriate). There are some genres such as musical theatre where regular key signature changes are common, and this warning can be ignored.
⁃ Check redundant time signatures: Checks for time signatures that are not needed (e.g. a change to 4/4 when the metre was already 4/4).

⁃ Title: No text in Title text has been included (may be ignored if intentional)
⁃ Composer name: No text in Composer text has been included (may be ignored if intentional)
⁃ Initial Tempo text: No tempo marking has been put on the first bar
⁃ Initial time signature: No time signature has been set in the first bar
⁃ Initial dynamic: No dynamic has been put on the first note of each part
⁃ Dynamic after 3 bars rest: Checks to see whether a dynamic has been (re)stated after a part has been silent for 3 or more bars.
⁃ Dynamic after long hairpin: Checks to see whether a dynamic has been put at the end of a hairpin that lasts a bar or longer. NB it ignores hairpins in grand staff instruments (as the dynamics could be placed in either staff), or diminuendos going to a rest (which are usually just expressive 'fade outs')
⁃ Rehearsal marks: For non-solo works longer than 30 bars, checks to see if rehearsal marks have been given. As this may not be appropriate to your work, this could be turned off.< br/> ⁃ Clef changes: Checks for very high passages with multiple ledger lines where a clef change could be used to improve readability.
⁃ Check l.v. ties: Checks to see whether a tie in a note looks like it’s being used as a ‘laisser vibrer’ tie, but has not been set to ‘l.v.’ in the Inspector
⁃ Pedal indications: For instruments with a sustain pedal (vibraphone, piano), looks to see whether some kind of pedalling indication has been given


This plug-in for the Sibelius music notation software checks your score for potential issues with accidental spelling.

There are four accidental checks:

⁃ Check augmented and diminished intervals: Checks for augmented and diminished intervals that are preceded or followed by another augmented or diminished interval — often a sign that an accidental has been misspelled. There are a few exceptions to this rule, however, such as two tritones in a row, which are not flagged.
⁃ Check double-sharps and double-flats: While double-sharps and double-flats are not in and of themselves incorrect, if the music is atonal or does not utilise strict tonal logic, then in general you should avoid using them, usually by respelling enharmonically. This check will go through and flag any double-sharps and double-flats.
⁃ Check B#, Cb, E#, Fb: While these accidentals are not in and of themselves incorrect, they are often considered inconsiderate, and in atonal music, are often unnecessary. The check does try and account for tonality, however, in a very crude fashion: it will not flag the Cb or Fb if there are more than 2 flats in the key signature; and it will not flag the E# or B# if there are more than 2 sharps in the key signature.
⁃ Check courtesy accidentals: This will flag any notes that do not have an accidental, but had a different one in the previous bar — often a good candidate for a courtesy accidental.