Urban Planning Emergency Procedure

---
name: urban-planning-emergency-procedure
description: |
  Respond to emergencies in planning departments and consultancy offices calmly, in role and in the right order.
  TRIGGERS - Use when a town planner needs a emergency response procedure for developers, councils and communities in planning departments and consultancy offices.
category: Urban Planning
license: MIT
version: 1.0
---
# Emergency Response Procedure — Urban Planning

Respond to emergencies in planning departments and consultancy offices calmly, in role and in the right order. The deliverable is an emergency procedure card: recognition, first actions, escalation and recording.
This skill is written for a town planner working with developers, councils and communities in planning departments and consultancy offices.

## When to use
- You are a town planner preparing, delivering or reviewing this part of your work in planning departments and consultancy offices.
- You need a defensible, repeatable approach that produces an emergency procedure card: recognition, first actions, escalation and recording.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Local plan | the statutory document guiding development in an area |
| Determination | the formal decision on a planning application |
| Material consideration | a planning factor legally relevant to a decision |

## Workflow
1. **Step 1** - Recognise the emergency early: know the presentations that matter for developers, councils and communities, especially missed consultation deadlines
2. **Step 2** - Take the immediate actions a town planner is trained and authorised for, using GIS mapping as drilled
3. **Step 3** - Call for help with a structured message: location in planning departments and consultancy offices, situation, what has been done, what is needed
4. **Step 4** - Keep developers, councils and communities and bystanders informed and safe while help arrives; hand over with a concise summary
5. **Step 5** - Record the event fully in planning applications afterwards, debrief the team, and update the procedure with lessons learned

## Profession-Specific Components
| Component | Details for Urban Planning |
|-----------|-------------------------------|
| Core documentation | planning applications; policy documents; site appraisals; consultation reports |
| Core tools & equipment | GIS mapping; planning portals; modelling software; consultation platforms |
| People involved | developers, councils and communities; the town planner; colleagues and other services in planning departments and consultancy offices |
| Primary record | planning applications — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in planning departments and consultancy offices] | **Objective:** [What this must achieve] | **Audience:** [developers, councils and communities and other stakeholders]

The finished output is an emergency procedure card: recognition, first actions, escalation and recording, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in planning applications.
2. **Short-term:** Complete the workflow steps and record outcomes against application determination times.
3. **Medium-term:** Review results, close actions, and update local procedures in planning departments and consultancy offices.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| application determination times | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |
| appeal outcomes | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |
| consultation engagement | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |
| policy adoption | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: missed consultation deadlines.
- Never let this happen: policy conflicts.
- Never let this happen: appeals lost on process.
- Work only within the competence and authority of a town planner; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to planning departments and consultancy offices's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A town planner in planning departments and consultancy offices applies this workflow for developers, councils and communities: they open
planning applications, work through the five steps using GIS mapping, and close by recording
the outcome against application determination times and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)