Wasl is a Saudi transport data platform associated with the Transport General Authority and operated through Elm's transport services. Its use and the data required depend on the regulated activity and the current service rules.
Start with the exact activity on your TGA licence. Read the current activity guide and the relevant Wasl service instructions, or ask the authority or approved provider to confirm the applicable workflow. Do not assume that every commercial vehicle follows the same process.
First, check whether your activity is in scope
Write down which vehicles, drivers and operating records the activity requires. Identify who owns each source record, who sends an update and who checks the response from the external service.
Before an initial submission, match vehicle identifiers and operator details to the official documents. Check driver details and any activity-specific relationship between driver and vehicle. Resolve mismatches before they become repeated exceptions.
Prepare the right records
If the activity requires tracking data, verify the approved device or integration requirements and the actual data flow. A live marker in an internal dashboard does not confirm that the external platform received or accepted it.
Keep the submission reference, response and correction history together. The evidence should show what was sent, when it was sent and whether it was accepted or rejected.
Handle changes and exceptions
Set a change process for a new vehicle, a vehicle leaving the fleet, a driver change or a changed operating assignment. The correct event and timing should follow the current rules for your activity.
When a record fails, separate a document mismatch from a device or connectivity issue. Give the case an owner and keep it open until the external response confirms resolution.
Verify the external result
Review exceptions after major fleet changes and at a regular interval. Compare the active fleet with the records visible in the relevant official or provider portal, where that access is available.
Inspection, insurance and other vehicle obligations may sit beside this workflow. Track them separately and check their own official requirements; acceptance in one system does not replace another obligation.
Build a repeatable review
A provider can help prepare data and surface errors. Ask which parts of the workflow it handles, what evidence it returns, and who is responsible for correcting a rejection.
Before selecting a system, test one new vehicle and one change or removal. Watch the record from your internal source through submission to external confirmation, including a failed case.
Keep a short procedure for the team: applicable activity, required records, change triggers, exception owner and place to find confirmations. Review it whenever the authority updates the activity rules.
This guide does not set fees, deadlines or penalties. Those details belong to the current TGA and service instructions for the relevant activity.
The TGA activity guide is the starting point for scope. Elm describes its transport products, including Wasl. Confirm the current operational requirement with the official service channel before acting.
For the wider fleet workflow, continue with the fleet management guide. If you are evaluating software, use the buyer guide to test how an external submission is evidenced.
This page lives at /wasl-guide.
