NOTE: Manually created shifts are not impacted by these new settings.

Clock In Geo-zone: Select Asphalt plant from the dropdown.

Clock In Offset: Enter -15. (if you pay prior to job start time enter in a negative number by adding a (-) before the number.)

Clock In Enter/Exit: Select Enter.

Clock Out Geo-zone: Select the jobsite from the dropdown.

Clock Out Offset: Enter 20.

Clock Out Enter/Exit: Select Exit.

Again, this miscellaneous offset time will only be applied if it exceeds the Shift Ticket’s default times, or in other words, the Adjusted Start/Stop Times.

When unchecked, no driver notification is sent and VST’s are processed.

The driver will receive a Driver App notification. If the driver declines the hours, they must enter a comment and the VST will indicate Rejected. When approved, the Shift Ticket reflects Accepted:

Rejected Shift Tickets may be investigated and modified as needed, and accepted tickets exported for payment. Declined tickets that are re-opened for changes will be re-sent to the driver when they are again internally approved.

Provides additional “Driver Start/Stop Time” to pay drivers for miscellaneous time before and after the Shift Adjusted Start/Stop Times on VSTs.

This feature only applies to company drivers, not third-party company drivers.

Enabled by unselecting the Disable Driver Time for VST checkbox. The Driver Start/End Time selections will appear under the Clock In (Enter/Exit, Geozone, & Offset) selections.

Leave this checked if you don’t wish to add additional Driver Time.

Click on the new checkbox labeled Disable First Load as Clock In for Shift Tickets.

Subsequently created shift tickets will then use the shift’s clock-in rule instead of the first load clock-in rule.

Note: If the Disable First Load as Clock In for Shift Tickets checkbox is checked after the Shift Tickets have been created, the shift tickets will have to be deleted and recreated to use the appropriate clock-in rule setting.

The VST Export, Detail PDF and other PDF/CSV outputs will then report consistent Hours values for shift tickets.

Note: The Decimal Precision field must first be set to 4 for this to work as documented. Please update this before creating further VSTs.

If the total time spent by a driver in Unauthorized Stops exceeds the number entered, the Shift Ticket will automatically display the total unauthorized stop time deducted in the Adjustments field.

These approval/denial comments can't be entered by brokers if that checkbox isn't checked, so we hide the column.

You could always email the VST PDFs to brokers, but with this checkbox checked, it provides a method for them to approve or deny them and then displays any comments they've entered.

Other clock-out rules may still be selected for shift tickets, but this will be the default once enabled.

Your target or desired amount of time (in minutes) you want all trucks to average at the Source for each shift. This will be set as the default target for the “At source time” Key Performance Indicator.

“If the trucks’ average time spent at the source on a shift is less than the entered threshold then the Key performance Indicator (KPI) will populate in green for hitting under the target time.”

Your maximum amount of time (in minutes) you want trucks to average at the Source for each shift.

“If the trucks’ average time spent is above the Upper threshold for a shift then the KPI will show as red for not meeting the target. If the truck average is below the Upper threshold but above the lower threshold the KPI will show in yellow. “

Your target or desired amount of time (in minutes) you want each truck to spend at the Destination. This will be set as the default target for the “At Dest time” Key Performance Indicator.

“If the trucks’ average time spent at the destination on a shift is less than the entered threshold then the Key performance Indicator (KPI) will populate in green for hitting under the target time.”

Your maximum amount of time (in minutes) you want trucks to average at the Destination for each shift.

“If the trucks’ average time spent is above the Upper threshold for a shift then the KPI will show as red for not meeting the target. If the truck average is below the Upper threshold but above the lower threshold the KPI will show in yellow.”

The amount of time (in minutes) that your first truck on each shift can be earlier than the entered “First Load time.”

Ex. Threshold set to 10 minutes and Truck 120 was scheduled to load first at 09:00 am – Actual first load is 08:50. The truck was 10 minutes early and will populate in green for hitting the target time. If the truck is 8 minutes early or late then it will show as yellow since it does not meet the 10 minute early window.

The amount of time (in minutes) that your first truck cannot exceed when running late to being the first load for a shift.

Ex. Threshold set to 30 minutes and Truck 120 was scheduled to load first at 09:00 am – Actual first load is 09:35. The truck was 35 minutes late and will populate in red for being 35 minutes over the target time. If the truck is only 20 minutes late then it will show as yellow since it does not exceed the upper threshold.

The amount of time (in minutes) that the first truck on each shift can be earlier than the entered “First Dump time” KPI.

Ex. Threshold set to 10 minutes and Truck 120 was scheduled to dump first at 09:30 am – Actual first dump is 09:20. The truck was 10 minutes early and will populate in green for hitting the target time. If the truck is 8 minutes early or late then it will show as yellow.

The amount of time (in minutes) that your first truck cannot exceed when running late to being the first dump for a shift.

Ex. Threshold set to 30 minutes and Truck 120 was scheduled to dump first at 09:30 am – Actual first dump is 10:35. The truck was 35 minutes late and the KPI will populate in red for hitting over the threshold. If the truck is only 20 minutes late then it will show as yellow.

Because Trucks arriving too early at the Source (Plant) could misleadingly inflate the First Load At-Source Wait Time, the Default Clock-in Offset (referenced above) will now be referenced when calculating the First Load At-Source Wait Time unless the Ignore Clock-In time for First-Load At-Source Calculation checkbox is checked. It is unchecked by default.

For example, if the Default Clock-in Offset is set to -15 (minutes), and the first Truck arrived at the Source at 6:30AM, is loaded at 7:05AM and exits the Source at 7:07AM, the First Load Wait Time will be 17 minutes (6:50AM-7:07AM). 6:50AM was determined by subtracting the Default Clock-in Offset (15 min.) from the Load Time (7:05AM). In contrast, previously, or if the new Ignore Clock-In time for First-Load At-Source Calculation checkbox is checked, the truck’s actual Source arrival time is used to calculate the First Load Wait Time. In this case, the Truck arrived at 6:30AM, got loaded at 7:05AM, and exited the Source at 7:07AM, so the First Load At-Source Wait Time is calculated to be 37 minutes (6:30AM-7:07AM).

You can set a default time (in minutes) between arrival and load for all shifts. Once configured, this default will automatically apply to future shift and dispatch orders. You also retain the ability to customize the arrival and load time on a shift-by-shift basis.

Once set, future shift and dispatch orders will use the setting for the time between arrivals and loads.

Arrival and load may also be customized on a shift-by-shift basis.

When enabled, this setting renames the "Plant" column header to "Starting Location" and the "Location" column header to "Haul Location" across Order Dispatch, Fulfill Dispatch, Dispatch Board (including the Shift Drawer), the Dispatch Assignment Report (web, PDF, CSV, and email), the Day-Of Actuals Report, and dispatch-related communications. It also reorders the location fields in Dispatch Board so that Starting Location appears first and Haul Location appears second. This is a label-only change — it does not alter the underlying data mapping. This setting is particularly useful for off-road CMS jobs where no plant is involved, or milling jobs where the source is a mill rather than a plant.

When enabled, the Dispatch Board sorts active shifts to the top of the page, with non-active shifts displayed below in standard alphanumeric order (0-9, A-Z). When disabled, all shifts are sorted alphabetically regardless of active status. The sort order dynamically recalculates when the dispatcher changes the viewed date on the calendar. This setting only affects the Dispatch Board.

When enabled, this setting overrides the default logic that determines what appears in the Plant and Location columns and applies a straightforward mapping: the shift's Source is displayed in the Plant column, and the shift's Destination is displayed in the Location column. This change is verified on the Dispatch Assignment Report (web, PDF, CSV, and email). The column headers remain labeled "Plant" and "Location" — they do not change. Note: when shifts use equipment-based geozones as the source or destination, location data may display incorrectly. This limitation is currently being addressed.

When enabled, the shift card displays the Paving Start and Paving End time range instead of the Shift Start and Shift End times, and the Live Shift Completion KPI progress bar is calculated based on the paving time window (including proper handling of night shifts crossing midnight). A note is displayed near the time on the shift card to indicate that Paving Time is being used. If either the Paving Start or Paving End time is missing, the system automatically falls back to using the standard Shift Start and Shift End times. This setting only affects the Live Shift Completion KPI bar, all other KPIs continue to use their existing calculation logic.

A unique Invoice Summary or Billing Summary number is now added to downloaded and emailed Virtual Shift Ticket (VST) PDFs (Email PDF and Download PDF buttons only).

Select between displaying an Invoice Summary or a Billing Summary number on the PDF. The number is based on each customer number (7349 below), starts at 000001, and increments from there.

Once an invoice (or billing) number is assigned to a ticket, or batch of tickets, for a particular broker by downloading or emailing a PDF, that number is displayed on the VST Edit, Approve and Export screen and will be included when the ticket, or batch of tickets, is exported via Export Batch.

Further, if the shift ticket is modified, the invoice/billing number is incremented. For example, the ticket PDF illustrated below is the 2nd iteration of invoice summary 7349000002, which is now numbered 7349000002.1.

The header column reflecting the charge amount under the Shift Summary section of Shift Ticket PDFs can now be customized to display either Est. Amount (default) or Amount by using the Header Name for Estimated Amount on PDF setting.

When Global Setting is disabled, the Mainline Paving Calculator section settings (KPIs) on Add/Edit Shifts also won't appear on the page.

This allows users to disable the Mainline Paving Calculator for particular shifts. The Default is Enable.

If Mainline Paving Calculator Calculator Shift Default is Disabled, it will disable Mainline Paving Calculator on all newly created shifts and the Mainline Paving Calculator Shift Settings section will not be displayed.

This will not affect current or past shifts only newly created shifts.

Note: When Mainline Paving Calculator is disabled globally, or for certain shifts, the Mainline Paving Calculator KPI columns on the Real-Time and Executive Scoreboards will remain but they will not return any data.