Mitigation registers and drafting conditions from them
Commitments buried in technical chapters rarely reach the condition schedule intact. A numbered mitigation register fixes that, and makes the draft conditions almost write themselves.
A mitigation register turns the commitments buried in twelve technical chapters into one numbered schedule that a case officer can convert into planning conditions without rewriting your evidence. Build it properly and the draft conditions almost write themselves, because every row already names the measure, the effect it addresses, the mechanism that secures it and the point in the programme when it bites. Leave the commitments scattered through the chapters and the officer will draft from the consultee responses instead, which is how schemes end up with conditions that contradict the assessment they came from.
The register is also the document that protects you later. When someone asks in year three why a bund is 2.5 metres high, the answer is a row with a chapter reference behind it.
Why a register beats scattered commitments
Technical chapters bury mitigation inside paragraphs of assessment. A noise chapter will say that with a 2.5 metre acoustic barrier along the eastern boundary the residual effect is minor adverse. That sentence is doing three jobs at once: describing a measure, fixing a specification and reaching a conclusion that depends on the measure being delivered.
Three problems follow. The measure is easy to miss on a read-through, so it does not reach the condition schedule. The specification lives only in prose, so the drawing shows a 2 metre fence and nobody notices. And the residual conclusion is conditional on something that was never secured, which is the point an objector or an inspector will find.
A register fixes all three by making the measure a row with an identifier. The chapter then refers to measure NV-04 rather than repeating the specification, and the identifier follows the measure through the conditions, the construction documents and the discharge applications.
Embedded, additional and residual
Separate the three or the register becomes unusable.
Embedded mitigation is designed in: the building set back from the boundary, the attenuation basin in the layout, the access geometry. It is already in the parameters or drawings the application seeks approval for, and it is secured by the plans condition rather than by anything separate. Flag it as embedded and cross-refer to the drawing number.
Additional mitigation is what the assessment recommends on top of the design: the acoustic barrier, the construction hours restriction, the bat boxes, the dust suppression regime. This is the material that needs a condition or an obligation, and it is the part of the register that officers work from.
Residual effect is not mitigation at all. It is the conclusion after both of the above, and it belongs in the register as a column rather than a row, so that anyone reading a measure can see what it is buying.
Where a measure depends on a monitoring result rather than being fixed at the outset, say so in the row. Adaptive mitigation is legitimate and common in lighting and noise work, but it has to be drafted differently, with a trigger and a response rather than a specification.
Assigning each measure to a delivery mechanism
Every row needs a mechanism, chosen on merit rather than habit.
| Mechanism | Suits |
|---|---|
| Plans condition | Embedded design mitigation shown on drawings |
| Standalone condition | A specification or scheme to be approved before a stated trigger |
| Construction environmental management plan | Site practice during the build, secured by one condition requiring the plan |
| Section 106 obligation | Off-site works, land transfer, financial contributions, long-term management |
| Separate consent regime | Highway works agreements, licences, environmental permits |
| No mechanism needed | Legal duties that apply anyway, such as species protection |
The last row matters. A condition restating a statutory duty fails the necessity test, and a register that lists "comply with the Wildlife and Countryside Act 1981" as a mitigation measure invites the officer to treat the whole document as padding.
Where the measure is construction practice, a single condition requiring a construction environmental management plan in accordance with the register is cleaner than fifteen separate conditions. The scope of that plan is the same ground covered by a Construction Management Plan, and the register becomes its appendix.
Drafting conditions directly from the register
A condition has to pass the six tests in the Planning Practice Guidance on the use of planning conditions: necessary, relevant to planning, relevant to the development permitted, enforceable, precise and reasonable in all other respects. Work through the register row by row against those tests before you offer the schedule to the authority.
Precision is where most drafts fail. "Appropriate dust mitigation shall be employed" is unenforceable. "The measures in Table 8.4 of the Air Quality Assessment dated 14 March shall be implemented for the duration of construction" is enforceable, because a monitoring officer can read it and check it.
Triggers deserve the same care. Pick the latest trigger that still delivers the mitigation in time: before first occupation of the relevant phase rather than before any development begins, before above ground works rather than before site clearance. Section 100ZA of the Town and Country Planning Act 1990 requires the applicant's written agreement before a pre-commencement condition is imposed on a grant of permission, so you will be asked in any event, and a register with sensible triggers already in it makes that conversation short.
Two drafting habits are worth adopting. Reference the document by title and date, never by "the submitted assessment", because documents get revised. And avoid reciting the specification in the condition when it is already in a dated document, since a condition that repeats a figure creates a second version of the truth.
Where a condition will not work
Some measures cannot be secured by condition, and the register should say which and why.
Anything requiring works on land the applicant does not control needs either a Grampian condition, preventing development until the works are done, or an agreement with the landowner. Anything requiring payment needs a section 106 obligation, which must satisfy the three tests in the Community Infrastructure Levy Regulations 2010: necessary to make the development acceptable in planning terms, directly related to the development, and fairly and reasonably related in scale and kind.
Long-term management is the recurring case. A habitat created as mitigation, or a lighting regime that has to be maintained for thirty years, needs a management plan with a named responsible body, a funding mechanism and a review cycle. A condition alone cannot deliver that beyond the life of the development, and the environmental zones and obtrusive light limits that a lighting scheme is designed against are only useful if someone is obliged to keep to them.
Monitoring and reporting duties
For each measure that is monitored, the register records what is measured, by whom, to what standard, how often, what the trigger value is, who receives the report and what happens if the trigger is breached.
That last column is the one people leave blank, and it is the one that makes monitoring meaningful. A noise monitoring condition with no consequence attached produces a filing cabinet of data and no behaviour change. A condition requiring works to stop and a revised method statement to be approved if a measured level is exceeded changes how the contractor plans the day.
Councils increasingly charge monitoring fees on section 106 obligations, so budget for them and check what the authority's published schedule covers.
Keeping the register current through determination
The register is a live document and it should carry a version number and a date on every page.
Set a rule at the outset for how changes are recorded: amend the row, keep the identifier, note the version in which the change appeared, and never renumber. Officers and consultees quote identifiers in their responses, and renumbering mid-determination destroys the audit trail.
When the authority issues its draft conditions, map them back to the register and send the mapping. A two column table showing condition 14 against measures NV-04 and NV-05, with one row flagged as not yet secured, is the most useful thing a consultant can put in front of a case officer in the fortnight before a committee.
Illustrative example: a 250 dwelling scheme produces 68 register rows, of which 31 are embedded and secured by the plans condition, 24 are delivered through a construction environmental management plan under a single condition, 9 need standalone conditions, and 4 go into the section 106 because they involve off-site highway works and long-term habitat management. The draft schedule falls from 40 conditions to 18. Figures are illustrative.
Where an Environmental Impact Assessment is involved, the Environmental Statement must be prepared by competent experts under the 2017 Regulations, so PlanScope's drafts are a starting point for those experts rather than a substitute. Browse all 66 PlanScope report types to see which documents a major application is likely to need.
This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
What columns should a mitigation register have?
An identifier, the chapter and effect it addresses, the measure itself, whether it is embedded or additional, the delivery mechanism, the responsible party, the trigger point, the monitoring arrangement and the residual effect. Keeping residual effect as a column rather than a row lets anyone reading a measure see what it buys.
What is the difference between embedded and additional mitigation?
Embedded mitigation is designed into the scheme, such as a set back or an attenuation basin, and is secured by the plans condition with a drawing reference. Additional mitigation is what the assessment recommends on top, such as an acoustic barrier or a dust regime, and that is the part needing conditions or obligations.
How do I make a mitigation condition enforceable?
Reference a named document with a date and a table number, rather than repeating the specification in the condition or using words like appropriate and adequate. A monitoring officer has to be able to read the condition and check compliance on site, which is what the precision test in the Planning Practice Guidance asks for.
When does a measure need a section 106 obligation instead of a condition?
Where it requires payment, land transfer, off-site works outside the applicant's control, or long-term management beyond what a condition can reach. The obligation must satisfy the three tests in the Community Infrastructure Levy Regulations 2010: necessary to make the development acceptable, directly related to it, and fairly and reasonably related in scale and kind.
Should the register be renumbered when measures change?
No. Keep the identifier, amend the row, and note the version in which the change appeared, with a version number and date on every page. Officers and consultees quote identifiers in their responses, so renumbering mid-determination destroys the audit trail and makes the mapping to draft conditions unreliable.
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.