Rate Your Micro-Mobility Infrastructure: A Hands-On Audit Checklist

Every city has that one bike lane that ends abruptly at a busy intersection, or a scooter parking corral that's always overflowing. These aren't just annoyances—they're signals that the micro-mobility network isn't working as intended. Whether you're a transportation planner, an urban designer, or a community advocate, you need a systematic way to evaluate what's on the ground. This guide provides a hands-on audit checklist you can use to rate your micro-mobility infrastructure, identify gaps, and make targeted improvements.

We'll walk through eight core assessment areas, each with specific criteria, common failure points, and practical scoring tips. By the end, you'll have a replicable framework that turns subjective impressions into actionable data. No need for expensive consultants—just a clipboard, a willingness to observe, and this checklist.

Why a Structured Audit Matters

Micro-mobility infrastructure—bike lanes, scooter parking, curb ramps, wayfinding signs—often gets built piecemeal. A protected lane here, a corral there, without a cohesive plan. The result is a patchwork that frustrates users and undermines adoption. A structured audit forces you to look at the system as a whole, not just individual components.

We've seen teams spend months debating a single intersection treatment while ignoring that the adjacent bike lane is too narrow to be safe. A checklist prevents that tunnel vision. It also creates a baseline: you can't measure improvement if you don't know where you started. Many cities now use audit scores to justify funding requests or to compare proposals from different vendors. The process itself builds consensus—when stakeholders walk a route together with a scorecard, disagreements become concrete and resolvable.

What Makes a Good Audit Tool?

An effective checklist balances detail with usability. Too many criteria and you'll never finish; too few and you miss critical issues. We recommend starting with 20–30 indicators across the eight domains below, each scored on a simple 1–5 scale. The key is consistency: define each score clearly so different auditors get similar results. For example, a 5 for bike lane width means at least 1.8 meters (6 feet) of unobstructed space; a 1 means less than 1 meter with debris. Calibrate your team with a practice walk before the real audit.

Network Connectivity and Continuity

The first question is whether your micro-mobility network actually connects the places people want to go. A beautiful protected lane that leads to a dead end is worse than no lane at all—it creates false expectations and dangerous last-minute maneuvers. Start by mapping the intended network against actual travel demand: where are the major residential areas, employment centers, transit hubs, and schools? Then audit each segment for continuity.

We recommend a simple test: ride the entire route from end to end. Note every point where the infrastructure changes, disappears, or forces you onto a high-speed road. Common breaks include intersections without cross-bike markings, bridges or underpasses that lack dedicated space, and transitions between different types of facilities (e.g., from a protected lane to a shared bike lane). Score each break for severity: is it a minor inconvenience or a safety hazard? A network that scores below 3 on average needs a connectivity improvement plan before any new segments are added.

Common Connectivity Failures

One frequent issue is the 'fading lane'—a painted bike lane that gradually loses markings and ends without warning at a busy intersection. Another is the 'orphan ramp': a curb cut that leads onto a sidewalk with no clear path to the street. These are often the result of projects from different departments not being coordinated. During your audit, photograph each break and note the surrounding context. Later, you can categorize them by type (missing link, poor transition, ambiguous wayfinding) and prioritize fixes that restore a continuous route.

Intersection Safety and Design

Intersections are where most micro-mobility conflicts occur. A well-designed intersection slows turning vehicles, makes rider intentions visible, and provides clear waiting areas. During your audit, evaluate each intersection along your network for four key elements: visibility, conflict points, signal timing, and physical separation. Start by standing at the corner during peak hours and watching how different users interact.

Visibility is often the biggest problem. Parked cars, foliage, or street furniture can block sightlines between drivers and riders. Note any obstructions that prevent a driver from seeing a cyclist waiting at the crosswalk or a scooter rider approaching from the right. Conflict points are the locations where paths cross—right hooks, left crosses, and through movements. Count how many conflict points exist and whether they are mitigated by markings, signs, or physical barriers. Signal timing should give riders a head start (leading bicycle interval) or a separate phase. If the intersection has no bicycle-specific signal, note whether the general traffic signal provides enough time for a rider to clear the intersection safely.

Scoring Intersections

We suggest a simple rubric: 5 points if the intersection has protected phases for micro-mobility, clear markings, and no visibility obstructions; 3 points if it has basic bike boxes or shared lanes but no signal priority; 1 point if it's a standard intersection with no accommodations and high traffic speeds. Prioritize intersections near schools, transit stations, and commercial corridors—these are where the most vulnerable users and the highest volumes converge.

Parking and End-of-Trip Facilities

Good infrastructure doesn't end at the destination. Without adequate parking, riders will lock bikes to signposts, block sidewalks, or simply not ride. Audit parking facilities for three dimensions: quantity, location, and design. Quantity is straightforward—count the number of racks or corrals and compare to estimated demand. A common benchmark is one bike parking space per 10 employees for office buildings, but this varies by mode share. Location matters: parking should be within 50 feet of the main entrance, visible from the street, and not tucked away in a dark corner. Design includes the type of rack (inverted U is the gold standard), spacing (at least 2 feet between racks), and whether it accommodates cargo bikes or scooters with different wheelbases.

Don't forget end-of-trip amenities like repair stands, air pumps, and lockers. While not strictly infrastructure, these facilities significantly influence whether people choose micro-mobility. During your audit, note the presence and condition of each. A broken repair stand is almost as bad as none—it frustrates users and signals neglect. Score parking as adequate (4–5) if there are enough well-designed racks at convenient locations; inadequate (1–2) if racks are full, poorly placed, or damaged.

Common Parking Pitfalls

One mistake we often see is installing racks that don't match the local fleet. A city with many e-bikes and cargo bikes needs wider spacing and sturdier anchors. Another is ignoring scooter parking: many cities install bike racks but provide no designated scooter corrals, leading to sidewalk clutter. If your audit reveals a mismatch, consider adding corrals or converting underused car parking spaces into micro-mobility hubs.

Maintenance and Surface Quality

Even the best-designed infrastructure degrades over time. Cracks, potholes, debris, and faded markings make routes unsafe and uncomfortable. Maintenance audits are often neglected because they require regular inspection cycles, but they're critical for user trust. Schedule your audit after winter or after a major construction project—these are times when surface quality tends to drop.

Walk or ride each segment and note surface defects: cracks wider than 1 cm, potholes deeper than 2 cm, loose gravel, standing water, or overgrown vegetation encroaching on the path. Also check for faded markings—lane lines, symbols, and signs should be clearly visible from 50 feet. Use a simple color code: green for good condition, yellow for minor issues (e.g., faded markings that are still legible), red for hazards that need immediate repair. Track the time since last maintenance; if a segment hasn't been inspected in over a year, flag it for priority.

Scoring Maintenance

A score of 5 means the surface is smooth, markings are bright, and there are no hazards. A score of 3 means there are a few cracks or faded areas but no immediate danger. A score of 1 means there are potholes, debris, or missing signage that make the route unusable. Aim for an average score of at least 3.5 across your network. If any single segment scores below 2, close it to micro-mobility until repairs are made.

Wayfinding and Signage

Good wayfinding reduces rider stress and prevents wrong-way riding or sudden turns. Audit signage for clarity, consistency, and placement. Signs should indicate the route number or name, the direction to key destinations, and the type of facility (bike lane, shared path, etc.). They should be placed at every decision point—intersections, forks, and ends of segments—and at regular intervals along long straight sections (every 0.5 miles or less).

Check that signs are not blocked by foliage or other objects, and that they are mounted at a height visible from a seated riding position (about 2–3 meters). Also look for pavement markings: directional arrows, shared lane markings (sharrows), and bicycle symbols. These should be refreshed every few years as they wear. A common failure is inconsistent naming—one sign says 'Greenway A' while another says 'River Trail', confusing users. During your audit, photograph every sign and note inconsistencies. Score wayfinding as excellent (5) if you can navigate the entire network without a map; poor (1) if you get lost at the first intersection.

Digital Wayfinding Considerations

While physical signs are essential, many riders now use apps for navigation. Your audit should also check whether the network is accurately mapped on popular platforms like Google Maps, Apple Maps, and local transit apps. If a bike lane exists but isn't shown on digital maps, it might as well not exist for many users. Contact the mapping providers to report missing data—this is a low-cost improvement that can have a big impact.

Equity and Accessibility

Micro-mobility infrastructure should serve everyone, not just confident cyclists in spandex. An equity audit examines whether the network reaches low-income neighborhoods, areas with high proportions of elderly or disabled residents, and communities of color. Start by overlaying a demographic map with your infrastructure map. Are there gaps in coverage that correlate with income or race? Many cities have found that protected bike lanes are concentrated in wealthier, whiter areas, while lower-income neighborhoods get only painted lanes or nothing at all.

Accessibility is another dimension: curb ramps must be wide enough for cargo bikes and adaptive cycles, and surfaces must be smooth for wheelchairs and strollers. Check that ramps are not blocked by parked cars or trash bins. Also consider the needs of people who use scooters or wheelchairs—infrastructure designed for bicycles may not work for them. For example, a bike lane that is too narrow for a scooter to pass a slower cyclist can create conflict. Score equity by the percentage of the network that reaches underserved areas (aim for 100% coverage) and accessibility by the proportion of ramps that meet ADA standards (aim for 100%).

Practical Steps for an Equity Audit

If you don't have demographic data, use proxy indicators: proximity to public housing, free lunch program participation, or limited English proficiency. Walk or ride in the areas you've identified as underserved and compare the infrastructure quality to that of higher-income areas. Document differences in lane width, maintenance, lighting, and parking. This evidence can be powerful for advocacy and funding applications.

Risks of Skipping or Rushing the Audit

Infrastructure decisions based on assumptions rather than data often lead to wasted resources and user frustration. We've seen cities install expensive protected lanes that don't connect to any destinations, or add parking corrals in locations nobody uses. The most common risk is building infrastructure that looks good on paper but fails in practice—a 'vanity project' that scores high on design awards but low on actual ridership. An audit prevents this by forcing you to test your assumptions against real-world conditions.

Another risk is neglecting maintenance. A new bike lane can degrade within two years if not properly maintained. Without regular audits, problems accumulate until the infrastructure becomes unusable, and riders revert to cars or sidewalks. This erodes public trust and makes it harder to justify future investments. Finally, skipping the equity dimension can lead to infrastructure that benefits only the already privileged, widening the mobility gap and generating community opposition. A thorough audit identifies these risks early, allowing you to course-correct before resources are committed.

The Cost of Inaction

Delaying an audit doesn't save money—it shifts costs to later, when repairs are more expensive and user confidence is lower. For example, a pothole that costs $50 to patch today can become a $500 repair if it grows. Similarly, a missing link that forces riders onto a dangerous road can lead to crashes that cost the city millions in liability. Regular audits are a form of preventive maintenance, and they pay for themselves many times over.

Frequently Asked Questions

How often should we conduct an audit? We recommend a full network audit annually, plus spot checks after major weather events or construction. High-traffic corridors may need quarterly inspections. The key is to establish a regular cadence and stick to it.

Who should be on the audit team? Include a mix of planners, maintenance staff, and community representatives. Ideally, include people who actually ride bikes or scooters in the area—they will notice things that others miss. Consider training volunteers from local advocacy groups to help with data collection.

What tools do we need? A clipboard, a camera or smartphone, a measuring wheel, and a printed checklist. For digital data collection, apps like Fulcrum or Survey123 allow you to geotag issues and attach photos. But start simple—paper works fine for the first audit.

How do we prioritize improvements? Use a matrix that combines severity (how dangerous or inconvenient is the issue?) with user volume (how many people are affected?). High-severity, high-volume issues get immediate attention. Low-severity, low-volume issues can be batched into a regular maintenance cycle.

What if our audit reveals major problems we can't fix immediately? Be transparent with the public. Publish the results and share your improvement plan, even if it's long-term. Riders appreciate honesty and will be more patient if they see a roadmap. Temporary fixes—like signage, temporary bollards, or rerouting—can mitigate the worst issues while permanent solutions are developed.

Turning Audit Results Into Action

An audit is only valuable if it leads to change. After you've collected your data, synthesize the findings into a report with three sections: (1) overall network score and key strengths, (2) priority issues ranked by severity and volume, and (3) a 12-month action plan with specific projects, budgets, and responsible parties. Present this report to decision-makers with clear visuals—maps with red-yellow-green ratings are powerful communication tools.

Don't try to fix everything at once. Pick the top three issues that will have the greatest impact on safety and ridership. For each, define a concrete outcome (e.g., 'reduce right-hook conflicts at Main and Oak by 50%') and a timeline. Assign ownership: who will design the fix, who will fund it, who will implement it? Without clear accountability, the report will gather dust. Finally, schedule the next audit for six months from now, and use the same checklist so you can track progress. Over time, you'll build a culture of continuous improvement that makes your micro-mobility network safer, more equitable, and more used.