You probably know that sinking feeling when you’re three months into a rail project and suddenly discover you need a protected species licence? The one that takes six months to get and can only be applied for during a specific survey season that ended two weeks ago?
Here’s the thing: around 70% of infrastructure projects still mishandle ecology surveys, leading to costly delays that could have been completely avoided. The problem isn’t the wildlife legislation under the Wildlife and Countryside Act 1981—it’s been around for decades.
The real issue is treating ecology as an afterthought instead of building it into your project from day one. Let’s fix that.
Here are the seven early ecology steps that’ll save your project timeline, budget, and sanity.
Step 1: Commission Your Preliminary Ecology Assessment (PEA) at Project Inception
Don’t wait until you’re ready to submit planning applications. The moment you have a rough project outline and site boundary, get your PEA sorted. This desktop study and initial site walkover will flag any ecological red flags early: whether that’s potential bat roosts in railway bridges, great crested newts in lineside ponds, or ancient woodland that’ll need careful handling.
A good PEA will tell you exactly what surveys you need and when you can do them. More importantly, it’ll tell you if there are any show-stoppers that might need a complete design rethink. Better to know now than when you’ve already committed to a timeline.
Step 2: Create Your Survey Calendar Before You Set Project Milestones
Here’s where most rail projects go wrong: assuming ecological surveys can happen year-round. They can’t.
- Bats are surveyed between May and September.
- Birds during March to August. Reptiles from April to October.
- Great crested newts? March to June, then September to October.
Print out an ecology survey calendar and stick it on your project office wall. Better yet, embed these constraints into your project management software. When you’re planning works near Network Rail infrastructure, you’re already working with possession windows and engineering restrictions: treat ecological survey seasons with the same respect.
Step 3: Budget Realistically (It’s Probably Less Than You Think)
Most teams massively overestimate survey costs while completely underestimating the cost of programme overruns. A comprehensive bat survey might cost £5,000. A six-month project delay? That’s easily £500,000+ in additional costs, not to mention the reputational damage.
Budget for the surveys you actually need based on your PEA findings. Don’t assume you need everything: a good ecologist will only recommend necessary surveys. And remember, early surveys often reveal that mitigation is simpler than expected. That “complex bat problem” might just need some adjusted LED lighting specifications.
Step 4: Integrate Ecology Into Your Critical Path
Stop treating ecology as a box-ticking exercise for planning submissions. Make it a critical path activity from the start. This means:
- PEA completed before detailed design begins
- All necessary surveys scheduled within appropriate survey windows
- Ecological reports finished in time for your design team to incorporate findings
- Protected species licence applications submitted as soon as surveys confirm the need
When ecology sits on your critical path, it gets the attention and resources it deserves. When it’s treated as an afterthought, it becomes the thing that derails your whole programme.
Step 5: Plan Your Site Access Strategy Early
Rail projects often involve complex access arrangements: especially when working near operational railways. Your ecological surveys need the same access your construction teams will eventually need. That bat survey of a Victorian railway bridge isn’t much use if the ecologist can’t actually access the structure safely.
Coordinate with Network Rail early about survey access requirements. Factor in the time needed for RISQS registration, PTS training, and arranging appropriate supervision. The last thing you want is survey seasons passing by while you’re still sorting access permissions.
Step 6: Build Relationships With Local Ecological Networks
Every rail corridor has its local ecological context: resident bat colonies, established badger territories, or rare plants that pop up in specific locations. Building relationships with local ecological groups, county ecologists, and wildlife trusts can provide invaluable intelligence about what you’re likely to encounter.
These relationships often pay dividends during the planning process, too. Local ecological groups can advocate for well-planned projects that demonstrate genuine environmental care, rather than oppose schemes that appear to ignore ecological considerations.
Step 7: Plan Your Mitigation Strategy Alongside Your Design
Don’t design your scheme in isolation then figure out mitigation later. The best rail projects integrate ecological considerations into the design from the start. This might mean:
- Positioning new structures to avoid important habitats
- Scheduling works outside sensitive periods
- Incorporating habitat creation into earthworks designs
- Planning temporary habitat provisions during construction
This integrated approach often delivers better outcomes for both ecology and project delivery. It’s much easier to design around a badger sett than to relocate one later. Smart design choices early can eliminate the need for expensive mitigation measures down the line.
Why Projects Still Get This Wrong
Despite established processes, the same patterns keep causing delays. Teams dismiss ecology as “just box-ticking” rather than recognising it as a genuine risk to programme delivery. Others take a reactive approach, only addressing ecology when planning officers flag issues: by which point the project is already behind schedule.
There’s also a persistent myth that environmental protection automatically equals project delays. The reality is that most delays attributed to wildlife protection are actually the result of poor project planning. When you integrate ecology properly from the beginning, it becomes a managed process rather than a last-minute crisis.
The Bottom Line
Ecological considerations don’t have to be project killers. When handled proactively, they become just another element of good project management: like managing utility diversions or coordinating with other infrastructure operators.
The secret is treating ecology as a critical path activity from day one, not something to worry about when you’re ready to submit planning applications. Get your PEA commissioned early, respect survey timing constraints, budget realistically, and integrate findings into your design process.
Most importantly, remember that the cost of getting ecology wrong: six-month delays, redesign work, emergency mitigation measures: far outweighs the cost of getting it right from the start.
Your future self, staring at a project that’s on time and on budget, will thank you for taking these seven steps seriously.
About the Author
Scott Latham is a Principal Ecologist and Full Member of CIEEM with over 15 years of experience delivering ecological solutions for infrastructure and development projects across the UK and internationally. He holds a Master’s in Environmental Science and a CL18 Bat License from Natural England.
At RSS Infrastructure, Scott leads ecological strategy and project delivery, working closely with engineering teams and clients to integrate ecology into rail and infrastructure schemes from day one. His experience includes managing complex ecological compliance for Network Rail projects, protected species licensing, and establishing survey strategies that keep projects on track.
Previously, Scott served as SAC Project Officer for Cannock Chase AONB, collaborating with local authorities on biodiversity planning and habitat protection—experience that informs his practical approach to balancing infrastructure delivery with environmental obligations.
Need help getting your ecology planning right from the start? Our team understands the complexities of rail infrastructure projects and Network Rail requirements. Drop me a line at scott.latham@rssinfrastructure.com to discuss the most appropriate early ecology steps and let’s make sure your next project stays on schedule.
