Routeava data guide

Send the smallest dataset that can answer the operating question.

Routeava does not need a complete customer database to begin. A limited, anonymized period is safer and usually sufficient for qualification.

Minimum fields

DateGroups work into employee-days and comparable periods.

Anonymous stop IDTracks recurring locations without requiring customer names.

Service address or coordinatesSupports geographic and travel analysis. Latitude and longitude are required by the current no-cost analysis engine.

Assigned technician or crewShows workload and territory assignments.

Job typePrevents unlike services from being treated as identical.

Planned order or timeShows the intended sequence or appointment constraint.

Completion statusSeparates completed, canceled, and rescheduled work.

Helpful additional fields

Actual arrival and departure, planned and actual service duration, recurrence frequency, customer time windows, employee start location, required skills or equipment, and approved job revenue.

Do not include

Payment-card data, bank records, Social Security numbers, medical records, government identification, passwords, or unrelated customer notes. Remove customer names when anonymous location IDs will work.

File rules

The intake accepts CSV, XLSX, PDF, PNG, and JPG. Automated Route Health analysis currently operates on a single-date CSV with unique stop IDs, assigned crews, latitude, longitude, planned sequence or time, and service duration. Other files remain useful for discovery and manual review.