To create new jobs, you can upload a CSV file with the appropriate information. This article guides you through the various formats and fields to use for a successful CSV upload. You can also manually create jobs in the dashboard by navigating to Dispatch → Add → Add job.
When you have created a new job CSV file, you can upload the file by navigating to Dispatch → Add → Upload jobs.
CSV file format
All valid CSV files are supported, with values in single quotation marks and comma separated.
Make sure your uploaded CSV does not have duplicate columns with the same header. If you import a file with duplicate headers, it could return an error, or you might find that the first column is uploaded, but all subsequent columns are ignored.
All field names are case sensitive. If your field name does not use the correct case, the field is generated using default values, rather than the values you have entered, and the data is dropped. Unrecognised fields are not stored as custom data on the shift.
Use the Type field to assign a job type. By default, if you leave this column blank, the Attend type is used. Use this field to determine what you expect to happen on this job, such as a pickup, or a delivery.
You can create multiple plans at once using the Plan Number column. One plan is created for each unique value in the column, with stops split between them. You can also use the Job Reference field to link stops as part of the same job. The order of the stops in the job is determined by the order of the rows in the CSV. Use the Job Number field to explicitly position a single stop within the job.
You can also add custom stop data fields to your job CSV. For more information about custom stop data, see the custom stop data article.
Required fields are:
AddressTypeTime Window StartTime Window EndService timeDate, orStart Date
Fields
Field name | Example | Details | Default value |
|
| The address of the job | blank |
| One of:
| The job type |
|
|
| Time the job starts |
|
|
| Time the job ends time for the job |
|
|
| Time that the job is expected to take, in seconds |
(2 minutes) |
|
| Date the job starts | the next day |
|
| Date the job ends | same as the start date |
|
| The latitude of the job. Must be accompanied by a longitude. | blank |
|
| The longitude of the job. Must be accompanied by a longitude. | blank |
or
| or
| The driver assigned to the job. Can be an email address, or an external reference string. | blank |
|
| If supplied, and this row also has a matching driver, then the resulting shift should have the supplied name | blank |
|
or
| The first value is the external reference for the vehicle capacity. The second value is the capacity cost of this job. | blank |
|
or
| The first value is the external reference of the requirements attribute. The second value is either true or false, or a numeric value | blank |
|
or or or | The first value is the external reference of the vehicle. The second value is the preference status, one of: allowed, disallowed, preferred, or dispreferred | blank |
|
| A job reference value. | blank |
|
| A specific position where the stop should be placed within the job. Use the | blank |
or
|
or
| An ID or external reference for a communications plan. For more information, see the Communications article | blank |
| Customer email address | blank | |
|
| Customer phone number | blank |
|
| The customer’s name | blank |
|
| Priority for the job | blank |
|
or
or | An ID, external reference, or email of the allowed drivers for the job. Use comma-separation to add multiple values. | blank |
|
| Which plan to add the job to | blank |