New Cores
🏛
Upload your report to begin
Pillar detects core carriers, new cores, and violations automatically
All Violations
All Core New Core Severe Soft
#TypeSeverityShip DateLoad # CarrierRelationshipOwnerViolator RC SentLock DateLaneCustomer
Core Carriers
New Cores
Rep Profile
Core carriers, new cores, and violations per rep
Select a broker above
Core Carrier Rules
How Pillar identifies and protects carrier relationships
1Core Carrier — Established
A carrier becomes a Core for a broker when they run 4 or more loads with that broker in a single calendar month.
The carrier is then locked to that broker — other reps cannot pitch them via blasts.
2Core Maintenance — 2-Load Rule
Once a carrier becomes a Core, the broker only needs 2 or more loads per month with that carrier to keep them as a Core going forward.
If a month falls below 2 loads, the chain breaks — the carrier must hit 4+ again to re-qualify.
Example: 4 loads in Feb → Core. 2 loads in March → still Core (maintained). 2 loads in April → still Core. 1 load in May → chain broken, needs 4+ again.
3New Core — Mid-Month Lock
A carrier becomes a New Core when they have 2 or more shipped loads with the same broker this month, where the expected delivery also falls this month.
This locks the carrier to that broker before they qualify as a full Core.
Lock triggers on the Actual Ship Date of the 2nd shipped load with that broker.
4Violation Detection
A violation occurs when a rep books a load with another rep's Core or New Core carrier.
The violation is only counted if the RC was sent on or after the carrier was cored. RCs sent before the lock date are not violations.
RC date is pulled from Load: Last Activity Date (falls back to Expected Ship Date if blank).
5Excluded Loads
Loads with status Cancelled, Voided, or Tonu are excluded from all calculations — they do not contribute to Core qualification, maintenance, or violations.
Step 1 of 8
Confirm before continuing