These updates are available on June 16, 2026. Hard refresh your browser or update the Docket Mobile App to make sure you're seeing the latest version.
Workflow Change: Exchange Tasks and Split Weight Allowances
When you run a dumpster exchange, Docket now calculates weight overages using the pick-up side's weight allowance, not the drop-off side's.
What Changed
- Exchange tasks now split into two sides: a pick-up side (the dumpster being collected) and a drop-off side (the new dumpster being placed).
- Each side carries its own weight allowance, waste material, cost per ton, and day overage cost.
- Weight overage calculations use the pick-up side's values, since that's the container with waste in it.
- Pick-up side fields are pre-populated from the original drop-off task.
Why It Matters
Previously, Docket calculated weight overages using the drop-off side's weight allowance. When the two dumpsters had different weight limits, that meant overages could go undetected and uncharged. Overages are now calculated using the correct side every time.
What to Do Next
Learn more about exchange tasks and split weight allowances in Docket: Exchange Tasks and Split Weight Allowances Overview and FAQs
Feature Update: IronRouteAI Improved Traffic-Aware Route Creation
IronRouteAI now factors in time-of-day traffic when building optimized routes, producing more optimized routes throughout the day.
Audience: IronRouteAI Users (Pro Plus Plan)
What Changed
- IronRouteAI uses traffic-adjusted travel times for morning rush, off-peak, and evening rush windows when calculating optimized routes.
- Routes generated at different times of day now reflect realistic drive times for that period.
Why It Matters
Previously, route optimization used distance-based calculations that didn't account for traffic. A route optimized at 6:00am could suggest a sequence that becomes inefficient by mid-morning once traffic conditions change. Optimization now adjusts based on when the manifest actually runs.
New to IronRouteAI?
Learn more about IronRouteAI and optimized routes in Docket: IronRouteAI Overview and FAQs
Feature Update: Pricing Matrix Auto-Population on Recurring Invoices
When you link a recurring C&R stop to a recurring invoice, the charges from your pricing matrix now populate automatically as line items.
Audience: Commercial and Residential Customers
What Changed
- Linking a recurring stop to a recurring invoice now triggers the pricing matrix to populate charges as line items automatically.
- Each line item reflects the rate configured in your matrix for that stop's activity type, bin type, and material.
Why It Matters
Previously, linking a recurring stop to an invoice generated a blank invoice every time. Every charge had to be manually re-entered from scratch, even though the rates were already configured in the pricing matrix.
Feature Update: Service Time Field Updates
Three changes to how service time works on stops shipped in this release.
Audience: Commercial and Residential Customers
What Changed
- The service time field on stop creation and editing no longer defaults to 8:00am. The field starts blank and a time is only saved when you enter one explicitly.
- You can now set and save a desired service time on unassigned ad-hoc stops. The saved time appears on the stop's Schedule card before the stop is placed on a manifest.
- Stops imported via XLSX or CLI no longer receive an 8:00am desired service time. They now import with no service time set, matching stops created manually.
Why It Matters
Previously, 8:00am was automatically applied to every stop, whether it was created manually, unassigned, or imported. That default could create confusion about whether a time had been intentionally set. Service time now only reflects what's been entered on purpose.
Fixes
C&R Pricing Matrix Template Failed to Download: The C&R pricing matrix template was failing to download in some environments due to a missing access token in the file URL. That's resolved. Downloads now work correctly.
Driver Start/End Location Missing from Route Comparison: When using the IronRouteAI route comparison modal, a driver's dynamic start or end location was not appearing on the optimized side of the comparison, which caused incorrect routing data to display. That's resolved. The optimized side now shows the correct start and end locations.
Wrong Yard Shown for Return-to-Yard Tasks in Comparison Modal: The IronRouteAI route comparison modal was ignoring per-task Return to Yard settings and showing the default yard instead. Affected tasks displayed the wrong yard location in the comparison view. That's resolved. The modal now uses the correct Return to Yard setting for each task.
Billing Issues Count was Incorrect in Assets: The billing issues count shown in the Assets section was displaying a higher number than the actual issues listed. That's resolved. The count now accurately reflects what's in the list.