Grid & Compliance 5 min read
Permitting rarely appears on a project risk register until it is already the problem. It is not usually one long delay – it is several short ones arranged badly, so they add instead of overlapping.
The approvals typically involved
Depending on jurisdiction and project, some combination of:
- Building or planning permission. Many rooftop installations qualify as permitted development or equivalent, particularly where they do not materially alter appearance or exceed height limits. Confirm rather than assume.
- Structural approval. Sign-off that the building takes the load, usually requiring a qualified engineer's report.
- Electrical permit and inspection. Local authority or authorised inspector.
- Fire authority review. Access pathways, DC isolation, rapid shutdown provisions where required, marking and signage. More involved where storage is included.
- Grid connection approval. Separate from all the above, usually the longest.
- Environmental or heritage screening. Situational – listed buildings, conservation areas, protected sites.
Sequencing them to overlap
The frequent mistake is running these in series because each feels like a prerequisite for the next. Most are not.
What can start immediately, before detailed design:
- Grid connection application, once capacity and connection point are decided.
- Planning enquiry, to establish whether formal permission is needed at all.
- Structural survey – and this should be early anyway, since findings constrain the layout.
- Roof warranty enquiry with the membrane manufacturer.
What genuinely needs design first: electrical permit, fire review, and final structural sign-off against the specific mounting arrangement.
Running the first group in parallel with design typically removes two to four months from the programme, at no cost beyond organisation.
Fire authority requirements shape the layout
Worth early attention because the requirements affect array geometry, not just paperwork.
Typical provisions include clear access pathways across the roof, setbacks from roof edges and ridges, clearance around roof access points and smoke vents, marked DC isolation points, and rapid shutdown capability in jurisdictions that require it.
These consume roof area – sometimes 10-15% of what a naive layout would use. Designing the array first and applying setbacks afterwards means redesign and a revised yield model. Ask the fire authority for their requirements before layout, not after.
Storage raises the bar
Adding batteries brings additional review: separation distances, gas detection, ventilation, suppression, and often a specific request for UL 9540A test data or its regional equivalent.
Authorities vary widely in familiarity with storage. Some have well-established processes; others are reviewing their first commercial installation and will, reasonably, take longer and ask more. A pre-application meeting is worth considerably more here than for solar alone.
Practical measures that help
- Find out who reviews what, early. A single phone call establishing the actual approval path prevents submitting to the wrong body.
- Ask for the checklist. Most authorities have one. Submitting against it directly avoids the commonest rejection reason, which is incompleteness.
- Use a local contractor for the submission where possible. Familiarity with a particular authority's preferences is worth real time.
- Keep one register of all approvals with status, owner and expected date. Sounds bureaucratic; prevents the situation where everyone assumes someone else submitted something.
- Build float into the programme. If you have an incentive deadline or a tariff window, do not plan to hit it with zero margin. Approval timelines are estimates, not commitments.
None of this makes permitting fast. It stops it being slower than it needs to be, which is usually the achievable win.