Library · Chargebacks · How to run this
Evidence-upload lag is not fight lag
Upload day − due day make lag days. Type both plus cases.
Pair: Evidence-upload lag on Chargebacks. Fight: alert-to-fight lag. Pack hours: evidence-pack hours.
What you type
Evidence due day — Day index when Disputifier evidence was due.
Upload day — Day index when that evidence uploaded.
Cases — Cases in that same lag window.
Lag days = upload day − due day. Pull packs earlier when lag days are fat — do not invent a lag chip.
What not to do
Do not invent lag days. Do not mix alert-to-fight hours into day indexes. Do not treat pack hours as upload lag. Do not average every MID when one owns the lag.
Related: Chargebacks, alert-to-fight lag, evidence-pack hours, representment win rate.
Procedure
- Type due day, upload day, and cases.
- Read lag days.
- Pull packs earlier when lag days are material.
Failure modes
- Inventing lag days.
- Mixing alert-to-fight hours into day indexes.
- Treating pack hours as upload lag.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Evidence-upload lag days
- Upload day − due day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this alert-to-fight lag?
- Sibling Disputifier clock. [Alert-to-fight lag](/manuals/disputifier-alert-to-fight-lag) prices lag hours \u00d7 cases. This page is upload day \u2212 due day.
- Is this evidence-pack hours?
- Related Chargeflow clock. [Evidence-pack hours](/manuals/chargeflow-evidence-pack-hours) is pack labor hours. This page is Disputifier evidence-upload lag.
- What lag days should I invent?
- None. Type due day, upload day, and cases from the same Disputifier window.