The signed job in a conservation area
A homeowner signs, pays a deposit, and the job is scheduled. The designer notices the street name sounds familiar. The house is in a conservation area and the panels are on the elevation facing the road. Nobody is sure what that means for this job. The install is put on hold while someone finds out, and the homeowner, who was told the install was in three weeks, is unhappy.
Why planning is checked late
- Surveyors and salespeople do not routinely check designations.
- Designation data is held by different bodies and councils, in different formats.
- Many jobs do not need planning, so it becomes an afterthought.
- Flat roofs, ground mounts and front-facing arrays raise different questions.
- There is no step in the sales process that forces a look.
Whether a particular job needs planning permission is for the homeowner, your team and the local planning authority. This is about noticing which jobs need a proper look.
What late surprises cost
Jobs on hold after deposit. Cancelled installs. Redesigns that change the price. Homeowners who feel they were not told. And, in the worst case, an install that should not have gone ahead as designed.
An address check at enquiry stage
- When an enquiry arrives, the address is checked against public designation data where available, such as conservation areas and listed buildings, using published datasets and APIs.
- The design details that matter are noted as they become known: roof elevation facing the road, flat roof, ground mount.
- Jobs where either raises a question are flagged in the CRM for a named person to look at before the quote.
- The person records what they found and what, if anything, the homeowner needs to do, and the quote reflects it.
- Flags carry through to scheduling, so a job cannot be booked with an open planning question.
Designation data is not complete everywhere, and a flag, or its absence, is not a planning decision. The check helps you notice; your team and the local authority decide.
What gets flagged
| Found | Flag |
|---|---|
| Address in a conservation area | Look before quote |
| Listed building | Look before quote |
| Front-facing array | Note for the person checking |
| Flat roof or ground mount | Note for the person checking |
| No designation found | No flag, data limits noted |
Fewer surprises after the deposit
Jobs that need a closer look are noticed at the start. Homeowners are told early what might be involved. Quotes reflect it. And schedules do not collapse because of something that could have been seen at enquiry.
Limits of the data, stated plainly
Public designation data is useful and incomplete. Coverage differs between areas, boundaries are not always precise, and some constraints are simply not published in a way a system can read. We would rather say that clearly than build something that gives a false sense of security.
So the check is built to notice, not to clear. A flag means a named person should look. No flag means nothing was found in the data available, and the check says so, which is different from saying no issue exists. Your team still applies its own judgement to unusual properties, such as flats, ground-mounted arrays and front elevations.
Most of the value comes from the timing. A question raised before the quote is a conversation. The same question raised after the deposit is a problem.
Has planning caught you out?
- You have found a designation after a job was sold.
- Planning is not part of your sales checklist.
- Jobs have been put on hold after deposit.
- Your team is unsure how to check designations quickly.