These updates are available on August 27, 2026. Hard refresh your browser or update the Docket Mobile App to v4.6.1 to make sure you're seeing the latest version.
Feature Update: Driver Reassignment Locked in the Mid-Day Preview
The driver selector is now locked while you're reviewing a mid-day reoptimization preview.
Audience: IronRouteAI Users (Pro Plus Plan)
What Changed
- The driver selector is disabled inside the mid-day reoptimization preview.
- This prevents applying a proposal that was built against a driver set that's since changed.
- Reassignment in normal planning mode is unaffected.
Why It Matters
Previously, you could reassign drivers while reviewing a mid-day reoptimization preview, even if the driver set had changed since the preview was generated. That could result in applying a plan built for the wrong drivers. Locking the selector during preview keeps the proposal tied to the driver set it was actually built against.
New to IronRouteAI?
Learn more about route optimization in Docket: IronRouteAI Overview and FAQs.
Feature Update: Start and End Yards on Recurring Routes
Recurring route templates now support optional Start Yard and End Yard fields.
Audience: Commercial and Residential Customers
What Changed
- Recurring route templates now include optional Start Yard and End Yard fields.
- Both fields pull from your existing yards list, the same list shown on the Route Tracker map.
- Choosing a start yard defaults the end yard to match, and you can still edit it separately.
- These fields aren't yet visible on the Docket Mobile App or the Route Tracker page. This is groundwork for future feature releases.
Why It Matters
Setting these now means your routes will be ready as new features roll out that make use of them.
New to Recurring Routes?
Learn more about recurring routes in Docket: Recurring Routes Overview.
Fixes
Mobile App Changes Logged as "Unknown" in Task History
Changes made to a task from the mobile app were showing up in Docket's task history as "Unknown" instead of the name of the person who made them, that's resolved. Task history now correctly attributes mobile changes to the user who made them.