Identify rough roads
See recurring roughness and probable impact locations, then use the data as a starting point for field inspection.
Road intelligence for local government
Know which roads need attention before complaints pile up.
Sucky Roads turns repeat drives into practical road-condition intelligence for towns, cities, counties, and state agencies. Use the data to focus inspections, watch recurring trouble spots, document changes, and verify what happens after maintenance.
Now accepting 2027 pilot partners. Pilot onboarding capacity is intentionally limited while we work directly with each participating agency.
Repeatable coverageUse phones in agency vehicles or community measurements to build road-condition history over time.
Action-orientedTurn measurements into ranked areas for inspection, repair follow-up, and reporting.
Privacy-awareFocus on the road condition rather than publishing individual driver travel histories.
How agencies use Sucky Roads
From everyday driving to a maintenance workflow.
Sucky Roads is designed to fit the work agencies already do instead of requiring a separate pavement survey every time a road needs another look.
Prioritize inspections
Rank problem areas by repeated observations so crews can spend more time checking the roads most likely to need attention.
Track repairs
Record maintenance activity and compare later passes to see whether measured conditions improved.
Build reports
Turn road-condition history into summaries that can support public works discussions, budgeting, and council or board updates.
Collect with fleet vehicles
Use mounted phones in vehicles already traveling agency routes to improve repeat coverage without asking employees to interact while driving.
Export and integrate
Operations and larger deployments can include reporting, exports, and GIS/API integration planning.
Sucky Roads measurements support inspection and planning. They are not represented as a certified pavement condition assessment.
Field tested on real roads
Built from actual driving, not a slide deck.
The detection system is being refined through repeated real-world drives on public roads using Android and iPhone devices mounted in vehicles. Development testing has included side-by-side device comparisons, repeat passes, offline uploads, GPS recovery, and filtering for phone movement versus road impacts.
Development field study
Real drives. Repeat measurements. Continuous tuning.
We use actual road measurements to find where devices agree, where false positives occur, and how repeat passes change confidence in a road condition. The same workflow is the foundation for agency pilots.
Example deliverables
See what an agency could receive.
These examples use simulated content so agencies can evaluate the workflow without mistaking demonstration data for measured road conditions.
Example agency dashboard
Preview prioritized roads, coverage, trend summaries, repair tracking, and reporting in a clearly labeled simulated workspace.
Open example dashboard →Sample road-condition report
See an illustrative report format for maintenance discussions, summaries, and before/after follow-up.
Open sample report →Live public map
See the actual public road measurements currently collected by Sucky Roads testers and contributors.
Open live map →Implementation
A straightforward pilot rollout.
Start with a defined service area and expand after the agency sees how the collection and reporting fit its workflow.
Define the pilot
Choose the roads, vehicles, staff contacts, goals, and reporting needs.
Configure collection
Set up mounted phones or agreed collection methods and confirm coverage expectations.
Build road history
Normal routes generate repeated observations while the dashboard begins ranking areas for review.
Review and expand
Evaluate findings, repair follow-up, and reporting, then decide whether to broaden the deployment.
Agency plans
Choose the scope that fits your roads.
Public pricing gives smaller agencies a clear starting point, while larger road networks can be scoped around coverage, integrations, and support needs.
For small towns getting started.
Use community and available road measurements to build a practical view of local conditions.
- Condition dashboard
- Ranked areas for inspection
- Summary reporting
- Agency onboarding
$2,500/year
Request Community demoFor teams managing daily road work.
Add regular fleet collection and maintenance workflows for agencies that want more consistent coverage.
- Community plan capabilities
- Phone-based fleet road-data collection
- Repair tracking
- Reports and exports
- Implementation support
Starting at $6,000/year
Request Operations demoFor broader road networks.
Scope coverage, departments, reporting, and integrations around a larger transportation network.
- Multiple departments and service areas
- GIS and API integration planning
- Custom pilot coverage
- Deployment and support plan
Custom pricing
Discuss County & StateAgency readiness
The details procurement and IT teams ask about.
Privacy & data
Review what the apps collect, how public road information is presented, and the principles behind the platform.
Privacy principles →Data methodology
Review how road measurements, repeat observations, and confidence are handled.
Data transparency →Onboarding & support
See the pilot process, support expectations, and common agency questions.
Agency support →Agency FAQ
Common questions before a pilot.
Do we need dedicated hardware?
No. An Operations pilot can begin with supported phones mounted in agency vehicles. The dedicated Sucky Roads Fleet hardware unit remains a prototype and is not required for a phone-based pilot.
Is the road score a certified pavement assessment?
No. Sucky Roads is designed to help identify and prioritize areas for inspection and follow-up. Agencies remain responsible for their normal inspection and engineering processes.
Can we start with only part of our road network?
Yes. A defined service area or set of routes is often the most practical way to evaluate coverage and workflow before expanding.
Can the data work with GIS?
GIS and API integration planning is available for larger deployments. The exact export or integration scope is determined during onboarding.
Is demo data mixed into the live public map?
No. The live public map is reserved for measured road data. Any example or simulated data is presented separately and clearly labeled as simulated.
Request a demo or pilot
See how Sucky Roads could fit your road program.
Tell us what your agency maintains, how you currently find problem roads, and what you would like to improve. We’ll use that to shape the demonstration and pilot scope.