Bloxham Conservation Area Re-Appraisal

December 3, 2025 Executive Director Place & Regeneration (Officer) Approved View on council website

This summary is generated by AI from the council’s published record and supporting documents. Check the full council record and source link before relying on it.

Summary

... the revisions to the Bloxham Conservation Area boundary were approved, and the Bloxham Conservation Area Appraisal was adopted.

Full council record
Purpose

To consider the approval of the
Bloxham Conservation Area Appraisal 2025, following its
re-appraisal.

Content

Resolved:
 
(1)       
That the revisions to the Bloxham Conservation Area boundary be
approved and the Bloxham Conservation Area Appraisal be
adopted.

Reasons for the decision

The conservation area appraisal has been
reviewed and consulted upon. It is recommended that. It is
recommended that the Executive Director Place and Regeneration,
using delegation within the Office Scheme of Delegation (Part 3 of
the Constitution), approve the appraisal presented at Appendix 1.
This includes five proposed boundary changes.

Alternative options considered

The following
alternative options have been identified and rejected for the
reasons as set out below.

Option 1: To seek
further amendments to the conservation area appraisal.
Officers consider that
the reviewed conservation area appraisal and the proposed changes
to the conservation area boundary are in the best interests of
preserving the district’s built
heritage.
 
Option 2: Not to agree
the recommended amendments – would result in the conservation
area not being updated.
Officers consider that
an updated appraisal and conservation area boundary are in the best
interests of preserving the district’s
built heritage.

Supporting Documents

Bloxham Conservation Area Re-appraisal.pdf
Appendix 1 - Bloxham Conservation Area Appraisal.pdf
Appendix 2 - Bloxham Conservation Area Boundary.pdf
Appendix 3 - Table of consultation repsonses.pdf

Details

OutcomeRecommendations Approved
Decision date3 Dec 2025
Subject to call-inYes