The commitments register in an environmental statement
The commitments register is the table that lets a case officer secure everything an environmental statement assumed. Here is how to structure it so conditions and obligations follow cleanly.
A commitments register is the single table in an environmental statement that lists every mitigation measure the applicant has promised, numbered, cross-referenced to the chapter that assessed it, with the delivery mechanism and the responsible party named. On a scheme with 14 technical chapters it is the only document that lets a case officer check whether the conditions and the section 106 actually capture what the assessment assumed.
Without it, mitigation lives in prose scattered across several hundred pages, and what gets conditioned is whatever the officer managed to find.
What the register does for the decision maker
The Town and Country Planning (Environmental Impact Assessment) Regulations 2017 require the environmental statement to describe the measures proposed to avoid, prevent, reduce or offset significant adverse effects, and to describe the residual effects that remain once those measures are in place. Those two requirements are linked, because a residual effect is only credible if the mitigation behind it will actually be delivered.
The register closes that loop. It tells the authority which measures the assessment relied on, so that any measure left out of the permission changes the conclusions. It tells the officer drafting conditions what has to be secured and in what form. And it gives the applicant a defence, because a scheme that has committed clearly to a list of measures is much harder to refuse on an effect that the measures address.
Officers read it first and the chapters second. Write it accordingly.
Embedded mitigation against additional mitigation
The distinction matters more than any other in the register, and it is the one most often blurred.
Embedded mitigation is designed into the scheme and assessed as part of the proposal. A building set back 25 m from a boundary, a layout that retains a tree belt, acoustic glazing specified in the drawings, a green roof shown on the plans. These are not promises, they are the development. They go into the register because the assessment depends on them, and because an amendment that removes them undermines the assessment.
Additional mitigation is applied to reduce an effect the scheme would otherwise have. A barrier, a monitoring regime, a restriction on working hours, a compensatory habitat, a travel plan with targets. These are promises, and they need a mechanism.
Mark each entry as one or the other. An authority that cannot tell the difference will try to condition the design, producing conditions that duplicate the approved drawings, or will leave genuine mitigation unsecured because it reads like design.
Numbering commitments so conditions can cite them
Use a numbering convention tied to the chapter, not a running sequence through the document. NOI-04 for the fourth noise commitment, ECO-11 for the eleventh ecology commitment, TRA-02 for transport. Then the number survives a reordering of the chapters, which always happens between draft and submission.
Keep the reference stable once the statement is issued. Where a commitment is withdrawn after a regulation 25 request, retire the number rather than reusing it, and note the withdrawal in the register. Authorities cite these numbers in conditions, and a condition referring to ECO-11 in a superseded version of the register is unenforceable in practice.
Each row needs six fields and no more: the reference, the commitment in a single sentence of plain obligation, the chapter and paragraph that assessed it, whether it is embedded or additional, the proposed mechanism, and the party responsible. Resist adding a column for discussion. The register is an obligations schedule, not a narrative.
Who delivers each commitment, and when
Name the duty holder by role rather than by organisation, because contractors change. The principal contractor, the appointed ecologist, the site manager, the management company, the operator.
Timing is the field that most often fails. A commitment that says "during construction" cannot be enforced, and one that says "before any works above slab level begin, and maintained for the life of the development" can. Use the project milestones the conditions will use: before development begins, before works above slab level, before first occupation, before the use starts, within the first planting season, annually for five years.
Watch for commitments that span the handover. Post-completion monitoring, habitat management over 30 years, travel plan reviews and management company obligations all survive the contractor leaving site, and each needs a party who will still exist.
Turning commitments into conditions and obligations
Three mechanisms carry mitigation, and most registers misallocate between them.
A planning condition suits a measure that controls how the approved development is built or used and can be expressed precisely. Conditions have to meet the six tests in the planning guidance: necessary, relevant to planning, relevant to the development, enforceable, precise and reasonable in all other respects. A commitment that cannot be stated precisely will not survive as a condition.
A planning obligation under section 106 suits a measure that requires payment, land, a long term management regime or something the authority cannot achieve by controlling the development itself. Habitat management across 30 years, off-site highway contributions, affordable housing and monitoring sums belong here.
A management plan approved by condition suits a bundle of operational measures. A Construction Management Plan typically absorbs dust suppression, wheel washing, working hours, deliveries, noise control and complaint handling, which saves a dozen separate conditions. The register should point to the plan and list what the plan must contain.
Mark the mechanism for every row before submission. Where the applicant proposes a condition and the officer prefers an obligation, that argument costs less in week three than in week eleven.
Monitoring and reporting against the register
The 2017 Regulations brought monitoring into the decision itself: where a development is granted permission and material adverse effects are identified, the authority must consider whether monitoring measures are appropriate. Some commitments therefore carry a reporting duty rather than a one-off action.
Set out, for each monitored commitment, what is measured, against what criterion, how often, by whom, to whom the result goes, and what happens if the criterion is not met. That last part is the one applicants leave blank, and it is the part an authority needs. A noise monitoring commitment with no remedial trigger gives the council data and no remedy.
Keep the monitoring proportionate to the residual effect. A commitment to monitor something the assessment found to have a negligible effect invites a condition nobody will ever discharge.
Keeping the register consistent across chapters
Registers fail on internal contradiction, and the cause is almost always that chapters were written by different consultancies to different deadlines.
Four checks before submission. Read every mitigation paragraph in every chapter and confirm it appears in the register, because a measure in the text and absent from the table is the commonest error. Confirm the register contains nothing that no chapter assessed. Check that a measure appearing in two chapters, such as a landscape bund that also provides acoustic screening, has one reference and consistent wording. And check the non-technical summary describes the same mitigation, since objectors read that version.
Then check the register against the drawings. An embedded measure that is not on the submitted plans is not embedded. Demolition and material reuse commitments in particular tend to sit in the register with nothing on the drawings behind them, which a pre-redevelopment audit and its content for material reuse can resolve. Where population and human health is a chapter, the same discipline applies to its measures, as health determinants inside a health impact assessment sets out.
An Environmental Impact Assessment and its environmental statement must be prepared by competent experts under the 2017 Regulations, and the commitments register is the part the whole team has to agree. 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. Enter your postcode on PlanScope to see which reports your site is likely to need.
Frequently asked questions
Is a commitments register required by the EIA Regulations?
Not by name. The 2017 Regulations require the environmental statement to describe the measures proposed to avoid, prevent, reduce or offset the adverse effects it identifies and to report the residual effects that remain. A register is the practical way of meeting that, and most authorities now expect one because it is the only way to check that conditions capture the assessment.
What is the difference between embedded and additional mitigation?
Embedded mitigation is designed into the scheme and shown on the drawings, such as a setback distance, a retained tree belt or specified glazing. Additional mitigation is applied on top to reduce a residual effect, such as a barrier, a working hours restriction or a monitoring regime. Embedded measures need protecting from later amendment; additional measures need a delivery mechanism.
How should commitments be numbered?
By discipline prefix and sequence, such as NOI-04, ECO-11 or TRA-02, rather than a running number through the whole document. Chapter order changes between draft and submission, and a discipline-based reference survives it. Retire a withdrawn number instead of reusing it, so that a condition citing an earlier version still points at the right measure.
Which commitments belong in a section 106 rather than a condition?
Anything requiring payment, the transfer of land, long term management or action the authority cannot secure by controlling the development itself. Habitat management over 30 years, off-site highway works, affordable housing and monitoring sums all sit better in an obligation. Conditions suit measures that control how the approved development is built or used and can be stated precisely.
Does the register need monitoring measures?
Where material adverse effects are identified, the authority has to consider whether monitoring is appropriate, so some commitments carry a reporting duty. For each monitored measure state what is measured, against what criterion, how often, by whom, who receives the result, and what happens if the criterion is not met. The remedial trigger is the part most registers omit.
Sources and further reading
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.