A city can have excellent plans and still make bad decisions.
The housing plan may call for 40,000 new homes around transit.
The transport plan may widen roads through those same districts.
The climate plan may call for more tree canopy.
The capital plan may fund a parking structure where the land-use plan expects a walkable centre.
The hazard plan may identify flood exposure where the growth strategy allocates the next major housing district.
Every document can be professionally prepared.
The system can still contradict itself.
This is the problem of plan integration.
The American Planning Association’s Plan Integration for Resilience Scorecard—PIRS—was developed to help communities examine whether their network of plans, policies and regulations reinforce or undermine resilience. APA’s current PIRS resources emphasise spatial comparison across multiple plans, identification of policy conflicts and the targeting of mitigation toward vulnerable places. APA’s current homepage still highlights the question “Do Planners Know Plan Integration Can Improve Local Resilience?” as a widely read issue because the challenge has become more pressing as cities accumulate separate climate, housing, mobility, hazard and capital plans.
UN-Habitat’s September 2026 housing work arrives at the same problem from another direction. Its current integrated housing-policy recommendations describe four dimensions of integration:
- horizontal—across policy sectors;
- vertical—across levels of government;
- spatial—linking housing to services, infrastructure and opportunity;
- temporal—connecting policy across time.
That framework is useful far beyond housing.
The reader job is therefore:
How can a city test whether its plans actually work together spatially, institutionally and over time—rather than simply declaring every new plan “consistent” with the others?
This article owns that question.
It does not replace eduKateSG’s existing Plan Stack, Concurrency Test, Housing Needs Assessment, transport, hazard, infrastructure or climate owners. It examines the links between them.
1. A city does not have one plan
Even a medium-size jurisdiction may have:
- comprehensive plan;
- local plan;
- housing strategy;
- transport plan;
- parks plan;
- school plan;
- climate plan;
- hazard mitigation plan;
- capital improvement programme;
- economic strategy;
- utility master plans.
Each may be valid.
Together they form a planning network.
The city is governed by the network, not by one document in isolation.
2. The first integration problem is vocabulary
One plan says “urban centre.” Another says “activity node.” Another says “growth hub.”
Do they refer to the same place?
Different departments often build their own terminology.
Plan integration begins by creating a crosswalk.
A shared spatial language reduces accidental contradiction.
3. Geography should be standardised
Plans may use neighbourhoods, catchments, census units, transport zones and hazard zones.
Overlaying them can be difficult.
Create common geospatial reference layers.
Integration becomes much easier when every plan can be compared on the same map.
4. The Plan Stack is not the same as plan integration
The existing TPW Plan Stack explains hierarchy: strategic plan, master plan, local plan and development control.
Plan integration asks a different question:
Do plans at similar or different levels reinforce one another?
A hierarchy can still contain contradictions.
5. Horizontal integration links sectors
Housing needs transport, schools and water.
A transport plan can support or undermine housing.
A parks plan can support climate resilience.
Horizontal integration asks:
Are sector plans working toward compatible outcomes?
This is often where cities fail.
Departments optimise their own system.
The city experiences the combination.
6. Vertical integration links levels of government
National policy may call for housing growth.
Regional government may control transit.
Local government may control zoning.
If each level acts independently, implementation breaks.
UN-Habitat’s 2026 framework explicitly identifies vertical integration as one of the four major dimensions of housing policy.
Planning needs this same discipline.
7. Spatial integration asks whether policies line up on the map
A policy can be reasonable in abstract and contradictory spatially.
Housing plan: intensify District A.
Flood plan: District A faces extreme future flood risk.
Transport plan: new transit in District B.
The conflict becomes obvious only on the map.
This is why spatial integration is powerful.
8. Temporal integration asks whether timing is aligned
Housing may be planned for 2030.
Sewer upgrade may be scheduled for 2040.
The plans are spatially consistent.
They are temporally inconsistent.
Time is a planning layer.
A Plan Integration Scorecard should record not only where policies apply but when they are expected to take effect.
9. Start with a plan inventory
Create a table of plan, owner, adoption date, horizon, geography and key implementation tools.
This simple inventory often reveals outdated plans, overlapping plans and missing ownership.
You cannot integrate a planning network you have not inventoried.
10. Include regulations, not only plans
Zoning may contradict the comprehensive plan.
A stormwater code may undermine infill.
A parking requirement may contradict climate goals.
APA’s PIRS framework includes plans and policy tools because implementation occurs through regulation.
A plan network without the code network is incomplete.
11. Include budgets and capital programmes
The capital budget may be the strongest implementation plan in the city.
If the comprehensive plan says “grow east” but capital spending builds roads and utilities west, the budget is implementing a different city.
Plan integration should include the capital improvement programme and major infrastructure budgets.
Money reveals priorities.
12. Include agency operating programmes where they shape land
Schools, utilities and transit agencies may not call their documents “plans.”
Their investment programmes can reshape urban growth.
A scorecard should include the documents that materially affect spatial outcomes.
Do not let institutional labels decide relevance.
13. The first score is policy direction
For each planning action in a place, ask whether it reduces, increases or remains neutral toward the chosen objective.
For resilience, APA’s PIRS method scores policies according to whether they reduce or increase vulnerability.
The same structure can be adapted to housing access, emissions and infrastructure efficiency.
14. A scorecard forces vague policies to become testable
“Support sustainable growth” is difficult to score.
“Direct 70% of new housing to transit-served centres” is clearer.
Integration analysis therefore reveals weak plan language.
A policy that cannot be mapped or measured may be difficult to implement.
15. Spatial scoring reveals concentration
Suppose five plans all direct public investment to the same low-risk neighbourhood.
Another vulnerable neighbourhood receives little.
The city may unintentionally deepen inequality.
Spatial scorecards show where policy support accumulates—and where it does not.
16. Integration is not the same as making every plan identical
Transport has different responsibilities from housing.
The goal is compatible direction.
A freight plan may need industrial truck routes.
A neighbourhood plan may seek walkability.
Integration means designing the interface rather than erasing freight.
Different systems can coexist.
17. Contradiction should be classified
Useful categories include direct contradiction, timing contradiction, metric contradiction, institutional contradiction and budget contradiction.
Classification helps select the remedy.
18. A contradiction log can be more useful than a long narrative
For each conflict, record plans involved, location, policy statements, risk, responsible agencies and resolution action.
This becomes a management tool.
Integration should produce tasks, not only observations.
19. Housing and transport are a classic integration pair
Housing plan: more homes around transit.
Transport plan: more road capacity based on suburban congestion standards.
The road standard can make transit-oriented housing harder.
APA’s 2026 smart-growth work specifically warns that context-insensitive level-of-service standards can undermine infill and housing.
Integration analysis surfaces the mismatch.
20. Housing and hazard planning are another
A city may allocate growth to cheap land.
That land may face flood, wildfire or heat.
The housing plan may solve affordability by creating climate vulnerability.
The hazard layer should enter before land allocation.
This is spatial integration.
21. Housing and school planning need timing alignment
Family housing increases.
Schools fill.
Opposition to future housing rises.
If school capacity planning lags, the housing plan loses political and practical viability.
School investment should follow realistic household forecasts.
22. Housing and sewer planning are inseparable
Zoning can allow density.
Sewer may not.
The TPW Sewer Capacity Map owns that infrastructure system.
Plan integration ensures the housing strategy uses its real capacity data.
23. Housing and parks plans can conflict through land competition
A redevelopment district may need homes and open space.
One plan protects a parcel for park.
Another counts it for housing yield.
The conflict should be resolved explicitly.
Do not let both plans count the same land differently.
24. Climate and transport plans can contradict each other
Climate plan: reduce vehicle kilometres.
Transport plan: widen roads.
Sometimes widening is necessary for buses or freight.
The plan should explain how the investment fits the climate objective.
Integration demands explanation rather than automatic consistency language.
25. Tree-canopy plans can conflict with utility plans
Tree canopy needs root space.
Utility corridors need clear access.
The same verge may be allocated to both.
A cross-section can resolve the conflict.
Plan integration often becomes design coordination.
26. Flood plans can conflict with public-realm plans
A waterfront plaza may be designed for daily use.
Flood infrastructure may require walls.
Integrated design can use raised edges or deployable barriers.
Separate plans can produce poor urban form.
Integration creates multi-functional infrastructure.
27. Economic-development plans can conflict with housing
A city may protect industrial land.
Housing demand may pressure that land.
The answer is not always conversion.
Plan integration should identify strategic industry and suitable transition areas.
This protects jobs and housing by making trade-offs explicit.
28. Freight planning must be included
Warehouses and logistics support the economy.
They also create truck and air-quality impacts.
Plan integration ensures freight and environmental justice are not separate conversations.
29. Capital plans should be scored against adopted spatial strategy
Map major spending:
- roads;
- sewers;
- schools;
- parks.
Then compare with growth areas and hazard zones.
If the money repeatedly goes elsewhere, either the plan or budget must change.
30. Maintenance budgets matter too
A city can build new infrastructure while existing neighbourhoods deteriorate.
The TPW Maintenance Ledger owner covers asset management.
Plan integration should ask whether capital growth and maintenance priorities are balanced.
31. Resilience requires redundancy across plans
Hazard plan may call for backup water.
Capital plan may not fund it.
Emergency plan assumes it exists.
This is a dangerous institutional gap.
Integration should trace critical assumptions.
32. Assumption mapping is a powerful technique
For each plan, list assumptions.
Housing plan: sewer available.
Transport plan: population forecast.
Climate plan: tree survival.
Then test whether another agency actually supports the assumption.
Many contradictions hide in assumptions, not policies.
33. Forecasts should use a shared baseline
Different plans may use different population forecasts.
Then every capacity conclusion differs.
Create a common baseline for population, jobs and households.
Allow scenario variation where needed.
The city should know when forecasts diverge deliberately.
34. Scenario planning can integrate uncertainty
One fixed future encourages siloed certainty.
Use shared scenarios: high growth, low growth and high climate stress.
Then test plans together.
World Bank planning tools increasingly use scenario approaches to explore growth and infrastructure.
Integration is easier when departments plan for the same plausible futures.
35. Digital twins can support integration—but are not integration themselves
APA’s 2026 smart-growth discussion mentions digital twins and scenario tools as useful decision support.
A digital twin can visualise growth and infrastructure.
If departments still use incompatible assumptions, the model only digitises contradiction.
Governance comes first.
Technology follows.
36. The integration team needs authority
A cross-department working group can identify conflicts.
Who resolves them?
Options include a chief planner, city manager or interagency committee.
Integration without decision authority becomes a discussion club.
Governance structure matters.
37. One department should own the integration register
Plans belong to many departments.
The contradiction log needs one custodian.
Planning is often a logical owner because it spans spatial policy.
The custodian does not control every department.
It keeps the shared system visible.
38. Every new plan should pass an integration check
Before adoption, compare with existing plans, identify conflicts and state resolutions.
This is better than waiting for contradictions to accumulate.
Integration becomes a routine quality-control step.
39. Plan amendments should trigger the same check
A zoning or plan amendment can create new conflict.
Digital systems can flag affected policies.
The planning system should update the network when one node changes.
40. Comprehensive plan updates are opportunities to reconcile
A major plan update can retire outdated strategies, align terminology and reset forecasts.
Do not merely add another document.
Use the update to simplify the planning network.
41. Outdated plans should be retired formally
A 2008 bicycle plan may still sit online.
Staff may not know whether it is active.
Maintain current and superseded status.
Institutional memory needs version control.
42. The public should know which plan controls
Conflicting plans confuse applicants and residents.
A plan register can state hierarchy, status and adoption date.
This makes the planning system legible.
43. Integration can improve public participation
Residents often hear separate consultations for transport, housing and climate.
They repeat the same issues.
Integrated engagement can show trade-offs.
This reduces consultation fatigue.
44. But integrated engagement should not become one giant meeting
Complexity can overwhelm people.
Use a common baseline with separate focused sessions.
Integration means connected decisions, not collapsing every topic into one workshop.
45. Equity should be a scorecard dimension
Policy support may cluster in wealthy areas.
Burdens may cluster elsewhere.
Plan integration can include who benefits and who bears cost.
Spatial scoring makes distribution visible.
46. Heat provides a strong example
APA’s PIRS for Heat maps heat risk and plan policies.
Then it asks whether mitigation policies target high-risk locations.
A tree policy is more valuable where heat exposure is high.
Integration therefore connects policy intensity to vulnerability.
47. Flood resilience can use the same method
Map future flood, housing growth and capital projects.
Identify contradictions such as new housing inside high future risk or sewer upgrades in low-priority areas.
A scorecard can convert a broad resilience goal into spatial action.
48. Wildfire planning also benefits
The WUI system may call for lower growth in one corridor.
Housing plan may rely on it.
The contradiction should be resolved before permits arrive.
Plan integration moves conflict upstream.
49. Public health can be another layer
Healthy-city plans may call for walking and clean air.
Freight or road plans may increase exposure.
Integration makes health outcomes a shared planning consideration.
50. The scorecard should not become a single composite score too early
A city may be tempted to publish an Integration score: 82/100.
That hides detail.
Better outputs include conflict maps and policy matrices.
A composite score can support communication.
It should not replace diagnosis.
51. Weighting requires transparency
If climate is weighted twice as heavily as transport, explain why.
Weights are policy choices.
The model should not disguise them as mathematics.
52. Qualitative contradictions matter
Not every conflict can be quantified.
One plan may promote heritage conservation while another promotes tower redevelopment.
Professional judgment is necessary.
A scorecard supports thinking.
It does not eliminate planning judgment.
53. Integration should identify synergies, not only conflicts
A school site can provide park space.
A drainage corridor can provide biodiversity and recreation.
A transit investment can support housing and emissions reduction.
Synergy mapping helps government invest once for several goals.
54. Multi-benefit projects should receive strategic priority
Public budgets are constrained.
Projects delivering transport, housing and resilience may offer higher public value.
Plan integration can inform capital prioritisation.
55. Implementation responsibility should be attached to each resolution
Conflict identified: housing growth ahead of sewer.
Resolution: advance sewer project.
Owner: utility department.
Deadline: 2029.
Without owner and date, integration remains aspirational.
56. The scorecard should update after capital budget adoption
Budget decisions can create new inconsistencies.
Annual review can compare adopted spending and spatial plan.
This creates continuous accountability.
57. Key indicators should be shared across plans
Housing near transit can serve housing, climate and transport.
Use one agreed indicator rather than three versions.
Shared metrics strengthen coordination.
58. A city should maintain an assumptions register
Fields can include population, job growth, hazard horizon and climate scenario.
Every plan states which assumption set it uses.
This reduces accidental inconsistency.
59. Integration can reduce duplicated studies
Housing plan commissions a population forecast.
Transport plan commissions another.
Waste of money.
A shared baseline saves resources.
Planning integration is also administrative efficiency.
60. Agencies should retain specialised models where necessary
Transport needs detailed travel models.
Water utilities need hydraulic models.
Shared baseline does not mean one model for everything.
Integration happens through common inputs and exchanged outputs.
61. The city should decide how conflicts are resolved
Possible rules include higher-order plan controls, newer plan controls or explicit council decision.
Do not leave staff to improvise.
A conflict-resolution protocol improves legitimacy.
62. Legal consistency requirements vary by jurisdiction
Some planning systems require zoning to be consistent with comprehensive plans.
Others use plans as guidance.
The management principle remains: the city should know when its policies point in different directions.
63. Inter-municipal integration matters in metropolitan areas
Housing in one municipality can depend on transit in another.
Flood waters cross boundaries.
Regional agencies may control roads.
Plan integration should sometimes extend beyond the city.
The institutional network must match the urban system.
64. National housing policy can support local integration
UN-Habitat’s 2026 integrated housing work stresses national frameworks connecting land, infrastructure, finance and local delivery.
This can reduce fragmented programmes.
Vertical integration is especially important where local governments lack finance.
65. Donor-funded plans should be integrated too
Cities can accumulate externally funded strategies.
A donor project may produce a climate plan.
If it is not linked to capital budgeting, it can sit separately.
Plan integration should include external programmes.
Ownership matters more than who paid for the report.
66. Private utility plans can matter
Electricity or telecom infrastructure may be controlled privately.
Their investments still shape growth.
Where possible, strategic planning should coordinate.
The city cannot integrate what it never discusses.
67. Major institutions should enter area planning
Universities, hospitals and ports can reshape districts.
Plan integration may include these quasi-public systems where impacts are large.
This does not make private plans municipal law.
It improves coordination.
68. A worked example: transit corridor
Housing plan: 20,000 homes.
Transport plan: new rail.
Capital plan: sewer delayed.
School plan: no new capacity.
Integration result: growth cannot arrive on schedule.
Action: reorder capital programme.
The scorecard turns contradiction into a sequencing decision.
69. A worked example: floodplain redevelopment
Economic plan: waterfront jobs.
Housing plan: mixed-use neighbourhood.
Flood plan: future extreme flood.
Integration result: development must incorporate resilience or shift.
The plans can be reconciled through design and land allocation.
70. A worked example: industrial district
Housing plan:
- conversion to apartments.
Freight plan:
- preserve logistics hub.
Environmental justice map:
- high truck burden nearby.
Integration result:
- segment the district.
Protect strategic logistics in one area.
Transition another.
Add clean-freight standards.
This is better than one plan “winning.”
71. A worked example: heat-vulnerable neighbourhood
Parks plan:
- tree planting citywide.
Heat map:
- severe exposure in three neighbourhoods.
Integration result:
- prioritise canopy there.
Same total tree budget.
Better spatial targeting.
This is the logic behind PIRS for Heat.
72. The Plan Integration workflow
Step 1 — Inventory plans and regulations.
Step 2 — Standardise geography and terminology.
Step 3 — Extract spatial policies.
Step 4 — Record time horizon and assumptions.
Step 5 — Score policy direction.
Step 6 — Overlay policies and vulnerability.
Step 7 — Identify conflicts and synergies.
Step 8 — Classify conflict type.
Step 9 — Assign resolution owner and deadline.
Step 10 — Align capital programme.
Step 11 — Update annually.
73. A Plan Integration audit
Ask:
- Is every active plan inventoried?
- Are obsolete plans marked?
- Is plan hierarchy clear?
- Are common spatial units used?
- Are key terms cross-walked?
- Are regulations included?
- Is the capital programme included?
- Are agency plans included?
- Is there a shared population forecast?
- Are job and household forecasts compatible?
- Are hazard scenarios shared?
- Are policy assumptions documented?
- Are housing and transport aligned?
- Are housing and schools aligned?
- Are housing and sewer aligned?
- Are growth and hazard maps aligned?
- Are climate and capital plans aligned?
- Are freight and environmental justice aligned?
- Are timing conflicts identified?
- Are budget conflicts identified?
- Are institutional conflicts identified?
- Are synergies mapped?
- Are equity impacts mapped?
- Is a contradiction register maintained?
- Does every conflict have an owner?
- Does every resolution have a deadline?
- Are capital budgets reviewed annually?
- Are new plans required to pass an integration check?
- Are plan amendments screened?
- Does the public know which plan is current?
- Are regional agencies involved where necessary?
- Are shared indicators used?
74. The deepest test is whether the city can explain one place with one coherent story
Pick a neighbourhood.
Ask:
- How many homes?
- What transport?
- What hazards?
- What public investment?
- What climate action?
- What schools?
- What jobs?
If every department gives a different future, the city does not have an integrated plan.
It has a stack of documents.
75. Plan integration is the governance of consequences
Every plan creates consequences for another system.
Housing creates school demand.
Roads shape emissions.
Flood defences shape public realm.
Plan integration is the discipline of tracing those consequences before they become conflicts in the field.
That is why it is so powerful.
76. The strongest scorecard changes budgets and maps
A plan integration exercise that ends with “more coordination is needed” has failed.
The output should change capital timing, land allocation and policy language.
Integration must reach implementation.
77. The mature planning system does not seek perfect consistency
Cities contain real trade-offs.
Industry and housing.
Growth and habitat.
The goal is not to erase disagreement.
It is to make contradictions visible, deliberate and governable.
The Plan Integration Scorecard succeeds when the city stops discovering conflicts after concrete is poured and starts resolving them while they are still lines on different plans.
Sources and further reading
- American Planning Association, Plan Integration for Resilience Scorecard for Heat: https://www.planning.org/publications/document/9257652/
- American Planning Association, Building Resilience Through Plan Integration: https://www.planning.org/pas/memo/2021/jan/
- American Planning Association, Do Planners Know Plan Integration Can Improve Local Resilience?: https://www.planning.org/blog/9210104/do-planners-know-plan-integration-can-improve-local-resilience/
- American Planning Association, Are We Being Smart About Smart Growth?, 14 April 2026: https://www.planning.org/blog/9327277/are-we-being-smart-about-smart-growth/
- UN-Habitat, Housing experts advance integrated approaches to adequate housing, 4 September 2026: https://unhabitat.org/news/04-sep-2026/housing-experts-advance-integrated-approaches-to-adequate-housing
- UN-Habitat, Strategic Plan 2026–2029: https://unhabitat.org/un-habitats-strategic-plan-2026-2029
- World Bank, Urban Planning and Land for Growth: https://www.worldbank.org/en/programs/tokyo-development-learning-center/tdd/tdd_on_urban_planning_and_land_for_growth
Continue reading: Strategic planning · Resilience · Full Town Planning Series Index.
78. Plan integration should distinguish shared objectives from shared instruments
Two departments can agree on the objective and still use incompatible tools.
Example:
Housing plan: support infill.
Transport plan: reduce congestion.
Both sound compatible.
If the transport plan uses a road level-of-service threshold that blocks infill, the instruments conflict.
Integration therefore has to examine goals, metrics and implementation rules.
Agreement at the slogan level is not enough.
79. Policy language should be classified by strength
Not every statement has equal force.
Mandatory: shall, must.
Directive: should, prioritise.
Aspirational: encourage, support.
A plan integration scorecard should record policy strength.
One weak aspiration should not be scored as equivalent to a funded mandatory programme.
80. Implementation mechanism should be recorded for every important policy
A plan says “increase affordable housing.” How?
Possible mechanisms include zoning, subsidy, public land and inclusionary policy.
If the mechanism is missing, the policy may be symbolic.
Integration analysis should connect policy → mechanism → agency → budget.
That chain reveals whether plans can actually deliver.
81. Budget alignment should use project-level geography
A capital programme may allocate $50 million to transport.
That number says little.
Map actual projects.
Which neighbourhood receives road, school, sewer or park?
Spatial budgeting reveals whether capital investment follows the plan.
82. Capital budgets should include renewal as well as expansion
New growth infrastructure is visible.
Maintenance is quieter.
A city can prioritise expansion while older neighbourhoods deteriorate.
Integration should compare expansion budget and renewal budget against equity and asset-management priorities.
83. Revenue assumptions should be shared too
One plan may assume strong development-fee revenue.
Another assumes low growth.
These cannot both be right.
Finance assumptions shape implementation.
Plan integration should therefore include revenue forecast and borrowing assumptions for major capital programmes.
84. Fiscal capacity can be a hidden contradiction
The city may adopt ten major strategies.
Together they require more money than exists.
This is a portfolio-level inconsistency.
Prioritisation is part of integration.
A plan network that cannot be funded is not integrated merely because maps align.
85. Project sequencing should be shown on one timeline
2027—transit design
2028—sewer expansion
2029—school opening
2030—housing phase 1
This makes sequencing visible.
If housing begins in 2027, the timeline exposes the problem immediately.
Temporal integration is easier to understand graphically.
86. Dependencies should be recorded explicitly
Project B depends on Project A.
Housing district depends on pump station and road connection.
If Project A slips, Project B should be flagged.
Modern project-management logic belongs inside strategic planning.
87. Critical-path planning can reduce false capacity
A plan may count 20,000 homes.
If all depend on one bridge, the bridge is the critical path.
The city should know this.
Strategic capacity is often controlled by a small number of enabling projects.
Plan integration reveals them.
88. Infrastructure contingencies should be planned
What if the bridge is delayed?
Can part of the housing proceed?
A robust plan includes alternative sequencing.
Integration should support resilience in implementation, not only hazard resilience.
89. Plans should share one parcel and land database where possible
Different departments may maintain duplicate land inventories.
One marks a parcel public housing opportunity.
Another marks future park.
A common parcel dataset reduces these contradictions.
The TPW Cadastre owner provides the broader land-information system.
90. Public-land strategy is a common integration failure
Government owns land through schools, utilities and agencies.
Each department sees its own asset.
A housing strategy may not know the land exists.
Integrated planning can create a cross-government public-land inventory.
This can unlock multiple public objectives.
91. School sites can serve multiple functions
A school can include playground, community space and emergency refuge.
Integrated planning can design these functions together.
This improves land efficiency.
It also requires governance agreements.
Synergy is not automatic.
92. Parks can provide stormwater and heat mitigation
A park plan can align with drainage and climate.
Instead of separate land reservations, one project can deliver recreation, flood storage and shade.
Integration finds these multi-benefit opportunities.
93. Streets can be mobility and public realm simultaneously
Transport agencies may see vehicle movement.
Urban design may see social space.
Integrated street planning includes buses, walking, trees and drainage.
The plan network should not assign the same street to incompatible single purposes.
94. Freight routes need environmental-justice integration
A freight plan may choose the shortest truck path.
That path may cross vulnerable residential areas.
Plan integration ensures freight is not treated as transport-only.
95. Industrial strategy should be linked to workforce housing
A city can attract logistics and manufacturing.
Workers need homes.
If employment growth is planned without housing, commuting pressure rises.
Economic development and housing should use compatible scenarios.
96. Tourism plans need housing integration
Tourism can increase jobs and short-term rentals.
A tourism strategy should therefore connect to workforce housing and housing stock.
Otherwise success in one sector can worsen another.
97. University plans should integrate with municipal housing
A university expands enrolment.
Student housing does not expand.
Pressure moves into neighbourhood rentals.
The city should integrate:
- institutional growth;
- housing forecasts.
Large institutions are urban actors.
98. Hospital expansion can also reshape housing demand
Healthcare growth creates:
- staff demand;
- shift transport.
Housing and transport strategies should anticipate it.
This is especially important where hospitals are major employers.
99. Climate mitigation and adaptation can conflict
A city may want:
- dense infill to reduce emissions.
The infill area may face:
- heat;
- flood.
The solution is not necessarily lower density.
It may be:
- resilient design;
- infrastructure.
Plan integration helps climate goals coexist.
100. Decarbonisation infrastructure needs land too
Grid upgrades.
Batteries.
Hydrogen.
These can compete with:
- housing;
- habitat.
Strategic plans should allocate energy infrastructure intentionally.
Energy transition is a land-use programme.
101. Plan integration should include emergency-management assumptions
Emergency plan may designate:
- school as shelter.
School plan may schedule demolition.
The contradiction can become serious during disaster.
Critical emergency assumptions should be screened against capital plans.
102. Emergency evacuation routes should be protected from conflicting growth
A new development may add:
- traffic.
If the same road is a wildfire evacuation route, hazard and growth plans need alignment.
The WUI owner provides detailed analysis.
The integration scorecard ensures the conflict enters strategic planning.
103. Long-range climate horizons should be standardised
One plan uses:
- 2050 sea-level rise.
Another uses:
- current flood map only.
The conclusions will differ.
The city should identify a common climate horizon for comparable decisions.
Different horizons can be used deliberately, but the reason should be explicit.
104. Data-update cycles should be aligned where possible
Housing data update annually.
Transport model every five years.
Hazard map after new science.
The integration system should record freshness.
An old input can create false conflict or false consistency.
Metadata matters.
105. Every shared dataset should have an owner
Population forecast:
- planning department.
Sewer capacity:
- utility.
Heat map:
- climate office.
Ownership ensures:
- updates;
- accountability.
A shared dataset without custodian decays.
106. Integration requires metadata standards
For each layer:
- date;
- source;
- projection year;
- confidence.
GIS overlays can look precise while using incompatible data.
Metadata is the discipline that keeps spatial analysis honest.
107. Conflict severity should be ranked
Not every contradiction deserves equal urgency.
Possible scale:
1 — minor
- wording difference.
2 — operational
- requires coordination.
3 — material
- delays implementation.
4 — critical
- safety or major capital conflict.
Ranking helps focus attention.
108. Resolution options should be classified too
A conflict can be resolved by:
- amending one plan;
- changing timing;
- changing geography;
- adding mitigation;
- accepting trade-off.
Integration is not always about choosing a winner.
Sometimes the solution is redesign.
109. Some conflicts should remain explicit
Example:
A heritage district limits redevelopment.
Housing plan wants more capacity.
The city may consciously choose:
- preserve heritage here;
- add housing elsewhere.
That is not failed integration.
It is a deliberate trade-off.
The failure is pretending both objectives can be fully achieved on the same parcel.
110. The scorecard should record accepted trade-offs
Document:
- conflict;
- decision;
- reason.
Future staff should understand why one policy was prioritised.
Institutional memory prevents repeated debate.
111. Public decision-makers should approve major trade-offs
Technical staff can resolve:
- terminology.
Elected bodies should resolve major value conflicts:
- growth versus conservation.
Integration clarifies what requires political judgment.
It should not hide politics inside a scoring formula.
112. The scorecard should be updated after major elections only where policy changes
A new administration may change priorities.
The planning network should reflect lawfully adopted changes.
Do not rewrite technical baselines simply because politics changes.
Separate:
- evidence;
- policy.
113. Integration can improve staff reports
When a major project is reviewed, staff can include an integration section:
Housing plan: aligned.
Transport plan: aligned.
Hazard plan: conflict requiring mitigation.
This helps decision-makers see cross-plan consequences.
APA’s 2026 interest in improving staff reports supports this broader need for clearer synthesis.
114. Integration should reduce repeated public arguments
If a neighbourhood plan already resolved:
- street connection;
the development hearing should not reopen the strategic question without reason.
A coherent plan network moves debate to the appropriate stage.
This makes development review more predictable.
115. Development review should still identify changed conditions
A plan may be old.
New hazard data may emerge.
Integration is not an excuse to ignore current evidence.
The decision system should allow:
- updated technical information.
Plans are frameworks, not blinders.
116. Plan integration can improve grant readiness
Many funding programmes ask whether projects align with:
- climate;
- housing;
- equity.
An integrated plan network can demonstrate this quickly.
Coordination can therefore improve access to external finance.
117. Integrated projects can be more competitive for funding
A transit project delivering:
- housing access;
- emissions reduction;
can meet multiple funding objectives.
The city should document these co-benefits.
Plan integration can strengthen the investment case.
118. Monitoring should distinguish output and outcome
Output
- 1,000 trees planted.
Outcome
- heat exposure reduced.
Plans often track outputs only.
Integration should connect outputs to shared city outcomes.
This avoids departments declaring success while the city-level problem remains.
119. Outcome indicators should be spatial where possible
Average city temperature can improve while one neighbourhood remains extremely hot.
Map outcomes.
Spatial inequality can disappear inside averages.
PIRS is powerful precisely because it spatialises policy.
120. Plan integration should include distributional outcomes
Who gets:
- investment;
- protection;
- housing access?
The Environmental Justice article in TPW-0203 adds a deeper zoning diagnostic.
Integration can flag distribution as a routine dimension.
121. A scorecard can become a negotiation tool between departments
Transport says:
- road needed.
Climate says:
- emissions problem.
The scorecard provides a shared evidence frame.
The departments can design:
- transit lane;
- freight access.
Integration creates structured negotiation.
122. Executive leadership should review unresolved critical conflicts annually
Do not let critical items remain in the register forever.
A yearly cross-department review can force decision.
Governance cadence turns integration into routine management.
123. Integration performance can be reported publicly
Possible metrics:
- critical conflicts resolved;
- capital projects aligned.
This creates accountability.
Avoid one misleading overall number.
Report substantive changes.
124. A city can integrate incrementally
Do not wait until all 40 plans are digitised.
Start with:
- housing;
- transport;
- capital;
- hazard.
Then expand.
Integration can deliver value quickly.
125. The first pilot area should be a place with real conflict
Choose a growth corridor where:
- housing;
- transit;
- flood;
all interact.
A pilot demonstrates the method.
Abstract scorecards are harder to institutionalise.
126. Integration should become part of staff onboarding
New planners should learn:
- plan inventory;
- shared datasets.
Otherwise institutional knowledge remains with a few senior staff.
Resilience includes staff turnover.
127. Consultant-prepared plans should use city data standards
External consultants often deliver:
- custom GIS;
- unique assumptions.
Require:
- shared baseline;
- machine-readable files.
This prevents fragmentation from being recreated by procurement.
128. Contract scopes should require integration review
Every new major plan should include:
- consistency matrix;
- conflicts.
This institutionalises the method.
Do not depend on voluntary good practice.
129. Interagency memoranda can formalise data sharing
Utilities or regional agencies may need agreements covering:
- update frequency;
- format.
Plan integration is partly an information-governance project.
Technical interoperability supports policy interoperability.
130. The scorecard should remain understandable
A method can become too complex.
If only one consultant understands it, it is fragile.
Use:
- transparent scoring;
- simple maps.
The tool should help planners think, not become a black box.
131. The deepest integration skill is asking the second-order question
Housing policy:
- what happens to schools?
Road policy:
- what happens to emissions?
Flood defence:
- what happens to public realm?
Plan integration is the habit of tracing consequences across systems.
That habit matters more than any single software package.
132. The ultimate result should be one governable future, not one document
A city does not need a mega-plan containing everything.
It needs:
- specialised plans that tell compatible stories.
The plans can remain separate.
Their assumptions, geography and timing should connect.
Integration succeeds when a resident, developer or public agency can look at one place and understand how the city’s major systems are supposed to evolve together.
133. Integration needs version control, not just meetings
Plans change on different schedules.
The transport plan may be updated in 2026.
The housing strategy may still use a 2023 population forecast.
The capital programme may contain a 2027 sewer project based on an earlier development scenario.
If staff discuss these documents without tracking versions, apparent agreement can hide inconsistent assumptions.
A plan-integration register should therefore record:
- current adopted version;
- effective date;
- forecast base year;
- geographic units;
- next scheduled review.
This turns coordination from memory into an institutional system.
134. Every major place should have a one-page integrated profile
A useful planning department can create a standard profile for each growth area.
The page can show:
- planned housing;
- jobs;
- transport capacity;
- school capacity;
- sewer capacity;
- major hazards;
- climate risks;
- capital projects;
- key policy dependencies.
The profile is not another plan.
It is a cross-plan dashboard.
A project team can immediately see where one sector’s promise depends on another sector’s delivery.
135. Integration should distinguish contradiction from sequencing
Two plans can appear inconsistent when they are actually describing different years.
A housing plan may allocate 8,000 homes.
The capital plan may fund the sewer upgrade only after 2030.
The correct answer may be:
housing is consistent with the long-term plan, but development must be phased until infrastructure arrives.
This is not a policy contradiction.
It is a sequencing dependency.
The scorecard should distinguish those conditions so that staff do not “solve” them by rewriting otherwise compatible policies.
136. Integration reviews should end with named decisions
A coordination meeting that produces only discussion has limited institutional value.
Each material conflict should end in one of five outcomes:
- Aligned — no action needed.
- Sequenced — policies agree but timing must be coordinated.
- Mitigated — conflict remains but a defined measure manages it.
- Revised — one plan must change.
- Escalated — the trade-off requires elected or senior executive decision.
This makes the scorecard actionable.
It also prevents the same conflict from returning to every meeting without ownership.
137. Accepted trade-offs should be recorded explicitly
Planning is not a machine that can maximise every objective at once.
A city may choose:
- more housing near transit despite some loss of low-intensity commercial land;
- stronger flood protection despite reduced development yield;
- a freight corridor despite local landscape impact.
The dangerous condition is not trade-off.
It is hidden trade-off.
An integration scorecard should record what was accepted, by whom, and why.
Future staff can then distinguish a deliberate policy choice from an accidental inconsistency.
138. The strongest scorecard becomes part of the annual operating cycle
Integration should not be a one-off exercise produced during a comprehensive-plan rewrite.
A practical annual cycle can ask:
- Which forecasts changed?
- Which capital projects slipped?
- Which hazards changed?
- Which housing allocations accelerated?
- Which policy conflicts became more severe?
- Which previous conflicts were resolved?
That makes plan integration a maintenance function.
Cities maintain roads, budgets and asset registers.
They should also maintain the relationships between their plans.
The Plan Integration Scorecard succeeds when the city can explain not only what each plan says, but whether all of those promises can still be true at the same time.