Railway boundaries and the infrastructure manager's view

Building next to a railway brings in a landowner with safety duties, standard requirements it will not negotiate away, and its own consent process running alongside the planning application. The infrastructure manager is a statutory consultee where development would materially change use of a level crossing, and planning authorities consult it as a matter of practice on anything adjoining the operational railway. Its objections are usually technical and resolvable. They are also slow to resolve, which is why the engagement should start at pre-application rather than after validation.

Nothing about this is optional. Work affecting the railway without an asset protection agreement will be stopped.

When the infrastructure manager is consulted

The statutory trigger in Schedule 4 to the Town and Country Planning (Development Management Procedure) (England) Order 2015 concerns development likely to result in a material increase in the volume or a material change in the character of traffic using a level crossing. Where your scheme would put more vehicles or pedestrians across a crossing, consultation is mandatory and the response carries weight.

Outside that trigger, authorities consult on development adjoining the railway because the infrastructure manager is the neighbouring landowner and a statutory undertaker with safety obligations.

Its response normally covers boundary treatment and trespass, structural proximity to cuttings, embankments and bridges, drainage towards the railway, lighting and glare towards the track, construction method and crane oversail, landscaping species and future tree fall, and noise and vibration affecting future occupiers.

Where the policies map shows a railway corridor designation that does not match what is on the ground, the route to resolving it is the same as for other mapping errors, set out in errors on a policies map and how to deal with them.

Standard requirements near the boundary

The published developer guidance sets out requirements that apply as a baseline, and the asset protection team applies them consistently.

The recurring ones are a trespass-proof boundary fence erected on the developer's own land and maintained by the developer, a clear strip inside the site boundary so that maintenance of the fence and the railway boundary does not require access to third party land, no foundations or structures bearing on or within a defined distance of the railway boundary, no drainage discharging onto railway land, and no overhanging eaves, gutters or balconies projecting towards the line.

Two of those are worth stressing because they change the layout. The clear strip reduces the developable depth of the site, which on a narrow plot matters a great deal. And the prohibition on drainage towards the railway means the surface water strategy has to find another receptor, which can be the critical constraint on a site with the railway on its low side.

Design to the requirements rather than arguing with them. The infrastructure manager has no planning duty to compromise and no incentive to.

Excavation, piling and surcharge near the line

This is the technical heart of the relationship, and it is where the asset protection engineer becomes the person who decides your programme.

The works that attract close scrutiny are piling and vibratory compaction near the boundary, excavation that could undermine a cutting slope or a retaining structure, surcharge loading from a building, stockpile or crane close to an embankment, dewatering that could affect ground conditions beneath the track, and any works to or near a bridge, culvert or retaining wall in the infrastructure manager's ownership.

What is required in response is a geotechnical assessment of the interaction, structural calculations, a method statement, and a monitoring regime with trigger and action levels for movement and vibration, agreed before work starts. A Geotechnical Assessment prepared to the relevant Eurocode and supported by site investigation is the document that underpins all of it.

Expect conservatism. The consequence of a track movement is a line closure, so the engineer reviewing your calculations will apply margins that a private development next door would not need.

Fencing, trespass and lighting towards the track

Trespass is the risk the infrastructure manager cares about most, because it kills people.

So the boundary has to be designed as a barrier rather than a line on a plan. That means an appropriate fence type for the setting, no features that assist climbing such as low walls, bin stores or planting against the fence, no gates or informal access points, and a layout that does not create a desire line towards the railway. Where the development includes a play area or a school, expect the requirement to be more demanding.

Lighting is the other safety matter, and the issue is signal sighting. External lighting must not dazzle train drivers, must not be confusable with a signal aspect in colour or position, and must not create glare from reflective glazing or cladding towards the driver's line of sight. A Lighting Assessment showing luminaire positions, orientation, cut-off angles and the resulting illuminance towards the track is the way to demonstrate it.

Landscaping belongs in the same conversation. Species that reach a height capable of falling onto the line are objected to, and leaf fall onto the railway is a recognised operational problem.

Noise and vibration from rail traffic

Residential development beside an operational railway has to deal with noise and vibration from trains, and the responsibility sits with the applicant rather than with the railway.

The planning principle, often described as the agent of change, places the onus on the new development to provide suitable mitigation where it is introduced into an area with an existing noise source. National policy and the guidance on noise both work on that basis, so a scheme beside a freight route cannot expect operational restrictions in its favour.

The assessment needs measurement rather than estimation. Continuous monitoring over a representative period, covering night-time freight movements, with maximum levels as well as averages, because a single passing freight train at night is what wakes people. A Noise Impact Assessment referencing the internal level guidance in the relevant British Standard, with a glazing and ventilation specification, is the normal output.

Vibration and ground-borne noise are separate and are often missed. Where the development sits close to the track, or over a tunnel, assessment against the relevant vibration standard may be needed, and the mitigation is structural rather than acoustic, which means it has to be designed in early.

Crane oversail and construction method

Cranes are the issue that stops jobs. The default position is that no crane may oversail the railway, and that a crane must be sited and configured so that it cannot reach or fall onto the operational railway.

Where oversail or close working is unavoidable, it requires specific agreement, usually including a crane position and radius plan, slew restriction, an exclusion zone, working only during agreed hours or possessions, and an independent check of the crane base design. Scaffolding, piling rigs, mobile elevating work platforms and delivery vehicles near the boundary are treated the same way.

Put all of it in a Construction Management Plan and share the draft with the asset protection team before submitting it to the council, because a plan approved by the authority but unacceptable to the infrastructure manager has to be redone. The same pattern applies to other safeguarding regimes, as discussed in Ministry of Defence safeguarding zones and explosives storage areas.

Agreements and asset protection processes

Three things run in parallel with the planning application, and each has a cost the developer bears.

1. An asset protection agreement covering the technical review, approval of method statements and site monitoring, with the infrastructure manager's costs recharged and an indemnity given by the developer.
2. A land or access agreement where any part of the works, including scaffolding, oversail or a service crossing, touches railway land.
3. Any separate consent for works to a structure in the infrastructure manager's ownership, such as a bridge parapet or a retaining wall.

Start the first of these when the planning application is submitted. The technical review is iterative, the engineers work to railway timescales rather than development ones, and approval may be tied to the availability of track possessions, which are booked months ahead.

One honest point: the requirements are demanding and the process is slow, and they exist because the consequence of getting it wrong is a derailment. Budget time rather than arguing.

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.