Site Analysis Report
Every expensive design change traces back to something about the site that was known but not looked at. Ground conditions, a right of way, a sewer easement, the neighbour's window. This is the systematic sweep before a line is drawn: what is there, what is allowed, what the site can hold, and which unknowns are worth paying to resolve now rather than at foundation stage.
What This Skill Produces
- Physical survey summary — topography, boundaries, existing structures, trees, ground conditions, and services
- A constraints and opportunities read — each constraint with its design consequence, and the aspects worth exploiting
- The statutory and legal position — planning designations, rights of way, easements, covenants, and party wall exposure
- Developable-capacity estimate — what the site could plausibly take, with the assumptions stated
- Orientation and environmental analysis — sun path, prevailing wind, noise sources, flood and drainage
- The risk register — the unknowns, what each could cost, and which are worth investigating before design
Required Inputs
Ask for these if not provided:
- The site — address, boundaries, area, and current use
- What surveys exist — topographical, measured building, arboricultural, ground investigation, drainage, asbestos
- The title information — registered title, easements, covenants, and rights of way if known
- The proposal, if there is one — what the client hopes to build, so capacity can be tested against it
- Local context — planning designations, neighbouring uses, access, and known local sensitivities
Framework: What Is There, What Is Allowed, What It Can Hold
- Separate the physical from the legal. A site can be perfectly buildable and legally constrained, or the reverse. Confusing the two produces schemes that die late.
- Walk the boundaries against the title plan. Fences and titles disagree more often than anyone expects, and the discrepancy is cheapest to find now.
- Find the buried constraints. Sewers, easements, and services crossing the site remove development area without appearing on any drawing.
- Convert every constraint into a design consequence. 'Protected tree' is a note; 'no foundations within 8 m of the northern boundary' is a constraint that shapes the plan.
- Test capacity with stated assumptions. A capacity figure without its assumptions is a number that will be quoted back at you.
- Price the unknowns. For each, what it might cost to be wrong, and what an investigation costs. Some are worth resolving now; say which.
Output Format
Site analysis: [address] · [date] · [prepared by]
Site: [address, area, current use, boundaries] · Surveys relied on: [list with dates, and what is missing]
Physical
| Aspect |
Finding |
Design consequence |
| Topography |
[levels, falls] |
[implication] |
| Ground conditions |
[what is known/assumed] |
[foundation implication] |
| Trees |
[species, protection status] |
[root protection area, exclusion zone] |
| Existing structures |
[condition, retention or demolition] |
[implication] |
| Services |
[what crosses the site, capacity] |
[diversion or easement implication] |
| Drainage |
[existing, outfall, flood zone] |
[strategy implication] |
Environmental: orientation and sun path [summary] · prevailing wind [direction] · noise sources [what and where] · overlooking [from where]
Statutory & legal: planning designations [list] · rights of way [where] · easements [what and where] · covenants [effect] · party wall exposure [which boundaries] · verification needed: [what a solicitor must confirm]
Developable capacity: [estimate] — assuming [the assumptions: setbacks, height, parking, amenity space]
Opportunities: [aspects worth exploiting — aspect, level change, existing structure, frontage]
Risk register
| Unknown |
If wrong, could cost |
Investigation cost |
Resolve before design? |
An appraisal framework, not a substitute for professional surveys or legal advice. Title, easements, covenants and rights of way must be confirmed by a solicitor; ground conditions, trees, drainage, and contamination require qualified survey. Planning designations must be checked against the authority's current records.
Quality Checks
Anti-Patterns
- Analysing from drawings alone. The site does not match the drawing, and the difference is the finding.
- Listing constraints without consequences. A list nobody can design from.
- Assuming the title matches the fence. A common and expensive error.
- A capacity figure with no assumptions. It will be quoted as a promise.
- Ignoring what has not been surveyed. Silence reads as 'no issue' and becomes a claim.
- Treating trees as a planning formality. Root protection areas remove real, unbuildable area.
Example Trigger Phrases
- "Carry out a site analysis for this plot"
- "Can this site take a four-unit scheme?"
- "What should I check before designing on this site?"
- "Write a feasibility appraisal for a backland site"
- "What are the constraints on this site?"
1---2name: site-analysis-report3description: Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building. Use when asked to carry out a site analysis, site appraisal, feasibility study for a plot, or to assess whether a site can take a proposed development. Produces the physical survey summary, the constraints and opportunities map, the statutory and legal position, the developable-capacity estimate, and the risks that need resolving before design starts.4---5
6# Site Analysis Report
7
8Every expensive design change traces back to something about the site that was known but not looked at. Ground conditions, a right of way, a sewer easement, the neighbour's window. This is the systematic sweep before a line is drawn: what is there, what is allowed, what the site can hold, and which unknowns are worth paying to resolve now rather than at foundation stage.
9
10## What This Skill Produces
11
12- **Physical survey summary** — topography, boundaries, existing structures, trees, ground conditions, and services
13- **A constraints and opportunities read** — each constraint with its design consequence, and the aspects worth exploiting
14- **The statutory and legal position** — planning designations, rights of way, easements, covenants, and party wall exposure
15- **Developable-capacity estimate** — what the site could plausibly take, with the assumptions stated
16- **Orientation and environmental analysis** — sun path, prevailing wind, noise sources, flood and drainage
17- **The risk register** — the unknowns, what each could cost, and which are worth investigating before design
18
19## Required Inputs
20
21Ask for these if not provided:
22- **The site** — address, boundaries, area, and current use
23- **What surveys exist** — topographical, measured building, arboricultural, ground investigation, drainage, asbestos
24- **The title information** — registered title, easements, covenants, and rights of way if known
25- **The proposal, if there is one** — what the client hopes to build, so capacity can be tested against it
26- **Local context** — planning designations, neighbouring uses, access, and known local sensitivities
27
28## Framework: What Is There, What Is Allowed, What It Can Hold
29
301. **Separate the physical from the legal.** A site can be perfectly buildable and legally constrained, or the reverse. Confusing the two produces schemes that die late.
312. **Walk the boundaries against the title plan.** Fences and titles disagree more often than anyone expects, and the discrepancy is cheapest to find now.
323. **Find the buried constraints.** Sewers, easements, and services crossing the site remove development area without appearing on any drawing.
334. **Convert every constraint into a design consequence.** 'Protected tree' is a note; 'no foundations within 8 m of the northern boundary' is a constraint that shapes the plan.
345. **Test capacity with stated assumptions.** A capacity figure without its assumptions is a number that will be quoted back at you.
356. **Price the unknowns.** For each, what it might cost to be wrong, and what an investigation costs. Some are worth resolving now; say which.
36
37## Output Format
38
39### Site analysis: [address] · [date] · [prepared by]
40
41**Site:** [address, area, current use, boundaries] · **Surveys relied on:** [list with dates, and what is missing]
42
43**Physical**
44| Aspect | Finding | Design consequence |
45|---|---|---|
46| Topography | [levels, falls] | [implication] |
47| Ground conditions | [what is known/assumed] | [foundation implication] |
48| Trees | [species, protection status] | [root protection area, exclusion zone] |
49| Existing structures | [condition, retention or demolition] | [implication] |
50| Services | [what crosses the site, capacity] | [diversion or easement implication] |
51| Drainage | [existing, outfall, flood zone] | [strategy implication] |
52
53**Environmental:** orientation and sun path [summary] · prevailing wind [direction] · noise sources [what and where] · overlooking [from where]
54
55**Statutory & legal:** planning designations [list] · rights of way [where] · easements [what and where] · covenants [effect] · party wall exposure [which boundaries] · **verification needed:** [what a solicitor must confirm]
56
57**Developable capacity:** [estimate] — assuming [the assumptions: setbacks, height, parking, amenity space]
58
59**Opportunities:** [aspects worth exploiting — aspect, level change, existing structure, frontage]
60
61**Risk register**
62| Unknown | If wrong, could cost | Investigation cost | Resolve before design? |
63|---|---|---|---|
64
65> An appraisal framework, not a substitute for professional surveys or legal advice. Title, easements, covenants and rights of way must be confirmed by a solicitor; ground conditions, trees, drainage, and contamination require qualified survey. Planning designations must be checked against the authority's current records.
66
67## Quality Checks
68- [ ] Physical and legal constraints are assessed separately
69- [ ] Boundaries were checked against the title plan, and discrepancies noted
70- [ ] Buried services and easements are identified or flagged as unverified
71- [ ] Every constraint states its design consequence, not just its existence
72- [ ] The capacity estimate lists the assumptions behind it
73- [ ] Unknowns are priced against the cost of investigating them
74- [ ] Missing surveys are named rather than silently assumed away
75
76## Anti-Patterns
77- **Analysing from drawings alone.** The site does not match the drawing, and the difference is the finding.
78- **Listing constraints without consequences.** A list nobody can design from.
79- **Assuming the title matches the fence.** A common and expensive error.
80- **A capacity figure with no assumptions.** It will be quoted as a promise.
81- **Ignoring what has not been surveyed.** Silence reads as 'no issue' and becomes a claim.
82- **Treating trees as a planning formality.** Root protection areas remove real, unbuildable area.
83
84## Example Trigger Phrases
85- "Carry out a site analysis for this plot"
86- "Can this site take a four-unit scheme?"
87- "What should I check before designing on this site?"
88- "Write a feasibility appraisal for a backland site"
89- "What are the constraints on this site?"