Templates, Checklists and Examples

Worked example: BS 4142 rating level arithmetic

6 min readBy PlanScope Editorial Team

Rating level minus background is the number a BS 4142 assessment turns on. This illustrative worked example shows how each quantity is derived and how mitigation at source changes the answer.

A BS 4142 rating level calculation has four quantities and one subtraction. Measure the background sound level, determine the specific sound level from the source, add any acoustic feature corrections to get the rating level, then subtract the background from the rating level. The excess is what the assessment turns on, and everything contentious in a BS 4142 report happens in the two steps before that subtraction.

The figures in the worked example below are illustrative and exist only to show the arithmetic.

The terms and what each one means

Four terms carry the method, and the standard uses them precisely.

The background sound level is the LA90 over the reference time interval: the level exceeded for 90 per cent of the period, representing the underlying quiet of the location without the source running.

The specific sound level is the LAeq of the source under assessment, at the assessment position, over the reference time interval.

The residual sound level is the ambient with the specific source removed. It matters when the specific sound has to be derived by subtraction rather than measured directly.

The rating level is the specific sound level plus acoustic feature corrections.

Reference time intervals are one hour during the day, taken as 07:00 to 23:00, and 15 minutes at night, 23:00 to 07:00. Using an hour at night, or a daytime 15 minute period, is a methodological error that an experienced reviewer will spot immediately.

Measuring the background

The background sound level is the measurement most often done badly, because it is the one that most affects the result and the one most exposed to judgement.

Measure at the assessment position, which is at the receptor rather than at the site boundary, and at a height representing the exposed facade. Measure over a period long enough to characterise the quiet times, which for a night-time assessment means several hours across more than one night.

Then choose the representative value. The standard does not prescribe an arithmetic mean, and taking the lowest single 15 minute LA90 of the week is as wrong as taking the average of everything. The usual approach is to identify the typical lowest levels during the period when the source will operate, exclude periods affected by extraneous events such as rainfall or a passing aircraft, and state clearly how the figure was chosen.

Record the weather. Wind speed and direction, rainfall and temperature all affect both measurement validity and propagation, and a reviewer will check them.

Determining the specific sound level

Three routes exist, in descending order of reliability.

Direct measurement at the receptor with the source operating and the residual sufficiently low. This is the cleanest and the least often available.

Measurement near the source, then calculation to the receptor using distance attenuation, directivity, screening and ground effects. This is the normal route for a proposed installation using manufacturer sound power data.

Derivation by subtracting the residual from the ambient. Valid, but the arithmetic becomes unstable when the specific sound is well below the residual, and the standard warns about it.

Whichever route is used, state the operating condition assessed. A condenser running at part load on a mild evening is not the design case, and the assessment should cover the worst realistic operating condition during the relevant period.

Acoustic feature corrections

Corrections are added to the specific sound level where the sound has a character that makes it more noticeable, and they are the part of the method most open to argument.

Feature Typical correction range
Tonality Up to 6 dB
Impulsivity Up to 9 dB
Intermittency 3 dB where readily distinctive
Other characteristics 3 dB

Tonality can be assessed subjectively or by the objective one-third octave band method set out in the standard. Use the objective method where the result is likely to be contested, and show the spectrum. A fan with a clear blade passing frequency, a transformer hum and a compressor whine all attract a correction.

Apply corrections once. Adding a tonal correction and an "other characteristics" correction for the same tonal quality is double counting, and it happens.

The worked example

Illustrative figures for a proposed external condenser serving a commercial unit, assessed at the nearest residential facade at night.

Quantity Value
Background sound level, LA90 over 15 minutes 32 dB
Specific sound level, LAeq over 15 minutes 38 dB
Tonality correction, objective method 4 dB
Rating level 42 dB
Excess over background 10 dB

Under the standard, a difference of around 10 dB or more is an indication of a significant adverse impact, depending on context. A difference of around 5 dB is an indication of an adverse impact, again depending on context. Where the rating level does not exceed the background, that indicates a low impact.

Now mitigate. An attenuator and a change of unit reduce the specific sound level by 8 dB to 30 dB, and the acoustic treatment also removes the tonal character, so no correction applies. The rating level becomes 30 dB, two below the background. The same installation has moved from the upper band of the standard's indications to a low impact, and the only change is at the source.

That is the lesson of the arithmetic. Mitigation at source is worth more than any argument about the background figure.

Context and the limits of the comparison

The standard is explicit that the numerical difference is an indication rather than a verdict, and that context has to be considered.

Context means the absolute level as well as the difference. A rating level of 28 dB against a background of 20 dB is a 8 dB excess in a very quiet rural location, and the absolute level may still be below any level likely to disturb sleep. The reverse case, a small excess over a high urban background, may matter more than the number suggests because the character of the sound is different from the existing soundscape.

Context also covers the design of the receptor. A dwelling with mechanical ventilation and acoustically treated glazing, where windows do not need to be opened for cooling, is in a different position from one relying on open windows, and the standard expects that to be taken into account rather than assumed away.

State the uncertainty. Measurement uncertainty, the uncertainty in manufacturer data and the uncertainty in propagation modelling all belong in the report, and an assessment reporting a rating level to one decimal place without an uncertainty statement is overstating its own precision.

Reporting it so a reviewer can follow it

Set out the measurement positions on a plan, the instrumentation and calibration record, the survey dates, times and weather, the raw data, the chosen background value with the reasoning, the specific sound derivation, each correction with its justification, the rating level, the comparison and the context discussion.

A Noise Impact Assessment built that way can be checked line by line, which is what a reviewing acoustician or an environmental health officer wants. Councils expect a suitably qualified author, and professional review is strongly advised. Drafting support can carry the structure and the policy narrative, while the measurements, the corrections and the judgement belong to the practitioner. The professional directory is one route to a reviewer.

Every figure above is illustrative. Use the current version of the standard and the authority's own requirements.

Enter your postcode on PlanScope to see which noise and environmental documents your scheme is likely to need.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. For specialist technical reports, qualified professional input may be required.

Frequently asked questions

What reference time intervals does BS 4142 use?

One hour during the day, taken as 07:00 to 23:00, and 15 minutes at night, 23:00 to 07:00. Using the wrong interval is a methodological error that invalidates the comparison, and it is among the first things a reviewing acoustician or environmental health officer checks in a submitted report.

How is the representative background level chosen?

By identifying the typical lowest LA90 values during the period when the source will operate, excluding periods affected by extraneous events such as rain or aircraft, and stating the reasoning. Neither a simple average of everything nor the single lowest measured value of the week is appropriate, and the standard does not prescribe an arithmetic method.

What corrections can be added to the specific sound level?

Corrections for tonality of up to 6 dB, impulsivity of up to 9 dB, intermittency of 3 dB where readily distinctive, and 3 dB for other characteristics. Each applies once. Adding both a tonal correction and an other characteristics correction for the same tonal quality is double counting and will be challenged.

What does the difference between rating level and background mean?

A difference of around 10 dB or more indicates a significant adverse impact, and around 5 dB indicates an adverse impact, both depending on context. Where the rating level does not exceed the background, that indicates a low impact. The standard treats the figure as an indication rather than a verdict.

Why does context matter as well as the difference?

Because the same excess means different things in different places. A small excess over a very low rural background may still sit at an absolute level unlikely to disturb sleep, while a modest excess over a high urban background can matter if the character of the sound differs from the existing soundscape. Receptor design is also relevant.

Sources and further reading

bs 4142noise assessmentacousticsrating levelworked example

This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.

More in Templates, Checklists and Examples

View all →
Templates, Checklists and Examples7 min read

Checklist for responding to planning objections

An applicant's response to objections is a sorting exercise first. Answer the material points with dimensioned evidence, acknowledge private law issues in one neutral sentence, and offer conditions where you cannot prove a point.

Read article →
Templates, Checklists and Examples6 min read

Checklist for handover of planning documents at completion

The planning file handed over at completion is what a buyer's solicitor asks for years later. Here is the index, and the records that are hardest to recreate.

Read article →
Templates, Checklists and Examples7 min read

Checklist for a tree works application under a TPO

TPO applications are free and decided in eight weeks, but vague descriptions get them refused. Here is the evidence that gets consent granted as proposed.

Read article →
Templates, Checklists and Examples7 min read

Checklist for a demolition prior notification submission

A demolition prior notification is narrow by design. The authority can consider only the method of demolition and the proposed restoration of the site.

Read article →
Templates, Checklists and Examples7 min read

Checklist for a larger home extension prior approval

A single storey rear extension deeper than 3m on a semi, or 4m on a detached house, needs prior approval under Class A. Here are the limits, the information to supply and how the neighbour consultation timetable works.

Read article →
Templates, Checklists and Examples7 min read

Checklist for responding to an invalid application notice

Until an application is validated there is no determination clock. Here is how to sort each item on an invalidity notice, decline requests that are not on the published local list, and protect the validation date.

Read article →