Operations guide

Import jobs, customers, and workers

Bring work orders, customer lists, and staff into RouteIQ Dispatch Software from a CSV file.

Updated October 23, 2026

Start from a sample. The Jobs, Customers, and Workers import screens each have a Sample CSV link. Download it, replace the rows with your data, and import it.

1. Import jobs

Open Jobs and select Import.
Upload CSV: choose a file up to 10 MB. The first row must be column headers. Commas, semicolons, and tabs all work as separators.
Map columns: columns with familiar names are matched automatically. Pick a field for each remaining column, or choose Don't import this column.
Review & import: check each row's status, then import. Each job is created with one dropoff stop.

Rows with problems are listed with the reason. The rest of the file still imports.

Job columns

Only the street address is required. Header names are matched without regard to case, spaces, or punctuation.

Field	Headers matched automatically
Street address (required)	Address, Street, Address 1, Service Address
Address line 2	Address 2, Apt, Suite, Unit
City, state, ZIP, country	City, State, Province, Zip, Postal Code, Country. Blank country means US.
Customer name	Customer Name, Name, Client, or separate First Name and Last Name. A full name is split at the last space.
Customer email and phone	Email, Phone, Mobile, Cell
Contact name and phone	Contact Name, Contact Phone
Scheduled start	Start Date, Date, Scheduled, Appointment
Due date	Due Date, Due By, Deadline
Service type	Service Type, Job Type, Type. Use the type's name or short code.
Stop instructions	Instructions, Notes, Comments. Drivers see these.
Internal notes	Internal Notes. Staff only.
External reference ID	Order Number, Work Order, Reference, Order ID
Zone	Zone, Territory, District. Checked against the address; a mismatch is a warning only.

Job rules

No email: the job is filed under an auto-created occupant customer for that address. Later imports at the same address reuse it. Occupant customers are never emailed.
With email: a customer name is required. A customer with that email is reused; otherwise one is created.
Start date: must be in the future. Blank means unscheduled.
Due date: a date with no time means the end of that day.
Order numbers: an external reference ID already used on this site, or repeated in the file, rejects the row, so re-importing a file doesn't duplicate those jobs.
Service type: required when your site has more than one active service type.
Address: an address that can't be found on the map rejects the row. So does an address in a banned zone.

Job date formats

Job dates without a time zone use your computer's time zone. A job date the wizard doesn't recognize is flagged, and the row imports without it.

Format	Example
Year first	`2026-11-02` or `2026-11-02 14:30`
Month first	`11/2/2026`, `11/2/26`, or `11/2/2026 2:30 PM`
ISO 8601	`2026-11-02T14:30:00-05:00`

2. Import customers and workers

Open Customers or Workers and select Import.
Upload CSV: choose a file up to 10 MB with column headers in its first row. Use the Sample CSV as a starting point, or keep your own headers and map them in the next step.
Map columns: review automatic matches, then assign a field to every remaining column or choose Don't import this column. Unrecognized columns are not silently ignored; every column must be mapped or explicitly skipped before continuing.
Review & import: check the row errors and the count ready to import. Correct the file if needed, or import the valid rows. Rows that fail the preview checks are skipped; the final results also show any rows that failed during import and the reason.

Customer and worker imports create or add people to the site. Their required contact and account fields differ from the job-import rules above.

Name: map a Full name column, or separate First name and Last name columns. Full names split at the last space to fill missing first or last names; both parts must be present.
Required contact and account fields: map Email, Phone, and Password. Passwords must contain at least eight characters and meet applicable password rules.
Phone country: optionally map a two-letter code such as US or GB. An omitted column or blank cell uses the site's phone country, falling back to US only if the site has none.
Display name: optional; defaults to first name and last initial.
Worker role: worker, dispatcher, or admin. Blank means worker. Organization admins cannot be imported.
Driver license fields: workers can include a license number, class, and expiration date. Use YYYY-MM-DD or M/D/YYYY for the date. An invalid license date prevents that row from importing.
Worker custom fields: create the definitions first, then map columns to their labels. Keys and labels can be matched automatically. Review the mapped values: invalid values prevent the row from importing, but missing required custom fields are not enforced by the import. These values are set only for workers newly added to the site. See worker custom fields for setup and supported value formats.

One email is one account.

If an email already has a RouteIQ Dispatch Software account, that account is added to your site. Its password, name, and phone don't change.

Troubleshooting

A job row was rejected as a duplicate

Its order number was already imported. Search jobs for that reference, or clear the column to import it as a new job.

A start date was rejected

Start dates in the past are not accepted. Update the date or leave it blank to import the job unscheduled.

A customer or worker row failed

Check the reason in the preview or results. Confirm required fields are mapped and filled, the password is valid, and the phone matches its explicit or site-default country. For workers, also check the role, license date, and any custom-field values.