The 2.5% Complete Streets Planning Set-Aside: How MPOs Can Fund Accessible Networks

The 2.5% Complete Streets Planning Set-Aside: How MPOs Can Fund Accessible Networks: start with the trip, not the device

A planning set-aside is most valuable when it changes the next capital decision, not when it produces a shelf report. MPOs can use the work to make accessible network needs visible in long-range choices. Federal transportation resources describe micromobility as small, low-speed human- or electric-powered devices and identify shared fleets as connections to other modes, including public transit.[1] A local policy should therefore define the transfer it intends to improve, the users it must not exclude, and the public-space conditions that make the connection trustworthy.

Set a policy question that can be answered

Frame the work around decisions the MPO actually controls: project selection, regional priorities, performance reporting, and coordination with member agencies. Use engagement to test whether the mapped network works for real trips. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[1]

A useful baseline combines a map review with repeated field observation. Observe peak arrivals, off-peak service, weather, lighting, parking behavior, boarding activity, and the condition of the walking route. Do not treat a map symbol as proof of an accessible connection. The observation record should say what was seen, when it was seen, and what remains uncertain. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[2]

Build an access-and-operations inventory

The inventory should distinguish physical conditions from operating conditions. Physical conditions include crossings, surfaces, grades, curb space, signs, and the ability to pass through. Operating conditions include vehicle availability, customer support, payment access, maintenance, enforcement, and communications. A policy that addresses only one category can leave the transfer incomplete. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[3]

Use the inventory to separate urgent corrections from longer-term capital work. A blocked route or confusing rule may need a rapid operational remedy; a missing crossing or connection may require planning, design, and funding. Both deserve a named owner, a deadline, and a way for the public to see whether the remedy happened. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[1]

Turn findings into accountable rules

The next step is a decision process. First measure the baseline. Then compare alternatives against access, safety, service, cost, and maintenance criteria. Choose an action with explicit conditions, implement it, and review the result with the same measures. This flow is more useful than a one-time score because it makes adaptation expected rather than exceptional. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[2]

Use metrics that reveal distribution, not only totals

Systemwide totals can hide a poor transfer at the locations that matter most. Report results by place, time period, and user-relevant condition. Pair administrative records with on-site audits and structured community feedback. Where data are incomplete, state the limitation instead of treating absence of a complaint as evidence of access. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[3]

Public reporting should be readable. Define each metric, name the reporting period, identify whether a number is measured or estimated, and explain the corrective action triggered by a missed target. If an operator supplies data, the agreement should specify format, frequency, privacy safeguards, validation, and the consequences of late or unusable reporting. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[1]

Design for access throughout delivery

Accessibility is a project-management discipline as well as a design concern. Include it in procurement, site selection, communications, construction staging, maintenance, customer service, and evaluation. Invite people with relevant lived experience to identify barriers before a final decision, and compensate engagement when local practice allows. The resulting record shows why a chosen action fits the full trip. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[2]

Funding and governance choices should reinforce the same purpose. A narrowly scoped project can still be valuable when it closes a documented gap and connects to a larger network strategy. Federal policy statements encourage transportation agencies to plan, fund, and implement walking and bicycling improvements, including links to transit, for people of all ages and abilities.[3] Translate that direction into local responsibilities rather than assuming a general aspiration will operate itself. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[3]

Implementation checklist

1. Publish the defined problem, boundary, and baseline.
2. Confirm accessible routes and operational alternatives through field review.
3. Assign owners, deadlines, performance measures, and public reporting.
4. Review results, correct failures, and decide whether to expand, revise, or stop.

The strongest Complete Streets planning set-aside policy keeps the focus on decision-ready analysis, accessible networks, and regional coordination. It gives staff a repeatable way to act, gives partners clear responsibilities, and gives residents a way to test the promise against the trip they actually make. That is the standard for moving from a persuasive concept to a reliable public service. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[1]

Finally, preserve a learning record. Keep the baseline, audit method, decision criteria, outreach summary, implementation changes, and periodic results together. This record lets a future staff member understand why a rule exists and whether it still serves its purpose. It also prevents a promising intervention from being judged only by anecdotes or a single launch-day snapshot. A policy can be revised without losing accountability when the evidence and reasons for the revision remain visible to the public. In Complete Streets planning set-aside, the unit of analysis should be a complete trip rather than a device, a block, or a single grant line. That perspective asks who can begin the trip, move through public space, understand the rules, and finish the transfer without an avoidable detour. It also makes tradeoffs visible early: a curb location may improve convenience for one user while constraining a pedestrian route for another. Documenting those tradeoffs in plain language creates a more defensible public decision.[2]

References

• [1] Federal transportation resource. https://www.fhwa.dot.gov/bipartisan-infrastructure-law/metro_planning.cfm
• [2] U.S. DOT program or guidance resource. https://www.fhwa.dot.gov/environment/bicycle_pedestrian/guidance/policy_accom.cfm
• [3] Federal data, standards, or policy resource. https://www.cdc.gov/active-people-healthy-nation/php/tools/transportation.html