Author
Listed:
- Divyansh Saini
- Harman Singh
- Bhavya Agarwal
Abstract
PurposeThis study develops a leakage-aware evaluation workflow for predicting shipment dispatch delays at the time of order, auditing when each predictor becomes available and quantifying how much apparent accuracy on the DataCo dataset derives from post-outcome information.Design/methodology/approachOn 172,765 completed DataCo shipments, a point-in-time audit identifies 21 order-time features and excludes post-outcome fields, including Late_delivery_risk. Five identically tuned models are compared over 15 order-grouped resamples with Nadeau–Bengio corrected t-tests (Holm-adjusted), cluster-bootstrap intervals, a chronological split, and exact SHapley Additive exPlanations (SHAP).FindingsThe leakage-free Random Forest attains R2 = 0.2719 (95% confidence interval 0.2569–0.2864). Restoring post-outcome fields raises R2 to 0.7589: a leakage inflation of ΔR2 = +0.4870 (same model, with versus without post-outcome inputs). A distinct diagnostic, the leaky model’s margin over a flag-threshold rule (ΔR2 = +0.0951), is meaningful only conditional on the leak. All five honest models lie within 0.0084 R2; SHAP indicates that order-time delay risk is structural, driven by mode, lane, and category base rates.Research limitations/implicationsFindings derive from one public dataset whose target is dispatch (not delivery) delay; generalisability claims are correspondingly modest.Practical implicationsDelay largely reflects infeasible service-level promises; the managerial levers are promise recalibration and base-rate triage, with measured detection rates (precision 0.864, recall 0.553) separated from assumed costs.Originality/valueA feature-level point-in-time audit, a quantification of leakage inflation on a widely used benchmark, and a replicable leakage-audit protocol including a target-permutation canary.
Suggested Citation
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:eme:mscrap:mscra-04-2026-0035. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Emerald Support (email available below). General contact details of provider: .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.