Refer developers, councils and communities onward and coordinate with other professionals and services.
TRIGGERS - Use when a town planner needs a referral & coordination for developers, councils and communities in planning departments and consultancy offices.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
Are you the author of Urban Planning Referral Coordination?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lionelsimai-urban-planning-referral-coordination)
---
name: urban-planning-referral-coordination
description: |
Refer developers, councils and communities onward and coordinate with other professionals and services.
TRIGGERS - Use when a town planner needs a referral & coordination for developers, councils and communities in planning departments and consultancy offices.
category: Urban Planning
license: MIT
version: 1.0
---
# Referral & Coordination — Urban Planning
Refer developers, councils and communities onward and coordinate with other professionals and services. The deliverable is a referral pack and a coordination log with responses tracked.
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 a referral pack and a coordination log with responses tracked.
- 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** - Confirm the referral is appropriate: what developers, councils and communities need that sits outside the town planner scope in planning departments and consultancy offices
2. **Step 2** - Prepare the referral from planning applications — relevant history, current status, the specific question being asked
3. **Step 3** - With consent, send the referral and log who received it and when; chase non-responses on a set schedule
4. **Step 4** - Share incoming findings back into the main record so the plan and application determination times stay joined up
5. **Step 5** - Close the loop with developers, councils and communities: explain what happens next, who owns it, and what to do if things worsen — mindful of missed consultation deadlines
## 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 a referral pack and a coordination log with responses tracked, 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.)