Verified moves device-to-database association from before shipment to the installation process. For accounts included in the phased rollout, the intended database can be identified through an install code, an existing MyGeotab login, or a supported trusted-installer work order. Partners and OEMs can also use supported APIs to integrate installation steps into their own workflows.

Associating devices at installation helps reduce reliance on pre-assigned device lists and manual serial-number entry. It also helps reduce the risk of a device being associated with the wrong customer database.

Verified supports three installer paths:

• Install code: For a third-party installer, a fleet administrator generates a time-limited code in MyGeotab. The installer enters it in MyInstall to identify the intended database.
• Direct MyGeotab access: Customers completing their own installations can access MyInstall directly in MyGeotab The system detects the database and no install code is needed.
• Trusted-installer work order: For supported work orders, the system identifies the associated database from the work order. The installer confirms the customer without entering a code.

All three paths lead to the same installation flow. The workflow checks whether the device is already assigned to another database, records the installation details, and sends an installation record to the Review Pending Installations page in MyG. The fleet manager can compare the record with the existing asset information and accept the changes for a new installation, swap, removal, or service visit.

API integrations: The new suite of installation APIs is in feature parity with MyInstall. All MyInstall use cases are supported, with the exceptions of IOX and GPIO. API-based support for IOX and GPIO is planned for the future. Supported partner and OEM integrations can use these APIs to initiate an installation session, check device status, register a device when required, and submit an installation, swap, removal, or service record. Integration availability and testing vary by partner.

A phased early-adopter expansion is planned for Q4 2026. November 16, 2026 is the current release target, not a confirmed general-availability date. Availability varies by segment and database.Following beta period, verified will be available to all users via feature preview launch