How the KPIs are calculated

Performance Tracker now reads each automatic metric from a specific source file name and marks the remaining operations metrics as manual.

1. Upload the exports

Use file names containing active review final, TicketQC REVIEW, TicketQC FINAL, Ticket Quality Error, invoice cycle time, total cycle time, or open jobs so rows go into the right calculation group.

2. Automatic KPIs run

Date-based KPIs use the selected From and To dates. Active/Review/Final and Invoice Cycle Time are current snapshots, so the newest upload becomes the displayed value. Invoice Cycle Time can exclude tickets from a selected date onward.

3. Customer updates continue

Open-job reports are grouped by customer and prepared from the uploaded open-jobs data.

Expected upload columns

The parser reads a single sheet with a header row. Active/Review/Final expects Status in column F, and Invoice Cycle Time expects Deliver/Pickup in column J.

Active/Review/Final, Ticket QC, Invoice Cycle Time
  • Ticket # or TicketID
  • Customer ID, Customer
  • OrderType, Order Category, Status
  • Job #, Type, City
  • Deliver/Pickup, Rental Start, Date Recv
  • Active/Review/Final uses column F Status
  • Invoice Cycle Time uses column J Deliver/Pickup
  • Ticket QC uses TicketQC FINAL rows divided by TicketQC REVIEW rows
  • Ticket Quality counts dated Ticket Quality error rows by ticket number
Open Jobs (optional)
  • Customer / Customer ID
  • Job #, Ticket #
  • Order Type, Address, Status
  • Age, Technician, Notes
  • Open Jobs is a current snapshot: no date range is needed, and each new upload replaces the previous Open Jobs upload.

Also supports the grouped "Customer: KEY - Name" section layout and displays regardless of the dashboard date range.

Metric by metric

Invoice Cycle Time (Final Edit to Invoice)

Target <= 3 days
Source
Invoice Cycle Time export. The file name must include invoice cycle time or total cycle time.
Formula
business days from the oldest included Deliver/Pickup date to today, or to the day before an optional exclude-from date, excluding weekends
Columns used:Column J: Deliver/Pickup

This is a current snapshot. An optional exclude-from date omits tickets dated on or after that day and stops the calculation on the preceding day. The newest Invoice Cycle Time upload replaces older snapshots.

Tickets QC'd - Review to Final Edit

Target >= 95%
Source
Ticket QC exports. File names must include TicketQC REVIEW and TicketQC FINAL.
Formula
TicketQC FINAL imported rows / TicketQC REVIEW imported rows x 100
Columns used:TicketQC REVIEW rowsTicketQC FINAL rows

The dashboard waits until both QC files exist for the selected date range, then compares final-stage tickets to review-stage tickets.

Ticket Quality

Target <= 10
Source
Ticket Quality Error export. File name must include Ticket Quality.
Formula
count Ticket Quality error rows dated inside the selected range
Columns used:Ticket Quality Date of Occurance / Date of OccurrenceTicket Quality Ticket Number

The dashboard displays the number of quality errors, not a percentage. TCR Total is no longer required. Error rows are identified by ticket number, so rows with a blank driver name still count when they have a usable date.

Team Responsiveness (within 1 hour)

Target >= 95%
Source
Manual entry using Monday-Friday week ranges
Formula
saved value for each selected Monday-Friday week

The user selects a true work-week range such as Monday through Friday. The range detail view shows saved weeks; dashboard editors can delete a value and admins can edit it.

Safety

Target <= 20
Source
Manual entry using Monday-Friday week ranges
Formula
sum saved safety event counts for every selected Monday-Friday week

Safety violations, including speeding violations, are tracked outside the TCR ticket export. The dashboard card shows the selected-month total while range detail keeps the week-by-week audit trail.

Incomplete Tickets

Target <= 10
Source
Manual entry using Monday-Friday week ranges
Formula
sum saved incomplete-ticket counts for every selected Monday-Friday week
Columns used:Labor TimeInternal Notes

The current TCR ticket export does not consistently include every field needed to detect incomplete tickets automatically. The dashboard card shows the selected-month total while range detail keeps the week-by-week audit trail.

Missed Jobs / Late Jobs / Client Callbacks / Reworks

Target <= 1
Source
Manual entry using Monday-Friday week ranges
Formula
saved weekly total for missed jobs + late jobs + client callbacks + reworks

These exceptions are tracked by operations because some missed jobs do not create a ticket row. The dashboard shows selected weeks without averaging them.

Ticket Status Snapshot

Target No target
Source
Active/Review/Final export. The file name must include active, review, and final.
Formula
count Status values in column F: A is Active, E or R is Review, and F is Final Edit
Columns used:Column F: Status

This is a current snapshot. Uploading a new Active/Review/Final file replaces the older snapshot and the dashboard shows the new counts without using the selected date range.

Want to see it in action?

Load the demo workspace with realistic operational data.