6.4 Action Steps, Responsibility & Scheduling

From Policy Language to Work You Can Track

Plan Implementation is about 12% of the AICP exam. Within that domain, section 6.4 Action Steps, Responsibility & Scheduling tests whether you can move from adopted goals and policies to an actionable implementation system. Beautiful policy text that never names who does what by when with which resources is not implemented—it is archived.

On scenario items, weak answers restate the goal ("promote housing affordability"). Strong answers specify action steps, responsible parties, partners, timing, dependencies, and management roles that keep work on schedule when political attention drifts.

What Counts as an Action Step

An action step is a discrete, assignable unit of work that advances a plan policy or objective. Good action steps are:

• Specific — "Amend parking standards in the B-2 district to remove minimums within ¼ mile of frequent transit" not "improve parking policy"
• Outcome-linked — clearly tied to a plan policy ID or objective
• Resource-aware — implies staff time, consultant budget, legal review, or capital dollars
• Time-bound — near-term, mid-term, or long-term with calendar or fiscal-year anchors where possible
• Verifiable — someone can say later whether it happened

Action steps sit below goals and policies in the classic hierarchy: vision → goals → objectives → policies → actions / programs / projects. Confusing levels produces either unmeasurable slogans or micro-tasks disconnected from public purpose.

Drafting Action Plans and Implementation Matrices

Most plans use an implementation matrix (or action agenda, work program, strategic plan table). Typical columns:

1. Action ID / description
2. Related goal / policy
3. Lead responsibility (department, agency, or external partner)
4. Supporting partners
5. Priority / phase (e.g., years 1–2, 3–5, 6–10)
6. Estimated cost band and funding source type
7. Dependencies (code change before capital build; land acquisition before park design)
8. Performance indicator (optional but powerful—links to monitoring in 6.5)

Exam cue: When a scenario shows a plan with only goals and maps, the missing piece is often this matrix—not another vision chapter.

Assigning Responsibility: Lead, Support, Partner

Responsibility is not a distribution of credit; it is assignment of accountability. Best practice:

• Name one lead with decision authority and capacity (planning department, public works, housing authority, parks, county commissioner's office, MPO staff, nonprofit partner only when governance allows).
• List supports that must contribute data, ROW, legal authority, or funding.
• Identify external partners (school districts, utilities, tribal governments, community development corporations, state agencies) with clear expected roles—not vague "collaborate."
• Flag actions that require intergovernmental agreements, board resolutions, or legislative changes before staff can execute.

Shared ownership without a lead is a classic failure mode. "Planning and Public Works will jointly implement complete streets" often means neither owns the CIP request, the design manual update, or the council briefing. Prefer: "Public Works leads capital delivery; Planning leads code and network prioritization; joint quarterly steering."

Capacity honesty matters. Assigning every equity and climate action to an understaffed planning division while capital departments control the dollars is political fiction. Planners may still coordinate and report, but the matrix should not pretend capacity that does not exist.

Scheduling: More Than Dates on a Spreadsheet

Scheduling aligns actions with real institutional clocks:

Phasing sequences prerequisites: inventory before prioritization; zoning before density-dependent fee programs; land control before design; pilot before citywide mandate. Critical-path thinking asks which delayed action blocks everything else.

Schedules should distinguish quick wins (procedural fixes, data releases, pilot programs) from structural reforms (code overhauls, major capital, institutional restructuring). Quick wins build credibility; structural reforms need multi-year protection in the CIP and work program.

Manage, Facilitate, Coordinate—Three Planner Roles

APA's implementation language emphasizes that planners manage, facilitate, and coordinate so adopted plans deliver on schedule:

• Manage — own a defined program or project (e.g., zoning update project management: scope, budget, consultant, hearings calendar, adoption package).
• Facilitate — design processes that move multi-party decisions (interdepartmental teams, community implementation committees, board work sessions) without owning every technical product.
• Coordinate — align schedules, funding requests, messaging, and conflict resolution across silos so related actions do not collide or leave gaps.

On the exam, do not assume the planner personally builds the road or operates the transit line. Do assume the planner is responsible for keeping the implementation system coherent: tracking status, surfacing blockers early, escalating policy conflicts, and returning evidence to decision-makers.

Governance Tools That Make Responsibility Real

Implementation systems often need more than a table in the plan appendix:

• Annual work programs that select a subset of plan actions for the coming fiscal year
• Cross-departmental implementation teams with charters and reporting lines
• Council or board implementation dashboards (public transparency builds pressure to perform)
• Memoranda of understanding / IGAs for multi-agency actions
• Project charters for major code or capital packages (scope, success criteria, sponsor)
• Sunset or check-in dates for pilot regulations and temporary programs

Without these, the matrix becomes a static PDF.

Worked Mini-Example

A comprehensive plan adopts a policy to "increase housing near frequent transit while reducing displacement risk." Weak implementation: one line—"Planning will promote TOD." Strong action package:

1. Code — Draft TOD overlay with density/height standards and anti-displacement tools; Planning lead; Legal support; 18-month schedule tied to housing element deadlines.
2. Program — Expand tenant counseling and right-to-counsel pilot near station areas; Housing Authority lead; Planning data support; funded via CDBG + general fund starting next budget.
3. Capital — Sidewalk and crossing package on the BRT corridor; Public Works lead; transit agency cost-share IGA; CIP years 2–4.
4. Partnership — Land-bank option agreements for 50 affordable units; CDC partner lead on acquisition; City gap financing resolution by council in year 1.

Each step has a lead, phase, dependency (code before relying on density bonuses), and schedule hook. That is 6.4 competence.

Common Exam Traps

• Leaving responsibility as "the City" or "stakeholders" with no lead
• Scheduling everything as year 1 with no capacity or budget realism
• Ignoring CIP/budget calendars when listing capital actions
• Confusing planner coordination with sole delivery of all infrastructure
• Writing actions that are really restated goals
• No dependency logic (capital before land control; enforcement before code adoption)

Bottom line for AICP: Action plans succeed when steps are discrete, responsibility is named with authority and capacity, and schedules follow institutional time. Manage, facilitate, and coordinate so the adopted plan becomes a living work program—not a shelf document.