Writing a Winning Micromobility RFP Response

Most cities do not hand out shared-mobility permits on a first-come basis. They run a competitive Request for Proposals (RFP) or Request for Applications (RFA), score every bid against a published rubric, and award a limited number of slots, often 2 to 4 operators for the whole city. That means your proposal is not marketing copy. It is an exam. Points win permits, and points are awarded for specific, verifiable commitments in the exact categories the city cares about. This lesson covers what evaluators score, how to structure a scooter share proposal that reads clean to a reviewer working through a stack of submissions, and the small mistakes that disqualify strong operators before anyone reads their safety plan.

If you have not yet mapped the regulatory landscape you are bidding into, read this lesson alongside the scooter rental permits and regulations guide so you understand permit caps, fee structures, and the difference between a permit program and a full RFP before you commit staff time to a response.

How city evaluators actually score your response

An RFP is graded, not read for pleasure. Somewhere in the document is a scoring rubric that assigns points or weights to each section. Your first job is to find that rubric and treat it as your outline. If safety is worth 25 points and community engagement is worth 5, you spend your best writing on safety.

Weights vary by city, but the scored buckets are remarkably consistent across North American micromobility solicitations. Use this as a planning baseline, then override it with whatever the specific RFP publishes.

Read the RFP like an auditor first

The single highest-return hour you will spend is reading the full solicitation twice before drafting. First pass: highlight every "shall", "must", and "required". Second pass: sort those into three lists, the mandatory minimums that disqualify you if unmet, the scored criteria that earn points, and the administrative rules like forms, page limits, and format. Operators lose on all three, but the minimums are where good bidders self-eliminate by assuming a requirement is negotiable when it is not.

Confirm you clear the mandatory minimums

Every RFP has pass/fail gates. If you miss one, your bid is rejected without scoring, no matter how strong the rest is. Check these before you invest in a full response:

• Data feed capability. Almost every city now requires a live Mobility Data Specification (MDS) provider feed and a public General Bikeshare Feed Specification (GBFS) feed. If you cannot produce both, you cannot bid. Levy's city compliance tools generate MDS 2.0 and GBFS 3.0 feeds, ingest city policy, and enforce geofences in real time, which clears this gate out of the box.
• Insurance and indemnification. Cities name exact per-occurrence and aggregate liability limits and require the city to be added as an additional insured. Confirm you can meet the exact limits the RFP prints, and secure the certificate before the deadline, not after.
• Local presence. Many programs require a warehouse, staging site, or staffed field operation inside the metro before day one. Have an address or a signed plan.
• Experience threshold. Some RFPs require a minimum number of prior deployments or rides operated. You can satisfy this by presenting the track record of the platform you run on: Levy powers 127+ active fleet partners and has processed 2.4M+ rides at 99.8% platform uptime, and runs its own rider rentals across 30+ cities in the US and Canada.

Structure the proposal so a tired reviewer says yes

Evaluators read many bids back to back. The proposal that scores well is the one that makes their job easy: it follows the RFP's own section order, answers each scored item directly under a matching heading, and leads every section with the commitment, then the evidence. Use this structure and adapt the section names to match the city's language exactly.

Winning the scored sections

Generic promises earn generic scores. Below is how to turn each scored category into points by pairing a commitment with a mechanism a reviewer can verify.

Operations and reliability

Reviewers want to know the fleet will not become sidewalk clutter or a pile of dead vehicles. Give them numbers: how many hours to rebalance a mis-parked vehicle, how many to remove a broken one, and how you decide where vehicles go. Levy's AI Ops produces demand forecasts and ROI-ranked rebalancing recommendations (move N vehicles from one zone to another by a target time, with a projected revenue lift), which lets you describe a data-driven rebalancing operation rather than a guess-and-drive one. These are recommendations your field team acts on, not automatic dispatch, and saying so plainly keeps you from overstating the capability. Reinforce reliability with maintenance: Levy stocks common US spare parts (tires, tubes, brake cables and pads, display panels, batteries) so repairs ship in days, and files the OKAI 90-day manufacturing-defect warranty on your behalf.

Safety

Safety points go to enforcement, not intentions. Anchor this section on concrete controls:

• Speed and no-go zones. Configure geofenced service areas, parking zones, no-go areas, and speed-limit zones, with real-time enforcement so a vehicle physically slows or stops where the city requires it.
• Parking and sidewalk compliance. Levy Vision runs helmet verification at unlock, parking-pose validation at end of ride, and sidewalk detection with throttle-cut enforcement. The parking classifier checks exactly four things at ride end: is the vehicle upright, is it inside the parking zone, is it blocking the sidewalk, and is the photo clear. That is a defensible answer to the sidewalk-clutter and pedestrian-safety questions cities ask.
• Rider behavior. Rider Score applies behavior-based safety scoring with a documented intervention ladder, reward tiers, and a helmet-selfie discount, so repeat offenders face escalating consequences while safe riders earn incentives.
• Rider protection. Embedded per-ride micro-insurance through Cover Genius (with a Slice fallback) is a rider-facing protection worth naming, and it is separate from the commercial liability coverage the city requires you to carry.

Equity

Equity is where thin proposals lose easy points. Cities want proof that lower-income and underserved residents can actually use the service. Use the pricing engine to commit to concrete programs: a discounted plan for qualifying riders configured through subscriptions, packages, and promotions, plus deployment quotas that place a defined share of vehicles in the equity zones the RFP names. Address access for riders without a smartphone or a bank card by describing your plan directly rather than glossing over it, because reviewers specifically look for it.

Accessibility

Accessibility is about physical and design access, and it is scored separately from equity. Speak to how your parking enforcement keeps sidewalks, curb ramps, and transit stops clear for wheelchair users and people with low vision, which is exactly what parking-pose validation and sidewalk detection protect. Match your vehicle mix to accessibility needs where the RFP allows, for example seated mopeds and step-through e-bikes for riders who cannot balance on a standing scooter.

Sustainability

Tie sustainability to operations, not slogans. Strong, verifiable points: an all-electric fleet, a repair-over-replacement maintenance model backed by US spare-parts stock that extends vehicle lifespan, and battery swapping with pack state-of-health tracking and a Juicer and Charger marketplace that cuts the van trips required to keep vehicles charged. Fewer charging trips means fewer field-operation miles, a metric sustainability reviewers understand.

Data and privacy

This section is often pass/fail and scored. State clearly that you provide a live MDS 2.0 provider feed and a public GBFS 3.0 feed, ingest the city's policy, and enforce stacked geofence priorities in real time. Levy's city compliance tools also include a city-portal magic link with managed key access, so you can describe exactly how the city will receive and audit your data. On privacy, commit to sharing only what the RFP requires and to the retention limits the city sets.

Match the vehicle mix to the program

Different RFPs favor different vehicle types. Tailor your proposed mix to what the city is soliciting and to the terrain, then explain why. Levy is hardware-agnostic across 30+ IoT vendors with a catalog of 150+ fleet-ready electric vehicles, so you are not locked to one form factor.

The fee proposal and financial viability

Cities score whether you can survive the permit term, not just whether you are cheap. Present the fee response in the exact format requested (per-vehicle fees, per-trip fees, or both), then demonstrate viability with a simple unit-economics summary: projected rides per vehicle per day, revenue per vehicle, and the fee load. Because Levy runs on a $0-upfront, revenue-share model where you pay when riders pay (20% of GMV under 100 active vehicles, dropping to 15% of GMV at 100 to 249 vehicles on an annual or approved term, with a $250 per month platform minimum credited against fees), you can honestly show a low fixed-cost structure that survives a slow ramp, which reviewers read as durability. Note that GMV is gross rider payments before taxes, fees, refunds, and tips, and your actual payout base is net revenue after Stripe processing (2.6% + $0.20 per transaction, shared proportionally), so treat any quick "gross minus fees" figure as a conservative estimate. Model your city, fleet size, and pricing in the Fleet Estimator, then drop the projected numbers straight into this section.

Common disqualifiers and how to avoid them

Strong operators lose on avoidable errors more often than on weak plans. Screen your response against every item below before submission.

1. Late or wrong-format submission. Missing the deadline by a minute, submitting to the wrong portal, or exceeding a page limit are automatic rejections in many cities. Treat the clock and the format spec as hard rules.
2. A missing mandatory form or certificate. An unsigned form, an expired insurance certificate, or a missing certification voids an otherwise complete bid. Your compliance matrix should list every attachment.
3. Failing a mandatory minimum. No MDS feed, insurance below the stated limits, or no local operations plan will fail you before scoring.
4. Unanswered scored criteria. If the rubric lists a requirement and the reviewer cannot find your response, you score zero on it. Mirror the RFP's headings so nothing hides.
5. Overclaiming. Inventing capabilities, statistics, or partnerships you cannot prove undermines your credibility across the whole document and can be grounds for disqualification. Claim only what you can demonstrate.
6. A generic, recycled response. Copy that never names the city, its neighborhoods, or its specific goals reads as low-effort and scores like it.

Final pre-submission checklist

A winning micromobility RFP response is disciplined, specific, and built around the city's own rubric, not your pitch deck. Get the mandatory minimums clean, answer every scored criterion under a matching heading, and back each commitment with a mechanism a reviewer can verify.