Shadow Run Scorecard

Match rate needed Count commodity text

Shippers

6 shippers, 72 loads, 8 critical fields per load. Select a shipper to see its mismatched fields.

Fields where the tender itself contradicts the rep's record. They are left out of the match rate until someone settles them.

A field matches when both values are equal after trimming spaces, ignoring case and writing dates and times one way; units are not converted, so a weight in kilograms fails.
Eight fields are critical (reference, pickup facility, delivery facility, pickup date, pickup appointment, delivery appointment, weight and stops), which makes 8 per load and 96 per shipper; commodity text counts only when the toggle is on.
A field the tender shows the rep got wrong is disputed, left out of the rate and listed under Needs a person.
A shipper's match rate is its matched critical fields divided by its compared critical fields.
Ready to skip review means the rate is at or above the bar, at least 10 loads were seen and no mismatch type appears twice.
Needs a config rule means the mismatches that repeat are all types that can be fixed in setup.
Keep in review covers everything else, and the reason column says why.

All data is synthetic. Every shipper, facility, reference number and load is made up.
The rep's record is the answer key, except where the tender shows the rep was wrong; those fields go to a person instead of counting against the agent.
Each load has 10 fields: reference/PO, pickup facility, pickup date, pickup appointment, delivery facility, delivery appointment, equipment, weight, stops and commodity. Equipment is recorded but not scored.
The TMS keeps times in Central. Values are shown exactly as stored; the comparison ignores case and format, not meaning.
The bar is the share of critical fields the agent must get right before a shipper's orders stop going through human review.
A shipper needs at least 10 loads in the shadow run before it can be judged ready.
Mismatch types come from simple checks, listed below. "Fixable in setup" means a deployment config rule can fix it without a product change.

Mismatch type	How it is spotted	Fixable in setup

Do new accounts run a shadow period where reps still key orders, or do you compare against the TMS afterwards?
Is go-live decided per shipper, per customer or per field?
What match rate takes a shipper off review, and is the bar higher for appointment times than for reference numbers?
When the rep's record and the tender disagree, who settles it?
Which fixes happen in configuration during deployment, and which go back to Engineering?