Frequently Asked
Questions.

The coverage area, participating vehicles, reporting requirements, and evaluation criteria are documented before collection begins.

Installation takes approximately five minutes per vehicle. The exact setup depends on the vehicle and pilot scope.

No. Existing fleet or volunteer vehicles collect data while driving their normal routes.

Initial data may be available during the first week. Timing depends on route coverage, driving frequency, and the size of the pilot area.

• No video is collected.
• No audio is collected.
• Location data is anonymized and is not presented as an individual driver history.

The agreed outputs may include a road-condition map, prioritized locations for review, supporting evidence records, and reporting exports.

Yes, where available and approved. Complaints, work-order history, public records, and imagery can provide context for field detections.

Detections are grouped into locations that staff can review, prioritize, and document. Raw sensor events are not presented as the primary working view.

RoadPulse vehicle-mounted sensors are the primary data source. Approved aerial or satellite imagery, public records, and municipality-specific datasets may add context, but they do not replace sensor observations.

Observations are linked to time and anonymized location data, map matched, grouped across repeated events, and scored for severity and confidence. The resulting outputs can include a pothole identifier map, road roughness layer, temporal comparisons, and exportable review records.

No. Volunteer data collection does not require a RoadPulse account.

No. Initial scoping conversations are free and non-binding.

Yes. Data ownership, security, reporting, access, and other municipal requirements can be reviewed before a pilot is defined. Applicable terms are documented for the specific engagement.