The Request Video workflow allows customers using T3 Dash Cam cameras to request, track, and review dashcam footage directly from Driver Safety.
Video requests are processed in the background, allowing work to continue while footage is retrieved.
Progress can be monitored through the Request Queue, and completed requests are automatically added to the Events tab for review.
Before you begin
Before requesting video, keep the following in mind:
Standard video requests can include up to 5 minutes of footage.
Timelapse requests can include up to 60 minutes of footage.
Timelapse playback is 15x speed by default.
Longer requests and higher resolution video may take additional time to process.
Completed requests appear in the Events tab under Requested Video.
Note: If facial recognition is enabled for the company, requested videos are not automatically processed for driver assignment.
Request video
Open Driver Safety page in T3.
Select the Events tab.
Click Request Video.
Select the asset.
Choose the desired date and time range.
Enable the Timelapse option to create a video for longer time intervals. Otherwise, Standard Video will be selected.
Standard Video (up to 5 minutes), or
Timelapse (up to 60 minutes).
Submit the request.
The request begins processing immediately in the background.
Track a request
After submitting a request, its status can be viewed in two places:
In-app progress notifications displayed within Driver Safety.
The Request Queue, available by selecting the download icon next to Events.
The Request Queue displays the current status for each request until processing is complete.
Review completed footage
When a request is finished:
Open the Events tab.
Filter or locate the Requested Video event.
Open the event to review the footage.
Request statuses
Depending on camera availability, requests may progress through several statuses.
Status | Description |
Queued | The request has been received and is waiting for the camera to become available. |
Downloading | Video is currently being retrieved. |
Video ready for review | The request completed successfully and the footage is available in Events. |
Camera unavailable | The camera could not be reached to retrieve footage. |
Why a request may fail
A request may not complete successfully for one of the following reasons.
Footage is unavailable
Video may not exist for the selected time period.
Availability depends on the organization's recording configuration and whether the asset was recording during the requested time.
Camera unavailable
If the camera has been offline for an extended period and cannot be reached, the request cannot be completed.
The Request Queue displays Camera unavailable when this occurs.
Best practices
To help requests complete as quickly as possible:
Request only the footage needed.
Use standard video when possible.
Reserve longer timelapse requests for situations that require additional context.
Keep in mind that higher resolution requests and multiple camera streams can require additional processing time.
Tip: A high-resolution request for a 5-minute clip from both road-facing and driver-facing cameras may take approximately 20 minutes to process.
FAQ
How long does a video request take?
Processing time depends on video length, resolution, the number of camera streams requested, and whether the camera is currently online.
Where can completed videos be found?
Completed requests appear in the Events tab as Requested Video events.
Can work continue while a request is processing?
Yes. Requests run in the background, and progress can be monitored from the Request Queue.
Why wasn't a driver assigned to my requested video?
Requested videos are not automatically processed by facial recognition services for organizations that use driver assignment.