Evaluating Your Curb & Parking Management Vendor: A Procurement Checklist for City & Decision-Makers

Evaluation Question

Strong Answer

Risk

Does the vendor operate under its own distinct brand with its own named reputation?

Vendor has a clear standalone identity, its own client relationships, and direct accountability for program outcomes.

Vendor is a division or cost center within a larger parent — performance signals get absorbed into a broader P&L with no individual accountability.

Is the advisory function structurally separated from execution functions the vendor will be asked to evaluate?

Vendor can clearly explain how its advisory role is independent from the platforms and partners it recommends.

The same organization advises on performance AND owns the tools being evaluated — creating structural pressure to protect platform revenue over honest counsel.

If the vendor underperforms, whose named reputation is at risk?

A specific, named organization with its own identity stands behind the work — leadership is directly accountable.

Accountability diffuses into a parent brand or holding structure with no clear owner of the outcome.

Evaluation Question

Strong Answer

Risk

Does the vendor control both your meter payment platform AND your citation/enforcement system?

Platforms are operationally independent; the vendor can demonstrate that enforcement routing decisions are driven by city priorities, not payment transaction volume.

A single vendor controls both — creating financial incentive to route officers toward meter violations to maximize payment app transaction fees rather than addressing safety-priority infractions.

Does the vendor that controls your meter payment platform also provide your demand pricing recommendations?

Pricing advice is demonstrably independent of the vendor's own transaction revenue model.

Vendor earns fees on every payment renewal and simultaneously recommends pricing — no financial incentive to suggest rate increases that might reduce transaction volume.

Can you switch one platform component without losing optimization across the others?

Modular design with data portability — switching one component does not degrade performance of the others.

Enforcement is operationally fused to payment data — switching either system means losing the optimization entirely. City faces a performance cliff, not a clean transition.

Evaluation Question

Strong Answer

Risk

Do enforcement recommendations achieve the city’s stated equity objectives?

Vendor proactively monitors and surfaces equity metrics — not just citation volume, but demographic and geographic distribution of enforcement pressure.

No equity monitoring in place, or equity monitoring is internal to the vendor with no independent verification. Meter-optimized routing may be concentrating citations in lower-income areas by design.

Is enforcement aligned with public safety outcomes, not payment transaction volume?

Priority violations (bus stops, fire zones, bike lanes, double parking) are weighted more heavily than meter lapse citations.

Routing system prioritizes meter violations. Safety-priority infractions are deprioritized because they don't generate payment renewal revenue.

Evaluation Question

Strong Answer

Risk

Has the vendor disclosed all ownership changes, acquisitions, or significant organizational restructuring in the prior 24 months?

Vendor answers directly and specifically — describes exactly how transition periods affected client-facing teams, resources, and program continuity.

Vendor is mid-integration (or has completed multiple integrations in quick succession) and cannot clearly explain where leadership attention and product investment are currently focused.

How many major acquisitions has the vendor completed in the past 18 months — and have those integrations been completed?

Integrations are complete and the vendor can demonstrate stable, dedicated program teams for your account.

Vendor has made multiple acquisitions in rapid succession — each integration cycle (typically 12–36 months) draws leadership attention inward; your program competes with internal reorganization for resources.

Who are the vendor's financial backers, and what is their investment horizon?

Publicly traded company aligned with long-term municipal contract terms (5–10 years) (a “forever home”).

Vendor is private equity (PE)-backed. PE-backed roll-up strategies are explicitly designed to consolidate, cut costs, and exit. Typically, PE targets a 5–7 year exit horizon — ownership, strategy, and leadership may change materially before your contract term ends.

Is the vendor's stated strategic rationale focused on your current program performance, or on a future-state technology vision?

Vendor's product roadmap and investment priorities demonstrably serve your existing enforcement, collections, and compliance needs.

Vendor's public positioning centers on long-term technology narratives (e.g., autonomous vehicle readiness) — signals where R&D investment and leadership attention will flow, not toward your current operational needs.

Evaluation Question

Strong Answer

Risk

Does the vendor's platform support open integration with third-party specialist partners — or does interoperability require the vendor's approval and involvement?

Vendor maintains documented, accessible APIs that allow specialist partners (multiple collections firms, tech providers, mobility operators) to integrate directly — without routing through a proprietary hub or requiring the vendor's involvement in each connection.

Vendor claims open standards compliance, but third-party integrations require the vendor's mediation, custom agreements, or platform-specific connectors — meaning the vendor controls which partners can participate in your ecosystem and on what terms.

Does the vendor have a financial incentive to recommend best-in-class specialist partners — or to consolidate your program onto their own platforms?

Vendor can demonstrate a track record of recommending and integrating third-party specialists even when they compete with the vendor's own offerings. Partner relationships are additive, not defensive.

Vendor's growth strategy is built on platform consolidation — each new capability they acquire or build reduces the surface area available to specialist partners. Over time, the ecosystem narrows to whatever the vendor owns.

Evaluation Question

What a Strong Answer Looks Like

Red Flag

Does the vendor have genuine cross-disciplinary depth — or breadth without mastery?

Vendor can demonstrate deep expertise in the disciplines relevant to your program (enforcement, collections, data science, equity design) — not just familiarity with each.

Vendor claims broad capability across all disciplines — but depth in one area competes with priorities in another; leadership attention is divided across too many service lines.

Can the vendor tell you when a different specialist partner would outperform them on a given segment of your program?

Vendor's accountability runs to program outcomes, not to protecting its own platform's share of the work — it will surface gaps honestly.

Vendor's advice is potentially shaped by its own revenue interest — recommending a competitor or replacement for underperforming components creates internal friction that the city never sees.

Is the vendor able to benchmark performance across multiple specialist partners on your behalf?

Vendor independently tracks and evaluates performance of all program partners against benchmarks, with no financial stake in any particular partner's share of the work.

No independent benchmarking function exists — each vendor self-reports, and no single accountable party is positioned to evaluate the system as a whole.

Where does your program sit in the vendor's global product roadmap — and who advocates for North American municipal enforcement needs (or United Kingdom, if the city-county council is situated in England) when platform decisions are made?

Vendor has dedicated North American product leadership with demonstrated influence over roadmap decisions. Can point to recent platform investments driven specifically by municipal enforcement, collections, or equity requirements in U.S. and Canadian markets.

Vendor operates across dozens of countries and prioritizes features with the broadest global applicability — North American municipal enforcement specifics (DMV integration, state-level collections law, equity reporting requirements, local citation adjudication workflows) compete with the needs of thousands of other cities for the same development resources.