Skip to main content

How KPI Targets Carry Forward

Understand how KPI targets set during shift activation are reused across future shifts in the same job.

Introduction

When you set KPI targets (like Tons per Hour or First Load time) during shift activation, FleetWatcher automatically copies those values to future shifts. This saves time and helps ensure consistency across multi-day jobs.

This article explains when targets carry over, how to update them, and what happens if you make a change midweek.


Navigation

To set or view KPI targets:

  • Go to: MMS > Shifts > Scheduled Shifts (before activation)

  • Go to: MMS > Shifts > Today’s Shifts (for active shifts)


When KPI Targets Carry Forward

  • KPI targets are initially set:

    • In the What section of Add/Edit Shifts

    • Or during shift activation on the Scheduled Shifts tab

  • Once you activate a shift, those KPI values are stored

  • When you activate the next shift in the same job (same Job Name + Project), those values are copied forward


If You Change a KPI Target

  • Edits made during activation (e.g., First Load = 7:00 AM → 6:45 AM) are saved

  • That new value becomes the default for the next shift

  • You can continue adjusting targets daily, and FleetWatcher will carry forward your latest version


Example

Shift Date

First Load Target Set

Result

Monday

7:00 AM

Stored and used for Tuesday

Tuesday

6:45 AM (edited)

Stored and used for Wednesday

Wednesday

(no edits)

6:45 AM carries forward again


Notes

  • Edits made in Today’s Shifts affect that shift only — they do not carry forward

  • If you skip a day, the system still remembers the last activated shift’s targets

  • This behavior applies to all KPI types:

    • Tons per Hour (Crew/Truck)

    • First Load / First Dump

    • TCpT

    • FpM

Did this answer your question?