"The Computer Says" Won't Cut It at Examination
When you're at examination and the inspector asks how you've calculated the need for additional GP capacity arising from your strategic allocations, you can't just say "the software told us" and move on.
Planning inspectors - quite reasonably - want to understand your methodology. What assumptions have you made about household size? What patient list size per GP have you used? What catchment distances? Why those figures and not others?
This is where a lot of software falls down. They give you an answer, but they don't show you the working. It's a black box. You input your sites, you get a number out, and you're expected to trust it.
The problem is that "trust the algorithm" isn't a defensible position at examination. Nor should it be.
What Makes an IDP Methodology Defensible?
A defensible methodology needs three things:
- Transparency: You can see what assumptions are being made
- Justification: Those assumptions are based on recognised standards or local evidence
- Flexibility: You can adjust them where your local circumstances differ
Take school place planning as an example. A defensible methodology would show you:
- The pupil yield multiplier being used (e.g., 0.3 primary pupils per dwelling)
- Where that multiplier comes from (DfE guidance, your own education authority data, local evidence from recent developments)
- The capacity you're assuming per school (based on published admission numbers)
- The catchment areas being applied (statutory catchments, walking distances, actual patterns of attendance)
If the inspector queries any of those assumptions, you can explain them. If your local circumstances differ from national averages - say, you've got higher-than-typical pupil yields because you're building family housing - you can show you've adjusted for that.
The Importance of Local Calibration
No national methodology fits every local authority perfectly. Your housing mix might differ. Your infrastructure standards might be more or less generous. Your local circumstances might mean different assumptions are appropriate.
Being able to calibrate the methodology to your area - and document why you've made those adjustments - is what makes analysis defensible.
With Coplug, you can:
- Input your own multipliers based on local evidence
- Adjust catchment areas to match your specific geography
- Use your own capacity data rather than national averages
- Document why you've made those choices
The platform provides sensible defaults based on recognised guidance, but they're transparent defaults you can inspect and adjust.
What This Means in Practice
When you're writing your IDP or preparing for examination you can confidently state: "Primary school need has been assessed using a pupil yield of 0.28 per dwelling (based on our education authority's evidence from recent major developments), applied across statutory catchment areas, with capacity calculated from published admission numbers. Full methodology is set out in Appendix B."
The inspector can probe that methodology. You can explain it. You can justify the assumptions. That's defensible.
The Bottom Line
Planning evidence needs to be robust enough to withstand scrutiny at examination. That requires methodology you can actually explain and justify, not outputs from a black box you're expected to trust.
Coplug's infrastructure analysis is built around transparent, adjustable methodology. You can see how it works, you can calibrate it to your area, and you can defend it under questioning.
Because "the computer says so" has never been - and should never be - an acceptable answer in plan-making.
So How Does Coplug Handle This?
Every infrastructure analysis in Coplug shows its working - right there in the interface.
When you run primary school capacity analysis, you can see:
- The demand multiplier being applied (and change it if your local data suggests different)
- How catchments are defined (and adjust them to match your statutory boundaries)
- What capacity assumptions are being made (and override them with your actual PAN data)
- The calculation method (clearly explained, not hidden)
This isn't about making things complicated. It's about giving you control over the methodology so you can defend it.
It does for over 30 infrastructure types, built in, to make it easy for you to set up, maintain, access and run an analysis comparing scenarios.



