Rung 1 of ten — the first thing checked and the longest-lasting exclusion on the sheet. One incident costs four weeks, not one. It is also the only category that does not come from the Amazon Scorecard at all.
A damage incident makes the driver Ineligible for a four-week window: the week it happened, plus the three that follow. It is rung 1, so it is checked before anything else, and because the ladder stops at the first match a driver inside a damage window is never even measured against the other nine rungs.
| Week relative to the incident | Result |
|---|---|
| Week of the incident | Ineligible |
| +1 week | Ineligible |
| +2 weeks | Ineligible |
| +3 weeks | Ineligible |
| +4 weeks | Window closed |
Four weeks is the constant DAMAGE_IMPACT_WEEKS in the shared rules file, and like
every other threshold it is written down exactly once, for both stations.
Not the Scorecard. Damage, terminations and attendance all come out of Jake Hallien's
FICO tracker — the BETA workbook on OneDrive — read automatically by
fico_tracker.py. The same findings also come through as Jake's weekly
WK <N> DAMAGE CANCEL: messages in his Slack DM with Dan, posted after Jaimee has
approved them.
recompute.py --check-tracker reports it in one line, and a
build attempt says so plainly instead of throwing.
What actually gets written in the Reason column. Gathered from roughly 15 real correction emails, so this is the observed vocabulary rather than a designed one — and it is explicitly not exhaustive. An unrecognised reason string is flagged for Dan, never quietly bucketed or guessed at.
| String | Means | Direction |
|---|---|---|
| Damage Defects | A damage finding for that week | → Ineligible |
| Damages | Same, shorter form | → Ineligible |
| Attendance and damage defects | Both at once (seen once) | → Ineligible |
| DAMAGES EXCUSED | An excused damage finding — an override, not a data-driven correction | → Eligible |
It sits directly under Damage, comes from the same tracker and the same Slack thread
(WK <N> Terminations: <names>), and behaves the same way: marked
Term. in Jake's tracker that week means Ineligible. The
correction string is simply TERM — a terminated employee wrongly marked
eligible.
Two separate things get called damage, and only one of them is a package.
Any package leaking anything, or any package you personally would not want delivered in its current condition, should not be delivered — mark it damaged.
In the Flex app:
TBA123456789 that is damaged.Afterwards: any other package that was in contact with the liquid or powder is also considered damaged. Contain the damaged package in weather bags or empty totes to limit further damage to you, the other packages, or the vehicle — use gloves or weather bags if necessary. When you return to the station, tell the On The Road Team what happened and hand them the damaged package.
Physical damage to the van or to customer property. It is tracked in Jake's workbook alongside package damage and feeds the same rung-1 exclusion, together with anything logged under Owner Discretion for extenuating circumstances. It is not yet uploaded to this site, so it reads No Data on the dashboards — the exclusion still runs, it simply is not displayed here.
If LMET is called for an incident, the Incident Form is the one to file.
Delivery defects — customer escalations, completion defects, the DPMO numbers — are a different category with different sources and different rungs. They live on the Defects page.
rules.py (DAMAGE_IMPACT_WEEKS). Findings from Jake
Hallien's FICO tracker via fico_tracker.py. Reason strings from
references/ripple-bonus-correction-vocabulary.md. Field procedure carried over
unchanged from Ripple Resources. Last checked 2026-09-20.