London
Richmond upon Thames anchors the Petersham & Ham reference point; Kingston upon Thames is the second authority found within 1,400 metres. Nearby conservation records include Petersham, Ham Common, Ham House, Parkleys Estate Ham and Richmond Park, as well as several Teddington and Twickenham entries. Those names provide a rich boundary screen but cannot classify a particular address. Richmond is the confirmed starting authority; Kingston is nearby context. The property must be plotted before any Petersham, Ham or park-setting consequence is attached to an architectural proposal.
Last updated
Practice leadership
Eyal Moran, Director and Lead Architect, is an ARB-registered architect, leading design judgement, planning strategy and technical coordination across client projects.
Verify on the Architects RegisterPlanning at a glance
Petersham & Ham
| Local planning authority | Confirm for the exact property address; the neighbourhood research point is not an address result |
|---|---|
| Likely approval route | Confirm from the exact address, property type, ownership, designation and proposed work before drawings begin |
| Statutory determination time | 8 weeks for most householder applications (13 weeks for major applications) |
| Typical drawing package | £395–£4,950 inc. VAT, fixed fee. Find my package → |
A Petersham and Ham design should follow Richmond’s live boundary result. If the property is confirmed within or affecting Petersham, Ham Common, Ham House or Parkleys Estate Ham, externally visible work may need drawings that explain its scale, roof, openings and material relationship to that specific context. Richmond Park should be referenced only where the site evidence supports a setting connection. A nearby Kingston record likewise needs an actual boundary reason. Without those links, the proposal should not be burdened with conservation narratives drawn from the wider search list.
Technical scoping for Petersham and Ham should record the authority point, designation check and measured existing condition together. Elevations, roof geometry, boundaries and levels can then be assessed against the applicable Richmond record, whether Petersham, Ham Common or another returned area. If Kingston is merely nearby, its source material should be excluded from the drawing basis. Accurate mapping is especially important because several conservation names overlap in ordinary language. The file should make clear which official boundary informed each external design choice and which similarly named records did not.
Local analysis
The ampersand in Petersham & Ham joins two locality names, not two planning jurisdictions. Richmond upon Thames is returned at the checked point, while Kingston upon Thames appears only within the surrounding 1,400 metres.
For a new commission, the decisive fact is the site’s actual authority position; Kingston should not enter correspondence, programme or design justification unless that position or a specific proposal relationship supports it. This matters architecturally because guidance attributed to the wrong borough can distort the stated rationale even when the drawings themselves are unchanged. Keep the route conditional until the address is verified.
Fifteen distinct conservation records were returned for Petersham & Ham, and every one is sourced to Richmond upon Thames even though Kingston appears in the authority radius. The locally named entries are CA6 Petersham, CA7 Ham Common, CA23 Ham House and CA67 Parkleys Estate Ham; CA62 Richmond Park and several Teddington or Twickenham records broaden the screen.
These titles are not interchangeable descriptions of one protected landscape. Any architectural claim should name the exact confirmed record and code, while the other entries remain unassigned proximity results. Nothing in the list establishes the property’s history, fabric or designation.
Local evidence
Code accuracy is especially useful on Petersham & Ham drawings because several familiar place names sit close together in the source. A site plan referring to CA6 Petersham must not silently become CA7 Ham Common, while CA23 Ham House and CA67 Parkleys Estate Ham require their own mapped justification.
If one relationship is established, show the proposal’s relevant elevation, section or context view and label that record exactly. A Kingston authority inset or a Teddington conservation note would be misleading without separate site evidence. The measured architectural information should remain complete even when no returned designation applies.
Useful local facts
A Petersham and Ham homeowner should provide the exact address and identify every external part of the proposal. We would verify Richmond, inspect the nearby Kingston boundary, and compare the site with Petersham, Ham Common, Ham House, Parkleys Estate Ham and Richmond Park.
The initial note would say which designation or setting is supported and which returned names are unrelated. That disciplined check gives the design team local precision without assuming that the presence of “Ham” in several conservation records makes them all applicable.
Local process
The Petersham and Ham delivery sequence should begin with a record-by-record map review, not with a generic heritage concept. Confirm Richmond, test the Kingston edge, and classify Petersham, Ham Common, Ham House, Parkleys Estate Ham and Richmond Park for relevance.
Develop and submit the design against the selected source only. Later technical information should maintain accepted external principles while resolving construction details. This produces a transparent evidence chain and avoids attributing requirements from a nearby Teddington, Twickenham or riverside record that has no demonstrated relationship to the property.
Decision checklist
Petersham & Ham presents a classification problem rather than a simple count problem. A property could be unrelated to all fifteen returned records, and the four names containing Petersham or Ham do not deserve priority merely through wording.
Feasibility should therefore identify which option-sensitive question exists—authority, direct boundary coverage or a particular setting relationship—and commission only the evidence needed to answer it. Where Richmond upon Thames is confirmed, Kingston proximity does not create a second consent route. The chosen design rationale should cite one established context, or state that the official screen produced no applicable conservation relationship.
Thinking about a project in Petersham & Ham?
Send the address and a short description. We will confirm the likely approval route and the drawings your project needs.
Local planning
The Petersham and Ham dataset contains several closely named Richmond records that must remain distinct. Petersham, Ham Common, Ham House and Parkleys Estate Ham are separate mapped entries, not interchangeable shorthand for the locality. Richmond Park and Riverside North add other possible setting questions, while nearby Kingston explains why an authority-edge check is prudent. A reliable interpretation should identify one relevant source for the exact site and mark the rest as proximity findings. This prevents a design statement from claiming multiple designations simply because their names all contain Ham or sit nearby.
Services
Architecture & Design
Extensions & Renovations
Planning & Consents
Heritage & Conservation
Technical & Building Regulations
Leasehold & Licence to Alter
Project Delivery & Support
For services without a dedicated Petersham & Ham page, use the London-wide overview to understand the scope, deliverables and next steps.
Architecture & Design
Interior Design
Extensions & Renovations
Planning & Consents
Heritage & Conservation
Leasehold & Licence to Alter
Project Delivery & Support
Nearby
Send the Petersham & Ham address, photographs and intended work. We will identify the authority, designation and building questions to resolve before a full design or technical package is commissioned.
