In this article, you will discover how to export task data outside of the Onfleet platform to perform your own analysis if desired. You can find an example of a task export .CSV sheet at the bottom of this article.
The export feature lets you analyze your Onfleet data, such as determining the average task durations, driver performance, and historical details like photos, signatures, completion notes, and feedback.
To export tasks, click the down arrow icon in the toolbar or use the "E" hotkey. Adjust the filters as needed, then click Download. A CSV file will be generated, and you’ll receive an email within a few minutes containing a download link.
The export file is delivered as a plain-text CSV with no formatting applied. We recommend opening it in a plain-text editor or ensuring your spreadsheet program does not apply automatic formatting.
Tasks can be exported based on Status (Completed, Assigned & Unassigned), Dates, (range can be from 24 hours to the maximum available in your Onfleet plan), Teams, Driver, and Connections (if applicable).
Note: If you would like to automatically remove columns you don't need, you can do so using an Excel macro. Follow our guide here.
Column Headers Definition
Here are some common column headers within an exported CSV file and their definitions:
| Header Name | Definition |
| Driver Number | A unique identifier for each driver within that export. The number is a driver ID shorthand for export use only and is only consistent within the exported file. |
| Task Number | This applies for assigned tasks only. This is the order of the task in the driver's assigned task list. |
| shortId | This is the task identifier. |
| departureTime | This time is either 60 seconds after the task has started, or when the driver has traveled 100m from the start task location (whichever comes first). |
| arrivalTime | This time is either the last time that a worker arrived within 150m of the task destination, or if they never are within 150m of the task destination, it is the same as 'Task completed'. |
| startTime | This time is the moment that the driver swipes/holds to start the task. |
| completionTime | This time is the moment that the driver swipes/holds to complete the task (after meeting any task completion requirements). |
Limitations
All task exports are restricted to a 32-day period, for all plan types. In order to export tasks over a longer period, it will be necessary to generate multiple task exports and later combine them into a single document. As an alternative to bypass the 32-day limitation, you can use our open-source developer tool for task exports.
Your export history limit for completed tasks is based on your plan type:
- Launch: 90-day
- Scale: 1-year
- Enterprise: Unlimited
Note: There is a 50,000 task limit per export, regardless of the billing tier.
For more details please visit our pricing page or click here to open a Support Ticket.
Automatically Delete Unwanted Columns in Task Export
If you use task exports to generate route sheets, manifests, or labels, you may want to remove irrelevant columns quickly. The steps below show you how to create an Excel macro to automate this process. Once set up, you can paste data into your macro-enabled sheet and run the macro to clean it automatically.
Step 1:
Download "Onfleet_Macro_Template.xlsm" (attached at the bottom of the article) - this is a blank macro-enabled workbook and comes with the macro installed. This will prevent you from having to copy/paste the macro text every time you want to run it.
Note: Make sure you download the file. Do not open in Google Sheets.
Step 2:
Export tasks from the dashboard. Open the CSV file and copy all the data, including the headers. This can be done with hotkeys:
- Mac: Hold ⌘ Cmd + A and then ⌘ Cmd + C
- Windows: Hold Ctrl + A and then Ctrl + C
Step 3:
Paste the data from the export into the "Onfleet_Macro_Template.xlsm". DO NOT select all to do this. Simply paste the data into the first cell "A1".
Step 4:
Enter the Visual Basic Editor in the template file. To do this, select "Tools" from the options taskbar in Excel, hover over the "Macro" option, and select "Visual Basic Editor".
Step 5:
Select the columns you’d like to include in the spreadsheet. You can refer to the column numbers in the table below as a guide. In the fourth line in the Visual Basic Editor, enter the column numbers which you’d like to keep after the "S = ".
For example, if you only want the columns: "Driver Number", "Task Number", "shortId", "status" you would enter: s = ",1,2,3,4,"
Note: keep the commas as entered above
Step 6:
Exit out of the Visual Basic Editor. To run the macro, go back to options and hover your cursor over "Macro" and select "Macros". Select the macro "RemoveColumns" and hit "Run". If done correctly, the program should delete all the columns except those you have selected. Please give Excel up to 30 seconds to execute the macro.
Save your new workbook as a different filename so you can reuse the workbook. Now that you are configured, simply paste data in your macro-enabled sheet and run the macro whenever you want to remove the unnecessary columns.
Columns:
| Column Name | Column Letter | Column Number |
Column Description
|
| Driver Number | A | 1 | Each driver will receive a new ID that is used for task exports, but note that this number will likely change with every export. |
| Task Number | B | 2 | This is the order of the task in the driver's assigned task list. |
| shortId | C | 3 | The Onfleet task identifier. |
| status | D | 4 | The state of the task - the task status could be unassigned, assigned, in-transit, succeeded, failed |
| creatorOrganization | E | 5 | The organization who created the task. |
| executorOrganization | F | 6 | The organization the task was delegated to for completion. |
| workerName | G | 7 | Driver's name. |
| destinationAddress | H | 8 | The location where the delivery is being sent. |
| destinationLonLat | I | 9 | This is the destination location in Longitude and Latitude. |
| recipientsNames | J | 10 | The name of the person/customer who is intended to receive the delivery. |
| recipientsNumbers | K | 11 | The phone number of the person who is intended to receive the delivery. |
| completeBeforeTime | L | 12 | The completeBeforeTime is the date and time before which a task should be completed. |
| completeAfterTime | M | 13 | The completeAfterTime is the date and time after which a task should be completed. |
| creationTime | N | 14 | The date and time the task was created. |
| startTime | O | 15 | The date and time the task was started by the driver. |
| completionTime | P | 16 | The date and time the task was marked completed by the driver. |
| didSucceed | Q | 17 | This field displays if the task was marked as successful at completion time. |
| completionNotes | R | 18 | Additional notes provided by the driver when completing a task. |
| completionLonLat | S | 19 | This is the completion time location in Longitude and Latitude |
| distance | T | 20 | This is the actual distance from the GPS information. |
| taskDetails | U | 21 | Task-specific information like an order number or list of items to deliver. |
| recipientNotes | V | 22 | specific instructions that apply to all tasks for this recipient ie: door codes, special drop-off locations, warnings, etc. Recipient notes will remain attached to this recipient and will appear on all their tasks until overwritten or deleted. |
| signatureUrl | W | 23 | The link to the customer's signature collected at delivery. |
| photoUrl | X | 24 | The link to the photo taken for the task at delivery. |
| feedbackRating | Y | 25 | The rating score provided by the customer after task completion. The rating is provided on a five star scale. |
| feedbackComments | Z | 26 | The comments provided by the customer after task completion/ item has been delivered. |
| forceCompletedBy | AA | 27 | The name of the Admin/user who completed a task manually in place of the driver. |
| startLonLat | AB | 28 | The address coordinates - longitude and latitude of the location when the driver started the task. |
| departureTime | AC | 29 | For an individual task this is the time when the worker departed 150 m from the start location. |
| departureLonLat | AD | 30 | The address coordinates - longitude and latitude of the location of the driver upon departure to make the delivery. |
| arrivalTime | AE | 31 | The time the driver arrives within 150 m of the destination location. |
| arrivalLonLat | AF | 32 | The address coordinates - longitude and latitude of the location of the driver's arrival |
| taskType | AG | 33 | This filed displays if the task is a drop-off or pickup task. |
| dependencies | AH | 34 | This field displays the associated tasks that are linked to a task or tasks that must be completed before a specific task. |
| failureReason | AI | 35 | This is the additional note provided when the Driver completes a task as failed. Additional information on Task completion Reasons Custom Task Completion Reasons |
| barcodesCaptured | AJ | 36 | This field displays the barcodes that the driver captured for the task. Multiple barcodes can be scanned for a single task. |
| trackingViewed | AK | 37 | This field will be populated if the customer clicked and tracked the driver in transit. |
| signatureText | AL | 38 | The provided signature for a task |
| metadata | AM | 39 | Any additional personalized data outside of Onfleet's data that has been added to an entity. Additional Metadata information Metadata |